[ http://tools.oasis-open.org/issues/browse/OFFICE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21206#action_21206 ]
Patrick Durusau commented on OFFICE-2839:
-----------------------------------------
Let me think about your wording.
Tying Booleans to fallbacks is just bad design. What happens when the Boolean is true and the other attribute has a value? Oh, we don't say. A lot. Really an ODF-Next issue at this point.
For future reference: true or string are the attribute values. Supports the function or is given a value (which it may or may not support).
Result is one (1) attribute, no loss of function and less clutter in both the schema and the standard.
> 20.393 style:writing-mode-automatic - misplaced text? see description
> ---------------------------------------------------------------------
>
> Key: OFFICE-2839
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2839
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Text
> Affects Versions: ODF 1.2 CD 05
> Reporter: Patrick Durusau
> Assignee: Patrick Durusau
> Priority: Minor
> Fix For: ODF 1.2 CD 06
>
>
> Reads in part: "The actual value for the writing-mode should be contained in a style:writing-mode attribute, so that consumers that do not support an automatic writing mode calculation or use a different algorithm always know the actual value."
> Shouldn't this (with some re-writing) appear under 20.392.1, the general section for style:writing-mode?
> Or to put it differently, why does the attribute value become a "should" under another attribute?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
