All:
Please check this out, what is your opinion?
--forwarded message--
Date: Mon, 17 Sep 2001 01:09:19 +0200 From: Pablo Saratxaga pablo@mandrakesoft.com To: Geoffrey Lee snailtalk@linux-mandrake.com Subject: Re: followup on gtk fontset problem. X-Mailer: Mutt 1.0us In-Reply-To: 20010916233445.A15083@anakin.wychk.org; from snailtalk@linux-mandrake.com on Sun, Sep 16, 2001 at 11:34:24PM +1000
Kaixo!
On Sun, Sep 16, 2001 at 11:34:24PM +1000, Geoffrey Lee wrote:
and it works very well... so I plan to change the language entries like this:
LANGUAGE=zh_CN.GB2312:zh_CN:zh:zh_HK:zh_TW.Big5:zh_TW LANGUAGE=zh_TW.Big5:zh_TW:zh_HK:zh:zh_CN.GB2312:zh_CN
so if a given translation doesn't exist in traditional/simplified Chinese; but exists in the other, then it will be displayed, insead of English. The hanzi are changed from traditional to simplified or viceversa automatically by gettext.
Do you mean the automatic conversion between GB -> Big5, or vice versa?
yes.
zh_TW - > zh_HK or vice versa should be Ok.
that doesn't involve any conversion :)
Trouble is, the terminology between GB / Big5 speakers is different ...
Yes, but, itsn't it better than displaying in English?
it is only in the case where a native translation doesn't exist; then if a translation of the other sort of Chinese exists, then a charset conversion is done and it is displayed. It only happens when a proper translation is not available
If this is the case, this wouldn't be "we have a translation so it must be better than nothing", it'd just confuse them ...
So you think that displaying in English is better?
- G.
I have looked some feedback of the users who found simplified (or traditional if they use simp. chinese) Chinese translation is 'misunderstanding'. I think what they meant is that they don't like the different terminology.
Leon
On Mon, 17 Sep 2001, Geoffrey Lee wrote:
All:
Please check this out, what is your opinion?
--forwarded message--
Date: Mon, 17 Sep 2001 01:09:19 +0200 From: Pablo Saratxaga pablo@mandrakesoft.com To: Geoffrey Lee snailtalk@linux-mandrake.com Subject: Re: followup on gtk fontset problem. X-Mailer: Mutt 1.0us In-Reply-To: 20010916233445.A15083@anakin.wychk.org; from snailtalk@linux-mandrake.com on Sun, Sep 16, 2001 at 11:34:24PM +1000
Kaixo!
On Sun, Sep 16, 2001 at 11:34:24PM +1000, Geoffrey Lee wrote:
and it works very well... so I plan to change the language entries like this:
LANGUAGE=zh_CN.GB2312:zh_CN:zh:zh_HK:zh_TW.Big5:zh_TW LANGUAGE=zh_TW.Big5:zh_TW:zh_HK:zh:zh_CN.GB2312:zh_CN
so if a given translation doesn't exist in traditional/simplified Chinese; but exists in the other, then it will be displayed, insead of English. The hanzi are changed from traditional to simplified or viceversa automatically by gettext.
Do you mean the automatic conversion between GB -> Big5, or vice versa?
yes.
zh_TW - > zh_HK or vice versa should be Ok.
that doesn't involve any conversion :)
Trouble is, the terminology between GB / Big5 speakers is different ...
Yes, but, itsn't it better than displaying in English?
it is only in the case where a native translation doesn't exist; then if a translation of the other sort of Chinese exists, then a charset conversion is done and it is displayed. It only happens when a proper translation is not available
If this is the case, this wouldn't be "we have a translation so it must be better than nothing", it'd just confuse them ...
So you think that displaying in English is better?
- G.
On Thu, Sep 20, 2001 at 10:55:56PM +1000, Leon Ho wrote:
I have looked some feedback of the users who found simplified (or traditional if they use simp. chinese) Chinese translation is 'misunderstanding'. I think what they meant is that they don't like the different terminology.
Yep.
I thought it might be confusing as well ..
Leon
On Mon, 17 Sep 2001, Geoffrey Lee wrote:
All:
Please check this out, what is your opinion?
--forwarded message--
Date: Mon, 17 Sep 2001 01:09:19 +0200 From: Pablo Saratxaga pablo@mandrakesoft.com To: Geoffrey Lee snailtalk@linux-mandrake.com Subject: Re: followup on gtk fontset problem. X-Mailer: Mutt 1.0us In-Reply-To: 20010916233445.A15083@anakin.wychk.org; from snailtalk@linux-mandrake.com on Sun, Sep 16, 2001 at 11:34:24PM +1000
Kaixo!
On Sun, Sep 16, 2001 at 11:34:24PM +1000, Geoffrey Lee wrote:
and it works very well... so I plan to change the language entries like this:
LANGUAGE=zh_CN.GB2312:zh_CN:zh:zh_HK:zh_TW.Big5:zh_TW LANGUAGE=zh_TW.Big5:zh_TW:zh_HK:zh:zh_CN.GB2312:zh_CN
so if a given translation doesn't exist in traditional/simplified Chinese; but exists in the other, then it will be displayed, insead of English. The hanzi are changed from traditional to simplified or viceversa automatically by gettext.
Do you mean the automatic conversion between GB -> Big5, or vice versa?
yes.
zh_TW - > zh_HK or vice versa should be Ok.
that doesn't involve any conversion :)
Trouble is, the terminology between GB / Big5 speakers is different ...
Yes, but, itsn't it better than displaying in English?
it is only in the case where a native translation doesn't exist; then if a translation of the other sort of Chinese exists, then a charset conversion is done and it is displayed. It only happens when a proper translation is not available
If this is the case, this wouldn't be "we have a translation so it must be better than nothing", it'd just confuse them ...
So you think that displaying in English is better?
- G.
Date: Mon, 17 Sep 2001 01:09:19 +0200 From: Pablo Saratxaga pablo@mandrakesoft.com To: Geoffrey Lee snailtalk@linux-mandrake.com Subject: Re: followup on gtk fontset problem. X-Mailer: Mutt 1.0us In-Reply-To: 20010916233445.A15083@anakin.wychk.org; from
snailtalk@linux-mandrake.com on Sun, Sep 16, 2001 at 11:34:24PM +1000
Kaixo!
On Sun, Sep 16, 2001 at 11:34:24PM +1000, Geoffrey Lee wrote:
and it works very well... so I plan to change the language entries like this:
LANGUAGE=zh_CN.GB2312:zh_CN:zh:zh_HK:zh_TW.Big5:zh_TW LANGUAGE=zh_TW.Big5:zh_TW:zh_HK:zh:zh_CN.GB2312:zh_CN
so if a given translation doesn't exist in traditional/simplified
Chinese;
but exists in the other, then it will be displayed, insead of English. The hanzi are changed from traditional to simplified or viceversa automatically by gettext.
Do you mean the automatic conversion between GB -> Big5, or vice versa?
yes.
a problem with this is about the iconv in glibc. When convert big5->utf-8->GB, some traditional characters will be lost. Because tradtional character that are not in GB2312 will not be mapped from utf-8->GB2312.
Either GBK should be used or utf8->GB2312 table should be updated.
zh-l10n-archive@lists.slat.org
-
Geoffrey Lee -
ha shao -
Leon Ho