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

            Bug ID: 66085
           Summary: org.openxmlformats.schemas.wordprocessingml.x2006.main
                    .STHint missing ENUM value
           Product: POI
           Version: unspecified
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XWPF
          Assignee: dev@poi.apache.org
          Reporter: chrisl...@hotmail.com
  Target Milestone: ---

Created attachment 38302
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=38302&action=edit
Failing Word Doc

Hi,

I'm not sure this is strictly the correct place to log this, but I don't know
where else to go.

We are currently attempting an upgrade of POI from v4.1.2 to v5.2.2. In this we
note in your release notes that this includes an update in conformance to the
ECMA-376 fifth edition spec. With the updated libraries, running the attached
Word Document we received an unexpected error:

string value 'cs' is not a valid enumeration value for ST_Hint in namespace
http://schemas.openxmlformats.org/wordprocessingml/2006/main.
  org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: string value
'cs' is not a valid enumeration value for ST_Hint in namespace
http://schemas.openxmlformats.org/wordprocessingml/2006/main

Having investigated this, I see that it's not really a problem with POI per se.
According to the PDF of the spec:
  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.

However, in the actual XSD used to generate the XMLBeans classes:
  ECMA-376-Fifth-Edition-Part-4-Transitional-Migration-Features.zip
    - OfficeOpenXML-XMLSchema-Transitional.zip
      - wml.xsd
        Line 1789 of the XSD there is no STHint.CS ENUM and thus no ENUM in the
code generated by XMLBeans.

So I can see that the POI classes are simply conforming to the XSD via XMLBeans
generation. For now we can work around this fact, but is this something you
guys are able to modify/fix as part of your processes?

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Reply via email to