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
I can also confirm that replacing the funky y aka ? in begin=? with a
y fixes the issue. In fact, Mac OS X still doesn't display one element
from that .svg file, but that's probably due to gradients or fuzziness.
At least now Chrome and FireFox display it properly, which they did not
before.
Apparently the changes in revision 12510
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/12510
allow current trunk at least to load affected files, despite warning about not
proper UTF-8.
Not closing the report - the corruption on save still occurs (tested on
Ubuntu 13.04 with
I can replicate with bpcleary's steps. My svg had a funky character that
looked like a Y. Replaced it with a Y and got on with things.
% inkscape --version
Inkscape 0.48.3.1 r9886 (Nov 1 2012)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Probably same problem here. I'm adding non-ascii attributes and opening
and saving Inkscape no longer can open it.
Inkscape 0.48.3.1 r9886, Linux arch 3.5.3-1-ARCH
** Attachment added: test.svg
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/499257/+attachment/3303770/+files/test.svg
Added a bug that duplicates this, so here is what I said there. I think
it's worth keeping the issue alive this way because I can't imagine most
users will open the SVG file in a text editor to fix the file after each
save.
--
Reproduction:
1. Open SVG file created using AI SVG export
The bug can be reproduced by creating a brand new svg file. This is not
related to imported files:
1) open Inkscape (0.48 in my case)
2) choose menu/File/Save as
3) input non ascii characters in title field such as Réseau
4) close Inkscape
5) Inkscape fails to open the file
6) Google Chrome fails
@Adrien - you talk about a Windows-specific issue which is tracked in
Bug #576126 “[win XP] cannot open file with non-ASCII chars in Save-as Title
field”.
(Only the native dialogs used in Inkscape on Windows have a 'Title' field)
--
You received this bug notification because you are a member
** Changed in: inkscape (Ubuntu)
Status: Confirmed = Triaged
** Changed in: inkscape
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/499257
Title:
saves svg
See also most recent duplicate
Bug #675170 “Exported Illustrator SVG with XMP results in xpacket encoding
problem in Inkscape”
https://bugs.launchpad.net/inkscape/+bug/675170
for a precise description and minimal test case (saving an empty
Illustrator CS3 document (SVG with XMP export) in
** Changed in: inkscape (Ubuntu)
Importance: Undecided = Low
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same problem when importing .PDF files in ubuntu inkscape 0.47 ; saving
to SVG ; reloading file. It worked with last year's version. Inkscape
seems to produce bad .xml output encoding, shall be trivial to fix...
maybe I should be upgrading now.
--
saves svg file, that it can't read afterwards
** Tags added: encoding
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I had the same problem with Inkscape 0.47 and Ubuntu 10.04.
- downloaded UbuntuLogo.svg from https://wiki.ubuntu.com/Artwork/Official
- installed Ubuntu logo by running sudo apt-get install ttf-ubuntu-title
- opened UbuntuLogo.svg with Inkscape 0.47
- removed the Ubuntu name and changed it to
** Changed in: inkscape (Ubuntu)
Status: Incomplete = Confirmed
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same issue affects me.
With Inkscape 0.46 under Win XP32 I remember it worked.
Now I'm using Inkscape 0.47 under Win 7 64 bit and can't reopen the modified
svgs
before manually removing the special character.
One of the affected (not yet by Inkscape changed) svg's is at:
** Also affects: inkscape
Importance: Undecided
Status: New
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for reporting this bug. I can confirm that the file will not
open (using the same Ubuntu Inkscape versions as you) and that
replacing the non-ascii character allows the file to be opened.
How did you edit the metadata? Did you directly enter it using the XML
editor in Inkscape or did
Confirmed on Windows XP, Inkscape 0.47, but I'm quite sure it's possible
to reproduce it on Ubuntu.
Steps:
1. Open Tomas' attached file with a text editor and replace encoding=UTF-8
with encoding=ISO-8859-1 .
2. Open the file with Inkscape.
3. Save it.
4. Open it again in a text editor: encoding
Alex Valavanis wrote:
How did you edit the metadata? Did you directly enter it using the XML editor
in Inkscape or did you use File-Document Metadata?
I used File-Document Metadata
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug
Bug #394472 (Wrong characters in imported PDF) is very close to this
one.
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
JazzyNico wrote:
I think that your original AI file was ISO encoded. That's the reason why
you've been
able to open and modify it once.
The issue is not that Inkscape doesn't open the file, but that it changes its
encoding.
Inkscape fails to open the file because in
?xpacket begin=ÿ
similar issue: bug #369861 in Inkscape: “Unable to open previously
imported pdf file”
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Rubin-mit-Schnee.svg
http://launchpadlibrarian.net/37029910/Rubin-mit-Schnee.svg
--
saves svg file, that it can't read afterwards
https://bugs.launchpad.net/bugs/499257
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
24 matches
Mail list logo
