TIP: Click on subject to list as thread! ANSI
echo: artware
to: Dallas Hinton
from: mark lewis
date: 2012-06-04 09:46:50
subject: readmaps.dat and writmaps.dat

ml> i'm looking for updated readmaps.dat and writmaps.dat that use CP437
ml> instead of IBMPC... hopefully the format of these two files has not

 DH> I'd be interested in this also -- I've had no luck getting TimEd to
 DH> display russian characters!

i see you are running the original like i am... v1.10 with the y2k patch...
i dug around and found that the first thing i was unable to do was use
CP437... it wasn't recognized at all and there was no CHRS control line
generated... i finally located another program that uses the same dat
files... MsgED... pulled some from there that were specifically set for
CP437, put them in place and tried... no luck... using the
READchangecharset option didn't show me any available character sets other
than IBMPC... i had to put the old dat files back in place and then TimED
would show all the character sets in them...

 DH> Please let me know if you succeed!

sadly, i don't think it is going to happen with what we're using right
now... both TimED and MsgED were written to FSC-0054 which has now been
superceeded by FTS-5003... as such, both were hardcoded for IBMPC and other
characterset names which were not really proper then and are definitely not
proper now... these days everything is CPxxx which are also going by the
wayside  as everything moves more to UTF-8 or UTF-16... UTF-8 works for
everything that i'm aware of but there are problems at times in conversion
to/from the old CPxxx stuff... we can easily go one way but not the
other... why? because CPxxx fits within UTF-8 but UTF-8 has more characters
than any of the CPxxx  sets...

while TimED's (and MsgED's) code has been released, not much has been done
with it... the original DOS and OS2 versions that we are running were
written and compiled with Watcom C... i'm not a C coder so there's very
little that i could do even if i wanted to...

as far as displaying russian characters goes, the way things are done
currently, the old school way, you'd have to switch your codepage to one
that contain those characters... right now you are most likely either CP437
or CP850... type chcp at the command line to tell you... when you know the
codepage that has those characters, then you would use chcp to change by
entering its number (ie: chcp 850 will set CP850... go back to CP437 with
chcp 437)... the problem is that when you change, you'll be totally
immersed and if the normal latin characters we're used to seeing are not
where we are used to finding them, then everything may be gibberish...
blindly typing chcp 437 should get you back to something recognizable...
unless you read russian or whatever language the codepage you switched to
uses ;)

the current choices with the available dat files are IBMPC, CANADIAN,
DUTCH, FINNISH, FRENCH, GERMAN, ISO-60, ITALIAN, NORWEG, PORTU, SPANISH,
SWEDISH, SWISS, UK, LATIN-1, and MAC... even the CP437 dat files i found
only replace IBMPC with CP437... everything else is still basically the
same...

)\/(ark

* Origin: (1:3634/12)
SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 953
@PATH: 3634/12 123/500 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

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™.