Jim,

the general feeling is we hope the problems go away as linux moves to one single filesystem encoding (utf-8), just like windows only has one encoding.

And indeed, problems have been going down, we even had users who reinstalled with different encoding (utf-8) to have all problems go away.

There must be a thread somewhere of Alex with a suggestion for a real fix.

Problem is: filenames are in the encoding of the filesystem, but we must store them in xml and in database as utf-8 as GRAMPS is utf-8 only internally.
So the filechooser returns names in encoding of filesystem. So we must convert back and forth.

Combined with this, we have some other limitations: keys in BSDDB database cannot be unicode, so we convert to str and back for that, and some dicts are done with unicode codepoint keys for some reason, not utf-8 (eg BookReport.py, the set_book is always called with a name that is unicode(entry_box.get_text() ), I have no idea why actually ...).

One of the difficult parts: what if user copies his data on a usb key, reinstalls with new OS (and other encoding), then moves his data from usb-key back to his harddisk. If usb key is under some windows FAT encoding, will the filenames of pictures still be the same ??

Benny

PS: please do your ANSEL magic in trunk, while it is still fresh in your mind ;-)

2007/10/23, Brian Matherly <brian@gramps-project.org >:
Jim,

I don't have any wisdom for you, but I am more than happy to assign #
                0000889 to you because it has me stumped.

~Brian

----- Original Message ----
From: James G. Sack (jim) <jgsack@san.rr.com>
To: GRAMPS Devel < gramps-devel@lists.sourceforge.net>
Sent: Monday, October 22, 2007 7:25:20 PM
Subject: [Gramps-devel] filesystem encoding problems survey


There seem to be recurring problems associated with filesystem
encoding,
(especially in 8-bit localizations but non UTF-8, I believe).

A quick survey (bug-tracker "project" Gramps 2.2) reveals these issues:
==> feel free to post additions, corrections & clarifications <==
- - -
  (.. resolution, severity/priority status[=assigned-to]) )
0000606: cannot open filenames which are not UTF-8 encoded
.. open, maj/norm feedback
  dups #648,661,669,644,835
  rel2 #889
0000648: Support non-ASCII filenames
.. dup, min/norm unassigned
dup< #606
rel2 #889
0000661: import of Gedcom file fails
.. dup, min/norm unassigned
dup< #606
0000669: import of GEDCOM files
.. dup, min/norm unassigned
dup< #606
0000644: Adding photo
.. open min/norm new
dup< #606
rel2 #889
0000835: Add a media with accent
.. open, crash/norm fb
  dup< #606
  rel2 #809
0000889: ODT: special character (accent) on media name
.. open, min/norm assigned=pez4brian
rel2 #835,648,606,644
- - -

In addition, there is a thread that seems to originate at
  Alex Roitman <shura@gr...> - 2007-10-15 07:19
  Re: [Gramps-devel] Fwd: Funny error messages [moved to devel list]

http://sourceforge.net/mailarchive/message.php?msg_id=1192432785.5525.26.camel%40pal
that, if I interpret things correctly, suggests a possibly pervasive
problem.

It looks like there may be scattered patches and workarounds in the
note-message threads of the tracker entries, but I confess to not quite
seeing how _everything_ fits together (if it does).

*************************************************
IF I AM IMAGINING A PROBLEM THAT DOESN'T EXIST..
==> please tell me! :-)
*************************************************

But if it is something that needs attention, I think I have some
comfort
with encodings, locale-settings, various tools, and test environments
for this kind of problem, so I would like to focus on this issue if
people feel it is worthwhile, and have no objection to my working on
it.

==> If so, I would like to request a restatement via reply to this
thread of recipes useful for demonstrating a) crashes, b) inability to
complete tasks, c) unexpected behavior and annoyances

Regards,
..jim

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel





-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Gramps-devel mailing list
Gramps-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gramps-devel