UTF-8 encoding fix of author tags in src files ready for Erlang 17

[sebmaynard]

No description provided.

[jlouis]

Looks like the build is failing on Travis-CI for some completely different reason. This probably need some help.

I would recommend you change the names for something in the ASCII alphabet though, since it would compile cleanly on all the different releases for which this runs. Otherwise you run into trouble with the older releases as well.

[sebmaynard]

I don't think I can bring myself to do that; it's Oscar's name! I'd be pissed if someone mis-spelt my name...

[ghost]

Lets see. Do I get this correctly.

In R17 OTP have changed from ISO8859-1 to UTF-8 as coding for source files,
including comments and function names and ... Right?

So, now we cannot write Erlang programs (that uses non ascii things) that can compile in both
R17 and earlier. Right?

Please, tell me I am wrong!

/Roland

----- Ursprungligt meddelande -----

Från: "Seb" notifications@github.com
Till: "esl/lhttpc" lhttpc@noreply.github.com
Skickat: onsdag, 9 apr 2014 17:39:51
Ämne: Re: [lhttpc] UTF-8 encoding fix of author tags in src files ready for
Erlang 17 (#44)

I don't think I can bring myself to do that; it's Oscar's name! I'd be pissed
if someone mis-spelt my name...

—
Reply to this email directly or view it on GitHub .

[eproxus]

@roland-karlsson-erlang-solutions-com You can, just include the relevant comment in the top of the file. For example: %% -*- coding: utf-8 -*-.

@sebmaynard I assume the most backwards compatible fix for lhttpc in this case is to add a latin1 comment to all the source files (I assume it is %% -*- coding: latin1 -*- but the documentation is a bit unclear on this one).

See http://www.erlang.org/doc/apps/stdlib/unicode_usage.html

[jlouis]

R16B understands utf-8 encoding as well with that line. So if you don't care about R15 and older, you could just enable the utf-8 encoding and be done with it. The question is for how long you want to support older code. The alternative is to use latin-1 encoding, which is both forwards and backwards compatible.