trans130 Introduction

Copyright (c) 1993-2000 by Kostis Netzwerkberatung
Talstr. 25, D-63322 Rödermark, Tel. +49 6074 881056, FAX 881058
kosta@kostis.net (Kosta Kostis), http://www.kostis.net/

This information may be used free of charge at your own risk.

trans Character Encoding Converter Generator Package

This is a snapshot of a work in progress. Things may change, other things may be added/removed. Please wait for the release. Sorry, no date scheduled, yet.

You may use this package free of charge at your own risk but you may not sell this package.

Should you be interested in using any component of this package in a commercial package you must contact me first to find terms. Don't worry, it won't cost you a leg and an arm, I just want to make sure that if there is money made out of this it doesn't pass me by completely. ;)

Currently there are 80 different Character Encoding Description Files supplied with this package, not counting the following files:

iso6429, iso646 (which are included by many other files)
iso10646, iso10646.mes (these are here for reference purposes)

trans covers 7-bit encodings such as ISO 646, 8-bit encodings such as many MS-DOS Codepages (also for IBM OS/2), Microsoft Windows Codepages, ISO 8859, HP, Adobe, Apple Macintosh, Atari, NeXTSTEP Character Encodings, some EBCDIC Encodings, koi8-r and a few more...

Should your favourite Character Encoding be missing, please contribute!

Where to get updates

The latest version of this package should be available at:

http://www.kostis.net/freeware/

How to create a Character Encoding Converter

To create translators, use make to compile, link and install all trans tools, first. Installing means moving the executables into a directory included in your command search path. In order to do that, check Makefile which uses "/usr/local/bin" as the default directory for installing binaries which you probably want to change.

Example: U*IX (e. g. Linux)

#
# use gcc
#
make # compile trans executables

Makefile offers a couple of options which you may want to use:

make install # this copies executables to /usr/local/bin
make clean # this deletes objects and executables - never mind warnings

make check # check cedf files (create error.log)

make html # create HTML tables from cedf files (check destination in Makefile)
make list # create list of cedf files (create encoding.lis)

make date # for my personal use only ;)
make pack # for my personal use only ;)
make uni # for my personal use only :) (unierror.lis)

SunOS using gcc seems to require

make COPTS='-DFILENAME_MAX=200 -DNO_STRUPR -O6'

After that, please change your working directory to the "bin" directory.

Please set an enviroment variable TRANS that points to the directory where this package resides on your computer *including* the trailing directory separator character

e. g.: TRANS="/usr/local/src/charsets/trans130/"

All Character Encoding Description Files reside in the cedf subdir.

If you don't set a variable TRANS the default location "/usr/local/lib/trans/" will be assumed (see file "tab.h", DIR_TRANS).

To test the translator generator after have done at least "make" and "make install", type

cd "$TRANS"bin
one

This should generate two translators between ISO 8859-1 and MS-DOS Codepage 850. Each translator consists of three files (e.g.):

isox850.c		the main program
isox850.h		the header file
isox850.tab		the translation table file

Each translator will #include the files

trans.c		the main invariant program
trans.h		the main invariant header file

You should be able to compile and link isox850.c and 850xiso.c easily. Read transtab.man to learn more about the syntax for transtab.

Have a look at maketabs respectively to get an inspiration for program names.

This package is written in ANSI-C using the two non-ANSI functions strdup () and strupr (). Sources for these functions are supplied should your compiler/library not contain them. Should you encounter any problems while trying to compile this package, your compiler is very likely not ANSI-C compliant. Should your compiler be ANSI-C compliant and still report warnings and/or errors, please let me know. I'll need the following data in order to to help you:

• Version of this package (e. g. V1.30)
• Operating System and Version
• Compiler name and Version
• Compiler options used (if any)

Directory tree for this package

The directory tree for this utility should look like this: