| 2009-11-27 10:56:37 |
h1repp |
description |
With Inkscape 0.47-3 on a german Windows XP SP3 I found: InkVIEW is unable to open files with non-ascii characters (like umlauts) in the filename whereas InkSCAPE opens and writes them without problem, so this is an Inkview-only or Inkview-still bug. Files in question validate successfully as SVG 1.1 on validator.w3.org. Inkview _can_ open those files when renamed to a pure ascii name.
gdb reports only program termination with return value 01. Sysinternals Procmon shows one QueryDirectory with the filename as filter successfully returning the filename, and then, after some fiddling with glib20.mo, an orderly program shutdown. It seems that Inkview treats the QueryDirectory result as 'no matching file found' when in fact it returns the correct filename containing non-ascii characters.
I remember there where similar issues with former versions of Inkscape on non-utf8 filesystems, but this one is on utf-8. |
With Inkscape 0.47-3 on a german Windows XP SP3 I found: InkVIEW is unable to open files with non-ascii characters (like umlauts) in the filename whereas InkSCAPE opens and writes them without problem, so this is an Inkview-only or Inkview-still bug. Files in question validate successfully as SVG 1.1 on validator.w3.org. Inkview _can_ open those files when renamed to a pure ascii name.
gdb reports only program termination with return value 01. Sysinternals Procmon shows one QueryDirectory with the filename as filter successfully returning the filename, and then, after some fiddling with glib20.mo, an orderly program shutdown. It seems that Inkview treats the QueryDirectory result as 'no matching file found' when in fact it returns the correct filename containing non-ascii characters.
I remember there were similar issues with former versions of Inkscape on non-utf-8 filesystems, but this one is on utf-8.
|
|
