Home Page The Club Computers News Links Glossary EYAWTK
Before Amiga Background ICS OCS ECS AGA ??? PPC
U-Boot SLB Linux Amiga OS Dual Boot Motherboards Peripherals Other
Initialisation Installation OS4 Updates About OS4 File Systems Networking Printing Other
Introduction File System Workbench Preferences Commands Error Msgs Miscellaneous

AmigaOS 4.0 - About OS4 - Commands

BUILDMAPTABLE Obsolete
Purpose: Create a binary mapping table to Unicode for diskfont.library from an ASCII mapping table.
Format: BUILDMAPTABLE <Unicode mapping table> [CHARSET <character set>]
Template: UNICODEMAPTABLE/A, CHARSET/K
Path: C:BUILDMAPTABLE

This command became obsolete with AmigaOS 4.0 Final - details shown for information only

The Amiga's Operating System only supports a character set of 256 characters, each allocated a system number from 0-255 (although some numbers are reserved for special printing/display-terminal functions like carriage return and line feed). The operating system associates a default, predefined character (or, 'glyph') to each displayable system number depending on the language being supported. (The glyphs for letters A-Z and a-z and the numerals 0-9 are allocated in the system number range of 48-112 along with some punctuation marks for operating systems intended to display this page.) The appearance, or font style, of the individual glyphs can be changed by selecting an alternative font style (e.g. 'Times'). However, some fonts do not have glyphs defined for all of the displayable operating system character numbers.

Some programs support many more than 256 characters (glyphs) because they represent characters in document files by using the Unicode character set (an international standard with a potential of hundreds of thousands, even millions, of characters).

In order for these programs to display the document characters on the screen, send them to a printer or create a PDF file, they have to translate from the Unicode number in the file to the appropriate system number for the operating system and language being used. This applies to both printable and non-printable characters such as names of variables, style tags, and element names. If a dialogue box is used to change, for example, a style tag, the programs have to translate the characters selected in the dialogue box (and therefore conforming to the operating system character set) into Unicode before inserting them as non-printable characters into the document file. The same is true of printable text typed into a program's text frames and boxes.

BUILDMAPTABLE converts Charset-To-Unicode mapping tables in text form (e.g. available at http://www.unicode.org/Public/MAPPINGS/) to mapping tables in binary form usable by diskfont.library.

You must specify a <Unicode mapping table> name when using the BUILDMAPTABLE command.

BUILDMAPTABLE can either display a text form of the parsed table or create a binary mapping table in the L:Charsets/ directory. Currently only 8bit charset mapping tables are supported.

If L:Charsets/character-sets or L:Charsets/custom-character-sets contains a MIME name for an 8bit charset where no mapping table in L:Charsets/ does exist, and you have a mapping table in text form, use BUILDMAPTABLE to create the binary mapping table and reboot (diskfont.library searches tables only once) to be able to use the new charset (e.g. in fonts or catalog files).

The expected format of text mapping tables is as follows:

  • Anything from a '#' character to the end of a line is considered a comment.
  • A valid line does contain the index on the left and the Unicode code point at the right side, in either hexadecimal (starting with 0x or 0X) or octal (starting with 0) or decimal form, separated by empty space, for example:   0xA4     0x20AC   #     EURO SIGN.
The CHARSET <character set> argument can be used to specify a MIME charset name or alias. The MIME charset name obtained from diskfont.library will be used as file name of the binary charset mapping table which will be stored in L:Charsets/. If the CHARSET parameter is omitted, no file will be written, instead the resulting mapping table is displayed in text form.

Example 1:

3.OS4:> BUILDMAPTABLE CP1258.TXT will parse the text file CP1258.TXT and display a list of entries with the index on the left and the Unicode codepoint at the right side. Note: unmapped entries (with Unicode codepoint 0) are not displayed.

Example 2:

3.OS4:> BUILDMAPTABLE 8859-1.TXT CHARSET LATIN1 will parse the text file 8859-1.TXT and create the file L:Charsets/ISO-8859-1 (latin1 is an alias for ISO-8859-1) which is useless (the ISO-8859-1 mapping table is a builtin part of diskfont.library and will not be loaded from disk).


Return to Commands Selection

Disclaimer: Amiga Auckland have prepared the above information for the use of its members based on our experiences and as such is subject to revision at any time. Amiga Auckland cannot guarantee any of the information and cannot be held accountable for any issues that may result from using it.


Copyright 2006 Amiga Auckland Inc. All rights reserved.
Revised: December 24, 2006.