Exports to relative paths should work properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Wishlist
|
Jon A. Cruz |
Bug Description
Being able to properly export SVGs to relative paths is a must when working
with SVG files in version controlled projects, because usually every user
involved in a project has the working copy in a different location.
Relative paths solve this problem, but currently they do not work as one
might expect. Relative paths need some point of reference, a base
directory. The natural assumption would be that this base directory is the
directory where the exported .svg file is located. But currently, on Win32,
this base directory is the current process working directory at the time
the export is made (usually the Inkscape installation directory). This
makes exporting with relative paths pretty much useless.
The base directory should be the one where the file being exported is
located. If a file is exported that was not saved at least once, the use of
a relative path should be disallowed.
Changed in inkscape: | |
assignee: | nobody → jon-joncruz |
Changed in inkscape: | |
status: | Confirmed → Triaged |
Changed in inkscape: | |
milestone: | none → 0.47 |
I confirm the need for a relative export path that is feature complete.