[OASIS Issue Tracker] Commented: (OFFICE-3449) ODF 1.2 CD05 Part 15.5.3 Text Insertion Interoperable Definition Required

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Dennis Hamilton commented on OFFICE-3449:
-----------------------------------------

I mentioned on OFFICE-3448 that we might need to double-check what consequences there are for white-space rules.

I assume that a <text:change> marker is treated as if it is not there when the white space rules are applied in defining what space is included in the text that is rendered.  

On the other hand, there is probably something to be said about what happens where a selection boundary can occur in white space.  It would seem that it needs to be limited to treatment of the white space as included in the renderable text and cannot fall in the midst of whitespace that is normalized away.  That is, the renderable space is either within the selection or not, but not diviisable.  This should be clear in the definition of where selection edges can be in the midst of text, and when space can occur within an edge of the deleted material.

> ODF 1.2 CD05 Part 1 5.5.3 Text Insertion Interoperable Definition Required
> --------------------------------------------------------------------------
>
>                 Key: OFFICE-3449
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3449
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, Part 1 (Schema), Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
>
>
> This is related to ODF-3448 and related issues around tracked changes.
> There is actually no description of what constitutes an insertion and what it takes to reject one.  (Acceptance is easy).
> All we have said is that <text:change-start> and a matching <text:change-end> element bound the insertion and associate it with a <text:insertion> element.
> But the span of markup betweem a <text:change-start> to its corresponding <text:change-end> has all the characteristics of a selection.  And rejecting the insertion is an act of deletion.  Although that deletion is presumably not tracked, a consumer that supports insertion rejection, must know how to heal the removel of the inserted markup similar to ways that markup is healed around the scar of a tracked deletion.

-- 
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