TIP: Click on subject to list as thread! ANSI
echo: utf-8
to: August Abolins
from: Michiel van der Vlist
date: 2020-01-25 22:05:00
subject: UTF-8 nodelist report

Hello August,

On Friday January 24 2020 18:02, you wrote to Oli:

 O>> But there shouldn't be any invalid characters in the nodelist.
 O>> They should be translated or stripped. A UTF-8 nodelist that is
 O>> not a valid UTF-8 file is a bit pointless.

Agreed.

 AA> So..  why not have "the process gods" do the correction, and share the
 AA> corrected version to the originator?

How? Conversion is easely done with Iconv. /If/ the encoding is known. But how 
does one know the original encoding if it is just one character? OK. in the 
case of Blörn it is not all that hard to guess. But what in the general case?

It should not be necessary. Responsible RCs should not submit nodelist segments 
with non ASCII characters for the ASCII nodelist.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
                                               
* Origin: http://www.vlist.eu (2:280/5555)

SOURCE: echomail via QWK@pharcyde.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™.