After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794535 - Cannot export to Cairo PDF with localized characters in file path
Cannot export to Cairo PDF with localized characters in file path
Status: RESOLVED OBSOLETE
Product: dia
Classification: Other
Component: win32
0.97.x
Other Windows
: Normal normal
: ---
Assigned To: Steffen Macke
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2018-03-20 16:09 UTC by rpr
Modified: 2019-03-20 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rpr 2018-03-20 16:09:16 UTC
On Dia 0.97.2 for Windows try the following:

1. Open/create a .dia file
2. File -> Export
3. Determine file type: Cairo Portable Document Format
4. Choose an export folder and file name
5. Save

If the export folder path contains non-Western characters (e.g. "c:\temp\Dia_Tástáil"), the export does not succeed and Dia gives an error:
"error while writing to export stream".

If the export folder path contains Western characters but the file name contains non-Western characters (e.g. "c:\temp\Dia_test\büg.pdf"), the export succeeds but the output file name contains wrong characters ("bĂĽg.pdf" in this example).

I reported that 7+ years ago as bug #634519. Hans Breuer commented it was a problem in interaction between Gtk+ and Cairo.

From https://sourceforge.net/projects/dia-installer/files/dia-win32-installer/0.97.2/ I installed dia-setup-0.97.2-2-unsigned.exe which was created on 2012-07-05.

Could this be fixed if Dia is recompiled with a newer version of Gtk+ for Windows?

-- rpr.
Comment 1 GNOME Infrastructure Team 2019-03-20 12:13:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/dia/issues/400.