Replace old-style compatibility/specification tables with new macro

[queengooborg]

In mid-2019, we have migrated all of the compatibility table information over to the BCD project. Recently, we have also transitioned to using BCD to generate the specifications table.

When I went and marked the old {{CompatXXX}} macros as deprecated in Yari, I happened to notice that there are a LOT of translations that are still using the old-style compatibility tables, which means readers may be getting outdated compatibility information. We should go through and replace all of these tables with ones generated by the new {{Compat}} macro. While we're at it, we should also replace the specifications tables with the {{Specifications}} macro as well.

Steps to fix pages:

• Find pages that use any of the following macros: CompatAndroid, CompatChrome, CompatGeckoDesktop, CompatGeckoMobile, CompatibilityTable, CompatIE, CompatNo, CompatOpera, CompatOperaMobile, CompatSafari, CompatUnknown, CompatVersionUnknown, spec, spec2, SpecName
• Replace all content in the "Specifications" section with {{Specifications}}
• Replace all content in the "Browser Compatibility" section with {{Compat}}

P.S. BCD has an open issue regarding how to handle localization for notes. We're open to suggestions, see mdn/browser-compat-data#114 for more!

[yin1999]

For replacing the specifications tables, I've using <table class="standard-table">[\s\S\r]*</table> to match and replace with {{Specifications}} if existed in en-US. The script I've used is here (in Golang, really simple, may not deal with all the cases).

And please check the modifications made by this script, because of the usage of standard-table in other tables.

[yin1999]

Hi @queengooborg, I found that yari will merge metadata from en-US when render a macro in l10n documents, so whether it's ok to remove browser-compat metadata from l10n documents (is there any other usage of this metadata)?

see: https://github.com/mdn/yari/blob/5d8d88976164b6f653c3f2de688f3cd76f8537bb/kumascript/index.js#L56-L69

[queengooborg]

Great catch, thanks for the info @yin1999! Since the en-US metadata is merged, then we can omit the frontmatter key -- I've updated the instructions accordingly!

[hochan222]

@queengooborg Hello!

Replace all content in the "Browser Compatibility" section with {{Compat}}

I have a question for confirmation. Is it ok to change everything to {{Compat}} as shown below?

• AS IS

<h2 id="Browser_compatibility">Browser compatibility</h2>

<p>{{Compat("api.Cache.put")}}</p>

• TO BE

<h2 id="Browser_compatibility">Browser compatibility</h2>

{{Compat}}

[hochan222]

ko-locale

• Specifications [ko] Replace old-style specification tables with new macro #7442
• Compatibility

[yin1999]

• TO BE

<h2 id="Browser_compatibility">Browser compatibility</h2>



{{Compat}}

This is ok, I've used this in l10n-zh.

[hochan222]

@yin1999 , Thank you for the reply 🙇🙇

[yin1999]

done for l10n-zh

[SphinxKnight]

just in case someone needs a regex or two:

\{\{\s*compatAndroid|\{\{\s*compatChrome|\{\{\s*compatGecko|\{\{\s*compatibilityTable|\{\{\s*compatIE|\{\{\s*compatIE|\{\{\s*CompatNo|\{\{\s*compatOpera|\{\{\s*compatSafari|\{\{\s*compatUnknown|\{\{\s*compatVersionUnknown

\{\{\s*spec\s*\(|\{\{\s*spec2\s*\(|\{\{\s*specName\s*\(

[YujiSoftware]

I wrote a script to migrate Specifications.
(Removed old spec macros and insert specifications macros)
https://gist.github.com/YujiSoftware/6ca47a35df8097c15dd5c1c4f7f23c3c

Already applied to ja.

[hochan222]

Done for l10n-ko. Have a nice day :)

[Graywolf9]

Done for es. Thank you so much!

[queengooborg]

Closing in favor of the new tracking issue at #11594.