imported images: no relative paths/wrong absolute path

Bug #166886 reported by Oschnabel
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

System: Windows2000 SP4
Inkscape: version 0.41 and version 0.42

During the import of images the path to the image will
be stored in SVG as absolute path in the Windows
notation ("F:\pic.png").
The storage of an relative path is not possible.
If the stored SVG is viewed in a Mozilla browser (like
Firefox), the image does not appear, because these
browsers understand only the correct notation
Hope, you can fix it.

There is a workaround for relative paths. After the
import of an image import it again on top of the first
one. The path of the first image will change to a
relative path "pic.png", while the second one stays in
absolute path notation. Then, the second picture can be
deleted. But this workaround is very time-consuming.

Thanks for fixing

Revision history for this message
Aludwin (aludwin) wrote :

Hi, I'd like to make some additional comments to the above:

   1. This bug is a big barrier to moving files around. I
moved all my files from one computer with one path structure
to another computer with a different path structure and had
all kinds of grief. Rather than using the file:// format, I
would rather always use the relative path by default.

   2. This bug also affects the "Export as bitmap" command -
the last name you typed includes the full path. Again, when
I moved my files to another computer and tried to export, I
had to go browse to the correct directory again.

I could probably help fix this with a bit of guidance (I
haven't worked on the inkscape code yet) - please contact me
 if interested.

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: NO

I think I finally fixed this. Now an image gets a relative xlink:href as
soon as it's imported, not after a save as before. The only exception is
when you import an image into a document which was never saved, in which
case we must have absolute hrefs because the base directory of the document
is not known yet.

Revision history for this message
su_v (suv-lp) wrote :

see also the recent discussions in bug #172162 “image links management”:
<> and its related blueprints.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.