Headers centering.
Inline headers without text disappeared.

The footnote reference is meant to be inside the figure itself. ISO/IEC DIR 2, p. 75.

Generate the headings dynamically for the ToC of the Word document; the page numbers will still need to be frozen.

ISO/IEC DIR 2 p. 52

Criteria:

• Upper case Latin then lower case Latin
• Letter without indices, letter with letter index, letter with numeric index
• Latin then Greek then Other

Bump version on changes please. Thanks!

Need output to deal with at least English, French, Chinese, and Russian. The metalanguage needs to be translated.

Given that IsoDoc contains the sections proper in the generation of IsoDoc HTML we can easily insert the TOC with proper anchors. This way we can get rid of the jQuery code in it.

Right now the .out.html output is the basic Microsoft-ready HTML file. We need to take out the Microsoft-specific features (TOC becomes generic Asciidoc TOC), and introduce cogent HTML styling

Stem expressions in Word are center aligned. To make them left or right aligned, need to wrap them in isodoc in

<m:oMathPara><m:oMathParaPr><m:jc
     m:val="left"/></m:oMathParaPr>
<m:oMath>
....
</m:oMath>
<m:oMathPara>

Caution is just boldface and inline.

@ronaldtse, you'll have to tell me what you want the footnotes to look like in the HTML output.

Number introduction as "0." if it has subclauses. ISO/IEC DIR 2 p. 43

Today's style of ISO HTML isn't very pretty or useable:
https://www.iso.org/sites/directives/2017/consolidated/index.xhtml#footnote-003-backlink

Maybe there should be an alternative style, with these features:

• TOC in sidebar, highlighting current section
• relevant footnote entry appears dynamically when footnote citation in view
• anchors named according to the section name

HTML templates are currently "filled-in" within isodoc using gsub. If the content included a phrase like For CSS we should use SCSS templates as you can see in asciidoctor-reveal.js (a key that is being replaced), then the templating won't work properly.

We should use template engines to interpolate the HTML instead.

For example, asciidoctor-reveal.js uses the Slim template language. Personally, I think we can use the Liquid template language to create HTML templates.

This way the content of the templates can be easily changed.

Formulae are referenced by container and formula number; e.g. "see A.2, Formula (A.5)."

For all container referencing, the container is skipped if we are currently in that container: if we are in A.2, we just reference "Formula (A.5)."

@opoudjis you probably have gone through this but ideally we should document in the README how the references are being rendered.

In Directives Part 2, https://www.iso.org/sites/directives/2016/part2/index.xhtml different referential targets have a different way of rendering:

22.4 Referencing
Clauses and subclauses need not be specifically referred to in the text.
Use, for example, the following forms for references to clauses and subclauses:
• “in accordance with Clause 4”;
• “details as given in 4.1.1”;
• “the requirements given in B.2”;
• “the methods described in 5.3 provide further information on...”.

23.4 Referencing
The purpose of a list should be made clear by its context. For example, an introductory proposition or a subclause title can serve to introduce the list. Lists need not be specifically referred to in the text.
If cross-references to list items are necessary, a numbered list shall be used. Within a subdivision, each list item in a numbered list shall have a unique identifier. Numbering restarts at each new clause or subclause.
Use, for example, the following forms for references to lists:
• “as specified in 3.1 b)”;
• “the requirements given in B.2 c)”.

24.4 Referencing
Notes need not be specifically referred to in the text.
If notes are referred to, use for example, the following forms for references:
• “an explanation is provided in 7.1, Note 2”;
• “see 8.6, Note 3”.

25.4 Referencing
Examples need not be specifically referred to in the text.
If examples are referred to, use for example, the following forms for references:
• “see 6.6.3, Example 5”;
• “Clause 4, Example 2 lists …”.

27.4 Referencing
If a formula is numbered, it should be referred to in the text. The purpose of a formula should be made clear by its context, for example, with an introductory proposition.
Use, for example, the following forms for references to mathematical formulae:
• “see 10.1, Formula (3)”;
• “see A.2, Formula (A.5)”.

28.4 Referencing
Each figure shall be explicitly referred to within the text.
Use, for example, the following forms for references to figures and subfigures:
• “Figure 3 illustrates…”;
• “See Figure 6 b)”.

29.4 Referencing
Each table shall be explicitly referred to within the text.
Use, for example, the following forms for references to tables:
• “Table 3 lists…”;
• “See Table B.1”.

ISODoc:-Top-Level Item 1.

Is this correct?

Outside of termnotes, all notes shall be numbered, but only if there is more than one in their container.

All notes are referenced by their container and Note number.

ISO 690.

Currently we use raw CSS for Word HTML and normal HTML.

It would be much cleaner to use SCSS (used in asciidoctor-reveal.js) or SASS to generate CSS as they support inheritance and inclusion.

1. Examples are numbered sequentially within a container, but not if they are the only example in their container.

2. Examples are referenced by container and example number.

3. Examples are rendered as boxed text.

23.4 Referencing
The purpose of a list should be made clear by its context. For example, an introductory proposition or a subclause title can serve to introduce the list. Lists need not be specifically referred to in the text.
If cross-references to list items are necessary, a numbered list shall be used. Within a subdivision, each list item in a numbered list shall have a unique identifier. Numbering restarts at each new clause or subclause.
Use, for example, the following forms for references to lists:
• “as specified in 3.1 b)”;
• “the requirements given in B.2 c)”.

If back quote is in the document, then back quote cannot be used as ASCII math delimiter

Current rendering mailto:[email protected]@vacheequipment.fic

The term being defined in asciidoctor-iso (and gb) does not appear in the title of the section: the term number is on its own as a title, and the term being defined is a separate boldface para, indented to line up with body text.

Currently a lot of XML processing happens in the asciidoctor-iso gem.

However, this gem (isodoc) should be used as the central place to create and edit isodoc files.

• The asciidoctor-iso gem should use the isodoc gem to build the ISOXML.
• The isoxml-html gem should use the isodoc gem to read into the ISOXML, and transform it into HTML.

For example, code like (asciidoctor/iso/blocks.rb):

      def stem(node)
        # NOTE: html escaping is performed by Nokogiri
        stem_content = node.lines.join("\n")

        noko do |xml|
          xml.formula **id_attr(node) do |s|
            s.stem stem_content, **{ type: "AsciiMath" }
            style(node, stem_content)
          end
        end
      end

should be:

      def stem(node, isodoc_current_node)
        # NOTE: html escaping is performed by Nokogiri
        stem_content = node.lines.join("\n")

        isodoc_current_node.stem(
          content: stem_content,
          type: "AsciiMath"
        )
      end

• isodoc title is now isolocalizedtitle (gbdoc title is inherited)
• bibliography now takes multiple dates in one array
• textelement is now a localizedstring

Move table footnotes inside of table, and do not treat them as footnotes but as notes within table, with letter references rather than numbers. HTML2Doc needs to ignore these footnotes.

Figure footnotes will do the same.

Just as is already being done for Word

Have Generic HTML generation as one class, and have Word HTML class inherit from it. Will undo a lot of the transformation functionality in postprocessing.rb and html.rb .

In the process, strip out any Word-specific HTML from the Generic HTML branch.