Traditional Chinese - 正體字

Regarding premium, indeed we prefer to have the focus on being advanced/pro/premium rather than paid/subscription etc. I.e. focus on the functions giving you more advanced capabilities rather than focusing on the fact you have to pay for them.

Regarding Taiwan vs Hongkong, I see Apple for the Finder has:

  • zh_CN
  • zh_HK
  • zh_TW

So indeed three different chinese translations. Is it perhaps a good idea to first focus on the Taiwan translation and once that is done, duplicate it and make a variant for HongKong?


Hi @mekentosj,

Regarding “Premium Feature”, we all share the same feeling. In fact here is the translation:

  • 收費/進階/專業/Premium 功能 ?? Not prefer “收費”
  • Paid/ Advance/ Pro/ Premium Feature?? Not prefer “paid”

About localization, here is my understanding:

  • zh_CN - Simplified Chinese: Mainly used in China and I know another team is working on it
  • zh_HK - Traditional Chinese: Mainly used in Hong Kong
  • zh_TW - Traditional Chinese: Mainly used in Taiwan

Actually the difference between TW and HK is minimal. e.g. Imagine the case in English (USA) vs English (British).

I agree we should focus on zh_TW and see if we can make the Hong Kong version. To be honest, I am 100% ok if there is only Taiwan version. :laughing:

1 Like

Ok perfect!

1 Like

How about use “優選”
“優” means excellent
“選” means choice

How to improve user experience and get more productivity? These features are excellent choices.

1 Like

First of all, not a big fan of “專業” or “高級” as those two feels unreachable.

I am leading toward “進階” if we really need to translate it as it is easy to to understand and emphasis on the advanced capabilities.

Otherwise, I would like to leave it as “Premium 功能” . I do check other reference e.g. Spotify Premium, YouTube Premium and they actually leave it as English and I think most of the people would understand. Like the App name Agenda,I wanted to leave it untranslated to keep the original idea from the developer.


I have some idea about “add” based on the meaning in context.

If the target is a existed one such “Add Attachments and Images” using “加入”
If the action will create some new material or content such as “Add New Note” using “新增”

1 Like

There are some differences between zh_CN and zh_TW/HK.But not too much.

1 Like

Suggest not to translate the formatting name such as Heading, Sub-Heading…
These style in current implementation is not work for Chinese characters.

Could you explain more on that?

Actually because of the italic font is not implemented in Chinese characters.
If we translated it to Chinese, it will be not that easy to determine the difference between each item.

截圖 2020-03-10 上午12.05.08

1 Like

I see, the italic format has no effect on Chinese characters. Maybe we should consider this as a bug?

Maybe we can still translate the style? Because even if you can see the difference in English, it has nothing to do with Chinese.

Time to summon @mekentosj for your advice.

1 Like

We indeed need to have a look what we’ll do here, for now let’s just assume we can differentiate the two and translate the styles, we’ll then decide whether to not show them as options or if there are alternatives.

1 Like

Don’t really think you can exclude styles based on the chosen language. To begin with, it is perfectly acceptable for a Chinese user to write some roman text, and there the styles apply. So I don’t think removing styles is the answer.

1 Like

Update: We have now moved the Simplified Chinese translation of Agenda to the OneSky platform.

Update: Hooray, the Traditional Chinese translation of Agenda is now available as part of Agenda version 10.0 :confetti_ball:. We’d invite everybody to give it a try and let us know if you find any aspects that can be improved, need to be corrected, or are giving issue. Join me in thanking all translators who worked so hard and with so much passion to add the Traditional Chinese translation of Agenda! :clap: :clap:

1 Like

I’m soooo glad to see the Traditional Chinese version finally comes to reality!!! However, there’re some mistakes should be corrected instantly cuz they are on an important place–Preview pages on App Store.
BTW I would like to know what can I do to help improving the translation. (Using OneSky or…?) :smiley:

Glad to hear that, @david_c and @marsping can you have a look and also point out, what exactly is wrong?

I have corrected the mistake in OneSky, there is a typo in the word 「大氣層」vs「大氣屠」, thanks @nicofan1226 for reporting the issue.


Thanks! We’ll update the screenshots in the next round.

I will spend some time in the sample document in the coming week. I think they needs more polishing but there were too many words. Hope I can catch up before the next release.

1 Like