Okay, now this is your registry record:
<translator>Abel Cheung <mailto>maddog@linux.org.hk <url>http://www.deaddog.org/ <disclaimer>
Thanks.
And there is some additional issue to be discussed: I have specified in the disclaimer that I want to join both zh_TW and zh_CN if the Chinese team can be splitted. I think you have mentioned about that some time before, but I didn't pay much attention to it, since at that moment the effort of simplified Chinese translation is not strong enough. Now I think it's time to talk about the splitting again.
Okay. Before taking the action we must talk to the team leader (and the whole team) to avoid bad feelings.
It would be good to mail this to both traditional Chinese and simplified Chinese translation team -- I've CC'ed a copy of this mail to both teams. The current "Leader" of Chinese team has quitted translation team, but I'm not sure why nobody has contacted TP about this. For now, would it be OK to set the leader of Chinese team to null?
Right now simplified Chinese has it's official translation team. It's team leader, Wang Jian, has also signed disclaimer for Chinese team too. So what should be done to ensure that splitting won't cause any trouble for TP?
Excuse the lack of my knowledge: is it possible to derive language flavor from the other mechanically (is there a command line tool to do this task?)?
Yes, the answer is "no". They differ not only in encoding, but in general wordings too. Directly converting one translation to another is quite unacceptable for another side.
In case your answer is "no", I guess the cleanest solution is to move the current 'zh' files and directories to 'zh_CN' (= simplified?) and then to copy this material to 'zh_TW' as intial translations (in case you think this is useful).
Perhaps the other way round, since most Chinese translations are for traditional Chinese(zh_TW) currently. In case this is not good enough, I am willing to sort them out manually.
Then it is the best to empty 'zh' and leaving a note there pointing to the 'zh_TW'/'zh_CN' variants; we did something similar for 'no': for the norwegian team we now have 'nb' and 'nn' as active teams.
Yes, the situation for Chinese team is a little similar to nb and nn. This can be the best arrangement.
Abel
Waiting for your advise (note, I will not have the time to arrange all the changes within the next days; around 2002-03-12 I'll have time to do it -- and I guess Martin is busy, too).
"R.I.P. Deaddog" maddog@linux.org.hk writes:
It would be good to mail this to both traditional Chinese and simplified Chinese translation team -- I've CC'ed a copy of this mail to both teams. The current "Leader" of Chinese team has quitted translation team, but I'm not sure why nobody has contacted TP about this. For now, would it be OK to set the leader of Chinese team to null?
If we are going to split teams, we definitely need a team leader for the "active" teams, see
http://www.iro.umontreal.ca/contrib/po/HTML/leaders.html
The reason is that we need to contact somebody in case of problems, somebody who speaks the language of the translators. Of course, if a team is inactive, there is no need to have a leader.
IOW, if we don't have a volunteer for team-leadership of zh_TW, we should not make the effort to change the status quo. Would you volunteer?
Perhaps the other way round, since most Chinese translations are for traditional Chinese(zh_TW) currently. In case this is not good enough, I am willing to sort them out manually.
All of them are BIG-5 encoded. That is sufficient indication that they are all traditional Chinese, right?
Yes, the situation for Chinese team is a little similar to nb and nn. This can be the best arrangement.
We'll also need assign translators to the new teams. It would probably be best if translators would speak up for themselves. Failing that, and given that most have email addresses from Taiwan and Hong Kong, would it be fair to move anybody who does not indicate otherwise to the zh_TW team?
Regards, Martin
On Thu, Feb 21, 2002 at 08:05:12AM +0100, Martin v. Loewis wrote:
If we are going to split teams, we definitely need a team leader for the "active" teams, see
http://www.iro.umontreal.ca/contrib/po/HTML/leaders.html
The reason is that we need to contact somebody in case of problems, somebody who speaks the language of the translators. Of course, if a team is inactive, there is no need to have a leader.
IOW, if we don't have a volunteer for team-leadership of zh_TW, we should not make the effort to change the status quo. Would you volunteer?
OK, I see the problem here. It would be ok for me to take up the management effort, but I must ask in my team for permission first. (Since the team is quite inactive, I don't think I have much to do *grin*)
Perhaps the other way round, since most Chinese translations are for traditional Chinese(zh_TW) currently. In case this is not good enough, I am willing to sort them out manually.
All of them are BIG-5 encoded. That is sufficient indication that they are all traditional Chinese, right?
It's good enough to know this. Yes, all current translations can be moved to zh_TW team then.
We'll also need assign translators to the new teams. It would probably be best if translators would speak up for themselves. Failing that, and given that most have email addresses from Taiwan and Hong Kong, would it be fair to move anybody who does not indicate otherwise to the zh_TW team?
If nobody speak for themselves, it'd be safe to move them to zh_TW team except one: Wang Jian, since he is the team leader of simplified Chinese translation effort.
What remaining procedures should be done before the split?
Abel
"R.I.P. Deaddog" maddog@linux.org.hk writes:
What remaining procedures should be done before the split?
None that I can think of, so I just implemented the split. The team pages are
http://www.iro.umontreal.ca/contrib/po/HTML/team-zh_CN.html http://www.iro.umontreal.ca/contrib/po/HTML/team-zh_TW.html
Updates to the statistics will run overnight, so you should be able to see the existing translations to Traditional Chinese show up tomorrow.
Please let me know if I made any errors. In particular, in case you want to have separate mailing lists, too, please let me know what mailing list to use for what team.
Regards, Martin
"R.I.P. Deaddog" maddog@linux.org.hk writes:
Okay, most iusses are already ansered by Martin.
In case your answer is "no", I guess the cleanest solution is to move the current 'zh' files and directories to 'zh_CN' (= simplified?) and then to copy this material to 'zh_TW' as intial translations (in case you think this is useful).
Perhaps the other way round, since most Chinese translations are for traditional Chinese(zh_TW) currently. In case this is not good enough, I am willing to sort them out manually.
Yes, you're right, of course. Note, I've saved these translations and I don't know whether they made it in (and whether they are still usefull, around August 2000):
. [10103: Jing-Jong Shyue ]<* mixed> some of our new PO files for zh_TW.Big5 (Triditional Chinese) . [ 15: Jing-Jong Shyue ]<1 text> . [1040: Jing-Jong Shyue ]<2 text> wget.po . [5770: Jing-Jong Shyue ]<3 text> lynx.po . [ 328: Jing-Jong Shyue ]<4 text> grep.po . [ 378: Jing-Jong Shyue ]<5 text> error.po . [2536: Jing-Jong Shyue ]<6 text> texinfo.po
I can send them to you for checking and re-submitting.
zh-l10n-archive@lists.slat.org
-
Karl Eichwalder -
martin＠v.loewis.de -
R.I.P. Deaddog