i18n support
Closed this issue · 24 comments
Hello.
I find this repo from HN today. I look at it and I think "I must translate it. It will be nice work for my study and global js culture.".
I'm Korean. Although I can't English well, I think I can translate it with some reference from dictionaries and some advice from its contributer. And I think if you decide to i18n this page, there will be with many contributors.
Please reply your opinion.
Yeah, if they confirm, I can translate entire page to Turkish. There will be more contributors to different language translations. Your idea is great :) Hope they will confirm this idea 👍
Hey guys, amazing, I need one responsible for each language, cause I'm Brazilian, if you accept, you can do this work. What do you think?
@allanesquina I can translate all page to Turkish 👍
@allanesquina I can translate all page to Traditional Chinese 👍
@allanesquina I want to do it. 👍
do you need a participant in Korean?
Fine, I'll create a new branch called i18n with an translation's structure and then we can work on it.
Good luck, soldiers! 👍
@allanesquina We are waiting your branch create 👍
👍
👍
👍
Such a great idea 👍
@allanesquina Can we use i18n branch now?
I think no. "Please Wait" was written.
So lets everyone create Pull Request 👍
I will wait until ready to go.
before show time, I suggest to fork and change my google docs sheet.
Hi guys, i'm sorry I made you wait, the .json file is incomplete, there's one item for each category, so I'll accept all pull requests now, but please, when I complete this file, be sure that your file be completed too.
Great idea @item4!
👍
Hey Soldiers, I fixed the workflow, now we can use grunt server to work. 👍
Hey, the file en-us.json is completed. \o/
Thanks @gabrielfurini 👍
I'm gonna translate to portuguese folks!
Welcome to the army @ivanbanov! 👍
Soldiers, please, help us to decide what kind of flag to use on the select element!
#194