ST_HINT is missing "cs" enumeration inside RNC/XSD schema files

Chris Lake 21 Reputation points
2022-05-25T01:33:09.76+00:00

Hi,

Whilst updating the our software to use the Java library "Apache POI", we came across an issue whereby the documentation for the ECMA-376 5th Edition standard specification differs from the WML.RNC and WML.XSD files contained in Part 1 "Strict" zips and Part 4 "Transitional" zips.

According to the spec, the "ST_HINT" type should have an enumeration for "cs" alongside "default" and "eastAsia", but it is missing:

  • Ecma Office Open XML Part 1 - Fundamentals And Markup Language Reference.pdf
    • 17.18.41 ST_Hint (Font Type Hint) p.1396 (page 1406)
      cs (Complex Script Font) is mentioned as a possible value
    • A.1 WordprocessingML p.3841 (page 3851)
      Line 1715 of the XSD shows 'cs' as a possible value.
  • ECMA-376-Fifth-Edition-Part-1-Fundamentals-And-Markup-Language-Reference.zip
    • OfficeOpenXML-XMLSchema-Strict.zip
    • wml.xsd
      Line 1712 of the XSD there is no ST_Hint "CS" enumeration and thus no Java ENUM in the code generated for the POI library.
  • ECMA-376-Fifth-Edition-Part-4-Transitional-Migration-Features.zip
    • OfficeOpenXML-XMLSchema-Transitional.zip
    • wml.xsd
      Line 1789 of the XSD there is no ST_Hint "CS" enumeration and thus no Java ENUM in the code generated for the POI library.

This is causing exceptions to be raised inside the Apache POI library when attempting to read a Word document using the hint. I'm unsure of the correct place to raise this issue, though the Apache bugs team pointed me here. Is this the place to report the issue, and can the RNC/XSD files be fixed?

For reference: https://bz.apache.org/bugzilla/show_bug.cgi?id=66085

Office Open Specifications
Office Open Specifications
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Open Specifications: Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
119 questions
{count} votes

Accepted answer
  1. Tom Jebo 1,906 Reputation points Microsoft Employee
    2022-06-01T23:36:28.557+00:00

    @Chris Lake ,

    I did confirm that this is likely going to need a bug (defect report) filed against the standard (ECMA and ISO both).
    You can look at the Annex A.(normative) Schemas – W3C XML Schema section in the standard to see the correct enums for ST_HINT.

    I will file this bug. If you need anything else, just post here. Otherwise, I'll consider this issue resolved.

    Tom

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Sreekanth Nadendla 321 Reputation points Microsoft Employee
    2022-05-25T18:46:06.207+00:00

    Hello ChrisLake-4489, thank you for your question related to Microsoft Open Specifications. One of the team members will review your question and assist you further.

    Regards,
    Sreekanth Nadendla
    Microsoft Windows Open Specifications

    0 comments No comments

  2. PJ Fanning 1 Reputation point
    2022-06-15T19:03:32.703+00:00

    Any progress on this?