Chinese, Traditional team / 正體中文翻譯團隊

之前收集過一些字串翻譯意見 (eg, FORUM = 討論區 / 論壇)，反應還不錯，但很多建議都 50/50 的支持率，這樣不能向前推進。
我想改變一下遊戲方式，看看有沒有人反對。

新的方式：
任何人提出翻譯建議，由相關 ADMIN 同意後，我們公佈，如果沒有人反對，就使用那些翻譯。

對個別翻譯特別喜好的，可以個別使用程式修正。
(ref: http://drupaltaiwan.org/forum/20110506/5182#comment-18593)

** 另外，除了 CORE 翻譯外，比較放鬆處理。(以讓更多人取得使用為主，格式問題次要)

大家有沒有什麼有趣的想法

Hello,

剛剛用翻譯檔安裝的時候才發現，安裝畫面出現的語言選擇是「Chinese, Tranditional (繁體中文)」，建議把 "繁體中" 文改成 "正體中文" 是不是會比較一致...

Arthur ...

早前這裏更新了，並支援遠程提交建議，大家有興趣可以看看：
Localzation Client 的安裝與使用，及同步協調翻譯
http://www.notabluescreen.com/l10n_client

請大家先看看這邊：
http://drupaltaiwan.org/forum/20091006/3727

我們常看見一些結構差不多的句子，希望能統一主體的翻譯，

以後我們就可以小學生造句子那樣，在適當的位置填空就可以了。

統一原因：
- 減少差異化
- 提供參考，讓管理員看到兩個意義沒錯的建議時，能做下決擇

其他題外話，請另開主題討論。

請大家至少包括一個例句。

例：
%title has been added to the cart.
%title 已新增到購物車。
%title 已新增至購物車。

has been added to 已新增到 / 已新增至

您好，
看到 Ubercart 建議翻譯字串數量很多，但好像包含不少簡體用詞及格式錯誤，如果可行的話，希望上傳者提供我一份完整的 PO 檔，讓我們能先使用軟體整理一下繁簡之詞及文字格式的問題，降低審核所需時間。

謝謝。

Due a bug in how the imports were handled lately (after standardization of data handling was implemented: http://localize.drupal.org/node/214), the imports had a new bug introduced with plural strings being imported as the string "Array". There were in total 105 such strings when the bug was noticed and reported in the issue queue by podarok of the Ukrainian team (thanks!). The bug was immediately fixed (hopefully), but for you to be able to clean up the translations more easily, I'm listing the bogus strings here. Due to how the server stores cached metadata of the strings, you should use the user interface to clean up these strings. Please contact the affected users to reimport their suggestions. Duplicate suggestions which either became active translations or are still in the awaiting queue will not be recorded again, so that should not give you more work to recover.

Thanks again for helping beta test this service, and for quickly reporting bugs as you notice them. It helps limit the extent of such issues to a smaller audience. I've posted this note to all groups affected and attached the list of strings affected. You can also look these up on the moderation interface by searching for 'Array' (which could have false positives, but will find all these instances).