On Sun, 3 Mar 2024 16:41:58 +0100, Karel Kral -> Nicholas Boel wrote:

Are you referring to having these issues with a version from 2018? If
so, I would suggest you upgrade to the latest version and see if you
have any of the same issues you have now.

Just did and same result (= same issues).

I would suggest trying some translation tables. I had to look back at
your original messages about this since it was a few weeks ago already.
I did see there that you said you are not using any (maybe one)
translation tables?

If that is the case, and you have the sources, try including 'golded-plus/cfgs/config/charsets.cfg' in your golded.conf and see if
that helps or not.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Karel.

07 Mar 24 18:40, you wrote to Nicholas Boel:

If that is the case, and you have the sources, try including
'golded-plus/cfgs/config/charsets.cfg' in your golded.conf and
see if that helps or not.

Already have that since ever.

For that group I have:

GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP

Using UTF-8 in putty, having LANG=cs_CZ.utf8 in bash, startin golded:
luit -encoding 'ISO-8859-2' ./gedlnx -f

(because GROUP A we have ISO-8859-2 as agreed coding)

As I wrote, I have issue in GROUP B, GOLDED here...

OK. Your case is actually simpler than I thought. You should have zero issues with pseudo-graphics.

Try to set LANG to cs_CZ.ISO8859-2 and that will solve your issue! No need to set it for the whole system. Just for golded session.

$ LANG=cs_CZ.ISO8859-2 luit -encoding 'ISO-8859-2' ./gedlnx -f

Your problem is that luit converts symbols from 8859-2 to UTF, but ncurses tries to work in UTF-8 mode because you have LANG=cs_CZ.utf8.

In my case I have separate session in Putty with KOI8-R. And run golded like this:

LANG=ru_RU.koi8r gedlnx -C<myconfig>

And have no issues with pseudo-graphics. But luit works too, just tried it.

Vitaliy

... 640K ought to be enough for anybody
--- GoldED+/LNX 1.1.5-b20240305-beta
* Origin: Aurora, Colorado (1:104/117)

Hello Nicholas.

07 Mar 24 17:11, you wrote to Karel Kral:

For that group I have:

GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP

Are you using the wrong translation table? I think you should be using cp437 -> il2, rather than ascii -> il2.

Most probably he does because it works for him prior to my last changes. So I assume that text conversion performed correctly.

Vitaliy

... 640K ought to be enough for anybody
--- GoldED+/LNX 1.1.5-b20240305-beta
* Origin: Aurora, Colorado (1:104/117)

On Thu, 7 Mar 2024 23:27:32 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote:

Are you using the wrong translation table? I think you should be using
cp437 -> il2, rather than ascii -> il2.

Most probably he does because it works for him prior to my last changes. So I assume that text conversion performed correctly.

By his previous messages, I'm led to believe his hasn't been working
properly for awhile.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas!

08 Mar 24 05:59, you wrote to me:

You might want to try iso-8859-2 in PuTTY, also, rather than UTF-8.
Then try the command line that Vitaliy recommended to use?

Just tested. No improvement for GOLDED, even worse in shell.

xlatcharset cp437 utf-8 437_u8.chs

If that .chs file isn't in your xlat directory, I believe you can grab
it from Golded sources on github.

Got that file, included into golded.cfg - for UTF-8. No improvement.

I also played with EDITREPLYRE, but also no change.

As it is about 4 characters, I think is bug in golded related to "Re: ". I have no issue with other messages (even using local czech characters, including quoting). In total I see everything OK, except few messages in International echos.

E.g. replying to you - you can see Subj. is OK.

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

Hello Nicholas!

03 Mar 24 08:52, you wrote to me:

If that is the case, and you have the sources, try including 'golded-plus/cfgs/config/charsets.cfg' in your golded.conf and see if
that helps or not.

Already have that since ever.

For that group I have:

GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP

Using UTF-8 in putty, having LANG=cs_CZ.utf8 in bash, startin golded:
luit -encoding 'ISO-8859-2' ./gedlnx -f

(because GROUP A we have ISO-8859-2 as agreed coding)

As I wrote, I have issue in GROUP B, GOLDED here...

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

On Fri, 8 Mar 2024 00:40:06 +0100, Karel Kral -> Nicholas Boel wrote:

For that group I have:

GROUP B
XLATPATH /home/fido/golded/xlat
XLATCHARSET CP437 LATIN-2 asc_il2.chs
XLATCHARSET LATIN-2 CP437 il2_asc.chs
XLATIMPORT CP437
XLATIMPORT CP437
XLATLOCALSET LATIN-2
MSGLISTWIDESUBJ YES
ENDGROUP

Are you using the wrong translation table? I think you should be using
cp437 -> il2, rather than ascii -> il2.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello Nicholas!

07 Mar 24 17:11, you wrote to me:

Are you using the wrong translation table? I think you should be using cp437 -> il2, rather than ascii -> il2.

I do not have xlat file like that.

Point is that in group B there I expect only English and old fashioned ascii 127 anyway.

Karel

--- GoldED+/LNX 1.1.5-b20240209
* Origin: Plast DATA (2:423/39)

On Fri, 8 Mar 2024 13:33:28 +0100, Karel Kral -> Nicholas Boel wrote:

Are you using the wrong translation table? I think you should be using
cp437 -> il2, rather than ascii -> il2.

I do not have xlat file like that.

Point is that in group B there I expect only English and old fashioned ascii 127 anyway.

This is from one of your previous messages, just so I stay on track with
what your settings are:

"Using UTF-8 in putty, having LANG=cs_CZ.utf8 in bash, startin golded:
luit -encoding 'ISO-8859-2' ./gedlnx -f"

You might want to try iso-8859-2 in PuTTY, also, rather than UTF-8. Then
try the command line that Vitaliy recommended to use?

If that doesn't work, you could try using this as well and see if it
does something different for you:

xlatcharset cp437 utf-8 437_u8.chs

If that .chs file isn't in your xlat directory, I believe you can grab
it from Golded sources on github.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)