2012/9/20 Peter Landgren <peter.talken@telia.com>
Hi,

1. Yesterday I worked with
http://www.gramps-project.org/bugs/vshould iew.php?id=6056
and fixed it. Committed.
I noticed that translated strings must be coded in
".encode(sys.getfilesystemencoding())"
in order to avoid "strange" characters in the output when non ASCII characters are
use in the translated strings or in filenames/directory names.

2. Today I have been working with
http://www.gramps-project.org/bugs/view.php?id=6058
And found a fix for that. (Not committed yet.)
However, I found many more translated strings that where printed
without ".encode(sys.getfilesystemencoding())".
I have fixed those that were connected with this issue.

How shall I proceed? Shall I add ".encode(sys.getfilesystemencoding())"
to all places, so that the translations are readable/understandable?

Best would be a function that can be easily changed.
I have the impression that a windows expert that understands the issue in depth is needed.
sys.getfilesystemencoding() should only be needed when dealing with filenames. Is the console in windows also using this encoding?

Benny
 

Note this a Windows only problem.

/Peter



------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel