| 1 |
On Tue, 30 Dec 2008 09:37:24 +0530 |
| 2 |
"Nirbheek Chauhan" <nirbheek.chauhan@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Tue, Dec 30, 2008 at 8:27 AM, Ben de Groot <yngwin@g.o> |
| 5 |
> wrote: |
| 6 |
> > Zac Medico wrote: |
| 7 |
> >> Nevermind, apparently GLEP 31 already requires ASCII anyway: |
| 8 |
> >> |
| 9 |
> >> http://www.gentoo.org/proj/en/glep/glep-0031.html |
| 10 |
> >> |
| 11 |
> > The way I read that GLEP is that in ChangeLog and metadata.xml |
| 12 |
> > we should accept the full range of UTF-8. |
| 13 |
> |
| 14 |
> I read that as "contents of portage tree should be in UTF-8, file |
| 15 |
> paths should be in ASCII" |
| 16 |
> |
| 17 |
> "It is proposed that UTF-8 ([1]) is used for encoding ChangeLog and |
| 18 |
> metadata.xml files inside the portage tree." |
| 19 |
> |
| 20 |
> "[...]it is proposed that UTF-8 is used as the official encoding for |
| 21 |
> ebuild and eclass files" |
| 22 |
> |
| 23 |
> "Patches must clearly be in the same character set as the file they |
| 24 |
> are patching." |
| 25 |
> |
| 26 |
> "Characters outside the ASCII 0..127 range cannot safely be used for |
| 27 |
> file or directory names" |
| 28 |
> |
| 29 |
> It is also worth mentioning that Python 3K uses UTF-8 as the default |
| 30 |
> encoding for it's files rather than ASCII as Python 2.X did. Why |
| 31 |
> should *we* go backwards? :p |
| 32 |
|
| 33 |
And none of that is relevant to Zacs original question, which is |
| 34 |
covered by the following section of the GLEP: |
| 35 |
"However, developers should be warned that any code which is parsed by |
| 36 |
bash (in other words, non-comments), and any output which is echoed to |
| 37 |
the screen (for example, einfo messages) or given to portage (for |
| 38 |
example any of the standard global variables) must not use anything |
| 39 |
outside the regular ASCII 0..127 range for compatibility purposes." |
| 40 |
|
| 41 |
Marius |
Archives