• Changing from CP866 to CP850

    From Flavio Bessa@4:801/189.1 to All on Wed Sep 20 09:27:16 2017
    Hello everybody.

    I have been playing around with GoldED for a while, but it's all configured to use CP866, which makes a few garbled characters here and there.

    I would like to change it to CP850 (which is good for Brazilian Portuguese), but I would like to know better a few parts of golded.cfg:

    XLATPATH /Users/flbessa/fido/etc/golded/cfgs/charset/
    XLATLOCALSET KOI8
    XLATIMPORT CP866
    XLATEXPORT CP866
    XLATCHARSET KOI8 CP866 koi_866.chs
    XLATCHARSET CP866 KOI8 866_koi.chs

    I understand I should replace CP866 for CP850, but what should I put at
    XLATLOCALSET? and I saw at the .chs directory that there's a ton of cp850-related files...

    Flavio

    ... I AM UnionNet Addicted! What about you?
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
  • From Andrei_Rachita@2:530/306 to Flavio Bessa on Fri Sep 22 08:31:35 2017
    Hi Flavio,

    I have the same issue with setting English characters.
    So far my GoldEd is still full of Russian characters.
    Since you know more than me on this topic, could you give me some directions (for noobies) on how I could change the codepage. I'm using Windows here.

    Thanks a lot,
    Andrei



    @MSGID: 4:801/189.1 59c25f39

    @PID: GED-NSFOSX 1.1.5-20090710

    @CHRS: CP866 2

    @TZUTC: -0300

    @TID: CrashMail II/Linux 0.7

    Hello everybody.

    I have been playing around with GoldED for a while, but it's all configured to use CP866, which makes a few garbled characters here and there.

    I would like to change it to CP850 (which is good for Brazilian Portuguese), but I would like to know better a few parts of golded.cfg:

    XLATPATH /Users/flbessa/fido/etc/golded/cfgs/charset/
    XLATLOCALSET KOI8
    XLATIMPORT CP866
    XLATEXPORT CP866
    XLATCHARSET KOI8 CP866 koi_866.chs
    XLATCHARSET CP866 KOI8 866_koi.chs

    I understand I should replace CP866 for CP850, but what should I put at XLATLOCALSET? and I saw at the .chs directory that there's a ton of cp850-related files...

    Flavio

    ... I AM UnionNet Addicted! What about you?
    --- MacFidoIP 1.0 (OSX)
    * Origin: Hyperion's Orbit - Resisting since 1995! (4:801/189.1)
    SEEN-BY: 57/0 103/705 116/102 130/210 153/250 154/10 203/0 221/1 240/1120 SEEN-BY: 240/1512 1661 5832 249/303 261/38 280/464 1041 1208 2020 5003 5006 SEEN-BY: 280/5268 5555 292/624 854 310/31 313/41 317/2 393/68 423/120 SEEN-BY: 530/306 712/848 770/0 1 100 340 772/0 1 500 2320/100 2432/390 SEEN-BY: 2448/44 2449/184 2452/250
    ATH: 801/189 261/38 393/68 770/1 280/464 5003 240/1120

    --- AfterShock/Android 1.6.5
    * Origin: pufa (2:530/306)
  • From Paul Quinn@3:640/1384 to Andrei_Rachita on Fri Sep 22 17:42:57 2017
    Hi! Andrei,

    On 09/22/2017 03:31 PM, you wrote to Flavio Bessa:

    I have the same issue with setting English characters.
    So far my GoldEd is still full of Russian characters.
    Since you know more than me on this topic, could you give me some directions (for noobies) on how I could change the codepage. I'm using Windows here.

    This is what I use on my older Windows 98SE, Andrei...

    -----8<-----C-U-T--H-E-R-E----->8-----
    ; typical character translation
    xlatpath m:\goldEd\xlat

    XLATLOCALSET CP850
    XLATCHARSET CP850 LATIN-1 850_ISO.CHS
    XLATCHARSET CP850 LATIN-9 850_LT9.chs
    XLATCHARSET CP850 UTF-8 850_UTF8.CHS
    XLATCHARSET LATIN-1 CP850 ISO_850.CHS
    XLATCHARSET LATIN-9 CP850 LT9_850.CHS
    XLATCHARSET UTF-8 CP850 UTF8_850.CHS
    XLATCHARSET CP437 CP850 437_850.CHS
    XLATCHARSET CP1252 CP850 1252_850.CHS
    XLATCHARSET DUTCH CP850 DUT_850.CHS
    XLATCHARSET GERMAN CP850 GER_850.CHS
    XLATCHARSET NORWEIG CP850 NOR_850.CHS
    XLATCHARSET SWEDISH CP850 SWE_850.CHS
    XLATCHARSET CP866 CP850 866_850.CHS
    XLATCHARSET CP850 CP850 IBM_IBM.CHS
    xlatcharset utf-8 utf-8 utf_utf.chs
    XlatCharSetAlias LATIN-1 ISO-8859-1
    XlatCharSetAlias CP437 IBMPC
    XlatCharSetAlias CP1252 WINDOWS
    XlatCharSetAlias NORWEIG ISO664-NO
    XlatCharSetAlias DUTCH ISO664-NL
    XlatCharSetalias SWEDISH ISO664-SE
    XlatCharSetAlias SWEDISH ISO-60
    XlatCharSetAlias CP866 +7_FIDO
    -----8<-----C-U-T--H-E-R-E----->8-----

    Caveats:

    I don't know why it works.
    I don't know what it does (very much).
    I make no guarantees that it will work.

    I recommend that you backup your current GoldEd configuration file first! Also, read through the list of referenced .CHS files that should be in your own
    "xlatpath", and remark-out those entries for files that are _not_ there.

    I do hope it might work for you... and Flavio. Enjoy!

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)
  • From Richard Menedetter@2:310/31 to Flavio Bessa on Fri Sep 22 22:28:58 2017
    Hi Flavio!

    20 Sep 2017 09:27, from Flavio Bessa -> All:

    XLATLOCALSET KOI8

    This is the charset that you use locally (on your computer).
    Eg LATIN-1

    XLATIMPORT CP866

    This is the charset that Golded will assume a message is written in if the message does not specify which charset it used. (eg. no chrs kludge)
    Eg LATIN-1 or CP437 or CP850

    XLATEXPORT CP866

    What charset should be used for sending out messages.
    Eg LATIN-1

    XLATCHARSET KOI8 CP866 koi_866.chs

    Here you add the translation files in the above case from koi to 866.

    I understand I should replace CP866 for CP850, but what should
    I put at XLATLOCALSET? and I saw at the .chs directory that there's a
    ton of cp850-related files...

    CP850 is DOS latin-1.
    Are you sure you want to use that?
    Eg. are you using a DOS system configured to CP850?
    All modern operating systems use UTF-8, sadly Golded does not really support it, and most fido SW is not able to show it correctly, so the next best choice is to configure the terminal to use iso-8859-1 (LATIN-1 in fido speak).
    That is what I do here on Linux.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Closed eyes are not always sleeping. (2:310/31)
  • From Torsten Bamberg@2:240/5832 to Richard Menedetter on Fri Sep 22 23:44:21 2017
    Hallo Richard!

    22.09.2017 22:28, Richard Menedetter schrieb an Flavio Bessa:

    All modern operating systems use UTF-8, sadly Golded does not really support it, and most fido SW is not able to show it correctly, so the
    next best choice is to configure the terminal to use iso-8859-1
    (LATIN-1 in fido speak). That is what I do here on Linux.
    Ah, okay. You don't use utf-8 on your local terminal. Very good to know.

    You have done a lot of work with the charsets in the past, and announced some very usefull archives with the informations and the charsets.
    Is it possible, to do this again for golded+ from your side?

    CU, Ricsi
    Bye/2 Torsten

    ... MAILBOX: Up 00d 05h 35m (BTUp2V1.5)
    --- GoldED+ 1.1.5-17
    * Origin: DatenBahn BBS Hamburg (2:240/5832)
  • From Christos Athanasopoulos@2:410/303 to Richard Menedetter on Sat Sep 23 10:36:36 2017
    Hello, Richard!

    22 Sep 17 22:28, from Richard Menedetter -> Flavio Bessa, in URL @OFGHIUrl:


    XLATLOCALSET KOI8

    This is the charset that you use locally (on your computer).
    Eg LATIN-1

    XLATIMPORT CP866

    This is the charset that Golded will assume a message is written in if
    the message does not specify which charset it used. (eg. no chrs
    kludge) Eg LATIN-1 or CP437 or CP850

    XLATEXPORT CP866

    What charset should be used for sending out messages.
    Eg LATIN-1

    XLATCHARSET KOI8 CP866 koi_866.chs

    Here you add the translation files in the above case from koi to 866.


    Thanks for the info. This would be very handfull for all of us in Greece that started the Region 41 again.

    Do you know what should be the above settings for someone who has ISO-8859-7 localy in his Linux and want to use Greek inside Golded? Its been a little bit of mess with all these codepage files...

    Best Regards, Christos
    --- -"Pappoulis's Blockfluete".
    * Origin: The Music Ace, Amaliada, Greece. (2:410/303)
  • From Richard Menedetter@2:310/31 to Torsten Bamberg on Sat Sep 23 14:16:30 2017
    Hi Torsten!

    22 Sep 2017 23:44, from Torsten Bamberg -> Richard Menedetter:

    You have done a lot of work with the charsets in the past, and
    announced some very usefull archives with the informations and the charsets. Is it possible, to do this again for golded+ from your side?

    Hmmm ... I think you are mixing up something.
    I did change a couple of default config files.
    Made a golded.cfg that was compatible with Golded3 and Golded+, adapted to the changes that ASA made for golded+.
    Also added goldhelp.cfg based on the work of Mike Herzog (sadly already passed away :(), etc.
    Those were added to the default config archive by ASA.

    I never changed any charset stuff, except config for it in golded.cfg.

    To be honest I think that the config did not change at all.
    What may be missing is definition of additional charsets.
    It does not look to hard (just list which chars get changed to which ones in the new charset) but I never had the need to add a new one.

    So sorry ... not much knowledge here ...

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Murphy was an optimist. (2:310/31)
  • From Richard Menedetter@2:310/31 to Christos Athanasopoulos on Sat Sep 23 14:28:02 2017
    Hi Christos!

    23 Sep 2017 10:36, from Christos Athanasopoulos -> Richard Menedetter:

    XLATLOCALSET KOI8
    This is the charset that you use locally (on your computer).
    Eg LATIN-1

    So you need to set this to LATIN-7

    XLATIMPORT CP866
    This is the charset that Golded will assume a message is written
    in if the message does not specify which charset it used. (eg. no
    chrs kludge) Eg LATIN-1 or CP437 or CP850

    You can set this eg to CP437
    (or to LATIN-7 in the greek message groups if you use that)

    XLATEXPORT CP866
    What charset should be used for sending out messages.
    Eg LATIN-1

    What charset are local greek messages written in usually?
    You can set it for example to LATIN-7, as long as you only stick to ASCII for non greek messages you will be fine.
    Or you can use the golded message group config, to set it to LATIN-7 in greek echos and CP437 in the others.

    XLATCHARSET KOI8 CP866 koi_866.chs
    Thanks for the info. This would be very handfull for all of us in
    Greece that started the Region 41 again.

    Do you know what should be the above settings for someone who has ISO-8859-7 localy in his Linux and want to use Greek inside Golded?
    Its been a little bit of mess with all these codepage files...

    The problem is you need to write the needed translations.
    latin-7 -> CP437
    cp437 -> latin-7
    also others if needed.

    Never done that myself ... but looking at the CHS files it looks doable.
    If you stick to the ASCII (lower 128 characters) you should get away with trivial translations.
    (eg empty files with only headers ;)
    Eg. empty translations, as you will only use chars > 128 in greek.

    If you want proper translations, you need to check the tables and write the translations yourself:
    https://en.wikipedia.org/wiki/ISO/IEC_8859-7

    Sorry that I am of no great use here :(
    Keep us updated.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: Everyone has photographic memory. Some don't have film. (2:310/31)
  • From Christos Athanasopoulos@2:410/303 to Richard Menedetter on Sat Sep 23 16:33:22 2017
    Hello, Richard!

    Reply to message from <23 Sep 17>, Richard Menedetter -> Christos Athanasopoulos, in URL @OFGHIUrl:

    Thanks again for your valuable help. It seems that it's not that easy in the end. In a few weeks that i'll have more time to spend, I'll try your sugestion.


    Best Regards, Christos
    --- -"Pappoulis's Blockfluete".
    * Origin: The Music Ace, Amaliada, Greece. (2:410/303)
  • From Richard Menedetter@2:310/31 to Christos Athanasopoulos on Sat Sep 23 17:28:18 2017
    Hi Christos!

    23 Sep 2017 16:33, from Christos Athanasopoulos -> Richard Menedetter:

    Reply to message from <23 Sep 17>, Richard Menedetter -> Christos Athanasopoulos, in URL @OFGHIUrl:

    You can edit your templates to not include the FGHI stuff ...
    Do not know exactly what it is, but it seems not to be used outside of russia.

    Thanks again for your valuable help. It seems that it's not that easy
    in the end.

    I am no expert on that topic.
    But I try to help.
    I hope others chime in.

    In a few weeks that i'll have more time to spend, I'll try your
    sugestion.

    Keep us informed.

    It would be easier if Golded would support unicode, but people have tried to add support, but the 8bitnes is deeply embedded into golded ... so it would be very hard, and people until now failed.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: KISS :-)* Keep It Simply Stupid! (2:310/31)
  • From mark lewis@1:3634/12.73 to Richard Menedetter on Sat Sep 23 14:57:12 2017
    On 2017 Sep 23 14:16:30, you wrote to Torsten Bamberg:

    To be honest I think that the config did not change at all.
    What may be missing is definition of additional charsets.
    It does not look to hard (just list which chars get changed to which ones in the new charset) but I never had the need to add a new one.

    i build golded+ from the repo... it came with a huge list of chs files and a conf file for them that was built by the xlatcfg.pl script that stas wrote... that conf file is 22k in size and should cover all character sets that are available... i have ~325 chs files in my charsets directory that golded+ can use...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... We do not mourn the loss of those who die fulfilling their destinies.
    ---
    * Origin: (1:3634/12.73)
  • From Kai Richter@2:240/77 to Paul Quinn on Sun Sep 24 10:22:46 2017
    Hello Paul!

    22 Sep 17, Paul Quinn wrote to Andrei_Rachita:

    XLATLOCALSET CP850

    I don't know why it works.

    I will try to explain what i think what it does.

    At first, your local computer has its own local charset.
    All text you save will be saved with that charset.

    Sometimes the text console or the command line interface can be set different from the system charset. Remember DOS config.sys and autoexec.bat files.

    If you start golded it must be compatible to that local charset.

    The next part is the translation of the codepage inside of mails.

    If you receive a LATIN mail it must be translated to CP850 to be viewed on a CP850 console.

    XLATCHARSET CP850 LATIN-1 850_ISO.CHS
    XLATCHARSET CP850 LATIN-9 850_LT9.chs
    XLATCHARSET LATIN-1 CP850 ISO_850.CHS
    XLATCHARSET LATIN-9 CP850 LT9_850.CHS

    Theses lines define the "how to" translate.
    I'm not sure which is the from/to column but let's say you have to do a translation from LATIN-9 to CP850 then the *.chs file LT9_850.CHS is used.
    (Or if i'm wrong the other one, 850_LT9.CHS)

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Richard Menedetter@2:310/31 to mark lewis on Sun Sep 24 16:27:16 2017
    Hi mark!

    23 Sep 2017 14:57, from mark lewis -> Richard Menedetter:

    i build golded+ from the repo... it came with a huge list of chs files
    and a conf file for them that was built by the xlatcfg.pl script that
    stas wrote... that conf file is 22k in size and should cover all
    character sets that are available... i have ~325 chs files in my
    charsets directory that golded+ can use...

    Same here
    ls -l /usr/local/etc/golded+/cfgs/charset/ |wc -l
    328

    But I do not have LATIN-7 files.
    If you have them feel free to send them towards Christos.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: I didn't do it, and I won't do it again. (2:310/31)
  • From mark lewis@1:3634/12.73 to Richard Menedetter on Sun Sep 24 15:00:16 2017
    On 2017 Sep 24 16:27:16, you wrote to me:

    i build golded+ from the repo... it came with a huge list of chs
    files and a conf file for them that was built by the xlatcfg.pl
    script that stas wrote... that conf file is 22k in size and should
    cover all character sets that are available... i have ~325 chs files
    in my charsets directory that golded+ can use...

    Same here
    ls -l /usr/local/etc/golded+/cfgs/charset/ |wc -l
    328

    exactly what i did :) :lol:

    But I do not have LATIN-7 files.
    If you have them feel free to send them towards Christos.

    i did kinda look but didn't see anything like that or any of the other entities
    you listed... they should be pretty easy to create, though... i think there was
    even a script or program that took two character sets and created the translation between them...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Bridges and tunnels are proof that we will not be denied.
    ---
    * Origin: (1:3634/12.73)
  • From Paul Quinn@3:640/1384 to Kai Richter on Mon Sep 25 08:49:40 2017
    Hi! Kai,

    On 09/24/2017 10:22 AM, you wrote:

    22 Sep 17, Paul Quinn wrote to Andrei_Rachita:

    XLATLOCALSET CP850
    I don't know why it works.

    I will try to explain what i think what it does.

    Thank you. But now I feel awful about causing you to twist & turn, trying to help me. At about 2255 last night I discovered why I was not really understanding what the XLAT section was doing. It was not my own creation, and
    I don't use anything like it on my Linux machines.

    You see, it was a direct import from a 'care package' that Michiel van der Vlist made for me back in March 2012. It was something Michiel was doing with his PC that seemed to fit my IBMPC/CP437 environment in that Win98 VirtualBox.
    He created the collection of .CHS files and the GoldEd configuration file section for me.

    I apologise for causing you to go to the effort of helping me. Thank you, kindly.

    Cheers,
    Paul.

    --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
    * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)