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-1221) Public Comment: <text:s> element (etc) needs to be removed (ODF 1.2)

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

Dennis Hamilton commented on OFFICE-1221:

I can't make heads or tails of the text in the Proposal section, and considering that the proposal and the first comment from Patrick were entered only minutes apart confuses me even more.

If <text:space> gives the number of spaces, what happens if that differs from what is in the element?  Also, having an element with an implicit xml:space that disagrees with the global xml:space assumption is messy.  Finally, what does it then mean to have xml:space="collapse"?

For <text:tab> I am even more mystified by the situation.  First, the destination of the tab (that is where it stops) is detemined by tab information in the applicable styles.  Absent handling of that, the paragraph start-margin relative position to stop at is given as a hint.  How does any of that relate to having a sequence of HT in the content? And I ponder xml:space="collapse" here too.

If the idea is to use collapsing of white-space as the default for paragraph-content, then having explicit <text:s>, <text:tab>, and <text:linebreak> are just fine.
If the idea is to turn it off in places and use white-space characters, I suppose a <text:span> with xml:space="preserve" would do just fine.  (I would leave <text:s>, etc., in the specification, but identify them as deprecated perhaps.  But I still don't see the importance of this. 

PS: The two defined values for xml:space are "default" and "preserve", not "collapse" and "preserve".

PPS: It strikes me that Alex Brown's example concerning search might be confusing searching in the XML markup and searching in the document within a processor.  I assume human users want to search on what is seen, not what might be its persistent form in the XML representation of the document.

> Public Comment: <text:s> element (etc) needs to be removed (ODF 1.2)
> --------------------------------------------------------------------
>                 Key: OFFICE-1221
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1221
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Text
>    Affects Versions: ODF 1.0, ODF 1.0 (second edition), ODF 1.1, ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Blocker
>             Fix For: ODF 1.3
> Copied from office-comment list
> Original author: "Alex Brown" <alexb@griffinbrown.co.uk> 
> Original date: 20 Feb 2009 06:24:27 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200902/msg00022.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]