Hello (again),
I am trying to import a jpg-image but this fails. Instead a 'broken image'-image is displayed. This happens when dragging&dropping from explorer, but also when using the import-menuentry.
I am using Bob's latest build.
best Steffen
Hello,
some additional findings:
I am using Bob's latest build.
I've switched back to a version from October 18th. Here import by drag&drop first did not work either. Then I tried to import an image from my root-dir. It worked. I think it is the empty spaces in the filename. I checked with bob's latest build. It still does not work. It still gives the 'broken image'-image.
best Steffen
Steffen Glückselig wrote:
Hello,
some additional findings:
I am using Bob's latest build.
I've switched back to a version from October 18th. Here import by drag&drop first did not work either. Then I tried to import an image from my root-dir. It worked. I think it is the empty spaces in the filename. I checked with bob's latest build. It still does not work. It still gives the 'broken image'-image.
Compare drag-n-drop from different locations to importing via the menu from those same locations. It could be a problem in the paths themselves, or a problem in drag-n-drop differing.
There are general path naming issues I'm tracking down (I mentioned in my other mail), then there are also file IO issues that were being dealt with and may have caused those broken images.
Jon, Just tried putting the � in a folder name and importing an image from it, file import gives the following:
** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xfctest\pagina005.gif] ** Message: unable to open file ** Message: D file pre is [ 43 3a 5c 73 76 67 5c 73 72 63 5f 69 6e 6b 73 63 61 70 65 5c 30 2e 34 30 5c 79 65 74 61 67 61 69 6e 5c 69 6e 6b 73 63 61 70 65 5c 6 9 6e 6b 73 63 61 70 65 5c 69 6d 67 fc 74 65 73 74 5c 70 61 67 69 6e 61 30 30 35 2e 67 69 66] ** Message: D file post is [ 43 3a 5c 73 76 67 5c 73 72 63 5f 69 6e 6b 73 63 61 70 65 5c 30 2e 34 30 5c 79 65 74 61 67 61 69 6e 5c 69 6e 6b 73 63 61 70 65 5c 6 9 6e 6b 73 63 61 70 65 5c 69 6d 67 c3 bc 74 65 73 74 5c 70 61 67 69 6e 61 30 30 35 2e 67 69 66] ** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xc3\xbctest\pagina005.gif] ** Message: png? No ** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xfctest\pagina005.gif] ** Message: unable to open file ** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xfctest\pagina005.gif] ** Message: unable to open file ** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xfctest\pagina005.gif] ** Message: unable to open file ** Message: fopen call pixbuf_new_from_file for [C:\svg\src_inkscape\0.40\ye tagain\inkscape\inkscape\img\xfctest\pagina005.gif] ** Message: unable to open file
(I've still got the defs for the debug output in there) path should be C:\svg\src_inkscape\0.40\yetagain\inkscape\inkscape\img�test\
drag and drop just gives
(inkscape.exe:3428): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 (gdk_ pixbuf_new_from_file): assertion `filename != NULL' failed
cheers
John
--- "Jon A. Cruz" <jon@...204...> wrote:
Steffen Gl�ckselig wrote:
Hello,
some additional findings:
I am using Bob's latest build.
I've switched back to a version from October 18th. Here import by drag&drop first did not work either. Then I tried to import an
image
from my root-dir. It worked. I think it is the empty spaces in the
filename. I checked with bob's latest build. It still does not work. It still
gives the 'broken image'-image.
Compare drag-n-drop from different locations to importing via the menu from those same locations. It could be a problem in the paths themselves, or a problem in drag-n-drop differing.
There are general path naming issues I'm tracking down (I mentioned in my other mail), then there are also file IO issues that were being dealt with and may have caused those broken images.
__________________________________ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com
Hi there, We switched some of the file/image loading code to try and eliminate some issues the code had with not utf chars in the last couple of days, it resulted in a day or so of complete breakage of bitmap images on windows (coding fixes for a platform you dont have access to cant be easy - but he managed it, cheers Jon) The current CVS is working again, try dling the latest off the inkscape site. http://www.inkscape.org/win32-snap/ the 30/10/04 build should be working. Let us know if the bug persists, and check the thing with spaces, as that could be another issue. (also if your still having trouble can you include the full path of the images your trying to load, as it could be to do with international chars)
cheers
John
--- Steffen Gl�ckselig <glueckselig@...278...> wrote:
Hello,
some additional findings:
I am using Bob's latest build.
I've switched back to a version from October 18th. Here import by drag&drop first did not work either. Then I tried to import an image from my root-dir. It worked. I think it is the empty spaces in the filename. I checked with bob's latest build. It still does not work. It still gives the 'broken image'-image.
best Steffen
This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
__________________________________ Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. http://messenger.yahoo.com
Hello,
The current CVS is working again, try dling the latest off the inkscape site. http://www.inkscape.org/win32-snap/ the 30/10/04 build should be working.
There's no such build on that site. I've downloaded the latest from Daniel's, though.
My experiences with that version (October 31st): *Problems with umlauts 'ü' in filename. *No Problem with white spaces. *The UTF8-error still persists.
best regards Steffen
participants (3)
-
John Cliff -
Jon A. Cruz -
Steffen Glückselig