Matt Kraai wrote:
> On Mon, Feb 16, 2009 at 11:58:20PM +0800, Arne Goetje wrote:
>> Matt Kraai wrote:
>>> We already appear to use a single source version for all three Chinese
>>> translations: Big5. Whether it's possible to change to UTF-8 is for
>>> someone more familiar with Chinese to say. I
On Mon, Feb 16, 2009 at 11:58:20PM +0800, Arne Goetje wrote:
> Matt Kraai wrote:
> > We already appear to use a single source version for all three Chinese
> > translations: Big5. Whether it's possible to change to UTF-8 is for
> > someone more familiar with Chinese to say. It's not sufficient to
Matt Kraai wrote:
> We already appear to use a single source version for all three Chinese
> translations: Big5. Whether it's possible to change to UTF-8 is for
> someone more familiar with Chinese to say. It's not sufficient to
> just switch the encoding of this file, though:
>
> $ make
> cd
On Mon, Feb 16, 2009 at 09:44:58PM +0800, Arne Goetje wrote:
> Deng Xiyue wrote:
> > If all Chinese translation are by default converted to BIG5 then it is
> > problematic. Simplified Chinese, as used in zh_CN locales, are supposed
> > to be converted to GB* encodings (GB2312, GBK, and GB18030, wh
Deng Xiyue wrote:
> If all Chinese translation are by default converted to BIG5 then it is
> problematic. Simplified Chinese, as used in zh_CN locales, are supposed
> to be converted to GB* encodings (GB2312, GBK, and GB18030, where
> GB18030 is the current standard encoding); whereas Traditional
Matt Kraai writes:
> On Mon, Feb 16, 2009 at 01:08:42AM +0800, Deng Xiyue wrote:
>> I don't know that translation of release announcement are put on web
>> using local locale instead of UTF-8. I have checked the simplified
>> Chinese page[1], which is encoded in GB2312. Maybe that is required b
6 matches
Mail list logo
