commonmark-web
commonmark-web copied to clipboard
We need i18n support
This may first require restructuring the code so all the localizable strings are in one centralized area, for ease of swapping out per language.
We also need a bit of UI at the start to let the user select a language -- or browser detection of the current language.
I'm in for the spanish (ecuadorian/south american) translation :P
A JSON file per language could be a good approach, but there are many options.
As for the UI, a browser detection feature + some [EN] [ES] [FR] at the bottom should be enough.
Let me know how i can help :)
I'm in for simplified Chinese (China mainland) translation. Agree with @juanmnl.
I think @Ismael-VC, who lead the adapation of the Julia language website to support i18n (https://github.com/JuliaLang/julialang.github.com/pull/252), could offer some useful advice here :) I believe the process to get the basic setup in place was fairly easy and straighforward with the major huldles coming from the organizational side rather than the technical one.