Confirmed users, Bureaucrats and Sysops emeriti
1,057
edits
MDN/Archives/Development/CompatibilityTables/Importer: Difference between revisions
MDN/Archives/Development/CompatibilityTables/Importer (view source)
Revision as of 19:13, 22 May 2015
, 22 May 2015→section_skipped: Noted one solution for skipped error
(Add some general notes on expected content and the parsing grammar) |
(→section_skipped: Noted one solution for skipped error) |
||
| Line 255: | Line 255: | ||
The parser was trying to match rule "{rule_name}", but was unable to understand some unexpected content. This may be markup or text, or a side-effect of previous issues. Look closely at the context (as well as any previous issues) to find the problem content. | The parser was trying to match rule "{rule_name}", but was unable to understand some unexpected content. This may be markup or text, or a side-effect of previous issues. Look closely at the context (as well as any previous issues) to find the problem content. | ||
====Possible solutions==== | |||
* Often, this is caused by the use of plain text or HTML instead of an expected KumaScript macro. For instance, specification tables should be using the SpecName and Spec2 macros instead of specifying text directly. | |||
=== spec_h2_id === | === spec_h2_id === | ||