Hello mark,

On 12 Dec 16 20:45, mark lewis wrote to Nicholas Boel:

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

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

 NB>> I've been told by Stas as well as others that they wouldn't do
 NB>> it. So unless someone comes out of the woodwork and makes it
 NB>> happen, I'm going to stick with my hunch.

 ml> considering that we don't hear from them any more, it is also, sadly,
 ml> understandable :(

I vaguely remember some talks about someone working on MsgEd and and
possibility of UTF-8 support, but that was awhile ago and I have no idea where
the idea ever ended up. I don't mind MsgEd either, and actually somewhat prefer
the layout and monotone colors used in it. At the time I tried it, it was just
more broken than Golded in the UTF-8 department so I continued with Golded
instead.

 NB>> I'm not sure what you mean here. My BBS has nothing to do with
 NB>> this. Two completely separate message bases at this point in
 NB>> time.

 ml> i was point to the thing that sysops are always having to do ""weird
 ml> stuff" behind the scenes to make things work they way they want them
 ml> to appear to be working for their users... the users see only a smooth
 ml> flow and have no clue what the operator is doing boiling potions and
 ml> casting spells to make work... i have several things on my system that
 ml> simply wouldn't be done without 4DOS/4OS2 and the ability to display
 ml> external files or call external scripts...

Ah, I see what you mean now. But in this case, it's a completely separate
project. Nobody else accessing my system will be using my "sysop reader/editor"
method of sorts. So I would like things to display properly both reading and
writing. Which they currently are. slrn uses iconv to translate everything to
UTF-8, which displays everything perfectly (the only issue so far is when
systems use "unknown-8bit" encoding, I see a little error but it doesn't seem
to affect anything. Heck, I may even be able to add some kind of readalias for
it and change it up to iso-8859-1 or something so at least I don't see the
error any more. Then vim handles my editing/posting, which has always worked as
expected.

So far so good, except for the fact that JamNNTPd currently doesn't support the
level 4 parameter even though everything I write falls under that level, but I
just started working on it, and damnit I'll get it to work. :)

 ml>>> hehehehe :)

 NB>> Just something else to tinker with. :)

 ml> i can think of plenty of other things "to tinker with" but one's
 ml> partner might not be so willing all the time ;) :)

While I'm sitting at home during the day due to a work related injury, she's at
work. So I have to find other things to keep me busy. :)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827