MK> I won't be betting the farm on that. Like I say above, UTF-8 characters MK> are UTF-8 characters despite what some might claim they are. The current MK> maintainer of Golded ought to know if indeed he actually cares about UTF-8 MK> compatibilty.
MK> I for one think this is on topic for this particular echo.
FTSC has documented the specification and has don its work. Implementing variable size fonts is not an easy task, pointing at other software that has managed to do so, only shows that it can be done.
I do not expect that the current maintainer is planning a rewrite to accomodate multi byte characters. Most of the work seems to be done by people who have cyrillic as ther main characterset, they have most to benefit from the use of UTF-8.
In some packages for linux, it is advised to set the character set to LATIN-1 and encapsulate Golded in "luit". "luit" with the proper parameter converts LATIN-1 to UTF-8 for proper presentation on the UTF-8 terminal, it also converts UTF-8 to LATIN-1 on the way back.
something like this : luit -encoding 'ISO 8859-1' ./gedlnx
Where gedlnx is the executable of golded on my system.
Golded works perfectly with input conversion to UTF-8 as local font for presentation on a utf-8 terminal. However on export conversions cannot work, and only utf-8 outgoing is possible. If you send UTF-8 encoded messages with characters outside the normal ascii set, no one can properly read the message unless the local terminal is UTF-8
Whoever know more on this subject, correct me. This is off topic for this area and the Chaiman of FTSC usually disagrees with me on matters concerning UTF-8 ;)
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)
