Skip to content
This repository was archived by the owner on Feb 29, 2020. It is now read-only.

Feedback on README.md? #4

Closed
srl295 opened this issue Jul 1, 2015 · 14 comments · Fixed by #7
Closed

Feedback on README.md? #4

srl295 opened this issue Jul 1, 2015 · 14 comments · Fixed by #7

Comments

@srl295
Copy link
Member

srl295 commented Jul 1, 2015

@nodejs/tsc — please put on agenda

@kosamari
Copy link

kosamari commented Jul 1, 2015

I think word internationalization (i18n) should be defined more deeper in this doc.

the confusing point for me is the comment on "out of scope" section Translation of Node documentation, messages, and other materials into specific languages.

Translation groups used i18n as sort of "project name" . When someone say "i18n" in context of node/iojs, as someone who has been working on translation team & non-native english speaker, it means docs and messages translation first.

More bullet points on what IS internationalization WG and what IS NOT is very much appreciated :)

@jasnell
Copy link
Member

jasnell commented Jul 1, 2015

@kosamari ... the Mandate section (https://github.com/nodejs/internationalization#mandate) hopefully calls some of those details out. The internationalization WG's responsibility would be the implementation of internationalization support (e.g. Ecma-402) within Node itself, as well as ensuring compliance with Unicode standards and other globalization efforts. This mission is distinct from that of the various i18n working groups that are involved with translation of various project assets such as documentation and the website.

@kosamari
Copy link

kosamari commented Jul 1, 2015

@jasnell thanks! and would appreciate the explanation in your comment included in readme :)... you know... for those of us wondering where translation people should/should not go.

@jasnell
Copy link
Member

jasnell commented Jul 1, 2015

I'll do a PR adding that tomorrow!
On Jun 30, 2015 9:26 PM, "Mariko Kosaka" [email protected] wrote:

@jasnell https://github.com/jasnell thanks! and would appreciate the
explanation in your comment included in readme :)... you know... for those
of us wondering where translation people should/should not go.


Reply to this email directly or view it on GitHub
#4 (comment)
.

@srl295
Copy link
Member Author

srl295 commented Jul 1, 2015

@kosamari thanks for your feedback! You've touched on why I wrote the "out of scope" section. I know there is a large and active group of people doing such translation. That work is much appreciated, and I wanted to make it clear that this was something different. Perhaps that should be called a "Translation WG"?

@mikeal
Copy link

mikeal commented Jul 1, 2015

Translation WG

They do more than translations though, they also manage native language social media, events, evangelism, etc. Maybe the "Global WG" or something.

@kosamari
Copy link

kosamari commented Jul 1, 2015

yeah I haven't been able to find better word for these teams they own social media accounts, manage blogs and translate things. So it does interact with website/evangelism/ and internationalization WG when y'all need language content to fill after tool and system are in place (I assume.)

@srl295
Copy link
Member Author

srl295 commented Jul 1, 2015

@mikeal Maybe "Global content"? It's sort of content vs. infrastructure. Running water vs plumbing.

@kosamari Yes, in some cases. Actually a lot of the core language content comes from http://cldr.unicode.org/ - 300 people have cast 630 thousand votes for several hundred languages in this round of input, so that would be the place to contribute content for core things like date and time formats. But there will also be content for things like the proposal in nodejs/node-v0.x-archive#9174

@mikeal
Copy link

mikeal commented Jul 1, 2015

It's not just content, they are an active community doing more than just stuff that feeds in to the website and whatnot -- it's best not to think of them as "content producers." Maybe "Global Community WG" and call the repo just "global."

@srl295
Copy link
Member Author

srl295 commented Jul 1, 2015

@mikeal That's a good point. They are not just content. I like Global Community fwiw - that shows that it's more people than technology oriented.

And maybe that could help here- this could be the "Int'l Technology WG" or something.

@mikeal
Copy link

mikeal commented Jul 1, 2015

The only thing that might be confusing w/ "Int'l Technology WG" is that it implies broader tooling work than the scope you're going for because we also have i18n tooling in the website and doc working groups that translators are using.

Names, the single hardest problem in computer science.

@srl295
Copy link
Member Author

srl295 commented Jul 1, 2015

as per TSC this repo has been renamed to Intl which parallels (but is not limited to) the Intl object.

@srl295
Copy link
Member Author

srl295 commented Jul 9, 2015

@mikeal @kosamari is this the 'homepage' of the Global Community WG in a manner of speaking?

@srl295
Copy link
Member Author

srl295 commented Jul 9, 2015

Example of scope: nodejs/node#26, nodejs/node#1494, nodejs/node#2165

srl295 added a commit to srl295/internationalization that referenced this issue Jul 15, 2015
srl295 added a commit to srl295/internationalization that referenced this issue Jul 15, 2015
@srl295 srl295 mentioned this issue Jul 15, 2015
@srl295 srl295 closed this as completed in #7 Jul 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants