-
Notifications
You must be signed in to change notification settings - Fork 60
Hindi(hi) localization #50
Comments
We're not accepting any more localizations right now as we figure out the best way to scale up with this. Thanks for the interest and keep checking back. Issue #34. |
Sorry it took so long. After all this time, we now decided to go back to the old system so we don't block on any translations anymore. This means that the translations live in the GitHub repository here. You can get more information on how to localize in the README. General flow:
Feel free to ping me for any questions you might have. |
Hey @MichaelKohler, Thanks for sharing this info. I followed the above suggested flow toward the goal for our local language translation done and I already have an existing fork of this repo but I didn't find any of our locale in these folders instead I found en.yml and I don't think that this could be of any help. I have couple of questions on this thread, which are as follows :
Cheers, |
Copy the en.yml to hi.yml and do your translations there.
You can take ES as example: https://github.com/mozilla/activate.mozilla.community/tree/gh-pages/_includes/es As of now, only the activities.html needs to be translated per language from the _include folder. For the _pages you should add all English md files you want to translate to the subfolder. For the _data folder, see above. There only the hi.yml needs to exist.
No, we're not going with Pontoon for now due to technical challenges on our side. For now, copy the relevant markdown pages to a subfolder "hi" and translate the markdown files there. |
Hi @MichaelKohler , |
My previous comment is still accurate. Please also check the README (contains that info as well). |
Maybe you need to check, whether your already existing fork is up-to-date enough. |
We are currently working on a refresh of the Activate page. This project is in its early stages, but what I can say now is that localization improvements (Pontoon) will be a big part of it. I'm closing this as it will be considered in the refresh. Once we will talk about about what locales to enable to be translated we will revisit all localization issues in this repository, so there is no need to create a new request somewhere. |
No description provided.
The text was updated successfully, but these errors were encountered: