On Sat, 15 Mar 2008 18:35:53 -0400, Alan Cox wrote: > The command line is unicode But only few system command filenames need the multi-byte encoding. > > What would happen during package review with an application that is > > completely in German without any English message object files? > > Why should that be different to English or Chinese ? What 'that'? I asked the previous question, because we do have a policy that spec files and package descriptions must be in American English. Some reviewers would even criticise my British English spelling. > > # service ???????? start > > Starting ???????? services: [ OK ] Look, what your MUA did to the proper encoding! It was UTF-8, in your message it's "us-ascii" and killed them. ;) > > In xterm that name displays as white-space, in Emacs with interleaved > > white-space, in Sylpheed without white-space. > > Diddums. We already use UTF-8 names in translations for the starting xxx > service strings and it just works. Yes you need the fonts to match your > locale but that has *NOTHING* to do with package naming. We don't translate package names, do we? So, what do we do with non-English package names that require non-default fonts before they can be displayed? > > Keeping English (AE and/or BE) as the project language helps against > > community fragmentation. > > By excluding anyone who doesn't fit your little clique. You can totally > avoid fragmentation by having one distro user only btw .. In what language does Fedora EMEA report to the board? In what language do the various committees report to the board? Let me emphasise that unlike you, I do not talk about "excluding" anyone. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
