Hello mark,

On Thu, 15 Dec 2016 18:49:32 -0500, mark lewis -> Nicholas Boel wrote:

 ml> i've never seen JAMNNTPd accept a UTF-8 post from a client... in fact,
 ml> it specifically refuses them on my OS/2 box... i've had to train my
 ml> users that if they see a certain message to open a menu on their client
 ml> and make sure they set the characterset to "Western" which is ISO-8859
 ml> one and then resend the message... then it is accepted and they can be
 ml> happy..

I'm translating all character sets to UTF-8 here via the "read" option. Seems
to be working as expected. Björn has also posted with UTF-8 on numerous
occasions (albeit only with the level 2 parameter, and only when replying to a
UTF-8 message - which just means he's translating and posting in the same
character set as the post he's replying to). So maybe it's just an OS/2 thing?

 ml> it can be if they are properly pointed to their UTF-8 equivelents...
 ml> the real problem is going the other way but ...

I hear ya. Makes me wonder if the CP437 -> UTF-8 translation file for Golded is
garbage then (I use the same one for both Golded and JamNNTPd).

 ml> yeah, i've seen a lot of that, too...

It would be nice if at least iconv could somehow be made to accept
"unknown-8bit" as CP437 or IBMPC, but alas.. we don't live in a perfect world.
:)

Regards,
Nick

--- slrn/1.0.3 (Linux)