Content deleted Content added
m redirect bypass from ISO/IEC JTC1 to ISO/IEC JTC 1 using popups |
m →Compatibility settings: italic |
||
Line 270:
These settings (including element with names such as ''autoSpaceLikeWord95'', ''footnoteLayoutLikeWW8'', ''lineWrapLikeWord6'', ''mwSmallCaps'', ''shapeLayoutLikeWW8'', ''suppressTopSpacingWP'', ''truncateFontHeightsLikeWP6'', ''uiCompat97To2003'', ''useWord2002TableStyleRules'', ''useWord97LineBreakRules'', ''wpJustification'' and ''wpSpaceWidth'') were the focus of some controversy during the standardisation of DIS 29500.<ref>{{ cite web | url=http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C9 | title=ODF/OOXML technical white paper — A white paper based on a technical comparison between the ODF and OOXML formats | publisher=Free Software Magazine}}</ref> As a result, new text was added to ISO/IEC 29500 to document them.<ref>{{ cite web | url = http://www.ecma-international.org/publications/standards/Ecma-376.htm | title = ECMA-376 2nd edition Part 4 (paragraph 9.7.3) | publisher = Ecma-international.org | access-date = 2009-09-16 }}</ref>
An article in ''[[Free Software Magazine]]'' has criticized the markup used for these settings. Office Open XML uses distinctly named elements for each compatibility setting, each of which is declared in the schema. The repertoire of settings is thus limited — for new compatibility settings to be added, new elements may need to be declared, "potentially creating thousands of them, each having nothing to do with interoperability".<ref>{{ cite web | quote="... OOXML chose this route. Rather than create an application-definable configuration tag there is a unique tag for each setting ... Currently, the only application's unique settings that are catered for are the applications that the standard's authors have decided to include, ... For other applications to be added, further tag names would need to be defined in the specification, potentially creating thousands of them, each having nothing to do with interoperability ..". | url=http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C7 | title=ODF/OOXML technical white paper — A white paper based on a technical comparison between the ODF and OOXML formats | publisher=Free Software Magazine }}</ref>
== Extensibility ==
| |||