OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-1211) Public Comment: Re:[office-comment] White-Space Processing (ODF all versions)

    [ http://tools.oasis-open.org/issues/browse/OFFICE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19395#action_19395 ] 

Dennis Hamilton commented on OFFICE-1211:


For this issue and the just-proposed refinement, I did not consider (1) the case of foreign element and externally-defined element flattening, (2) any appearance of an xml:space attribute, and (3) the fact that non-validatoring XML processors cannot determine whether an element is limited to element content.

For (3) I presume that, whether or not the processor can tell, the ODF 1.2 consumer can make the determination for those elements that are defined in the ODF 1.2 specification.  

For (2) I presume that xml:space is not allowed in any of the elements defined in the ODF 1.2 specification.  Whether foreign elements that are flattened might have xml:space conditions applicable to them is probably a bad idea and xml:space should probably be prohibited in foreign elements that would be subject to flattening.

For (1) I think we only need to address this for foreign elements that are subject to flattening (so their character data occurs under a <textp:p> or <text:h> provision.  For elements from other specifications, such as <math:math> and anything else, I am not sure that there is anything we can say without looking more closely at such specifications for any profiling that might be required to blend under an ODF element. 

NOTE that I am assuming that an OpenDocument Consumer has to deal with white-space provisions and treatment of element-only vs. mixed content even if the element is not supported, at least when the unsupported element appears under <text:p> or <text:h>.

> Public Comment: Re: [office-comment] White-Space Processing (ODF all versions)
> ------------------------------------------------------------------------------
>                 Key: OFFICE-1211
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1211
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Text
>    Affects Versions: ODF 1.0, ODF 1.1, ODF 1.2, ODF 1.2 Part 1 CD 4 
>         Environment: This issue now applies to ODF 1.2 CD04 section 21.2 and ODF 1.2 CD04-rev09 section 3.18.  There are DIFFERENT issues in ODF 1.0/1.1 and IS 26300:2006 section 1.6 where an incorrect statement is made.
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Trivial
>             Fix For: ODF 1.2 Part 1 CD 5, ODF 1.2 CD 05
> Copied from office-comment list
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp> 
> Original date: 18 Feb 2009 13:13:10 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200902/msg00012.html

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]