Decide on subdomain #1

gaearon · 2019-01-31T00:13:28Z

Should it be cn, zh, zh-cn, zh-hans, or something else?

The text was updated successfully, but these errors were encountered:

zhongdeming428 · 2019-01-31T00:50:00Z

I prefer cn as the subdomain,just like https://cn.bing.com/?mkt=zh-CN

gaearon · 2019-01-31T00:59:21Z

What if somebody later wants to start a Traditional Chinese translation?

robertying · 2019-01-31T02:54:32Z

Something like Wikipedia's:

Simplified Chinese (Mainland) https://zh.wikipedia.org/zh-cn/
Traditional Chinese (Hong Kong) https://zh.wikipedia.org/zh-hk/
Traditional Chinese (Macao) https://zh.wikipedia.org/zh-mo/
Simplified Chinese (Malaysia) https://zh.wikipedia.org/zh-my/
Simplified Chinese (Singapore) https://zh.wikipedia.org/zh-sg/
Traditional Chinese (Taiwan) https://zh.wikipedia.org/zh-tw/

Well, I don't think we can achieve all these variants for now. So using zh-cn for Simplified Chinese and zh-tw for Traditional Chinese with cn.reactjs.org seems conventional.

Simplified Chinese https://cn.reactjs.org/zh-cn/
Traditional Chinese https://cn.reactjs.org/zh-tw/

QC-L · 2019-01-31T02:54:53Z

I think it would be better to use cn.
Traditional Chinese translation use zh-hant or zh-tw.

shaodahong · 2019-01-31T06:00:02Z

yeh, better to use cn

haimengzhang · 2019-01-31T07:12:35Z

using zh-cn for simplified and zh-tw for traditional is more intuitive as I see it more often. second @robertying, but that being said, zh-cn is a child category of zh-hans, and zh-tw ofzh-hant, with the parent categories meaning Chinese written in simplified scripts and Chinese written in traditional scripts ( according to the long outdated IANA). The CSS3 language code only uses two options though:zh-hans and zh-hant .

https://www.w3schools.com/tags/ref_language_codes.asp

haimengzhang · 2019-01-31T07:24:35Z

What if somebody later wants to start a Traditional Chinese translation?

@gaearon I think we can maintain both versions? zh-cn and zh-tw seem to be most economic choices

gaearon · 2019-01-31T10:05:37Z

The problem is we can’t have two languages on one domain. This would make the website more complex. So we need to choose two different subdomains.

gaearon · 2019-01-31T10:05:59Z

cc @chloewlin, any thoughts?

QC-L · 2019-01-31T10:25:23Z

I think it should be divided into two repos.
If together, it is not easy to synchronize with en repo.

gaearon · 2019-01-31T10:29:16Z

Maybe let’s go with cn for Simplified and tw for Traditional?

chloewlin · 2019-01-31T10:32:53Z

@gaearon I agree. I also prefer cn for Simplified and tw for Traditional for its clarity and simplicity.

QC-L · 2019-01-31T10:33:55Z

@gaearon @chloewlin
NoNoNo, use tw is not good. I think it should be used zh-tw.
Because it will be very dangerous

shaodahong · 2019-01-31T10:39:46Z

@QC-L i understand your worry, but weibo also use tw.weibo.com

discountry · 2019-01-31T10:42:06Z

@gaearon @chloewlin Using cn and tw would cause political issues to the whole React project.

We should avoid that, it's not wise to do so.

BTW, if we use cn and tw , we also need hk, that would make a simple problem to a complex one.

gaearon · 2019-01-31T10:44:29Z

I wasn’t aware of the political implications. Sorry about this!

Do zh-tw and zh-cn have any issues too?

haimengzhang · 2019-01-31T10:45:02Z

How about zh-cn as a domain for simplified and zh-tw for traditional? Are we not going to have two subdomains? @gaearon

…

On Thu, Jan 31, 2019, 4:33 AM QiChang Li ***@***.*** wrote: @gaearon <https://github.com/gaearon> NoNoNo, use tw is not good. I think it should be used zh-tw. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNCzNrjMGFHzBYDdyV0TSM8hn5Bs4tks5vIsaTgaJpZM4abUo2> .

shaodahong · 2019-01-31T10:45:11Z

agree, political issues are important

gaearon · 2019-01-31T10:45:59Z

Also, Vue docs go with cn — is that problematic too in a way?

