TIP: Click on subject to list as thread! ANSI
echo: fidonews
to: MICHIEL VAN DER VLIST
from: KEES VAN EETEN
date: 2019-05-27 14:50:00
subject: FidoNews 36:21 [01/07]: G

Hello Michiel!

27 May 19 14:29, you wrote to me:

 KE>> Those who are able to read UTF-8 encoded messages are free to do so in
 KE>> echo areas that promote that encoding. Publishing UTF-8 encoded
 KE>> messages in general areas like FIDONEWS, where UTF-8 readers are a
 KE>> minoriity, is even worse than mixing 8-bit encodings in one message.

 MvdV> That is a matter of opinion. As a techie I would say that mixing 8 bit
 MvdV> encodings in one and the same message or in one and the same file is
 MvdV> technically incorrect and therefore "worse".

 As a reader of messages, where my replacement system is not configured to
 the diverse World of encodings used, messages with messed up umlauted
 characters, are more readable, then UTF-8 encoded messages with a rich use
 of two byte characters.

 But by the time I get smapinntp and Thunderbird as well as my python reader
 properly installed, I will be OK again when I am nosy.

 Butt still, it are all kludges, that are far from the Holy Grail.

 Promoting UTF-8, where there are only poor kludges, is just as usefull as
 complaining that Fidonet has to modernize. It will not produce the
 software, that is needed. Toning down your expectations and writing
 example implementations brings far more.


Kees

--- GoldED+/LNX 1.1.5--b20180707
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.