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-2771) 10.3.7 <draw:path>shape expression underspecified



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

Patrick Durusau commented on OFFICE-2771:
-----------------------------------------

And remove the following paragraph and note, which don't make sense without more context. Plus insert svg:d cross-reference.

> 10.3.7 <draw:path> shape expression underspecified
> --------------------------------------------------
>
>                 Key: OFFICE-2771
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2771
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Graphics, Part 1 (Schema)
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This applies to the <draw>path> description as it occurs in ODF 1.2 CD05 Part 1 section 10.3.7
>            Reporter: Dennis Hamilton
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2 CD 06
>
>
> There is no information here on where the path-segment actions are listed and how their start points, end points, control points, and other parameters are found for coordination in the precise specification of the desired path.
> One can presume that the svg:d attribute can have something to do with it. Since draw is bound to a namespace under the authority of the ODF specification, it would be helpful if there was more about how this element and its siblings actually provide the information for the desired shape to be characterized in an OpenDocument Document so that it can be drawn correctly by an OpenDocument Consumer. 
> I have no proposal for this.  I assume that there is at least one implementation that could be reverse-specified to provide the necessary interoperable specification of the shape feature.

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