Package: gramps Version: 4.1.1~dfsg-2 Severity: serious Tags: pending Hi,
I have been made aware of several upstream bugs that render Gramps unusable for users that have special characters in their database (i.e. languages other than English). For example: https://gramps-project.org/bugs/view.php?id=8134 https://gramps-project.org/bugs/view.php?id=8258 https://gramps-project.org/bugs/view.php?id=8357 https://gramps-project.org/bugs/view.php?id=8360 https://gramps-project.org/bugs/view.php?id=8117 The bugs occur in Gramps 4.1.1 when users are asked to upgrade their database because of the switch to Python 3. This is the explanation from Nick Hall from the Gramps Project: "The database contains a mix of unicode and strings. When a record in python2 format is loaded into python3, unicode gets converted into a str, but the way strings are converted depends on the encoding setting. If "bytes" is specifies then strings are converted into bytes, otherwise they are also converted to str. By default strings are converted into str using the ASCII encoding. This will cause errors if the strings contain utf-8 encoded unicode." I have cherry picked the commits from upstream that fix the problem, and it should be uploaded soon. Regards, Ross
signature.asc
Description: OpenPGP digital signature
