MDN/Development/CompatibilityTables/Translation: Difference between revisions

Add forward-looking statements about the translation process
(Add translation of Maturity names)
(Add forward-looking statements about the translation process)
Line 2: Line 2:


The browser compatibility API and the API-back compatibility tables are in alpha testing.  
The browser compatibility API and the API-back compatibility tables are in alpha testing.  
In the future, it will be a lot easier to translate strings. Some ideas are:
# If a table has non-localized strings, the JS will know it, and MDN visitors will be prompted to contribute a translation for that string.
# The contribution interface will provide a translation interface focused on an MDN page.
# The contribution interface will provide a translator interface, showing a high-level view of the translation state for a locale, and where the English variant has been updated since the local variant.
The work priorities are:
# Make it ''possible'' to translate strings, even if it is difficult or technical.
# Make it ''easy'' to translate strings, with useful interfaces
# Make it ''natural'' to translate strings, as a side-effect of viewing the site.


== Viewing Translated Content ==
== Viewing Translated Content ==
Line 8: Line 20:
* The importer has a preview of translated content, as seen by the API.  Go to [https://browsercompat.herokuapp.com/importer/ the importer], find the page you are interested in (for example [https://browsercompat.herokuapp.com/importer/726 Web/CSS/display], and use the links in the "Languages" section to see the content (partially) translated into that locale.
* The importer has a preview of translated content, as seen by the API.  Go to [https://browsercompat.herokuapp.com/importer/ the importer], find the page you are interested in (for example [https://browsercompat.herokuapp.com/importer/726 Web/CSS/display], and use the links in the "Languages" section to see the content (partially) translated into that locale.
* When a feature has been committed to the API, you can view the API translated strings, such as [https://browsercompat.herokuapp.com/view_feature/730 Web/CSS/display].  This works identically to the importer's sample views, but works with the committed API data available for MDN pages.
* When a feature has been committed to the API, you can view the API translated strings, such as [https://browsercompat.herokuapp.com/view_feature/730 Web/CSS/display].  This works identically to the importer's sample views, but works with the committed API data available for MDN pages.
== This is not the final version ==


== <nowiki>{{EmbedCompatTable}}</nowiki> KumaScript macro ==
== <nowiki>{{EmbedCompatTable}}</nowiki> KumaScript macro ==
67

edits