The subject of translating the website or part of it is sth has popped up more than a couple of times.
Personally, I would be absolutely in favor of that.
The challenge here is to split the material in parts, so that a translator/maintainer can work just with the translations, without having to deal with code, while keeping the whole thing manageable (and secure from vast variations, from one version to another, or in case sth slightly changes, e.g. in our standard library)
Also, we should set some guidelines and start setting priorities. Obviously, there are languages that could be given higher priority, for reasons of relevance, number of speakers, etc. (I, for instance, am a Greek native speaker, but I don't think anybody will care that much; now, say Spanish, Mandarin, I don't know... obviously, I would consider that a higher priority). In that, we should also consider if there is enough time/people to maintain these translations (e.g. adding a translation in You-name-it and being stuck with it in our very next release doesn't make any sense - so obviously commitment of the maintainers of the translations will be important! :) )
A way (just a way I would think right now) in which the translatable material could be structured:
Library
Description of a module
Function
Description
Options
Description
Sections
Home
Getting Started
In A Nutshell (obviously just the intros, not everything)
Language (this could be broken into more identifiable parts!)
Command Line
Library
Homepage (in case we decide to translate the whole website, which - if we go that far - "why not?!")
The different text sections of the page
Deep breath. If you are lost, it's ok.
Again: just brainstorming in written form, without necessarilymaking much sense...
The subject of translating the website or part of it is sth has popped up more than a couple of times.
Personally, I would be absolutely in favor of that.
The challenge here is to split the material in parts, so that a translator/maintainer can work just with the translations, without having to deal with code, while keeping the whole thing manageable (and secure from vast variations, from one version to another, or in case sth slightly changes, e.g. in our standard library)
Also, we should set some guidelines and start setting priorities. Obviously, there are languages that could be given higher priority, for reasons of relevance, number of speakers, etc. (I, for instance, am a Greek native speaker, but I don't think anybody will care that much; now, say Spanish, Mandarin, I don't know... obviously, I would consider that a higher priority). In that, we should also consider if there is enough time/people to maintain these translations (e.g. adding a translation in You-name-it and being stuck with it in our very next release doesn't make any sense - so obviously commitment of the maintainers of the translations will be important! :) )
A way (just a way I would think right now) in which the translatable material could be structured:
Deep breath. If you are lost, it's ok. Again: just brainstorming in written form, without necessarilymaking much sense...
But... as they say: "algo es algo" lol. 🚀