Re: [Xlog-discussion] xlog 0.8 and 0.9 not compatible (UTF-8)

[Tomi Manninen]

On Thu, 29 May 2003, Joop Stakenborg wrote:

> > ** (xlog:2077): WARNING **: Invalid UTF8 string passed to
> > pango_layout_set_text()
> 
> thanks for sharing your observations. This sounds rather annoying and I 
> really don't know what to do about it now :-(

How about checking the UTF8 validity at read and converting if necessary?
Something like

  if (g_utf8_validate() == FALSE)
        g_locale_to_utf8();

Or if you want to keep the logs in national character sets then simply do 
a g_locale_from_utf8() when writing and g_locale_to_utf8() when reading 
the logs.

However I think upgrading the logs to UTF8 could be a good idea, it would
make exchanging the logs with people around the world work flawlessly. It
will break compatibility if someone wants to downgrade xlog but I think
that's pretty minor problem, considering the program still works, you only
get some garbage in a log field. Maybe you could write a simple converter
program for that in case it's really needed.

BTW I have now tried to make gMFSK as UTF8 clean as possible. For example
I now have a FELDHELL transmitter that can render Kanji, Hebrew, Cyrillic
or whatever you happen to have fonts installed for (and a default
installation gives you a lot of fonts these days... :)

-- 
Tomi Manninen           Internet:  address@hidden
OH2BNS                  AX.25:     address@hidden
KP20ME04                Amprnet:   address@hidden