----------------------------------------------------------------------------------
@MSGID: 1:153/757.21@fidonet 1388c253
@REPLY: 1:154/10 6621b7c0
@PID: OpenXP/5.0.58 (Win32)
@CHRS: CP437 2
@TZUTC: -0400
Hello Nicholas!
AA>> It stays UTF-8 going out when replying to UTF-8 messages
AA>> that had arrived via nntp. It just not work that way
AA>> with FTN messages.
NB> Oh, you mean it uses a UTF-8 CHRS kludge? Or do you mean the UTF-8 text
NB> is unchanged when you reply to it, even though it displays all question
NB> marks for the text?
(BTW.. I purposely did not reflow your quote above. However, it
should be automatically limited to 79 chars including the
indent and your quote initials.)
Good question. I would have to run some tests to remind myself
what it does. But I seem to recall reading somewhere that if an
original nntp message arrives with utf-8, it will go out with
the same char-type: utf-8. The chars in the nntp message
should not change in the editor if the original arrived as utf-
8.
However, OpenXP does not render all utf-8 chars readable.
Link up with the UTF-8 (ftn) echo and see how OpenXP handles
the content there. I did a variety of UTF-8 tests there in
January 2020.
For the heck of it, here is the multi-language "Happy New Year"
table. Let`s see what OpenXP does with it here:
> Arabic: ??? ????? ?????
> Argentine: Feliz Aдo Nuevo
> Armenian: ????????? ??? ????
> Basque: Urte Berri On!
> Bengali: ??? ???? ???
> Bohemian: Vesele Vanoce
> Brazilian: Feliz Ano Novo
> Bulgarian: ??????? ???? ??????
> Catalan: FeliЗ any nou!
> Cantonese: ????
> Croatian: Sretan Bozic
> Czech: Stastny Novy Rok
> Danish: Godt NytЖr
> Dutch: Gelukkig Nieuwjaar!
> English: Happy New Year
> Espaдol: Prвspero Aдo Nuevo
> Esperanto: Gajan Kristnaskon
> Estonian: Head uut aastat
> Finnish: Onnellista Uutta Vuotta
> Flemish: Gelukkig nieuw jaar
> French: Bonne AnnВe!
> Frisian: Seine yn it Nije Jier!
> Gaelic: Shona Nua bliana
> Galician: Ano Novo
> German: GlБckliches Neues Jahr!
> Greek: ю?ч???хц??? ч? ??? ?ч??
> Hebrew: ??? ???? ???????
> Hindi: Shub Naya Baras
> Hungarian: Boldog Uj Рvet
> Icelandic: Hamingjusamur Nytt Ar
> Indonesian: Selamat tahun baru
> Italian: Felice Anno Nuovo
> Japanese: ???????????????
> Latin: Annum Nuovo!
> Nederlands: Gelukkig nieuwjaar
> Norwegian: Godt NyttЖr
> Polish: Szczesliwego nowego roku
> Portuguese: Feliz Ano Novo
> Rumanian: Anul Nou Fericit
> Russian: ? ????? ?????
> Spanish: Prвspero Aдo Nuevo
> Swahili: Mwaka Mpyaз
> Swedish: Gott Nytt Пr
> Turkish: Kutlu Olsun
> Ukrainian: ? ????? ?????
> Zulu: Jabulela unyaka omusha
AA>> Even yours..
AA>> https://ibb.co/bdxGz5t
NB> Are you using the Linux version? I only ask because your
NB> tearline doesn`t have anything to do with `Win`, or
NB> `Win32`, or `Windows` like mine did.
My messages should have the MAILER-ID kludge. It`s Win(32).
NB> I wonder if I set this up on Linux with the exact same
NB> settings if things might be a bit different.
Matching the terminal window size with Linux to the one in
OpenXP would be a good start. Atleast you will then see any
free-flow messages full width.
--
../|ug
--- OpenXP 5.0.58
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)
SEEN-BY: 50/109 104/117 134/100 153/0 135 143 148
149 151 757 802 7083 154/10
SEEN-BY: 218/840 221/1 6 360 280/464 5555 301/1
335/364 341/66 234 460/58
SEEN-BY: 463/68 467/888 3634/12 5000/111 5001/100
5005/49 5015/46 5019/40
SEEN-BY: 5020/715 846 848 1042 4441 12000 5030/49
1081 5054/8 5058/104
SEEN-BY: 5060/900 5061/133 5075/128 5083/444
@PATH: 153/757 221/6 5020/1042 4441