-
Notifications
You must be signed in to change notification settings - Fork 15
Feedback on README.md? #4
Comments
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 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 :) |
@kosamari ... the Mandate section (https://github.com/nodejs/internationalization#mandate) hopefully calls some of those details out. The |
@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. |
I'll do a PR adding that tomorrow!
|
@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"? |
They do more than translations though, they also manage native language social media, events, evangelism, etc. Maybe the "Global WG" or something. |
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.) |
@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 |
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." |
@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. |
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. |
as per TSC this repo has been renamed to Intl which parallels (but is not limited to) the |
Example of scope: nodejs/node#26, nodejs/node#1494, nodejs/node#2165 |
Resolves nodejs#4
Resolves nodejs#4
@nodejs/tsc — please put on agenda
The text was updated successfully, but these errors were encountered: