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-1816) NEEDS-DISCUSSION:ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER JP2-25

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

Dennis Hamilton updated OFFICE-1816:

              Summary: NEEDS-DISCUSSION: ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER  JP2-25  (was: ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER 	JP2-25)
        Fix Version/s: ODF 1.0 Errata CD 5
                           (was: ODF 1.0 Errata 02)
    Affects Version/s: ODF 1.0
                       ODF 1.0 Errata 02

1. For example, 15.9 contains the only uses of the phrase "escape line" and nowhere in ODF 1.0 is the term defined or is there any citattion to where there might be such a definition.

2. I am not very confident about "glue point" either, and section 9.2.19 is not all that clear about what is going on, especially when to expect one of the 4 standard glue points, how many of them there are for a gtiven shape (and where they might be) and whether or not user-defined ones have to be numbered "in rotation" (see ID sub-heading) although that seems inappropriate.

3. However, I suspect one might gain some insight into what "escape line" means if we interpret it to mean "connector-line escape" from the outline of the shape.  That is a lot of reading between the lines though.

4. I think this is too harsh and itself too vague: "Rejected, the correction of this defect would exceed the limits of OASIS errata and therefore it will be addressed in ODF 1.2. The behavior in question is implementation dependent for purposes of ISO 26300."   There is a lot of behavior that might be in question here.  If we are not prepared to identify the implementation-dependent behaviors, I don't think we should wave that flag here.

5. recommend  that there be no action on this defect item, but that the explanation be more like "No resolution.  Further consideration is required.   Resolution  is deferred to a future revision of the specification."  

> ---------------------------------------------------------------------------
>                 Key: OFFICE-1816
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1816
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.0, ODF 1.0 (second edition), ODF 1.0 Errata 02
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.0 Errata CD 5
> Transcribed from http://www.itscj.ipsj.or.jp/sc34/open/1078.htm
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
> QUALIFIER 	omission
> REFERENCES IN DOCUMENT 	Clauses 9.2.9 and 15.19
> NATURE OF DEFECT 	These subclauses are understandable only if the reader uses OpenOffice and examine the output.
> SOLUTION PROPOSED BY THE SUBMITTER 	Add diagrams, and explain start positions, start shapes, start gule points, and so forth.

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]