Subj : UTF-8 nodelist report
To   : Michiel van der Vlist
From : August Abolins
Date : Sun Jan 26 2020 21:38:28

On 1/25/2020 4:05 PM, between "Michiel van der Vlist : August Abolins":

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

 M> How? Conversion is easely done with Iconv. /If/ the encoding
 M> is known. But how does one know the original encoding if it
 M> is just one character?


Hello Michiel!

Yes.. according to wiki there are 1,112,064 code points.  There are many
language encodings available. It could be very difficult to make a
correct guess the first time.   :(


 M> ..OK. in the case of Blorn it is not all
 M> that hard to guess.

Yes.. and there is much less typing effort involved than playing around
with MOB flags!  <G>


 M> ..But what in the general case?

The language encoding could be guessed based on the originating
country/town field.  Or, have a U,<flag> to ID a specific encoding? The
latter seems to be the way to go.

Maybe a topic for FUTURE4FIDO! ;)


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

Yes.. the fidoverse is small enough, documented enough (FTSC), and
hands-on-enough that this could be remedied very easily.



-- 
Daudz baltu dieniņu, Laimiņa dodi, Diženi raženi, Dzīvojoti!

--- Thunderbird 2.0.0.24 (Windows/20100228)
 * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

.