Translating and fixing hi.yml

Actual Behaviour and suggested fix

hi.yml contains some problematic translations. A major problem is with sentence termination. While English sentences ends with ., hindi sentences end with ।. This problem can be tackled in most cases but there are a few in which . is added in index.hbs files which do not get translated. I would like to fix that by changing some index.hbs files. Should I proceed with this idea? What do you suggest?

Is there a convention for assigning i18n tags? There is . at the end of environment7 i18n tag and I want to add a new i18n tag at the end to replace the ., what name should I use (something similar to environment7a?

Would you like to work on the issue?

Yes, please assign me.

[ayushjainrksh]

I have updated 3 more pages in the hi.yml file in this PR.

[limzykenneth]

@ayushjainrksh I do want to have this fix while we have a relatively few number of translations, however seeing as the proposal submission period of GSoC just ended and there were some interest in looking at the translation system itself from a number of potential applicants I don’t want the work done on this right now to be superceeded by another project that maybe moves the whole translation system to another platform (Transifex, as @montoyamoraga mentioned, for instance), in just a couple months.

Also we can fix this now but as mentioned this require taking into account ongoing translation work, not just that there will be a few additional terms to translate but rather also that it could complicate the merge process for those contributors, which is why this isn’t going to be a simple fix involving just code changes on one end.