Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to GoldED Public Release discussion...  <--  <--- Return to Home Page
   Networked Database  GoldED Public Release discussion...   [237 / 433] RSS
 From   To   Subject   Date/Time 
Message   Richard Menedetter    Christos Athanasopoulos   Changing from CP866 to CP850   September 23, 2017
 2:28 PM *  

Hi Christos!

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

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

So you need to set this to LATIN-7

 FB>>> XLATIMPORT CP866
 RM>> This is the charset that Golded will assume a message is written
 RM>> in if the message does not specify which charset it used. (eg. no
 RM>> 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)

 FB>>> XLATEXPORT CP866
 RM>> What charset should be used for sending out messages.
 RM>> 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.

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

 CA> Do you know what should be the above settings for someone who has
 CA> ISO-8859-7 localy in his Linux and want to use Greek inside Golded?
 CA> 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)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to GoldED Public Release discussion...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0715 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_n96hqe2ddlonjgpbhe39s8odq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_n96hqe2ddlonjgpbhe39s8odq5, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_n96hqe2ddlonjgpbhe39s8odq5, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0