Quantcast

Documentation creation in Russian

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Documentation creation in Russian

Andrey Shnayder
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.

Thank you.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Richard Carlsson-2
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.

Hi!
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.

    /Richard
_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Andrey Shnayder
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 <[hidden email]>:
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.


Hi!
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.


    /Richard
 
_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions

test.erl (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Bill McKeeman

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: [hidden email] [mailto:[hidden email]] On Behalf Of Andrey Shnayder
Sent: Tuesday, October 28, 2008 5:51 AM
To: Richard Carlsson
Cc: [hidden email]
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 <[hidden email]>:

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.


Hi!
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.


    /Richard

 


_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Lev Walkin
Bill McKeeman wrote:
>
>
> 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/

On the contrary, it is going to make faster many things that are
acurrently slow.

Since our contradictory propositions are equally unsubstantiated,
the mathematical expectation is that the utf-8 solution is going to be
just as fast as the present state of things.

> *From:* [hidden email]
> [mailto:[hidden email]] *On Behalf Of *Andrey Shnayder
> *Sent:* Tuesday, October 28, 2008 5:51 AM
> *To:* Richard Carlsson
> *Cc:* [hidden email]
> *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 <[hidden email]
> <mailto:[hidden email]>>:
>
> 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.
>
>
> Hi!
> 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.
>
>
>     /Richard
>
>  
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> erlang-questions mailing list
> [hidden email]
> http://www.erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Dave Smith-23
In reply to this post by Richard Carlsson-2
Hi Richard, 

When you say people are working on it, are you referring to EEP 10?  This deals with a lot of good stuff, including Lists, Binaries, IO and conversion modules.

It doesn't, however, deal with source file encodings.  It also doesn't mention atoms and shell support.   Has any thought been given to these?  If so, would they be include in EEP 10? or other EEP?

Thanks

2008/10/28 Richard Carlsson <[hidden email]>

Hi!
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.

   /Richard
_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions


_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Documentation creation in Russian

Bill McKeeman
In reply to this post by Lev Walkin
Lev, When one of our propositions is substantiated, the truth will be known.  Since I do not have to invest in the experiment, I am content to wait.  /s/ Bill

-----Original Message-----
From: Lev Walkin [mailto:[hidden email]]
Sent: Tuesday, October 28, 2008 9:44 AM
To: Bill McKeeman
Cc: Andrey Shnayder; Richard Carlsson; [hidden email]
Subject: Re: [erlang-questions] Documentation creation in Russian

Bill McKeeman wrote:
>
>
> 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/

On the contrary, it is going to make faster many things that are
acurrently slow.

Since our contradictory propositions are equally unsubstantiated,
the mathematical expectation is that the utf-8 solution is going to be
just as fast as the present state of things.

> *From:* [hidden email]
> [mailto:[hidden email]] *On Behalf Of *Andrey Shnayder
> *Sent:* Tuesday, October 28, 2008 5:51 AM
> *To:* Richard Carlsson
> *Cc:* [hidden email]
> *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 <[hidden email]
> <mailto:[hidden email]>>:
>
> 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.
>
>
> Hi!
> 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.
>
>
>     /Richard
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> erlang-questions mailing list
> [hidden email]
> http://www.erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
[hidden email]
http://www.erlang.org/mailman/listinfo/erlang-questions
Loading...