Skip to content
This repository was archived by the owner on Nov 21, 2018. It is now read-only.

io.js API localization: open questions #211

Closed
sejoker opened this issue Feb 19, 2015 · 6 comments
Closed

io.js API localization: open questions #211

sejoker opened this issue Feb 19, 2015 · 6 comments

Comments

@sejoker
Copy link

sejoker commented Feb 19, 2015

Hi,

as website content is translated by most localization groups I would like to open the discussion about io.js API localization.
The open questions so far:

  • when we can start?
  • what the structure of the folder should be?
  • how it would be merged into main website?

Would love to here your thoughts.

@therebelrobot
Copy link
Contributor

We haven't yet migrated over the documentation to the website group, we're currently looking into what kind of tooling we want to maintain all of that, so the localization of it would end up being a bit premature. @iojs/website what timeline are we looking at for getting all of this moved over?

@stringparser
Copy link
Contributor

We, iojs/iojs-es, have started to translate the api, no hurry, but just in case I leave this comment here as a ping :)

@Olegas
Copy link
Contributor

Olegas commented Mar 9, 2015

We at iojs-ru have some doc pages already translated too.

@bnb
Copy link

bnb commented Jun 22, 2015

This is an issue that can be handled by the Docs WG. I've marked it as invalid and docs to ensure its responsibility is handed to the Docs WG. If you want to discuss this issue, see nodejs/docs#10.

@stringparser
Copy link
Contributor

@bnb thanks a lot

@bnb
Copy link

bnb commented Jun 22, 2015

@stringparser No problem. If you want this addressed, feel free to open an issue there and reference this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants