1
0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-26 07:33:47 +00:00
emacs/etc/charsets
Paul Eggert bc511a64f6 Prefer HTTPS to FTP and HTTP in documentation
Most of this change is to boilerplate commentary such as license URLs.
This change was prompted by ftp://ftp.gnu.org's going-away party,
planned for November.  Change these FTP URLs to https://ftp.gnu.org
instead.  Make similar changes for URLs to other organizations moving
away from FTP.  Also, change HTTP to HTTPS for URLs to gnu.org and
fsf.org when this works, as this will further help defend against
man-in-the-middle attacks (for this part I omitted the MS-DOS and
MS-Windows sources and the test tarballs to keep the workload down).
HTTPS is not fully working to lists.gnu.org so I left those URLs alone
for now.
2017-09-13 15:54:37 -07:00
..
README Prefer HTTPS to FTP and HTTP in documentation 2017-09-13 15:54:37 -07:00

# README file for charset mapping files in this directory.

# Copyright (C) 2003-2017 Free Software Foundation, Inc.
# Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011
#   National Institute of Advanced Industrial Science and Technology (AIST)
#   Registration Number H13PRO009

# 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 3 of the License, 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.  If not, see <https://www.gnu.org/licenses/>.

(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 files in the
admin/charsets directory in the Emacs source.