Minor and Typographical Corrections

[mbeckerle]

Add items of this kind as comments to this issue.

[mbeckerle]

HTML spec has an issue with the grammar for textNumberPattern in section ...

The production for prefix doesn't have a line-ending before it.

This does not show in the PDF version of the spec, only the HTML version. Furthermore, if you view the HTML in "reading mode" the problem also evaporates.

See screenshot below:

[mbeckerle]

"usesits" typo in footnote page 10 of GFD 240 pdf.

[mbeckerle]

This string appears in the description of textNumberRep: '}JKLMNOPQR' or '^£¥·©§¶¼½¾ '
There are two spaces after the word "or", and there should be no space after the ¾ character before the quotation mark.

[mbeckerle]

String "idivmod" in section 17.2 should be just "mod"

[mbeckerle]

Tables 46 and 47 in Sections 14.2.1 and 14.2.1 break badly across page boundaries in the ISO published version, perhaps in the OGF one but I didn't check that.
Table 48 is another that we need to make sure does not break across a page boundary.

[mbeckerle]

Section 9.1 paragraph 1 is broken. This may be a more major issue than just a "typographical" error.

Here's an image of the PDF for this paragraph:

You can see that after the word "Checking" it somehow got corrupted.

I believe the section should have this text:

The DFDL logical parser is a recursive-descent parser[10] having guided, but potentially unbounded look ahead. A DFDL parser reads a specification (the DFDL schema) and it recursively walks down and up the schema as it processes the data. This is done in a manner consistent with the scoping of properties and variables described in Section 8 Property Scoping and DFDL Schema Checking.

The unbounded look ahead means that there are situations where the parser MUST speculatively attempt to parse data where the occurrence of a Processing Error causes the parser to suppress the error, back out and make another attempt.
...

A period was added after "Checking", and the spurious content:

Property Scoping
Property Scoping Rules

removed.

Note also that the entire phrase "Section 8 Property Scoping and DFDL Schema Checking" is supposed to be a section cross reference.

[mbeckerle]

In the sections on property precedence there are two uses of packedDecimalSignCodes. They both should be binaryPackedSignCodes.

[mbeckerle]

The language in the definition for dfdl:decimalSigned property should use the terms "signed number" and "unsigned number" to be consistent with other sections it references.