Differences between extended ASCII character sets
If you find that your extended ASCII implementation does not have characters in the same positions as the one in bineas.dat, note the positions of those codes, and then enter a unique value between 07100 and 07777 in the corresponding position of your new file. These codes represent punch combinations which are relatively rare, having punches ‘&–0’ all set.
The code you choose acts as a marker to prevent Quantum replacing the code with a blank. For example, if ä is code 222 under your implementation of the extended ASCII character set, you might choose punch code 07111 to represent it. When Quantum reads ä, it stores code 07111; when it writes out the data, it reads this code and, when it looks it up in bintab.qt, find that it represents ä. You therefore find ä in the new data file.
You can then convert your code file as described above.
If you prefer, you can create a new input code file rather than editing one of those provided. You can enter codes in octal, decimal or hexadecimal as long as all codes in the file are of the same format, and each code is separated from its neighbors by white space, either spaces, tabs or new-lines.
Note Before you attempt this, contact UNICOM Systems, Inc.
To convert the file
When you are ready to convert the text file, type:
bintab [-odhx] input output
Parameters
-odhx
See below.
input
The name of the file you have created.
output
The name under which the binary conversion is to be saved.
Options
The options indicate what type of values the file contains:
–o
octal (this is the default and may be omitted)
–d
decimal
–h
hexadecimal
–x
hexadecimal
See also