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-703) Public Comment:OpenDocument 1.2v7-02: 1.5 White Space Processing



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

Dennis Hamilton commented on OFFICE-703:
----------------------------------------

Andreas: I think the cases arise because CR followed by NL (LF) is treated as if it is a single NL as is a CR not paired with an immediately-following NL.  (Actually an unpaired NL followed immediately by a CR should receive the same treatment but I don't think collapsing of NL and white space has ever been specified that way for XML.)(

I also think that EOL is not an XML or Unicode concept with regard to the use of these characters and it would be good not to introduce a variant notion.  These are line breaks, they may end up just collapsed to white space, and they may be trimmed from the beginning and end of content, so we need to get on top of that and be precise about how this interacts with XML rules, and why it is thought to be needed.  Also, there is the interesting question whether we are talking about something that applies after automatic XML processing happens, now that I think about it.

[Note 1: This needs to be checked against [XML10] and the use of xml:space to see whether this section is even needed or if it is only necessary to reaffirm an XML normative requirement or affirm an XML-specified preference ("should").]

[Note 2: I think we should use Unicode code-point notation here as elsewhere, simply because XML encodings are referenced against Unicode, whatever the actual encoding happens to be.  Need to look at that too, with regard to other encodings that have characters with no Unicode counterpart and vice versa.]

> Public Comment: OpenDocument 1.2v7-02: 1.5 White Space Processing
> -----------------------------------------------------------------
>
>                 Key: OFFICE-703
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-703
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Dennis Hamilton
>            Priority: Blocker
>
> Copied from office-comment list
> Original author: "Dennis E. Hamilton" <dennis.hamilton@acm.org> 
> Original date: 18 May 2008 07:21:41 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200805/msg00030.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]