At 10:43 24.03.01 +0800, James Henstridge wrote:
>On Sat, 24 Mar 2001, Hans Breuer wrote:
>
>> At 20:50 19.03.01 +0100, Cyrille Chepelov wrote:
>> >Oh, (sorry, I sorely lacked time to report this) ; when exporting files
with
>> >ISO8859-1 characters (such as éèàâê) (\'e\`e\'a\^a\^e in latexish) into
WMF,
>> >it looks like something in the process converts stuff into UTF8, but
doesn't
>> >do it all the way: in the final printout, you see two characters for each
>> >original accented character (ie, you get éèà âê for the previous
>> >string).
>>
>> The "something" which converts to UTF8 is apparently libxml. I've changed
>> the wmf plug-in to use g_utf8_to_utf16 () and TextOutW, which finally does
>> the trick.
>
>At the moment, dia works a lot better with libxml 1.x. libxml2 does weird
>stuff to non UTF-8 strings when it is expecting UTF-8. The way to fix
>this is to change over to using unicode for the file format. I suppose
>this will be post 0.87 though.
>
But the windows port does use libxml-1.8.7 and I'm getting "weird" stuff,
if leaving the 7-Bit space. Looking more closely to it gives the
impression, that it is not coming from libxml but from Gkt-1.3 (before
Pango, but switched to UTF-8 internally). This is what the windoze port is
forced to use, because there never was a stable Gtk-1.2.x for windoze at all.
So my first tip - not to use non ASCII characters with Dia - would leave
you on the safe side ...
BTW: doing the official 0.87 now would be fine with me. (There were
multiple 0.86 versions for windoze anyway, because of the menu callback
issues.)
Thanks,
Hans
-------- Hans "at" Breuer "dot" Org -----------
Tell me what you need, and I'll tell you how to
get along without it. -- Dilbert
