# \[NEW RELEASE\] sonar-l10n-zh-tw-plugin-1.0

**URL:** <https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402>\
**Category:** Plugin Development\
**Created:** [November 8, 2019, 2:49pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402 "2019-11-08T14:49:17Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 8, 2019, 2:49pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/1 "2019-11-08T14:49:18Z")

</div>

Hi, all,

I would like to add the sonar-l10n-zh-tw Plugin to your market place.

Short description: Traditional Chinese translation pack for SonarQube.

SonarQube compatibility: 7.0 and higher

Link to SonarCloud project dashboard: [https://sonarcloud.io/dashboard?id=timlee\_sonar-l10n-zh-tw](https://sonarcloud.io/dashboard?id=timlee_sonar-l10n-zh-tw)

Link to PR: [https://github.com/SonarSource/sonar-update-center-properties/pull/71](https://github.com/SonarSource/sonar-update-center-properties/pull/71)

Download URL: [https://github.com/timlee/sonar-l10n-zh-tw](https://github.com/timlee/sonar-l10n-zh-tw)

Release notes: [https://github.com/timlee/sonar-l10n-zh-tw/releases/tag/v1.0](https://github.com/timlee/sonar-l10n-zh-tw/releases/tag/v1.0)

- It is the first release of the plugin, please add the plugin to the Plugin Library page.  
Thank you!

Regards,  
Tim Lee

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 8, 2019, 9:12pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/2 "2019-11-08T21:12:49Z")

</div>

Hi Tim,

Welcome to the community and congrats on your plugin!

I’m sorry but I have to ask a dumb question. There’s already a well-maintained Chinese localization plugin in the Marketplace. What’s the difference from a user perspective between it and yours?

Also, so you know, I’ll be out of pocket for the beginning of next week and probably catching up for the end, so it will be a while before I get back to you on this topic.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 9, 2019, 10:02am UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/3 "2019-11-09T10:02:52Z")

</div>

Hi, Ann,

Thank you for your reply.

Traditional Chinese is used by the people in Taiwan, Hong Kong, Macau and overseas Chinese communities. The already existing Chinese localization plugin contains Simplified Chinese used in China, Singapore and Malaysia.  
In Taiwan, there are many companies and developers like and use SonarQube, so I created a Traditional Chinese Language Pack for SonarQube.

Please see the links below for clarification.

> **[Traditional Chinese characters](https://en.wikipedia.org/wiki/Traditional_Chinese_characters)**
>
> Traditional Chinese characters (traditional Chinese: 正體字/繁體字; simplified Chinese: 正体字/繁体字, Pinyin: Zhèngtǐzì/Fántǐzì) are Chinese characters in any character set that does not contain newly created characters or character substitutions performed after 1946.\[dubious – discuss\] They are most commonly the characters in the standardized character sets of Taiwan, of Hong Kong and Macau. The modern shapes of traditional Chinese characters first appeared with the emergence of the clerical script during...

  

> **[Simplified Chinese characters](https://en.wikipedia.org/wiki/Simplified_Chinese_characters)**
>
> Simplified Chinese characters (简化字; jiǎnhuàzì) are standardized Chinese characters prescribed in the Table of General Standard Chinese Characters for use in mainland China. Along with traditional Chinese characters, they are one of the two standard character sets of the contemporary Chinese written language. The government of the People's Republic of China in mainland China has promoted them for use in printing since the 1950s and 1960s to encourage literacy. They are officially used in the Tradi...

  

> **[Chinese Wikipedia](https://en.wikipedia.org/wiki/Chinese_Wikipedia)**
>
> The Chinese Wikipedia (traditional Chinese: 中文維基百科; simplified Chinese: 中文维基百科; pinyin: Zhōngwén Wéijī Bǎikē) is the Standard Chinese language edition of Wikipedia. It is run by the Wikimedia Foundation. Started on 11 May 2001, the Chinese Wikipedia currently has about 1,080,000 articles and about 2,837,000 registered users, of which 84 have administrative privileges.
> The Chinese Wikipedia has been blocked in Mainland China since May 2015.
> The Chinese Wikipedia was established along with 12 oth...

  
[https://en.wikipedia.org/wiki/Language\_localisation](https://en.wikipedia.org/wiki/Language_localisation) for “Examples of language tags”

Best!  
Tim Lee

---

<div class="post-metadata">

**Author:** ![xuhuisheng](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/xuhuisheng/32/182_2.png) [@xuhuisheng](https://community.sonarsource.com/u/xuhuisheng)\
**Post date:** [November 14, 2019, 9:56am UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/4 "2019-11-14T09:56:02Z")

</div>

HI, Ann,  
I had asked this question serveral years ago. SonarQube team answered that sonarQube didn’t support zh\_CN (Language,Culture)\_(Region), The only support l10n format is zh (Language, Culture).

My first commit is sonar-l10n-plugin-zh\_CN.jar, then I change the file name to sonar-l10n-plugin-zh.jar.

Does SonarQube support the ‘zh\_CN’ format l10n right now?

🙂

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 19, 2019, 5:08pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/7 "2019-11-19T17:08:45Z")

</div>

Hi,

To be transparent on this, I’m holding off on moving forward with this plugin until I have an answer to @xuhuisheng’s excellent question. The evaluation step for a i18n plugin is super-simple, so depending on the answer this could move quite quickly after that.

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 20, 2019, 2:40pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/13 "2019-11-20T14:40:27Z")

</div>

Hi, Ann,

Thank you for your reply and also thanks to xuhuisheng’s effort on the Simplified Chinese Language plugin.  
Hope SonarQube can support the Traditional Chinese Language later.

Regards,  
Tim

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 21, 2019, 6:11pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/14 "2019-11-21T18:11:59Z")

</div>

Hi guys,

TLDR;  
I’ve requested changes to the PR. Other than that it looks good except that I would like to see a small change to the plugin description before I add the plugin to the marketplace.  
&nbsp;

* * *

After a little internal investigation, we’ve learned this:

> The backend API is designed to support the official bcp47 standard : [https://tools.ietf.org/html/bcp47](https://tools.ietf.org/html/bcp47). The internal representation is the Java class [Locale](https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html), which is compliant with this standard. We then look for a translation file matching the locale.
> 
> But tests show that the API can only find the (Language,Culture) part. The region is ignored. Looks like a bug.
> 
> The plugin proposed is working because it provides both `core_zh.properties` and `core_zh_tw.properties` files. They are identical, and the `zh_tw` file is ignored.

So first the “Looks like a bug” part: I sense no enthusiasm on our side to pursue this. So let’s not hold our collective breath.

Next I asked myself if this was a breaking / blocker bug. What happens if I have both l10n-zh plugins installed? I found that the server loaded fine and web pages were rendered as expected. So then I turned on localization in my browser. I got this:

 ![Selection_782](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/2X/6/6f870760c0ab21bdb2bc885a0976bd2ab7b6ad66.jpeg)  
You guys will have to tell me which version I’m looking at. 😂

So! Since there’s no apparent conflict (probably just first-loaded-wins) between this new plugin and the extant one, I don’t see a barrier to Marketplace entry. However, since this comes down to the user being careful about which l10n plugin she chooses, I request @Tim that you update your plugin description to reflect that it is not compatible with the “Chinese Pack” (that’s the description that shows up in the Marketplace), re-release, and update your PR accordingly. Feel free to expand on the incompatibility in your documentation. Or not. @xuhuisheng, whether or not you want to add a note about not being compatible with your plugin is up to you, since you got here first. 😄

And thanks to both of you for your continued efforts to bring SonarQube to a wider audience!

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 22, 2019, 6:50pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/15 "2019-11-22T18:50:39Z")

</div>

Hi Tim,

I need a few more changes in your PR.

FYI I’m out of the office for Thanksgiving next week. See you in December!

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 22, 2019, 7:29pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/16 "2019-11-22T19:29:52Z")

</div>

Hi Ann,

Thank you for your help with this plugin.

> [@ganncamp](#):
>
> You guys will have to tell me which version I’m looking at. 😂

This is a Simplified Chinese version. I think it might be first-loaded-wins. 😄

I have updated the plugin description to reflect that it is not compatible with the “Chinese Pack”, re-release and update the PR accordingly.  
Please see if there are any problems. Thank you.

> [@ganncamp](#):
>
> FYI I’m out of the office for Thanksgiving next week. See you in December!

Happy Thanksgiving and see you in December!

Best!  
Tim

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [November 22, 2019, 8:21pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/17 "2019-11-22T20:21:03Z")

</div>

Hi Tim,

Your PR updates caught me before I left. I approved & merged, but it seems that your URLs were both wrong. Shame on me for not checking them. I’ve updated and now the publish job succeeds. So…

Congrats, you’re in!

_And_ please double-check next time. _I_ certainly will. 😉

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![pierreguillot](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pierreguillot/32/46022_2.png) [@pierreguillot](https://community.sonarsource.com/u/pierreguillot)\
**Post date:** [November 26, 2019, 1:15pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/18 "2019-11-26T13:15:15Z")

</div>

Hi, i tracked the issue [here](https://jira.sonarsource.com/browse/SONAR-12750). Hopefully it will be tacked in a hardening sprint. You can watch the ticket to get notified of progress.

---

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 26, 2019, 2:30pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/19 "2019-11-26T14:30:36Z")

</div>

Hi, Pierre,

Thank you for your information.  
I will watch the ticket to get notified of progress.

Best!  
Tim

---

<div class="post-metadata">

**Author:** ![Tim](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@Tim](https://community.sonarsource.com/u/Tim)\
**Post date:** [November 28, 2019, 4:18pm UTC](https://community.sonarsource.com/t/new-release-sonar-l10n-zh-tw-plugin-1-0/16402/20 "2019-11-28T16:18:55Z")

</div>

Hi, Ann,

Thank you for letting me in!  
It’s my first time to release a plugin. I certainly will double-check next time.😉  
Happy Thanksgiving!

Tim
