metanorma/metanorma-ietf

Problem with table validation

ronaldtse opened this issue · 1 comments

Metanorma XML Syntax: (XML Line 000399:31): attribute "valign" not allowed here; expected attribute "align", "colspan" or "rowspan"
Metanorma XML Syntax: (XML Line 000400:31): attribute "valign" not allowed here; expected attribute "align", "colspan" or "rowspan"
Metanorma XML Syntax: (XML Line 000401:31): attribute "valign" not allowed here; expected attribute "align", "colspan" or "rowspan"
Metanorma XML Syntax: (XML Line 000406:31): attribute "valign" not allowed here; expected attribute "align", "colspan" or "rowspan"
Metanorma XML Syntax: (XML Line 000407:31): attribute "valign" not allowed here; expected attribute "align", "colspan" or "rowspan"
...
<table id="_9080178b-a022-42d3-8386-2e6a5e5a0555" unnumbered="true">
<thead>
<tr>
<th valign="top" align="left">Month Number</th> <<<<<< THIS LINE >>>>>>
<th valign="top" align="left">Month/Year</th>
<th valign="top" align="left">Maximum value of date-mday</th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">01</td>
<td valign="top" align="left">January</td>
<td valign="top" align="left">31</td>
</tr>
<tr>

Source:

[cols="3",options="header,unnumbered"]
|===
| Month Number  | Month/Year           | Maximum value of date-mday

| 01            | January              | 31
| 02            | February, normal     | 28
| 02            | February, leap year  | 29
| 03            | March                | 31
| 04            | April                | 30
| 05            | May                  | 31
| 06            | June                 | 30
| 07            | July                 | 31
| 08            | August               | 31
| 09            | September            | 30
| 10            | October              | 31
| 11            | November             | 30
| 12            | December             | 31
|===

The grammar checked in on github has this update, and it's been there for a month: c2809ad#diff-4511a8ce873e74960ce4b5f550bef9a6b4a22a8fcad9122e0b93e5620027bf52. If you aren't accessing the grammar updates, that is not my problem, that is a problem with the gem releases being held up for six weeks.