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] Updated: (OFFICE-3032) Public Comment:Feedback for OpenDocument-v1.2

     [ http://tools.oasis-open.org/issues/browse/OFFICE-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Brauer updated OFFICE-3032:

1. Remove Note 1 from section 3.11

2. Adapt note on 3.18 to "Note: The elements that have specific rules for the handling of white space characters are <text:p>, <text:h> and their child elements. 6.1.2"

No action for the other comments. See JIRA issue OFFICE-3032 for details.

I've added the two changes as resolution.

Patrick, can you check the use of "with" vs. "within" (first comment). The change actually would have to take place in the XSLT style sheets, but I need you opinion on this.

I will further check if we can provide a better example image for 19.626.

> Public Comment: Feedback for OpenDocument-v1.2
> ----------------------------------------------
>                 Key: OFFICE-3032
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3032
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General, Part 1 (Schema), Public Review
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Robert Weir 
>            Assignee: Michael Brauer
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
> Copied from office-comment list
> Original author: Aaron Digulla <digulla@hepe.com> 
> Original date: 16 Jul 2010 13:18:12 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201007/msg00003.html
> Text of the comment:
> 1. There are a lot of entries that read "The <xyz> element is usable  
> *with* the following elements: ..." Shouldn't that be *within*.
> That said, I would prefer a table here which lists the parent/child  
> elements in a more readable way.
> Maybe you should even move this information into an appendix where it  
> can be found in compact form instead of spreading it throughout the  
> text and interrupting the flow of read.
> 2. "To represent a text cursor position within a document, a  
> processing instruction with PITarget opendocument (see ยง2.6 of  
> [XML1.0]) should be used. The name of the cursor position processing  
> instruction, cursor-position, shall follow the PITarget opendocument."  
> ... Uh what? How about:
> "To represent a text cursor position within a document, use the  
> processing instruction '<?opendocument cursor-position?>' (see  
> PITarget). The processing instruction may have arbitrary  
> implementation specific attributes."
> 3. "A common view setting for is the position of the text cursor when  
> saving the document." Odd sentence. How about: "Text views will  
> usually use this to remember the text cursor position when saving the  
> document."
> 4. "Styles for a document are defined in container elements according  
> to their type, common, automatic and master." ... 'common' what?
> 5. "3.18White Space Processing and EOL Handling" This section says  
> that some elements have special rules for handling of WS characters.  
> Then there is a note about text:p and text:h. Is this an example? Or  
> are these all elements with special WS rules? For the reader, it would  
> be better to have a list of all elements (with links) which have  
> special WS rules.
> 6. "6.1.4<text:tab>" confuses me. Why would I want to use this element  
> instead of a TAB character?
> 7. "19.15.1<chart:chart>, <chart:series>" Please split this extremely  
> long text into sections where you explain each chart type individually.
> 8. "19.626table:embedded-number-behavior" The example image is pretty  
> cluttered. I suggest to move the string/text annotations above the  
> example string and the numeric annotations below plus small colored  
> boxes around the parts of the example string to make it easier to  
> digest.

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]