Thomas Diehl 寫道:
The bigger problem is that I have been unable for several months already to get any feedback on how you wish to proceed? We are just a few weeks away from the 2.2.1 release and KDE 3.0 is scheduled for early next year and I can't I see any recent commits to the traditional Chinese translations (esp. in the 2_2_BRANCH of the CVS which will become 2.2.1). Not to mention a conversion to utf-8.
I'm very sorry that I and other contributors (maybe) are very busy so we don't pay much attention to KDE developement recently. Nevertheless, as far as I know, the big5 translation doesn't break anything in KDE 2.2, i.e., it still works well in KDE 2.2. To my opinion, it should not be dropped. However, if it's the KDE's policy forcing every translation team to use UTF-8, we'll follow. I'll see what I can do this weekend.
The only thing that still bother me is, the name zh_TW.Big5 is not appropriate when we change to UTF-8 (since it's not correct then). As I suggested before, we should use zh_TW.
Could you help to change the directory name?
Am Montag, 20. August 2001 09:42 schrieb Chih-Wei Huang:
I'm very sorry that I and other contributors (maybe) are very busy so we don't pay much attention to KDE developement recently. Nevertheless, as far as I know, the big5 translation doesn't break anything in KDE 2.2, i.e., it still works well in KDE 2.2. To my opinion, it should not be dropped. However, if it's the KDE's policy forcing every translation team to use UTF-8, we'll follow. I'll see what I can do this weekend.
Well, it already was dropped from 2.2 although not mainly because of the missing utf-8 conversion but because of the incompleteness of the translation (kdelibs, desktop.po and kdebase should be completely translated, but kdebase for traditional Chinese is presently at 48.1%, see http://i18n.kde.org/stats/gui/i18n-table-KDE_2_2_BRANCH.html).
However, if it's the KDE's policy forcing every translation team to use UTF-8, we'll follow. I'll see what I can do this weekend.
Great. Please remember that this is about the files in KDE_2_2_BRANCH of CVS, not in HEAD.
(About the renaming issue I'm going to send a separate mail with CC to Stephan Kulow and Hans Petter Bieker)
Regards,
Thomas
On Mon, 20 Aug 2001, Thomas Diehl wrote:
Well, it already was dropped from 2.2 although not mainly because of the missing utf-8 conversion but because of the incompleteness of the translation (kdelibs, desktop.po and kdebase should be completely translated, but kdebase for traditional Chinese is presently at 48.1%, see http://i18n.kde.org/stats/gui/i18n-table-KDE_2_2_BRANCH.html).
If there's no problem, I think I can help working on it too starting from next week. Not sure if others from Hong Kong can help too, but I'll try my best to ask. However, cwhuang, you help is needed most.....
But certainly this needs time, as I have skimmed through previous KDE zh_TW translations, and found that they need *EXTENSIVE* review and modification. This is even more time-consuming than working on new translations (that's my experience from taking over the abandoned gnome translations from shyue). Reworking on it means it's quite impossible to release any zh_TW translations until KDE 3.0 (just a guess).
Conversion from Big5 encoding to UTF-8 is not a problem at all, this is very easy. The most problematic part is to find somebody to REVIEW and TEST the translation.
Abel
Am Montag, 20. August 2001 09:42 schrieb Chih-Wei Huang:
The only thing that still bother me is, the name zh_TW.Big5 is not appropriate when we change to UTF-8 (since it's not correct then). As I suggested before, we should use zh_TW.
Could you help to change the directory name?
I have to leave that to the people responsible for CVS and kcmlocale matters (ie to Coolo and to Hans Petter). Maybe they can comment on this.
Personally, I suspect that we won't probably do that for 2.2.1 since this should only be a bug fix release with minimal code changes. (I'm also no sure how this naming scheme would break the utf-8 conversion?)
After 2.2.1 we will probably have a lot of renaming since we are aiming at a conversion to 3-letter codes. This would be a better occasion to find a solution for the naming of traditonal Chinese as well.
Regards,
Thomas
zh-l10n-archive@lists.slat.org