[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OFFICE-4046) bad QName pattern in manifest RNG
[ https://issues.oasis-open.org/browse/OFFICE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=77147#comment-77147 ] Michael Stahl edited comment on OFFICE-4046 at 6/9/20 10:48 AM: ---------------------------------------------------------------- this pattern is only used by one attribute "manifest:preferred-view-mode" as one of 4 alternatives: {noformat} <attribute name="manifest:preferred-view-mode"> <choice> <value>edit</value> <value>presentation-slide-show</value> <value>read-only</value> <ref name="namespacedToken"/> </choice> </attribute> {noformat} i'm not aware of an application that uses a value corresponding to this QName pattern. LibreOffice does not support it at all. PowerPoint 2013 supports the value "presentation-slide-show" which is separate from QName pattern. https://interoperability.blob.core.windows.net/files/MS-OODF3/%5bMS-OODF3%5d.pdf <quote> 2.1.1322 Part 3 Section 4.8.11, manifest:preferred-view-mode a. The standard defines the attribute manifest:preferred-view-mode, contained within the element <manifest:file-entry> This attribute is supported in PowerPoint 2013, PowerPoint 2016, and PowerPoint 2019. PowerPoint only supports reading a value of "presentation-slide-show" </quote> so i think we could get away with not fixing this in ODF 1.3. of course this depends on how much of a delay would be caused by fixing it... was (Author: michael.stahl): this pattern is only used by one attribute "manifest:preferred-view-mode" as one of 4 alternatives: {noformat} <attribute name="manifest:preferred-view-mode"> <choice> <value>edit</value> <value>presentation-slide-show</value> <value>read-only</value> <ref name="namespacedToken"/> </choice> </attribute> {noformat} i'm not aware of an application that uses a value corresponding to this QName pattern. LibreOffice does not support it at all. PowerPoint 2013 supports the value "presentation-slide-show" which is separate from QName pattern. https://interoperability.blob.core.windows.net/files/MS-OODF3/%5bMS-OODF3%5d.pdf 2.1.1322 Part 3 Section 4.8.11, manifest:preferred-view-mode a. The standard defines the attribute manifest:preferred-view-mode, contained within the element <manifest:file-entry> This attribute is supported in PowerPoint 2013, PowerPoint 2016, and PowerPoint 2019. PowerPoint only supports reading a value of "presentation-slide-show" so i think we could get away with not fixing this in ODF 1.3. of course this depends on how much of a delay would be caused by fixing it... > bad QName pattern in manifest RNG > --------------------------------- > > Key: OFFICE-4046 > URL: https://issues.oasis-open.org/browse/OFFICE-4046 > Project: OASIS Open Document Format for Office Applications (OpenDocument) TC > Issue Type: Bug > Components: Part 3 (Packages), Schema and Datatypes > Affects Versions: ODF v1.3 CSPRD01 > Environment: OpenDocument-manifest-schema-v1.3.rng in CSD01 > Reporter: Michael Stahl > Priority: Major > > somehow the repeats are missing in the QName pattern: > <rng:data type="QName"> > <rng:param name="pattern">[^:]:[^:]</rng:param> > </rng:data> -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]