Bug 25032 - Loading PDF file fails if its path contains non-ascii characters
Summary: Loading PDF file fails if its path contains non-ascii characters
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: glib frontend (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-11 06:38 UTC by Michael Schumacher
Modified: 2010-01-07 01:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Patch (1.57 KB, patch)
2009-11-11 07:10 UTC, Carlos Garcia Campos 		Details | Splinter Review
0001--glib-Use-PDFDoc-wchar_t-.-on-Windows.patch (1.42 KB, patch)
2009-12-31 10:40 UTC, Hib Eris 		Details | Splinter Review
Show Obsolete (1) View All

Description Michael Schumacher 2009-11-11 06:38:37 UTC 
This bug has been filed against GIMP, see https://bugzilla.gnome.org/show_bug.cgi?id=544560

While we are able to work around the problem in GIMP code, it would still nice to see this fixed in poppler. See https://bugzilla.gnome.org/show_bug.cgi?id=544560#c7 and https://bugzilla.gnome.org/show_bug.cgi?id=544560#c8 for hints about the reason and fix for this problem.
Comment 1 Carlos Garcia Campos 2009-11-11 07:10:12 UTC 
Created attachment 31112 [details] [review]
Patch

Would this patch fix the problem? I can't test it and I have no idea about win32, so it's like a shoot in the dark.
Comment 2 Hib Eris 2009-12-31 10:40:23 UTC 
Created attachment 32386 [details] [review]
0001--glib-Use-PDFDoc-wchar_t-.-on-Windows.patch

Hi Carlos,

Your patch did not work, because apparently you cannot use g_utf8_to_utf16() to convert to wchar_t when you are compiling with g++ (it only works with gcc).

I wrote this new patch based on yours, and it works for me with Evince.
Comment 3 Carlos Garcia Campos 2010-01-07 01:35:06 UTC 
Pushed to poppler-0.12 and master. Thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.