Hello mark,

On Thu, 15 Dec 2016 15:44:48 -0500, mark lewis -> Nicholas Boel wrote:

 NB>> into the code a bit. Hopefully nothing breaks, but I think I've
 NB>> managed to get what I wanted even though I didn't go about it the
 NB>> proper way. :)

 ml> can you post what you did/changed to get level 4 indicated for UTF-8?

I did in my previous message to Tommi. It was hard coded to use level 2. I just
changed it to use 4 instead. Unfortunately, this hack will only work in a UTF-8
only environment, meaning no translating on outgoing messages.

 ml> also, i just realized, how'd you get JAMNNTPd to accept UTF-8 in the
 ml> first place??

I'm not sure what you mean? JamNNTPd has always accepted translations to UTF-8,
just not from. For example, I can't translate this message to CP437 from
UTF-8.. but I don't ever see a reason to have to do that. I use "defaultpost
UTF-8" as well as one single "post * UTF-8" with no translation table defined.
My outgoing UTF-8 messages don't need translation.

Granted, translating from say CP437 to UTF-8 doesn't always work well either
when it comes to line and box drawings, but if the message is indeed marked
properly, and slrn utilizing iconv, I don't see why it wouldn't work. At this
point I've noticed most stats postings or BBS ads with line/box drawings do not
contain a CHRS kludge, therefore it's considered "unknown-8bit" and will not
convert to UTF-8 via iconv or JamNNTPd's translations. Most of those posts go
ignored anyways, so it's not a big deal.

Regards,
Nick

--- slrn/1.0.3 (Linux)