gaearon · 2019-01-31T10:46:49Z

@haimengzhang

If zh-cn and zh-tw aren’t problematic they sound ok to me as subdomains.

discountry · 2019-01-31T10:47:04Z

@gaearon Vue only has one Chinese doc.

shaodahong · 2019-01-31T10:47:36Z

maybe use cn and zh-tw

haimengzhang · 2019-01-31T10:47:57Z

Sounds good to me. Tw and cn is indeed a very sensitive issue😅

…

On Thu, Jan 31, 2019, 4:44 AM Dan Abramov ***@***.*** wrote: I wasn’t aware of the political implications. Sorry about this! Do zh-tw and zh-cn have any issues too? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNCxbLCbMIMcc57WOKYEV7GVNnx8R7ks5vIskOgaJpZM4abUo2> .

shaodahong · 2019-01-31T10:48:19Z

like facebook https://zh-tw.facebook.com/

haimengzhang · 2019-01-31T10:52:46Z

Hmm i think however we use it, it will be a bit political. Say just the choice of not choosing zh-hk instead of zh-tw. Western media and countries like US take Taiwan as a country, but China is on the opposite stance. So either way, the choice of picking tw has some political flavor.

…

On Thu, Jan 31, 2019, 4:48 AM 骗你是小猫咪 ***@***.*** wrote: like facebook https://zh-tw.facebook.com/ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNC1m3hVRbge9gcigAW0BqCk53vfp-ks5vIsn0gaJpZM4abUo2> .

chloewlin · 2019-01-31T10:52:58Z

I am fine with zh-tw if it helps us stay away from potential controversies and stay focused on producing quality, up-to-date translations that help React docs accessible to more developers. Thank you everyone for being so thoughtful! 🙂

gaearon · 2019-01-31T10:53:17Z

Can tw be zh-hant then?

haimengzhang · 2019-01-31T10:55:56Z

Yes, that sounds most neutral of all.

…

On Thu, Jan 31, 2019, 4:53 AM Dan Abramov ***@***.*** wrote: Can tw be zh-hant then? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATTNC7kmPGo4pmomfX7QMq3DyPwgBJhSks5vIssegaJpZM4abUo2> .

gaearon · 2019-01-31T11:00:20Z

The other concern is typing. If it’s too long, it could be annoying and alienating. I don’t know how many websites in practice use two/five/seven letter codes.

Is zh-tw controversial or is it only tw?

I think zh-cn and zh-tw could be a good tradeoff overall between typing and accuracy. But I don’t know if those are considered problematic in any way.

cyanial · 2019-01-31T11:05:26Z

I don't think the developer will notice it. they are focusing their works. For me, zh-tw and zh-cn are not problematic. BTW, I'm a Chinese developer.

discountry · 2019-01-31T11:06:31Z

@gaearon

zh-CN	中文(简体)
zh-HK	中文(香港)
zh-MO	中文(澳门)
zh-SG	中文(新加坡)
zh-TW	中文(繁体)

The majority uses simplified Chinese, so we could keep the cn for simplified Chinese version doc.

And zh-tw is just a language code, it's not sensitive. We can use it for traditional one.

Simplified Chinese and Traditional Chinese are not just different characters, we use different phrases and words, so I think we need to spread the two translation in two repos.

Let's try to make this simple and efficient, do not make a small problem turn into a bigger one.

shaodahong · 2019-01-31T11:12:42Z

The focus on language, not country

gaearon · 2019-01-31T11:15:01Z

Thanks everyone for your perspectives. I’ll consult more people and learn more about this issue and then will post our proposal later today. I agree that we need to be efficient and not spend too much time on this. But on the other hand I want to make sure we’ve done due diligence here and don’t cause unnecessary controversy. I’ll post later!

shaodahong · 2019-01-31T11:15:13Z

cn for simplified and zh-tw for traditional make easy

discountry · 2019-01-31T11:17:35Z

@gaearon

cn.reactjs.org for simplified Chinese.
zh-tw.reactjs.org for traditional Chinese.

And we also need a https://github.com/reactjs/zh-tw.reactjs.org repo for conveniences.

Let's keep this simple and neutral.

Thanks a lot, we could also wait for a better proposal.

chloewlin · 2019-01-31T11:29:51Z

