view etc/charsets/README @ 91137:00323e98bffb

Don't include Freetype headers. Include "ftfont.h". (struct ftfont_info) [HAVE_LIBOTF]: New members maybe_otf and otf. (ftfont_open) [HAVE_LIBOTF]: Initialize the above members. (ftfont_driver) [HAVE_LIBOTF, HAVE_M17N_FLT]: Don't set font_otf_capability and font_drive_otf, set ftfont_shape. (ftfont_list): Adjusted for the change of :otf property value. (struct MFLTFontFT) [HAVE_LIBOTF, HAVE_M17N_FLT]: New struct. (ftfont_get_glyph_id, ftfont_get_metrics, ftfont_check_otf) (adjust_anchor, ftfont_drive_otf, ftfont_shape_by_flt) (ftfont_shape) [HAVE_LIBOTF, HAVE_M17N_FLT]: New function.s (DEVICE_DELTA) [HAVE_LIBOTF, HAVE_M17N_FLT]: New macro. (otf_gstring, gstring, m17n_flt_initialized): New variables.
author Kenichi Handa <handa@m17n.org>
date Sat, 01 Dec 2007 02:39:27 +0000
parents b875692f1ec6
children 4595caa03b6b
line wrap: on
line source

# README file for charset mapping files in this directory.
# Copyright (C) 2003
#   National Institute of Advanced Industrial Science and Technology (AIST)
#   Registration Number H13PRO009
# Copyright (C) 2003 Free Software Foundation, Inc.

# This file is part of GNU Emacs.

# GNU Emacs is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.

# GNU Emacs is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.

# You should have received a copy of the GNU General Public License
# along with GNU Emacs; see the file COPYING.  If not, write to
# the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.


(1) Format of mapping files

Each line contains a code point and the corresponding Unicode
character code separated by a space.  Both code points and Unicode
character codes are in hexadecimal preceded by "0x".  Comments may be
used, starting with "#".  Code ranges may also be used, with
(inclusive) start and end code points separated by "-" followed by the
unicode of the start of the range

Examples:
0xA0 0x00A0  # no-break space

0x8141-0x8143 0x4E04 # map onto a Unicode range


(2) Source of mapping files

All mapping files are generated automatically from data files freely
available on the Internet (e.g. glibc/localedata/charmaps").  See the
file ../../admin/charsets/Makefile for the detail.