Re: [Gramps-devel] Graphviz based reports

[<rom...@ya...>]

> I use sys.getfilesystemencoding() on self.dot.write charset.

I get a conversion (.dot to image) warning with patch (no problem with
generated .dot) :

"Warning: Unsupported charset "UTF" - assuming utf-8"

Also, this will display "-8" character on generated image ...

Using charset = "%s" % encoding, seems to fix this issue.



Jérôme a écrit :
>> An issue is filed here that we can use to track the
>> conversation:
>> http://bugs.gramps-project.org/view.php?id=1485
>>
>> If you don't have the time or motivation to look at
>> it, I would understand. But I trust that you would be
>> able to find the right solution.
> 
> I provide a patch, which fix this issue on my side (French non-ASCII
> characters, utf8) ...
> 
> I use sys.getfilesystemencoding() on self.dot.write charset.
> 
> Also, I am not certain I will use latin1 option !!!
> 
> 
> 
> Brian Matherly a écrit :
>> Eero,
>>
>>>> One thing that I know is missing is the "latin"
>>>> option. I really have no idea how that worked, or
>>> what
>>>> it did.
>>>   Not all PS fonts
>>>     are created equal;
>>>   some are mapped unicode,
>>>     some to latin1.
>>>  
>>>   GraphViz cannot know,
>>>     user needs to tell.
>>>
>>>   Doesn't matter much though
>>>     until you output other than ASCII
>>>   then it's not WYSIWYG
>>>     but YrkBrl@$¤! instead!
>>>
>>>
>>> GraphViz FAQ on character->glyph mapping:
>>>
>>> For Postscript, the input must be either the ASCII
>>> subset of UTF-8 or 
>>> Latin-1. (We have looked for more general solutions,
>>> but it appears that 
>>> UTF-8 and Unicode are handled differently for every
>>> kind of font type in 
>>> Postscript, and we don't have time to hack this
>>> case-by-case. If someone 
>>> wants to volunteer to work on this, let us know.)
>> Since you are the expert on this, and I am completely
>> clueless when it comes to encodings, would you be
>> willing to take a look at this?
>>
>> The fundamental question is:
>> Do we still need the "Latin 1" option for the user, or
>> can we figure it out ourselves based on the font and
>> output type?
>>
>> An issue is filed here that we can use to track the
>> conversation:
>> http://bugs.gramps-project.org/view.php?id=1485
>>
>> If you don't have the time or motivation to look at
>> it, I would understand. But I trust that you would be
>> able to find the right solution.
>>
>> Thanks,
>>
>> ~Brian
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Gramps-devel mailing list
>> Gra...@li...
>> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>>
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel