All users were logged out of Bugzilla on October 13th, 2018
What problems would this solve? =============================== MDN articles can be translated to Hindi, which is one of the primary languages of India and is spoken by 180 million people. Who would use this? =================== Users speaking Hindi What would users see? ===================== MDN articles translated to Hindi What would users do? What would happen as a result? =================================================== MDN can be used by people speaking Hindi. Is there anything else we should know? ======================================
Assignee: nobody → jbeatty
Component: General → Localization
Product: Mozilla Developer Network → Developer Documentation
hello, i would like to translate this Bug into Hindi Language. So where to start .
Assignee: jbeatty → nobody
Component: Localization → Localization
Product: Developer Documentation → Mozilla Developer Network
Whiteboard: [specification][type:feature] → [specification][type:feature][newlang]
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Maris, the requested locale was hi not hi-IN why have you created hi-IN?
:groovecoder, please see comment 4
Status: RESOLVED → REOPENED
Flags: needinfo?(mars) → needinfo?(lcrouch)
Resolution: FIXED → ---
I copied the approach of https://www.mozilla.org/hi-IN/ and https://support.mozilla.org/hi-IN/home to match what they did with Verbatim: https://localize.mozilla.org/hi_IN/ Do we need to change it?
No, no, I was curious :-) That's a good reason, it solves several problem as other web sites often just copy the locale of their own page. Note that in some case, it may be more critical (like if a language is spoken by two countries at war where contributors of one country may refuse to contribute on the language just because of the locale.
(In reply to Jean-Yves Perrier [:teoli] from comment #8) > No, no, I was curious :-) That's a good reason, it solves several problem as > other web sites often just copy the locale of their own page. Ah, I misunderstood then. I thought we needed (hi) specifically, not (hi-IN). Can we close this bug?
We were requested hindi translation, but we can do this with hi or with hi-IN. (And to be fair, I found good reasons to do hi-IN after my original question ;-) So you don't really misunderstood me) Let's close this :-)
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago → 5 years ago
Resolution: --- → FIXED
I had asked for hi based on the same convictions mentioned in comment 8. But hi-IN works just as well for now. Hope the localization team does a good work here.
You need to log in before you can comment on or make changes to this bug.