TIP: Click on subject to list as thread! ANSI
echo: golded
to: MARK LEWIS
from: NICHOLAS BOEL
date: 2015-06-04 16:58:00
subject: Re: The NAB twisted take

Hello mark,

On 03 Jun 15 23:52, mark lewis wrote to Nicholas Boel:

 NB>> What editor are you using?

 ml> ummm... really? peek at my control lines ;)

So you're saying you're using the INTERNAL Golded+ editor? If so, it's no
wonder nothing is working for you. You have to use a real UTF-8 compatible
external editor (like nano or vi) to write in UTF-8. Golded+ doesn't support
UTF-8 whatsoever as far as I can tell.

 ml>>> in fact, no ALT-xxx codes are working :/

 NB>> That's odd. Are you sure you have UTF-8 enabled properly?

 ml> i didn't enable anything... this installation is in the same state it
 ml> comes from the factory in...

What does "locale" output?

 NB>>>> Also, if you're interested, I can give you some advice as to
 NB>>>> how to change your "UTF-8 2" to "UTF-8 4" as well. :)

 ml>>> yeah, i'd also like to be able to see the single and double line
 ml>>> graphic characters as well as the various block ones, too...
 ml>>> apparently i don't have my translate stuff set up properly...
 ml>>> what i'm using is from the -dev repo in its entirity... i've
 ml>>> crossposted this to the golded echo so we can continue over
 ml>>> there :)

If you use a 512 glyph UTF-8 font, you won't see the CP437 characters properly
(they are mapped differently) unless you convert them with iconv. You can,
however use a limited 256 glyph UTF-8 font that will display it properly with a
couple "echo" lines set in your profile.

 NB>> That would be two different beasts entirely. In order for me to
 NB>> see and use as much UTF-8 as possible on here, I have to use a
 NB>> 512 glyph font which remaps the ANSI characters differently. So I
 NB>> don't see any of those unless I convert them using iconv, or use
 NB>> a 256 glyph font, in which case you're not using or seeing as
 NB>> much UTF-8 as possible.

 ml> i see double or triple characters where ""high ascii"" should be
 ml> appearing... that tells me that this reader is translating them to
 ml> utf-8... if i don't see those, i see one or more question marks in
 ml> white circles...

If it's Golded+ itself, it's not translating to UTF-8. Golded+ doesn't support
UTF-8, which is why I've worked around it to use an external editor that CAN
support what I'm reading and writing. If anything, it's translating to garbage
because you don't have your character translations setup correctly.

 NB>> In either case, Golded itself won't display most of it properly
 NB>> when using UTF-8. It's only when you load up the temp message
 NB>> file in a UTF-8 compatible editor that it will display correctly.

 ml> that doesn't sound right... i shouldn't have to quote the post to see
 ml> it correctly...

Welcome to the world of sysop readers. None of them support UTF-8 properly.
That's why using an external editor is the only way to accomplish the task.
Golded+'s internal reader will not display UTF-8 properly. So when I quote the
message and shell out to nano, I then see everything the way it's supposed to
be seen.

As non-right as it sounds, thats our only current option unless you or someone
else with the knowledge wants to create a new sysop reader/editor that does in
fact support it. :)

 ml> how can i check what font is being used? this reader shows single and
 ml> double line borders itself just fine... just none of those in the
 ml> stats echo are showing properly... that's the main testing area...
 ml> when that stuff displays properly, then everything else should too...

Sure, if you have everything mapped to CP437. However, it won't display
properly if you try to convert everything to UTF-8. I tinkered with the
character translations quite a bit in the past, but haven't looked at them for
awhile now. I would have to jump back into the config and see where I left off
with all that. 

What I do remember, though.. is some Russian or Ukranian sysops netmailing me
that my CHRS kludge was showing "UTF-8 4" but while using a 256 glyph font was
producing CP437 messages. I had to switch to a 512 glyph font in order for it
to be a "proper" UTF-8 encoded message. *shrug*

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.