67
edits
MDN/Development/CompatibilityTables/Translation: Difference between revisions
MDN/Development/CompatibilityTables/Translation (view source)
Revision as of 16:05, 20 November 2015
, 20 November 2015Add translation of Maturity names
(Update EmbedCompatTable section for L10n:CompatTable macro) |
(Add translation of Maturity names) |
||
| Line 265: | Line 265: | ||
In the future, code will be able to determine if a <code>view_feature</code> endpoint contains untranslated strings for a locale, and a web-based contribution interface will make it easier to translate the needed strings. | In the future, code will be able to determine if a <code>view_feature</code> endpoint contains untranslated strings for a locale, and a web-based contribution interface will make it easier to translate the needed strings. | ||
== Maturity names == | |||
The Specification Table uses the [https://developer.mozilla.org/en-US/docs/Template:Spec2 Spec2] macro to translated specification maturities. The API processes this and [https://developer.mozilla.org/en-US/docs/Template:SpecName SpecName] to populate the Maturity and Specification resources. | |||
There is not yet a macro like <nowiki>{{EmbedCompatTable}}</nowiki> for embedding API-backed specification tables in MDN. | |||
To translate a Maturity into a new language: | |||
# Update the Spec2 macro | |||
# Ask jwhitlock to re-import the data (using [https://github.com/mdn/browsercompat/blob/master/tools/load_spec_data.py tools/load_spec_data.py]) | |||