Skip to contentSkip to conversation

proper file encoding

U-Boot Mike Frysinger 2 participants 2 messages Feb 14, 2009 – Feb 16, 2009

lore
Share & tools
lore
#0 lore raw

is there any statements that i cannot find dictating the proper encoding of files ? considering git itself whines when things are not proper utf8 encoded, i'd expect that this would carry over to the files in u-boot itself. for example, the MAINTAINERS and the CREDITS files are both using iso-8859-1 encoding. this can readily be seen with people who have umlauts in their names, although some places have been avoided by using the ASCII form of "oe" and "ue" rather than ? and ?. i'd certainly prefer if we take a hard stance on documentation and similar files by requiring unicode encoding. i'd prefer all files be unicode, but i wouldnt care nearly as much with source code (comments and such).

at any rate, it's easy enough to fix:
iconv -f iso-8859-1 -t utf8 MAINTAINERS > f && mv f MAINTAINERS iconv -f iso-8859-1 -t utf8 CREDITS > f && mv f CREDITS ... and probably some more files ...

as for why i care: it's a lot easier to copy & paste contact information from these files when creating commit messages if i didnt have to manually fix the broken encoding ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090214/c5d8245a/attachment.pgp

#1 lore raw

Dear Mike Frysinger,

Quoted 6 lines · In message <[email protected]> you wrote:

is there any statements that i cannot find dictating the proper encoding of files ? considering git itself whines when things are not proper utf8 encoded, i'd expect that this would carry over to the files in u-boot itself. for example, the MAINTAINERS and the CREDITS files are both using iso-8859-1 encoding. this can readily be seen with people who have umlauts in their

There is no formal declaration yet, but so far encoding has always been iso-8859-1 (resp. iso-8859-15).

Quoted 5 lines

names, although some places have been avoided by using the ASCII form of "oe" and "ue" rather than ? and ?. i'd certainly prefer if we take a hard stance on documentation and similar files by requiring unicode encoding. i'd prefer all files be unicode, but i wouldnt care nearly as much with source code (comments and such).

I prefer to stick with iso-8859-1.

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You got to learn three things. What's  real,  what's  not  real,  and
what's the difference."           - Terry Pratchett, _Witches Abroad_