ISO Rice: Different order of the %key, notes and footnotes in the table

[anermina]

Table 1 includes the following elements:

• notes
• footnotes
• abbreviations

They are ordered as above in the original document.

However, they cannot be properly generated if the abbreviation is put last

using the following markup (same result without [%key]; footnotes are added inline):

NOTE: Ce tableau est basé sur l'<<ISO7301,table=1>>.

NOTE: Certains contrats commerciaux peuvent exiger des complémentaires à celles fournies dans le présent tableau.

NOTE: Seul le riz (cargo) rouge entièrement décortiqué est pris en considération dans le présent tableau.

[%key]
N/A:: N'est pas applicable.

I believe it is not intended to use [%key] after the notes. Therefore, these elements are encoded in the following order:

• abbreviations
• notes
• footnotes

and generated like this:

Is it fine to keep the current encoding, or we need to address this issue as a request for enhancement/a bug?

[ronaldtse]

ISO DIR 2 says this.

1. It says Footnotes always at the bottom
2. The abbreviations are part of Key. So using Key to encode is correct.
3. NOTEs and other text can appear but the order is undetermined. This still means before Footnotes.

look at 29.6:

From this table, we can see that the order is:

• text
• NOTEs
• Footnotes

It doesn’t say where the Key/Abbreviations is located, but Footnotes must be at the bottom.

Let us enquire ISO about this.

[ronaldtse]

Email sent to ISO.

[ronaldtse]

Official answer from ISO's Yvonne Chen:

1 Is the component order: Text > Note > Footnote > Key?

Personally I try to follow the order of Key > Text > Note > Footnote.

2. Should the “Key” section have the “Key” in bold as a header, like ISO DIR 2 Table 11?

Yes, “Key” should be in bold.

[anermina]

Thank you, @ronaldtse !

@opoudjis , could you please help with the second requirement to generate the boldfaced "Key" title in the table footnotes when the key element is used?

[ronaldtse]

@anermina could you please help file that issue under metanorma-iso? Thanks!

[anermina]

@ronaldtse @opoudjis the issue is now addressed in metanorma/metanorma-iso#1162.

[ronaldtse]

Thanks @anermina

[opoudjis]

How the fragment now renders:

Archive 6.zip