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-2707) ODF 1.2 Section 5.1No Longer Differentiates In-Line Text

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

Oliver-Rainer Wittmann commented on OFFICE-2707:

> In ODF 1.0/1.1, it is stated that "the children (including text) of paragraph element's make up the text content of any document. ... This should significantly ease transformations into other formats, since transformations may ignore any child elements of paragraph elements and only process their text content, and still obtain a faithful representation of text content."

The same is said in my opinion in ODF 1.2 - see chapter 6.1.1, first paragraph and the note at the end.

> Then, certain occurrences of paragraph elements are *ruled out* as contributing to that "in-line text".

The same we have in ODF 1.2, but instead of term "in-line text" we use term "character content".

> However, there were some omissions. For example, comments in tracked-change elements can contain paragraph elements, but this was not an identifed exception. Also, the tracked-change for a deletion can include paragraph elements, and they should not be included as if in-line text either.

Yes, I agree.
This is not in the intrinsic scope of this issue and I propose to track it in another issue.

> Also, there are other elements that include text content, such as <text:h> but that are overlooked in the ODF 1.0/1.1 statement.

Here, I disagree.
Term "paragraph elements" is used in ODF 1.1 which in 4.1 of ODF 1.1 are defined as the elements <text:h> and <text:p>.

> THE QUESTION: Do we still want to identify the only text content that need be extracted in a transformation to obtain "a faithful representation" the text content of a document.

I think so and in my opinion this is done in the same way as it is done in ODF 1.1. But in ODF 1.2 is reformulated and we are no longer using term "in-line text".

> ODF 1.2 Section 5.1 No Longer Differentiates In-Line Text
> ---------------------------------------------------------
>                 Key: OFFICE-2707
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2707
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema), Text
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This change applies to ODF 1.2 Part 1 CD04 through ODF 1.2 Part 1 CD04-rev09.  Previous versions distinguished in-line text in some manner and would have been subject to OFFICE-2706
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> There is no longer any differentiation between in-line text and text elswhere (that is, character data content of <text:h> and <text:p> elements), as is done in ODF 1.0/1.1/IS 26300 and, in modified form, ODF 1.2 Part 1 CD03 and earlier.  The informational indication of text which might be extracted as in-line text content is removed.  
> There is no argument that the differentiation between in-line text and text of other kinds is not that simple.  However, this change is not noted as something of material importance that differs between ODF 1.2 and earlier versions.

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]