Closed
Bug 1218525
Opened 10 years ago
Closed 9 years ago
[Compat Data] Localize strings in the API
Categories
(developer.mozilla.org Graveyard :: BrowserCompat, enhancement)
developer.mozilla.org Graveyard
BrowserCompat
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sphinx_knight, Unassigned)
Details
(Whiteboard: [type:bug][bc:infra][bc:l10n])
What did you do?
================
1. Went on https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Promise/resolve
2. Hovered over Desktop/mobile icons, over different browsers icons
What happened?
==============
The names of the "browser categories" appeared in English (since the API doesn't have the localized strings).
The names of the different browsers appeared in English (idem).
What should have happened?
==========================
Hovering should have displayed the french strings since this page belongs to this locale.
Localized strings should be added on the API to be rendered properly.
Is there anything else we should know?
======================================
I'm willing to translate the strings in FR and to use the API to add them :)
This bug is a kind of follow-up of this email: https://groups.google.com/forum/#!msg/mozilla.mdn/0o7k4tJbcxg/0N2JqMOpBQAJ
Comment 2•10 years ago
|
||
I've shortened the summary. Two notes:
1. This bug sounds like it's mainly for translators. We also need to a bug, which covers the implementation of a frontend allowing to enter those translations.
2. This bug may be split into several bugs, one for each language, like it's done for the blockers of bug 1207344. So each l10n can be tracked individually.
Sebastian
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [Compat Data] Adding localized strings that are not related to a specific feature in the API → [Compat Data] Localize strings in the API
Comment 3•10 years ago
|
||
I've created a wiki page describing how to translate API-backed tables:
https://wiki.mozilla.org/MDN/Development/CompatibilityTables/Translation
This describes the current, very manual method of translating strings, but the methods should be available to our alpha users.
Comment 4•10 years ago
|
||
Thank you, John!
I've tried it out right now and it works fine (even when it is currently a bit cumbersome).
(In reply to Sebastian Zartner [:sebo] from comment #2)
> We also need to a bug,
> which covers the implementation of a frontend allowing to enter those
> translations.
Is there already a bug filed for this? If not, should I create one?
Sebastian
Flags: needinfo?(jwhitlock)
Comment 5•10 years ago
|
||
I don't think there is a bug, but shobson would know for sure, and where it should be filed.
Flags: needinfo?(jwhitlock) → needinfo?(shobson)
Comment 6•10 years ago
|
||
To my knowledge, there are not any bugs tracking work on the contribution interface. We haven't settled on a way to do this yet (contribution interface? pontoon interface?).
Flags: needinfo?(shobson)
Comment 7•9 years ago
|
||
Hi! As there is a way to translate project's strings I'm gonna close that bug. However I'll follow up very soon with dedicated l10n bugs.
Status: NEW → RESOLVED
Closed: 9 years ago
Keywords: in-triage
OS: Other → All
Resolution: --- → FIXED
Whiteboard: [specification][type:bug] → [type:bug][bc:infra][bc:l10n]
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•