Bug#215205: language-chooser: Language order shouldn't be alphabetical

. "C" is not (even roughly) equivalent to "en_US". -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#160284: ITP: po-debconf -- Manage translated Debconf templates files with gettext

ey all only seem to be related to the slightly varying vendor tables, and not a problem when iconv is used consistently. What other problems are there that are severe enough to need this? -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#160284: ITP: po-debconf -- Manage translated Debconf templates files with gettext

hould get the same thing. (If one or the other is in UTF-8, the text is being converted anyway, so this doesn't matter.) Could you elaborate? -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#160284: ITP: po-debconf -- Manage translated Debconf templates files with gettext

;m not sure what he meant. I just think that storing text in different encodings according to his "Description-ll_LL.ENCODING" suggestion shouldn't be done unless it's *really* needed, and if it's *really* needed, I'm interested in knowing why. -- Glenn Maynard --

Re: Bug#160284: ITP: po-debconf -- Manage translated Debconf templates files with gettext

mentioned it). Could you give an example or a reference? (This would be a major bug, since round-trip compatibility is extremely important.) If I'm forced to support legacy encodings internally in a future i18nized project, I'd like to have a very clear understanding of why ... -

Re: Trying to fix slang

hat the drop-in utf8 diversion is no longer available. -- Glenn Maynard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]