05 Jun 15 07:31, you wrote to me:   
      
    NB> Whoops! A little premature on sending that last message off. :)   
      
   not a problem...   
      
    ml>> what are you using for your XLAT* lines in your golded confs? i'm   
    ml>> using the ""advanced"" conf from the repo with a few slight mods but   
    ml>> nothing to the XLAT* lines... that means that i'm also using the CHS   
    ml>> files in the separate charsets.conf file as generated by stas'   
    ml>> script... i think i read that this is what you are also using...   
      
    NB> I have a bunch of things mapped to UTF-8 using the translation tables and   
    NB> whatnot, but I think the real difference is in those others mentioned.   
   Here   
    NB> I'm setting my xlatlocalset, xlatimport, and exlatexport to UTF-8,   
    NB> basically forcing it to use it no matter what.   
      
   i think i've tried that with no joy...   
      
    ml>> the main thing is that some are trying to push utf-8 in to fidonet...   
    ml>> this editor and MSGED are the two closest to being able to do this...   
      
    NB> Well, Golded+ does support twice as many character translations as MsgEd   
    NB> does, but that's besides the point.   
      
   actually, all three readers, TimED, GoldED and MsgED, use the same chs   
   translation files... if others can't translate as much as golded does, that   
   just means that they don't have the additional chs files and they don't have   
   the config stuff telling them what chs files to use for which translations...   
      
    NB> If by "closest" you mean "very far away from" then yes. :)   
      
   hahaha...   
      
    NB> But at this point the only *REAL* way to do it is the way Maurice does   
    NB> it.. which is basically all manually (no thanks). :)   
      
   thta or we find/develope another reader/editor that handles the various FTN   
   message storage formats and handles the translation to the local ""code page""   
   properly for display...   
      
    ml>> TimED may also be close since it is also now FOSS but i've not looked   
    ml>> at it in its new incarnation... someone has to step up if the network   
    ml>> is to advance like some say it has to if it is wanting to keep up...   
      
    NB> At this point I don't think it will happen, unless those that mentioned   
    NB> tinkering with something do actually get something out into the wild. But   
   I   
    NB> have it pretty close and can deal with it's drawbacks as long as I need   
   to.   
      
   yeah, i don't know what anyone is doing with them...   
      
    NB> Anyhow, you had mentioned that the STATS echo looks off to you. In the   
    NB> last 10 messages posted there, when I switch to ter-i14b and use a 256   
    NB> glyph font, both of Bill's posts display correctly, but none of yours   
    NB> do.   
      
   i don't know why... bill is using the same script i am using to generate the   
   traffic graph and the transfer stats chart... the graph uses the single line   
   frame characters and then at least two or three of the box characters for the   
   bars on the graph...   
      
    NB> Are you trying to post them in UTF-8 or in CP437?   
    NB> What charset is the system using that is posting them?   
      
   they are plain CP437 from a CP437 machine...   
      
    NB> It almost seems like your posts aren't being posted correctly,   
      
   they're being posted properly... there's no translation at all on that machine   
   or in the posting software... i just connected to my system with netrunner and   
   looked at my last night's stats echo posts and they are properly displaying   
   the box frame and block characters as they should be... syncterm shows them   
   properly, too...   
      
    NB> which is why you're having issues seeing them properly. You said lines   
    NB> and double lines do display okay over there?   
      
   yes, golded has them at the top around the message header info and on the area   
   selection screen...   
      
    NB> If you're referring to Bill's posts then I'd have to agree. Though   
    NB> something is definitely wrong with the ones you posted.   
      
   can't be since they're pure CP437 all around...   
      
    ml>> so, what can you tell me about your "utf-8 4" settings? do you know   
    ml>> what you changed or set for that?? not that it will help with this   
    ml>> incorrect rendering mess :(   
      
    NB> I created my own very basic translation table, including:   
      
    NB> 0       ; ID Number   
    NB> 0       ; Version Number   
    NB> 4       ; Level number of table to display   
      
    NB> UTF-8   ; From set   
    NB> UTF-8   ; To set   
    NB> END   
      
    NB> Named it utf8_utf8.chs   
      
    NB> And in golded.cfg, I added this:   
      
    NB> xlatcharset    utf-8    utf-8    utf8_utf8.chs   
      
    NB> So I basically just fooled it into thinking I was translating what I was   
    NB> already using. It's a hack, but it works. :)   
      
   i might try that... it seems to be similar to the 437_437, 850_850 and others   
   of the same nature... except that those all contain the upper 256 characters   
   whereas yours doesn't have any at all... hummm...   
      
   i think we're back to the point we got to a while back when trying to get T's   
   local console to show these ""high ascii"" characters properly... i have just   
   switched this golded script to using those echo escape code you posted... they   
   are the same as being used on T's machine... i also set golded to CP437 which   
   should be seen in the control lines on this post... i went to the stats echo   
   and looked, again, at my graph posting and it looks better but none of the box   
   characters are being shown... only the frame characters... the boxes are being   
   shown as question marks in a white circle and i think that means that there's   
   nothing in the character table in the font for them... that puts me/us back to   
   the damned font mess so i guess i'll have to root around in the ubuntu and/or   
   debian support areas to try to find a font that does pure CP437 with all the   
   proper 256 glyphs...   
      
   )\/(ark   
      
   ... We are free, but not to be evil.   
   ---   
    * Origin:  (1:3634/12.73)