I agree that this is simply a matter of two different languages. For example, terminologies such as servers (伺服器 vs. 服务器), libraries (函式庫 vs. 库), or even tutorials (教學手冊 vs. 教程) are phrased differently. The Chinese of tw or zh-tw will always be Traditional Chinese (繁體中文), which is pretty neutral in my opinion.

hijiangtao · 2019-01-31T11:31:27Z

Maybe we need more discussion about how to handle the subdomain for Traditional Chinese Translation, but it seems pretty clear currently, which is cn is well known in representing Simplified Chinese Translation.

I quickly look through some famous repositories and here's what I found:

There's a bunch of cases, we can discuss the subdomain for Traditional Chinese Translation thoroughly in the future, but I suggest don't waste too much time on that for Simplified Chinese, if you also think cn is good enough in representing Simplified Chinese Translation.

gaearon · 2019-01-31T11:46:38Z

I agree with the proposal to use cn for the Simplified Chinese docs. It seems to be commonly accepted in the front-end community and uncontroversial in this discussion.

I will need more time to choose the Traditional Chinese domain. I’ll post in this thread after we have done so, but for now this shouldn’t need to stop us from work. We haven’t set up a repo for it anyway yet.

Thank you all again! This was very helpful.

gaearon · 2019-01-31T18:44:25Z

After talking to people on different sides of this issue, we've decided to use the neutral script codes to avoid any appearance of the political stance. We don't intend to host multiple dialects of Traditional and Chinese translations, so zh-hans and zh-hant will be sufficient.

We could possibly add redirects from shorter domains in the future if enough people complain about it. But for now I think this is sufficient and addresses the issue. Thanks again to everyone for sharing your opinions and concerns.

tesseralis mentioned this issue Jan 31, 2019

reactjs.org Localization Forks reactjs/react.dev#1605

Closed

8 tasks

gaearon closed this as completed Jan 31, 2019

reactjs locked as resolved and limited conversation to collaborators Jan 31, 2019

Decide on subdomain #1

Decide on subdomain #1

Comments

gaearon commented Jan 31, 2019

zhongdeming428 commented Jan 31, 2019

gaearon commented Jan 31, 2019

robertying commented Jan 31, 2019 • edited Loading

QC-L commented Jan 31, 2019 • edited Loading

shaodahong commented Jan 31, 2019

haimengzhang commented Jan 31, 2019 • edited Loading

haimengzhang commented Jan 31, 2019

gaearon commented Jan 31, 2019 • edited Loading

gaearon commented Jan 31, 2019

QC-L commented Jan 31, 2019

gaearon commented Jan 31, 2019

chloewlin commented Jan 31, 2019 • edited Loading

QC-L commented Jan 31, 2019 • edited Loading

shaodahong commented Jan 31, 2019

discountry commented Jan 31, 2019

gaearon commented Jan 31, 2019

haimengzhang commented Jan 31, 2019 via email

shaodahong commented Jan 31, 2019

gaearon commented Jan 31, 2019

gaearon commented Jan 31, 2019

discountry commented Jan 31, 2019

shaodahong commented Jan 31, 2019

haimengzhang commented Jan 31, 2019 via email

shaodahong commented Jan 31, 2019

haimengzhang commented Jan 31, 2019 via email

chloewlin commented Jan 31, 2019 • edited Loading

gaearon commented Jan 31, 2019

haimengzhang commented Jan 31, 2019 via email

gaearon commented Jan 31, 2019

cyanial commented Jan 31, 2019

discountry commented Jan 31, 2019

shaodahong commented Jan 31, 2019

gaearon commented Jan 31, 2019

shaodahong commented Jan 31, 2019

discountry commented Jan 31, 2019

chloewlin commented Jan 31, 2019 • edited Loading

hijiangtao commented Jan 31, 2019 • edited Loading

gaearon commented Jan 31, 2019

gaearon commented Jan 31, 2019

robertying commented Jan 31, 2019 •

edited

Loading

QC-L commented Jan 31, 2019 •

edited

Loading

haimengzhang commented Jan 31, 2019 •

edited

Loading

gaearon commented Jan 31, 2019 •

edited

Loading

chloewlin commented Jan 31, 2019 •

edited

Loading

QC-L commented Jan 31, 2019 •

edited

Loading

chloewlin commented Jan 31, 2019 •

edited

Loading

chloewlin commented Jan 31, 2019 •

edited

Loading

hijiangtao commented Jan 31, 2019 •

edited

Loading