1. xemacs
  2. mule-ucs


stephent  committed e770198

doc updates <873czewip4.fsf@tleepslib.sk.tsukuba.ac.jp>

  • Participants
  • Parent commits 2d8c744
  • Branches default

Comments (0)

Files changed (3)

File ChangeLog

View file
+2002-03-06  Simon Josefsson <jas@extundo.com>
+	* doc/mule-ucs.texi (Overview):
+	* README.XEmacs: 
+	Typo fix in init file example.
+2002-02-07  Stephen J. Turnbull  <stephen@xemacs.org>
+	* doc/mule-ucs.texi (Top): Fixup copyrights.  Add information
+	about bug reporting.  Add a little more information about
+	un-define-change-charset-order'.
+2002-01-25  Stephen J. Turnbull  <stephen@xemacs.org>
+	* doc/mule-ucs.texi (Overview): Document input method and charset
+	ordering issues.
 2002-01-07  Adrian Aichner  <adrian@xemacs.org>
 	* Makefile (HTML_FILES): New.

File README.XEmacs

View file
 For UTF-8, also include
 (set-coding-priority-list '(utf-8))
-(set-coding-category-system 'utf-8 utf-8)
+(set-coding-category-system 'utf-8 'utf-8)
 in your init file.  UTF-8 has a very characteristic signature; false
 negatives and positives should be very rare.  UTF-16 is difficult and

File doc/mule-ucs.texi

View file
 @c Version values, for easy modification
 @set VERSION $Revision$
-@set UPDATED Thursday, 13 December, 2001
+@set UPDATED 25 January 2002
 @c Entries for @command{install-info} to use
 @c Copying permissions, et al
-This file documents Mule-UCS, a package providing efficient Lisp-based
-coding support (specifically, Unicode) for Emacs and XEmacs.
+This file documents the XEmacs package distribution of Mule-UCS, a
+package providing efficient Lisp-based coding support (specifically,
+Unicode) for Emacs and XEmacs.
 Copyright @copyright{} 1997 MIYASHITA Hisashi
-Copyright @copyright{} 2001 Stephen J. Turnbull
+Copyright @copyright{} 2001, 2002 Free Software Foundation, Inc.
 Permission is granted to make and distribute verbatim copies of this
 manual provided the copyright notice and this permission notice are
 This is version @value{VERSION} of the Mule-UCS manual, last updated on
+@value{UPDATED}.  It documents the XEmacs package distribution of
+Mule-UCS.  It should be applicable to other versions of Mule-UCS with
+slight changes.  Please report errors and variations among platforms to
+@email{stephen@@xemacs.org,Stephen Turnbull}, for incorporation in
+future versions of this manual.
 @c You can find the latest version of this document on the web at
 @c @uref{http://www.xemacs.org/}.
 Copyright (C) 1998, 1999, 2000 Free Software Foundation, Inc.
+This file is part of the XEmacs distribution of Mule-UCS.
 Mule-UCS 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
 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
+with XEmacs; see the file COPYING. If not, write to the Free Software
 Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
 (set-coding-priority-list '(utf-8))
-(set-coding-category-system 'utf-8 utf-8)
+(set-coding-category-system 'utf-8 'utf-8)
 @end example
 implemented in XEmacs itself.  Mule-UCS provides some utilities in the
 @file{un-tools} library, but these are of unknown reliability.
+Since Mule-UCS uses regular Mule code internally, and does not create an
+internal Mule charset for UCS, your normal input methods, whether native
+(Wnn), Lisp + backend (new Tamago), all in Lisp (Quail), or XIM-based
+(kinput2) should work with Unicode files without any change in your
+setup or habits.  Input methods supported by terminals (cxterm,
+localized keyboards) should also work (if they work on the native
+Chinese!) as long as the terminal coding system is set properly by
+Mule-UCS was written by a Japanese and thus gives priority to Japanese
+by default.  This means that Unicode characters that are unified from
+various Asian character sets (eg, the single horizontal stroke meaning
+"one" is present in all of them) will be presented in the Mule buffer as
+Japanese characters, and displayed with a Japanese font.  @emph{No
+information will be lost or corrupted} as long as you @emph{save back to
+Unicode}.  (That's what "unification" means.)
+However, if you wish to use Mule-UCS to translate Unicode to national
+subsets other than ASCII, Latin-1, and Japanese, you must change the
+priorities.  This also allows you to satisfy cultural preferences for
+glyph styles by defaulting to an appropriate font.  Use
+@samp{un-define-change-charset-order}.  For the common case of the Latin
+character sets, where by international standard as well as common
+practice characters common to more than one character set are considered
+identical (not "unified" as for the Han characters in Unicode), the
+@file{latin-unity} package may be of use.
+@c #### need examples of un-define-change-charset-order usage
+(Mule-UCS does not understand Plane 14 tags.  Therefore attempts to
+translate multilingual texts into non-Unicode encodings such as ISO 2022
+will have to be done by hand.)
 That is all that most users of Mule-UCS need to know.
 Mule-UCS is still under development and any problems you encounter,
-trivial or major, should be reported to the Mule-UCS developers.
+trivial or major, should be reported to the Mule-UCS developers.  Use
+the standard package bug address @email{mule-ucs-bugs@xemacs.org}.
 @c #### @xref{Bug Reports}.
 @subsubheading Behind the scenes
 This section tries to explain what goes on behind the scenes when you
 visit a file encoded in Unicode with Mule-UCS.
+#### to be written
 @c For the end user
 @node Obtaining Mule-UCS, History, Overview, Top
 @chapter Obtaining Mule-UCS.