[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-1697) Editor Note: Section18.184 fo:font-variant
[ http://tools.oasis-open.org/issues/browse/OFFICE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12550#action_12550 ]
Michael Brauer commented on OFFICE-1697:
----------------------------------------
Re1: As for now, we have a reference to XSL 1.0. So, this note can be removed.
Re 2: Yes, we omit inherit. We do so for all svg:* and fo:* formatting properties. My suggestion would be state this once in the introduction to chapter 19 (Formatting Attributes), but we could also state this for each property individually.
Re 3: fo:text-transform is not deprecated in XSL as far as I know, but I'm fine with removing the sentence ""For some implementations, the fo:font-variant and fo:text-transform attributes are mutually exclusive. If both attributes are used simultaneously and have different values than normal and none, then the result is undefined."
> Editor Note: Section 18.184 fo:font-variant
> --------------------------------------------
>
> Key: OFFICE-1697
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-1697
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Affects Versions: ODF 1.2
> Reporter: Robert Weir
> Assignee: Patrick Durusau
> Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 18.184 fo:font-variant
> Ed. Note In case we switch to XSL1.1, this must be 7.9.8.
> Ed. Note We only omit inherit.
> Ed. Note I would strike the following text because fo:text-transform was retained in CSS only for compatibility reasons and is not recommended for use in XSL. Suggest we deprecate fo:text-transform and say not to use it with fo:font-variant. If anyone does, that is clearly beyond the text of the standard. "For some implementations, the fo:font-variant and fo:text-transform attributes are mutually exclusive. If both attributes are used simultaneously and have different values than normal and none, then the result is undefined.
> Oliver says:
> "ad 1st editor's note: see my comment above - 18.407
> -- ad 2nd editor's note: not supported values from XSL should be
> explicitly named.
> -- ad 3rd editor's note: I have no solution. --> status "red"
> "
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]