I've confirmed this bug on Mac OS X 10.9.5 with Inkscape versions 0.48.5_6 and 0.91.99.13797 via MacPorts as well as 0.48.5, 0.91 Pre3, and 0.91+devel-r13822 via the .dmg's distributed at inkscape.org.
/Cloud/OSS/go/src/github.com/agl/pond/icons/pond-icon-blob-1.svg:141: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xFF 0x22 0x20 0x69 id="metadata4"><?xpacket begin="?" id="W5M0MpCehiHzreSzNTczkc9d"?><x:xmpmet All the relevant files are in this pull request if you want to see them : https://github.com/agl/pond/pull/153 I've reproduced the errors both when saving as an Inkscape .svg file and when saving as a plain .svg file. Also, originally the .svg file was created with Adobe Illustrator, but while Adobe's .svg file is readable from Mac OS X's Preview, none of the Inkscape .svg files are. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/499257 Title: saves svg file, that it can't read afterwards Status in Inkscape: A Vector Drawing Tool: Triaged Status in inkscape package in Ubuntu: Triaged Bug description: Binary package hint: inkscape $ lsb_release -rd Description: Ubuntu 9.10 Release: 9.10 $ dpkg -s inkscape | grep Version Version: 0.47~pre4-0ubuntu1 Loading attached file in inkscape results in: $ inkscape Rubin-mit-Schnee.svg Rubin-mit-Schnee.svg:2588: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xFF 0x22 0x20 0x69 id="metadata3"><?xpacket begin="�" id="W5M0MpCehiHzreSzNTczkc9d"?> However, that file was written by inkscape itself and not modified manually by myself after. I think the problem was caused by myself adding metadata to the file (from within inkscape) that contain non-ascii characters, since that was more or less the only thing I remember I did after loading the file in inkscape (when it still worked) and before saving it. After saving it inkscape was not able to read it any more. *t PS: after replacing the character displayed above in the error message with a random ascii character, inkscape was able to load the image with no problem. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/499257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp