MK> Bottomline is the CHRS kludge solves nothing but I for one can and do MK> appreciate the effort especially when it correctly identifies the MK> codepage.
In principle the CHRS kludge works in Goldedplus.
I also use the kludge for a display routine for e.g. raw packages. Based on the CHRS kludge I select the parameters for iconv, to get a consistent display of messages with different CHRS kludges, worls like a charm. The same display routine is used for the output of queries on a mysql database with echo messages. When converted to UTF-8 and piped to less, every thing looks fine. Your moos and the Ukraianian text all come out wonder full.
There is one source of messages where there is a problem, but actually, I think it is the proper implementation if the same codepage is used by all. When UTF-8 messages arrive from Bjorn Felten, the text in the binary header is in an 8 bit character set. The message body is in UTF-8.
That may be a drawback for some, but e.g. when you want to present a message index it is far faster if only the structured binary header is to be read. When also the CHRS kludge has to be looked for, you add a lot of work. Some say so what, plenty of cpu power nowadays.
Now if you look for Bjorn there are at least 4 different presentations of the o with diareses. I have the same problem with sql searches in my database. Many will say, well who would want to look for Bjorn, well sometimes I do. ;) Especially in interesting times. ;)
Kees
--- FPD v2.9.040207 GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
