MK> Personally I prefer to use 'iconv' which can work either way, such as: MK> iconv -f utf8 -t latin1, for proper presentation to an iso-9959-1
As far as I know iconv en luit are related. Iconv is a oneway filter, luit a twoway filter.
MK> terminal. However the original utf-8 message would be required to MK> *only* MK> contain characters that can be converted to iso-9959-1 characters which MK> may or may not be the case. Also converting from cp437 to latin-1 may MK> fail especially regarding the line drawing characters that the cp437 and MK> similar codepages (eg cp866) *must* have for their crippled terminals.
You are always bound by the largest common denominator.
KvE>> Chaiman of FTSC usually disagrees with me on matters concerning KvE>> UTF-8
MK> He also wrote a document about the history of UTF-8 which is extremely MK> debatable creditibility-wise but that is probably off topic here as well, MK> not that it matters any. I seriously doubt he is up to standards. Have MK> you ever seen any evidence to the contrary?
I have no opinion there as I have not read the document. And even then I doubt if I would discuss the writer.
MK> ... A M├╕├╕se once bit my sister ...
The UTF-8 to LATIN-1 cannot cope with this translation.
Instead of Moose with the o's slashed, it show as capital A with a tilde, followed by a comma for each slashed "o".
As I tried to explain there is no problem converting 8 bits to utf-8, converting utf-8 to 8 bits cannot be done in Golded.
I am not going into this, as I recently had the same discussion when the turmoil with the election started. The the character that caused the part of the turmoil was also also outside the range of the utf-8 to xxxx conversion tables. You will think nothing happens, because when a replay reaches you the moose is still in utf-8. On most other systems it is MA,A,se with tilde's on the A.
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)
