Use i18n for common strings

[avivkeller]

While we can't translate the docs themselves, we can translate some of our constant strings.

[flakey5]

How would these be distributed in releases? Putting them into subfolders like https://nodejs.org/docs/latest/api/<locale>/buffer.html?

[AugustinMauroy]

If I recall correctly, the TSC completely vetoed the translation.

[avivkeller]

Can you link that? I thought they vetoed translating the docs themselves, (the files in core), not the strings we use to generate them (the files here).

While we can't provide fully translated docs, we can at least translate some of the commonly used phrases (I.e. "Source Code: ", "Added in: ", etc.)

[AugustinMauroy]

cc @ovflowd

[avivkeller]

I'll work on adding a --locale flag today.

[ovflowd]

The TSC vettoed translation for the API docs. Navigation cues (and other common strings) should be translateable. Unfortunately due to the nature of API docs, these need to be purely on the client-side. In other words the "content" should not be translated, but anything that is layout/component should be translateable.

Meaning:

• Static generated JSON files part of the JS bundle
• React does a client-side switch (and stores translation key on a local storage)
• next-intl also works that way on a client-side-only mode; But since we don't use Next.js here, we gotta use use-intl (https://www.npmjs.com/package/use-intl) which is the underlying core of next-intl

[flakey5]

Just confirming- we can do this on the client side w/o requiring js to run in the client's browser, correct?

[ovflowd]

Just confirming- we can do this on the client side w/o requiring js to run in the client's browser, correct?

wdym? React is client side JavaScript running on the Client-Side browser.

[flakey5]

wdym? React is client side JavaScript running on the Client-Side browser.

Re nodejs/node#52343 (comment)

[ovflowd]

wdym? React is client side JavaScript running on the Client-Side browser.

Re nodejs/node#52343 (comment)

Ah yes, then it just goes to English :)