[erlang-questions] Documentation creation in Russian

Bill McKeeman Bill.McKeeman@REDACTED
Tue Oct 28 14:14:39 CET 2008

A word about utf8 support.  Python supports utf8 and ascii as separate types.  I think this was a good decision.  If Erlang replaces ascii with utf8, it will slow down a lot of things that are currently fast.  /w/

From: erlang-questions-bounces@REDACTED [mailto:erlang-questions-bounces@REDACTED] On Behalf Of Andrey Shnayder
Sent: Tuesday, October 28, 2008 5:51 AM
To: Richard Carlsson
Cc: erlang-questions@REDACTED
Subject: Re: [erlang-questions] Documentation creation in Russian

Thank you for your reply, Richard!
I have created small test module with edoc comments in russian. I have attached it to the message.
2008/10/28, Richard Carlsson <richardc@REDACTED<mailto:richardc@REDACTED>>:
Andrey Shnayder wrote:
> Hi,
> I need to generate the documentation on my erlang modules in russian. I
> try to use edoc and docbuilder (they use the same functions however),
> but I get the error:
> -------------------------------------------------------------------------
> ** exception exit: {badarg,[{io,put_chars,
> [<0.74.0>,
> ["<?xml version=\"1.0\" encoding=\"latin1\" ?>\n",
> "<!DOCTYPE erlref SYSTEM \"erlref.dtd\">\n",
> ........
> in function io:o_request/2
> in call from edoc_lib:write_file/4
> -------------------------------------------------------------------------
> If I write comments in English there are no errors, but I need
> documentation in russian. Can you help me? Files encoding is utf-8.

There is no real support for UTF-8 in Erlang right now (people
are working on it), so most things assume Latin-1 encoding in
input and output. If you can send me a minimal test case (a small
.erl file in UTF-8 that causes the crash) I can try and find a
workaround for edoc.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20081028/52695ccf/attachment.htm>

More information about the erlang-questions mailing list