ODF 1.1 Section 5.1.1 has dangling material meant to be deleted

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • ODF 1.1 Errata 01
    • Affects Version/s: ODF 1.1
    • Component/s: Text
    • None
    • Environment:

      This defect appears in all versions of the OASIS ODF 1.0 Standard.

    • Hide

      1. In Errata for ODF 1.1 to be used in the alignment of IS 26300 and ODF 1.1, create an erratum that deletes the dangling sentence fragment.

      2. During the FPDAM review for the ODF 1.1 amendment to IS 26300, add this erratum in comments on the FPDAM only if the FPDAM has not already corrected the situation.

      Show
      1. In Errata for ODF 1.1 to be used in the alignment of IS 26300 and ODF 1.1, create an erratum that deletes the dangling sentence fragment. 2. During the FPDAM review for the ODF 1.1 amendment to IS 26300, add this erratum in comments on the FPDAM only if the FPDAM has not already corrected the situation.
    • Hide

      Delete the last line in 5.1.1, just before the beginning of the "Space Character" subsection.

      Show
      Delete the last line in 5.1.1, just before the beginning of the "Space Character" subsection.

      In section 5.1.1 White-space Characters, just before the "Space Character" subheading, there is a single line containing a dangling sentence fragment

      ". in other words they are processed in the same way that [HTML4] processes them."

      This is text that was removed from the first paragraph of section 5.1.1 as part of expanding and clarifying the treatment of white-space characters. This fragment appears to have been left in the document by mistake. The clarified procedure does not appeal to [HTML4] and there is no such appeal in the further restatement that is now proposed for ODF 1.2.

            Assignee:
            Dennis Hamilton (Inactive)
            Reporter:
            Dennis Hamilton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: