Bug 33998 - Unique XML Element IDs
Summary: Unique XML Element IDs
Status: RESOLVED MOVED
Alias: None
Product: cairo
Classification: Unclassified
Component: svg backend (show other bugs)
Version: 1.10.2
Hardware: All All
: medium enhancement
Assignee: Emmanuel Pacaud
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 11:45 UTC by fedora.dm0
Modified: 2018-08-25 13:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Adds a random string to XML element IDs (12.37 KB, application/octet-stream)
2011-02-07 11:45 UTC, fedora.dm0
Details

Description fedora.dm0 2011-02-07 11:45:28 UTC
Created attachment 43037 [details]
Adds a random string to XML element IDs

This is a feature request to add a random string to the IDs used in SVG output.  The goal is to be able to use several images in the same parent XML document without having conflicting element IDs.  My current use-case is having multiple plots etc. generated by Cairo/R included throughout mathematical documents written in XML-based languages.

Attached is a quick patch I made that is little more than tweaked pattern replacement, but has the intended effect to illustrate my request.  (It most likely needs to be retouched by someone familiar with the source.)
Comment 1 Emmanuel Pacaud 2011-02-14 01:30:40 UTC
I don't think it's a good idea to have this feature in cairo itself, as it would make the uncompressed file output bigger that what it is currently. It's the tool that merges several SVG files into one that should handle the possibility of conflicting ids.
Comment 2 GitLab Migration User 2018-08-25 13:59:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/304.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.