Subj : openxp chrs
To   : Nicholas Boel
From : August Abolins
Date : Thu Apr 18 2024 21:02:00

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)

.