From: Damjan <[EMAIL PROTECTED]>
> > I couldn't load ACM's with any kbd package (1.04 including).
> > I tried "setfont -m", and "mapscrn"
>
> Unfortunately I am not quite sure what an ACM is.
An ACM is "Application Charset Map" the same thing as the screen maps,
but an ACM converts bytes to Unicode values.
There must be a misunderstanding here about what a screen map is.
It is a reordering of a font. Often a permutation.
Has little relation to character sets or encoding,
and is typically used to adapt to a hardware font
built into the video ROM of some card.
On the other hand, a unicode map gives the unicode value(s)
for glyphs in a font. It can be given separately, but is
usually part of the font file.
For example, iso02_to_cp1250.trans is a screen map, and contains
...
0x85 0x85 # HORIZONTAL ELLIPSIS
0x86 0x86 # DAGGER
0x87 0x87 # DOUBLE DAGGER
0x88 0x88 # UNDEFINED
0x89 0x89 # PER MILLE SIGN
0x8A 0xA9 # LATIN CAPITAL LETTER S WITH CARON
0x8B 0x8B # SINGLE LEFT-POINTING ANGLE QUOTATION MARK
0x8C 0xA6 # LATIN CAPITAL LETTER S WITH ACUTE
0x8D 0xAB # LATIN CAPITAL LETTER T WITH CARON
...
and koi8r.uni is a unicode map, and contains
...
0xbe U+256c
0xbf U+00a9
0xc0 U+044e
0xc1 U+0430
0xc2 U+0431
0xc3 U+0446
...
> I have no problems loading screen maps with mapscrn
> or setfont -m. If an ACM is a screenmap, can you send
> me the file you try to load?
> Maybe I have to add some compatibility mode to kbd
> in case console-tools has changed the format.
console-tools supports two formats:
- byte -> unicode
where unicode can be a hex number in the form U+xxxx
or an UTF-8 character enclosed in single quotes.
- byte -> font_index
which is the equivalent of loading a "byte -> U+F000 | font_index"
font map.
I'll send you an example cp1251.acm in private mail.
OK, so you are trying to load a unimap, and console-tools
has added some strange representation. Looking at it puts
my xterm into strange modes. Let me paste from emacs:
...
0x8e 'Ð\213'
0x8f 'Ð\217'
0x90 'Ñ''
0x91 'â\200\230'
0x92 'â\200\231'
...
Hmm. Binary stuff is a bad idea in such files, but perhaps
a true UTF-8 fan does not regard this as binary.
Anyway, I made loadunimap and setfont recognize also this
version of unimaps. Reading it and dumping it again, I get
...
0x8e U+040b
0x8f U+040f
0x90 U+0452
0x91 U+2018
0x92 U+2019
...
Andries
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
