12 Dec 16 22:02, you wrote to me:

 NB>>> The whole point is to have full UTF-8 capability. A CP437 wrapper
 NB>>> binary would only ruin that.

 ml>> yeahbut you can see those drawing characters properly! now, if
 ml>> someone would figure how to map them to their UTF-8 representations,
 ml>> then we'd be a whole lot better off... i spent many hours mucking
 ml>> about on my web site just trying to get them to show properly in file
 ml>> descriptions (where they shouldn't even be) and finally got something
 ml>> that was ""acceptable"" but left a bad taste behind... properly
 ml>> mapping them would take care of this going forward... as long as that
 ml>> mapping is done locally and only for display... once one tries to
 ml>> take tha and move backward so their BBS users can also see them, it
 ml>> won't work because the mapping is one way only :(

 NB> Do you have this wrapper handy?

yeah... i forget who pointed me to it... it comes as source and is very easy to
compile...

[time passes]

ahhh... get it from here: https://github.com/keaston/cp437


 NB> If so, go ahead and drop it in my inbound so I can take a peek at it.
 NB> If it fixes the general display of Golded as well as the messages in
 NB> it (since UTF-8 isn't displayed properly anyways until I shell to vim
 NB> for editing), it may actually come in handy as I don't think it would
 NB> muck up my current locale or anything I do in vim.

i don't know if it affects programs run via shelling out or not... i use the
internal editor...


FWIW: i use the following command line to start my golded with cp437...

  ~/cp437/cp437 ~/fido/bin/golded -c~/fido/etc/golded.conf


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... All hail the Mighty Soybean!
---