Hello Nicholas,

On Saturday November 04 2023 10:48, you wrote to golded+ inspector:

 NB> Wondering if any one of these commits changed something in regards to
 NB> a workaround a small (probably very small) handful of people have been
 NB> using since about as far back as I can remember.
[..]
 NB> basically irrelevant. This makeshift conversion table doesn't seem to
 NB> be working any more for that purpose.
[..]
 NB> When posting outgoing messages with 'xlatexport utf-8' is there an
 NB> easy way to hard code using the proper 'CHRS: UTF-8 4' kludge instead
 NB> of it using the level 2 parameter?

I got your netmail and I am afraid I can not be of much help. Except maybe for this:

Many years ago - on my request - in order to produce a proper "UTF-8 4" kludge line an optional second parameter was added to the level number line in the .chs file. My 850_utf8.chs file starts with this:

4                 ; ID number
1                 ; version number
;
2 4               ; level number
;
CP850             ; from set
UTF-8             ; to set

Note the "2 4" in the third non comment line. The '2' is to signal that the actual tranlsation is a level 2 operation. The '4' is the level to present in the CHRS kludge line.

As this was added many, many years ago I expect it to be present in your Golded versions as well.

Hope this helps.



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303