Hello mark!

** 04.04.19 - 12:20, mark lewis wrote to August Abolins:

AA>> I have Config/Options/MessageReader configured with UTF-8 enabled
AA>> (it's actually the default.

AA>> But UTF-8 chars don't seem to render properly.

AA>> It that a bug?

ml> what is your OS using? that's the key... if you are on winwhatever, you
ml> may be using CP1252 but in modern winwhatever, it could be UTF-16...

On XP here with my T60 Thinkpad.  I've never played/changed codepage  
settings.  I'm not even sure how to do that.


ml> ...then it is not rendered at all or maybe it is rendered as a box
ml> with an 'x' in it or possibly as a question mark... if there's a
ml> character in that position in the 256 byte codepage, you may see the
ml> wrong glyph...

oxp displays the ? char where I expect the utf-8.  The same text looks  
perfect in Thunderbird/nntp.   So, the boss node is retaining the  
integrity of utf-8.  But oxp is breaking it.  (I'm not sure what WinPoint  
would do.)


ml> FWIW: the message i'm replying to carries a "CHRS: ASCII 1" control
ml> line... this is perfectly fine since your post contains only 7bit ASCII
ml> characters...

I don't know how to pre-view the CHRS with oxp.  I can request various  
header info, but CHRS is not one of them.  Thanks anyway.


ml> if you are interested in looking further,
ml> http://ftsc.org/docs/fts-5003.001

I may check it out some time in the future.  BTW.. I skimmed through some  
of the other fts docs a few weeks ago.  The one about the BEER tag had me  
ROTFL.  Are there any more like that?

Regards,
  ../|ug

--- OpenXP 5.0.36
 * Origin: /|ug's Point, ONT, CANADA (2:221/1.58)