-={ jeudi, avril 02 2015, 11:25:04 -0700 }=-

Hey Alan!

 AI> I just converted a file to utf-8 and it looks good on my console.

Of course it does.  ;-)

Speaking of working kernels, I switched to kv3.18.10 now that the 3.18 branch
has been deemed longterm by the kernel gurus.  Works as good as the 3.19.2
version for what I had working on there.

 AI> the BBS has some built in stuff, like lines above and below this
 AI> reply that just look fugly when I'm in utf-8 mode.

Understood.  Probably 8-bit characters that aren't compatable with proper
terminals.  Many a BBS developer got suckered into phoney-baloney codepages (eg
cp437) believing they were universal and/or "high/upper ascii" which is total
BS.  Not much one can do about that other than to convince the developer to
ditch that obviously flawed mindset.

 AI> Hopefully I can get that all looking better.

Not if they are hardcoded into the BBS viewer/editor.  If they are part of the
message(s) then coverting them to the utf8 equivalents should work but I
haven't seen many utf8 documents that use that many so-called graphical
characters such as box/line drawing characters.  For messaging, control
characters aside, most of not all characters are text characters as a rule with
a few exceptions such as a Euro or dollar or cents sign for example.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.33(1)-release (x86_64-atom-linux-gnu)