REPLY: 2:280/5555 67ce0c30
MSGID: 1:154/10 67ce4c4d
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-03-02
Hey Michiel!

On Sun, 09 Mar 2025 22:23:24 +0100, you wrote:

 > It is not the keyboard. Contrary to what they do in Belgium, in The
 > Netherlands we do not use a special Dutch keyboard with dedicated keys
 > fo the special characters. We use the same physical US keyboard that you
 > have. It is the keyboard driver that takes care of the special
 > characters. Some keys have been made into "dead keys" by the driver.
 > E,g, to get an 'e' with diaresis I first press the key for the double
 > quote, followed by the 'e'. To type the double quote itself, i have to
 > press that key twice. It is easy once you are used to it.

After 30+ years of not doing it, it may be difficult to get used to it. I'm
not saying it's impossible, as I can do ALT-0235 to get the desired "ë", but
it's a bit of a challenge to try to remember to do every time I type my name.
:)

 > Understood. So I take it you are not really interested in the UTF
 > nodelist project to get your name with an 'ë' in the nodelist?

I actually thought we discussed this some time ago. I also believe I was
getting the DAILYUTF from you at some point, but possibly when your system
went down, and stayed down for some time, it was stopped for some reason (I
don't think I ever turned it off).

Is anyone in zone 1 involved (I'm unsure if ZC1 is able to forward it on for
me)? Or would the submissions need to go to Ward, since I'm an RC?

 > The ZC does double processing. One for the ASCII list and one for the
 > UTF list. For the UTF list MakeNl is run with ALLOW8BIT set. For regions
 > that dot not participate in the UTF list, the ZC uses the ASCII segment
 > for both list. For regions that do participate, their seperate UTF
 > region segment is used for the UTF list.

I suppose anyone involved would have to double process with and without the
ALLOW8BIT option, correct?

 > RC20 does not participate in the UTF nodelist project. He does not send
 > two different segments. But his segment is not pure ASCII, it contain
 > some characters in Latin-1. So for the ASCII list, the ZC's MakNl
 > substitutes question marks for the non ASCII characters. For the UTF
 > list, they are passed "as is". But that was only was noticed after I
 > started my weekly error report.

Is it even LATIN-1? Or does it just end up that way because of CP437 probably
turns into ISO-8859-1 on Windows? Isn't CP437 -> ISO-8859-1 basically the same
as ASCII -> UTF-8 where everything in the former is also represented in the
latter (then again, ASCII would be part of many, if not every charset)?

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20240309
 * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
SEEN-BY: 4/0 90/0 104/119 105/81 106/201 124/5016 128/187 153/757
SEEN-BY: 153/7715 154/10 30 50 110 700 701 203/0 218/700 220/20 221/0
SEEN-BY: 221/6 226/30 44 50 227/114 229/110 114 310 317 426 428 470
SEEN-BY: 229/700 705 240/1120 5832 280/464 5003 5006 5555 291/111
SEEN-BY: 292/854 8125 301/1 310/31 320/219 341/66 234 423/120 460/58
SEEN-BY: 467/888 712/848 770/1 900/0 902/0 26 905/0 5020/400
PATH: 154/10 280/464 341/66 902/26 229/426