From: Mike Frysinger Date: Sat, 14 Feb 2009 01:25:47 -0500 Subject: [U-Boot] proper file encoding Message-ID: <200902140125.47790.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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