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] (OFFICE-3995) Allow native SVG instead of <office:binary-data> for images


    [ https://issues.oasis-open.org/browse/OFFICE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=78401#comment-78401 ] 

Michael Stahl commented on OFFICE-3995:
---------------------------------------

[~regina.henschel], hmm that might be an option... but the problem is, we don't want to prescribe any specific version of SVG.

maybe something like this:

An <W3Csvg:svg> element contains an XML SVG markup fragment.
This [is/shall be/should be] a Conforming SVG Document Fragment as described in [SVG] https://www.w3.org/TR/SVG11/conform.html section G.2, or equivalent conformance clauses in other SVG Recommendations as published by W3C that use the same W3Csvg XML namespace.

> Allow native SVG instead of <office:binary-data> for images
> -----------------------------------------------------------
>
>                 Key: OFFICE-3995
>                 URL: https://issues.oasis-open.org/browse/OFFICE-3995
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: New Feature
>            Reporter: Regina Henschel
>            Priority: Major
>             Fix For: ODF 1.4
>
>         Attachments: Relax_19Nov20.diff
>
>
> Currently applications need to use the <office:binary-data> element to store an embedded SVG-image, in case they will save to a single XML file (flat ODF). That means that the SVG-image has to be encoded to BASE64. But an SVG-image is an XML-document and therefore it would be possible to use it directly, similar as done with MathML objects. The proposal has the changes that allow use of native SVG for images where now <office:binary-data> is needed.
> Remarks to the proposal:
> The namespace attribute in element <svg:svg> is needed, because OpenDocument producer bind the prefix "svg" to the namespace "urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0".
> The referenced document is a Candidate Recommendation. In case it will be released until the release of ODF 1.4, the URL has to be adapted.
> I'm not sure, whether the restriction "at most one" is correctly described by the schema.
> My proposal is not, to use <svg:svg> instead of the <draw:image>, because then the useful attributes draw:mime-type and draw:filter-name, and using <text:p> element for e.g. a caption would not be possible. And the proposal is not about adding an <svg:svg> element as drawing object on same level as e.g. <draw:rect>.
> Defining svg-svg follows the way it is done for math-math.
> I'm not sure, whether to force xlink in case of package format. That needs discussion.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]