[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ISO 2022

Frank da Cruz wrote on 1999-11-05 18:52 UTC:
> I suppose you could also cat it directly if xterm had a Cyrillic font
> with cp866 encoding.  I don't know, maybe it does.

If you want to get a CP866 font for xterm, then just get and unpack

  http://www.cl.cam.ac.uk/~mgk25/download/ucs-fonts.tar.gz

and copy into the same directory

  ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP866.TXT

Then simply enter

  ./ucs2any.pl 9x18.bdf CP866.TXT Microsoft-CP866
  bdftopcf <9x18-Microsoft-CP866.bdf >9x18-Microsoft-CP866.pcf
  gzip -9 9x18-Microsoft-CP866.pcf

and enjoy your new 8-bit font antiquity.

BTW: Over the weekend, I will make the probably last major change to the
ucs-font package: At the moment, some fonts have their glyphs
left-aligned (right pixel column free for inter-character spacing) and
some have their glyphs right-aligned (left column free). This looks like
a historic accident, and I think I will make all fonts left-aligned
(like 6x13), to simplify maintenance and to allow the fonts to be used
together. I did this already for 12x13ja to allow it to be used with
6x13 without glyphs touching each other. Are there any specific reasons
to prefer right alignment? I prefer left-alignment, because this causes
most characters to be aligned with their reference point and because the
default 6x13 font has it this way. I also think (haven't checked
though), that the xterm default boldening method moves the glyph one to
the right to overstrike it.

Markus

-- 
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org,  WWW: <http://www.cl.cam.ac.uk/~mgk25/>

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/