Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add Internationalization Support #206
We have a community gulf to fill between East and West because of having entirely different websites, entirely different tools for communication and because of cultural differences.
So we fix that, by adding translations right here, to the EthereumClassic.org website.
@hitchcott can help us.
The goal would be to have either a runtime toggle (ideal) or to generate the static HTML multiple times.
I want the ETC Consortium (@zoulaihui) and ETC Asia communities (@ChrisXK) to have the option of just mapping directly to EthereumClassic.org (with Chinese by default through their URL), or to maintain their own websites which refer back to this Global one.
This approach does not just give us a means of bringing China and the West closer, but also gives us a path for other language communities (German, Italian, Spanish, French) to do the same.
The desired workflow would be:
Most of the time, the original articles are written first in English. If that happens, we would want that article to show up for people using other languages too - but it will be in English for them until a translated version is available.
For non-English original articles - ie. something written in Chinese about a meetup in Beijing, I am not sure that we would want that to be showing for everyone else. We should only have the drop-back to English. So if there is no "local language" version then drop back to English, and if there is no English version either then don't show it.
So I am a French person. Chinese article added. I do not see it.
So I am a French person with that same scenario, but for some reason the article gets translated directly to French, but not to English. In that case I see nothing, and then I see the French version.
So we are favoring English (because of its universality), and have English as a default, and only show localized or drop-back to English.
There is built-in internationalization support in the Gatsby framework, so this should not be hard:
The naming format follows .languageKey.js for files and /languageKey/path/fileName for URLs.
File - src/pages/about.en.js
URL - /en/about
Brilliant - thank you, @Automata-korea!
Everyone - here is how easy it was for me to add a blog post to the site. We should all really try to do that whenever we can rather than using Medium, because then it works within China too, and we are not trapped within the Medium empire.
I just pushed the v2 branch which shows how I intend the i18n to be structured.
Over the coming days I'll be migrating the english content into this branch.
After some research I wasn't able to use the vanilla i18n plugin as it's fairly simple (and doesn't scale for large websites with blogs etc), so I implemented a custom page generation script in
The localised content and UI strings are managed in the
@Athethepainter are you at devcon?
For anybody who has not already noticed, I have created additional Github issues for each of these translations. @hitchcott is working on the actual internationalization structure and support, which is what this issue is tracking. Then when that is done, and we have all the site content updated in English, it will be time for the translation work to be being.
Please can everybody here add themselves as "Member" to the ethereumclassic organization?
I understand that people CAN self-join. "Are we gradualy going to publish the contents in different language as we will maybe not finish all at the same time with the content?" Yes - gradually as people have time.…
On Wed, Oct 9, 2019 at 3:08 AM TheEnthusiasticAs ***@***.***> wrote: Should not the person be invited by Cody or similar? I got my today and joined already? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#206?email_source=notifications&email_token=AA4427HURIPHPMB4QSFYL63QNTD5FA5CNFSM4I5DIX6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAVCT6Q#issuecomment-539634170>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA4427DS6PT2PHWDHFFM6P3QNTD5FANCNFSM4I5DIX6A> .
@Athethepainter, @MileyFu you should get an invitation from DontPanic soon.