--- xml/htdocs/proj/en/glep/glep-0031.html 2004/11/11 21:38:14 1.3 +++ xml/htdocs/proj/en/glep/glep-0031.html 2005/11/07 22:26:59 1.4 @@ -8,7 +8,7 @@ -->- +
|Title:||Character Sets for Portage Tree Items|
|Author:||Ciaran McCreesh <ciaranm at gentoo.org>|
|Post-Date:||28-October-2004, 1-November-2004, 11-November-2004+|
|Post-History:||28-Oct-2004, 1-Nov-2004, 11-Nov-2004|
The existing tree uses a mixture of encodings. It would be straightforward to fix existing ChangeLogs and metadata files to use UTF-8.-
The echangelog tool is character-set agnostic. In order to properly +
The echangelog tool is character-set agnostic. In order to properly enter UTF-8, developers would have to switch to a UTF-8 shell session. This only applies if the developer is entering new text which uses 'fancy' characters -- existing characters are not mangled.
Certain text editors are incapable of handling UTF-8 cleanly. However, -since the echangelog tool is generally the correct way to generate +since the echangelog tool is generally the correct way to generate ChangeLog entries, this should not be a major problem. Generating metadata.xml files correctly in these editors could become problematic. -The vim and emacs editors, which appear to be most widely used, +The vim and emacs editors, which appear to be most widely used, are both capable of handling UTF-8 cleanly -- for vim, this could be -configured automatically via the gentoo-syntax () package.+configured automatically via the gentoo-syntax () package.
|||RFC 3629: UTF-8, a transformation format of ISO 10646 http://www.ietf.org/rfc/rfc3629.txt|
|||ISO/IEC 10646 (Universal Multiple-Octet Coded Character Set)|
|||ISO/IEC 8859 (8-bit single-byte coded graphic character sets)|
|||The app-vim/gentoo-syntax package,
@@ -175,16 +174,16 @@
This document has been placed in the public domain.-
-vim: set tw=74 fileencoding=utf-8 :-