CVS update by stephent xemacs/etc/unicode/unicode-consortium,
GB12345.TXT, KSC5601.TXT ...
xemacs-cvs at xemacs.org
xemacs-cvs at xemacs.org
Sat Jan 27 13:29:09 EST 2007
User: stephent
Date: 07/01/27 19:29:09
Modified: xemacs/etc/unicode/unicode-consortium BIG5.TXT CNS11643.TXT
GB12345.TXT JIS0201.TXT JIS0208.TXT JIS0212.TXT
KSC5601.TXT OLD5601.TXT SHIFTJIS.TXT
Added: xemacs/etc/unicode/unicode-consortium COPYING oreilly.html
unicode-consortium.html
Log:
Fix up copying situation in etc/unicode/unicode-consortium. <87mz4471zg.fsf at uwakimon.sk.tsukuba.ac.jp>
Revision Changes Path
1.78 +25 -0 XEmacs/xemacs/etc/ChangeLog
Index: ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/ChangeLog,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -p -r1.77 -r1.78
--- ChangeLog 2006/12/29 18:09:38 1.77
+++ ChangeLog 2007/01/27 18:28:57 1.78
@@ -1,3 +1,28 @@
+2007-01-28 Stephen J. Turnbull <stephen at xemacs.org>
+
+ Thanks to Mike Fabian <mfabian at suse.de> for bringing the issue
+ to my attention.
+
+ * unicode/unicode-consortium/COPYING:
+ * unicode/unicode-consortium/oreilly.html
+ * unicode/unicode-consortium/unicode-consortium.html
+ New files clarifying copying conditions for mapping tables.
+
+ * unicode/unicode-consortium/GB12345.TXT
+ * unicode/unicode-consortium/BIG5.TXT
+ * unicode/unicode-consortium/CNS11643.TXT
+ * unicode/unicode-consortium/HANGUL.TXT
+ * unicode/unicode-consortium/JIS0201.TXT
+ * unicode/unicode-consortium/JIS0208.TXT
+ * unicode/unicode-consortium/JIS0212.TXT
+ * unicode/unicode-consortium/JOHAB.TXT
+ * unicode/unicode-consortium/KSC5601.TXT
+ * unicode/unicode-consortium/KSX1001.TXT
+ * unicode/unicode-consortium/OLD5601.TXT
+ * unicode/unicode-consortium/SHIFTJIS.TXT
+ Mapping tables downloaded from a Unicode, Inc. URL with
+ permissive conditions.
+
2006-12-21 Aidan Kehoe <kehoea at parhasard.net>
* unicode/unicode-consortium/8859-7.TXT:
1.3 +33 -26 XEmacs/xemacs/etc/unicode/unicode-consortium/BIG5.TXT
Index: BIG5.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/BIG5.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- BIG5.TXT 2002/03/13 08:51:40 1.2
+++ BIG5.TXT 2007/01/27 18:29:03 1.3
@@ -4,8 +4,6 @@
# Table version: 0.0d3
# Table format: Format A
# Date: 11 February 1994
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,9 +23,22 @@
#
# General notes:
#
-# This table contains the data Metis and Taligent currently have on how
-# BIG5 characters map into Unicode.
#
+# This table contains one set of mappings from BIG5 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of BIG5 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# BIG5 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between BIG5 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
# WARNING! It is currently impossible to provide round-trip compatibility
# between BIG5 and Unicode.
#
@@ -52,37 +63,33 @@
#
# 1. In addition to the above, there is some uncertainty about the
# mappings in the range C6A1 - C8FE, and F9DD - F9FE. The ETEN
-# version of BIG5 organizes the former range differently, and adds
-# additional characters in the latter range. The correct mappings
-# these ranges need to be determined.
+# version of BIG5 organizes the former range differently, and adds
+# additional characters in the latter range. The correct mappings
+# these ranges need to be determined.
#
# 2. There is an uncertainty in the mapping of the Big Five character
-# 0xA3BC. This character occurs within the Big Five block of tone marks
-# for bopomofo and is intended to be the tone mark for the first tone in
-# Mandarin Chinese. We have selected the mapping U+02C9 MODIFIER LETTER
-# MACRON (Mandarin Chinese first tone) to reflect this semantic.
-# However, because bopomofo uses the absense of a tone mark to indicate
-# the first Mandarin tone, most implementations of Big Five represent
-# this character with a blank space, and so a mapping such as U+2003 EM SPACE
-# might be preferred.
-#
-#
+# 0xA3BC. This character occurs within the Big Five block of tone marks
+# for bopomofo and is intended to be the tone mark for the first tone in
+# Mandarin Chinese. We have selected the mapping U+02C9 MODIFIER LETTER
+# MACRON (Mandarin Chinese first tone) to reflect this semantic.
+# However, because bopomofo uses the absense of a tone mark to indicate
+# the first Mandarin tone, most implementations of Big Five represent
+# this character with a blank space, and so a mapping such as U+2003 EM
+# SPACE might be preferred.
#
# Format: Three tab-separated columns
# Column #1 is the BIG5 code (in hex as 0xXXXX)
# Column #2 is the Unicode (in hex as 0xXXXX)
# Column #3 is the Unicode name (follows a comment sign, '#')
-# The official names for Unicode characters U+4E00
-# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
-# where XXXX is the code point. Including all these
-# names in this file increases its size substantially
-# and needlessly. The token "<CJK>" is used for the
-# name of these characters. If necessary, it can be
-# expanded algorithmically by a parser or editor.
+# The official names for Unicode characters U+4E00
+# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
+# where XXXX is the code point. Including all these
+# names in this file increases its size substantially
+# and needlessly. The token "<CJK>" is used for the
+# name of these characters. If necessary, it can be
+# expanded algorithmically by a parser or editor.
#
# The entries are in BIG5 order
-#
-# Any comments or problems, contact <John_Jenkins at taligent.com>
#
#
0xA140 0x3000 # IDEOGRAPHIC SPACE
1.3 +32 -23 XEmacs/xemacs/etc/unicode/unicode-consortium/CNS11643.TXT
Index: CNS11643.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/CNS11643.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- CNS11643.TXT 2002/03/13 08:51:41 1.2
+++ CNS11643.TXT 2007/01/27 18:29:04 1.3
@@ -4,7 +4,6 @@
# Table version: 0.0d1
# Table format: Format A
# Date: 21 October 1994
-# Author: John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -24,9 +23,23 @@
#
# General notes:
#
-# This table contains the data currently has on how
-# CNS 11643-1986 characters map into Unicode.
#
+# This table contains one set of mappings from CNS 11643-1986 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of CNS 11643-1986 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# CNS 11643-1986 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between CNS 11643-1986 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
+#
# WARNING! It is currently impossible to provide round-trip compatibility
# between CNS 11643-1986 and Unicode.
#
@@ -42,7 +55,7 @@
# duplicate versions of some ideographs which are included in Unicode only
# once. They include the following:
#
-# 0x1243E through 0x12440, HANGZHOU NUMERAL TEN, TWENTY, and THIRTY
+# 0x1243E through 0x12440, HANGZHOU NUMERAL TEN, TWENTY, and THIRTY
# 0x12721 through 0x12939, KangXi radical set
#
# Entries for these characters are not included in this table.
@@ -50,32 +63,28 @@
# Notes:
#
# 1. There is an uncertainty in the mapping of the CNS 11643-1986 character
-# 0x1256D. This character occurs within the CNS 11643-1986 block of tone marks
-# for bopomofo and is intended to be the tone mark for the first tone in
-# Mandarin Chinese. We have selected the mapping U+02C9 MODIFIER LETTER
-# MACRON (Mandarin Chinese first tone) to reflect this semantic.
-# However, because bopomofo uses the absense of a tone mark to indicate
-# the first Mandarin tone, most implementations of CNS 11643-1986 represent
-# this character with a blank space, and so a mapping such as U+2003 EM SPACE
-# might be preferred.
-#
-#
+# 0x1256D. This character occurs within the CNS 11643-1986 block of tone marks
+# for bopomofo and is intended to be the tone mark for the first tone in
+# Mandarin Chinese. We have selected the mapping U+02C9 MODIFIER LETTER
+# MACRON (Mandarin Chinese first tone) to reflect this semantic.
+# However, because bopomofo uses the absense of a tone mark to indicate
+# the first Mandarin tone, most implementations of CNS 11643-1986
+# represent this character with a blank space, and so a mapping such as
+# U+2003 EM SPACE might be preferred.
#
# Format: Three tab-separated columns
# Column #1 is the CNS 11643-1986 code (in hex as 0xXXXXX)
# Column #2 is the Unicode (in hex as 0xXXXX)
# Column #3 is the Unicode name (follows a comment sign, '#')
-# The official names for Unicode characters U+4E00
-# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
-# where XXXX is the code point. Including all these
-# names in this file increases its size substantially
-# and needlessly. The token "<CJK>" is used for the
-# name of these characters. If necessary, it can be
-# expanded algorithmically by a parser or editor.
+# The official names for Unicode characters U+4E00
+# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
+# where XXXX is the code point. Including all these
+# names in this file increases its size substantially
+# and needlessly. The token "<CJK>" is used for the
+# name of these characters. If necessary, it can be
+# expanded algorithmically by a parser or editor.
#
# The entries are in CNS 11643-1986 order
-#
-# Any comments or problems, contact <John_Jenkins at taligent.com>
#
#
0x12121 0x3000 # IDEOGRAPHIC SPACE
1.3 +10 -14 XEmacs/xemacs/etc/unicode/unicode-consortium/GB12345.TXT
Index: GB12345.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/GB12345.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- GB12345.TXT 2002/03/13 08:51:48 1.2
+++ GB12345.TXT 2007/01/27 18:29:04 1.3
@@ -7,21 +7,17 @@
# Author: Glenn Adams <glenn at metis.com>
# John H. Jenkins <John_Jenkins at taligent.com>
#
-# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
+# The Name above appears to be inaccurate; this is in fact the
+# table for the 1990 revision of GB12345.
#
-# This file is provided as-is by Unicode, Inc. (The Unicode Consortium).
-# No claims are made as to fitness for any particular purpose. No
-# warranties of any kind are expressed or implied. The recipient
-# agrees to determine applicability of information provided. If this
-# file has been provided on magnetic media by Unicode, Inc., the sole
-# remedy for any claim will be exchange of defective media within 90
-# days of receipt.
-#
-# Recipient is granted the right to make copies in any form for
-# internal distribution and to freely use the information supplied
-# in the creation of products supporting Unicode. Unicode, Inc.
-# specifically excludes the right to re-distribute this file directly
-# to third parties or other organizations whether for profit or not.
+# This file was copied into XEmacs from
+# http://examples.oreilly.com/cjkvinfo/unicode/gb12345-90.txt
+# and is covered by the O'Reilly Associates copying policy in
+# http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html.
+# A copy of that notice is in oreilly.html in this directory. This
+# data file is an appendix to the book *Chinese, Japanese, Korean,
+# and Vietnamese Information Processing* by Ken Lunde, published by
+# O'Reilly Associates (ISBN-13 978-1565922242).
#
# General notes:
#
1.3 +16 -10 XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0201.TXT
Index: JIS0201.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0201.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- JIS0201.TXT 2002/03/13 08:51:50 1.2
+++ JIS0201.TXT 2007/01/27 18:29:04 1.3
@@ -4,8 +4,6 @@
# Table version: 0.9
# Table format: Format A
# Date: 8 March 1994
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,21 +23,29 @@
#
# General notes:
#
-# This table contains the data the Unicode Consortium has on how
-# single-byte JIS X 0201 characters map into Unicode 1.1
-# (ISO/IEC 10646:1-1993 UCS-2).
#
+# This table contains one set of mappings from JIS X 0201 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of JIS X 0201 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# JIS X 0201 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between JIS X 0201 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
+#
# Format: Three tab-separated columns
# Column #1 is the shift JIS code (in hex as 0xXX)
# Column #2 is the Unicode (in hex as 0xXXXX)
# Column #3 the Unicode (ISO 10646) name (follows a comment sign)
#
# The entries are in JIS order
-#
-# These mappings are provisional, pending definition of
-# official mappings by Japanese standards bodies.
-#
-# Any comments or problems, contact <John_Jenkins at taligent.com>
#
#
0x20 0x0020 # SPACE
1.3 +23 -11 XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0208.TXT
Index: JIS0208.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0208.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- JIS0208.TXT 2002/03/13 08:51:50 1.2
+++ JIS0208.TXT 2007/01/27 18:29:04 1.3
@@ -4,8 +4,6 @@
# Table version: 0.9
# Table format: Format A
# Date: 8 March 1994
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,21 +23,35 @@
#
# General notes:
#
-# This table contains the data the Unicode Consortium has on how
-# JIS X 0208 (1983) characters map into Unicode.
#
+# This table contains one set of mappings from JIS X 0208 (1990) into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of JIS X 0208 (1990) and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# JIS X 0208 (1990) and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between JIS X 0208 (1990)
+# and Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
+#
# Format: Four tab-separated columns
# Column #1 is the shift-JIS code (in hex)
# Column #2 is the JIS X 0208 code (in hex as 0xXXXX)
# Column #3 is the Unicode (in hex as 0xXXXX)
# Column #4 the Unicode name (follows a comment sign, '#')
-# The official names for Unicode characters U+4E00
-# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
-# where XXXX is the code point. Including all these
-# names in this file increases its size substantially
-# and needlessly. The token "<CJK>" is used for the
-# name of these characters. If necessary, it can be
-# expanded algorithmically by a parser or editor.
+# The official names for Unicode characters U+4E00
+# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
+# where XXXX is the code point. Including all these
+# names in this file increases its size substantially
+# and needlessly. The token "<CJK>" is used for the
+# name of these characters. If necessary, it can be
+# expanded algorithmically by a parser or editor.
#
# The entries are in JIS X 0208 order
#
1.3 +23 -11 XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0212.TXT
Index: JIS0212.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0212.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- JIS0212.TXT 2002/03/13 08:51:50 1.2
+++ JIS0212.TXT 2007/01/27 18:29:05 1.3
@@ -4,8 +4,6 @@
# Table version: 0.9
# Table format: Format A
# Date: 8 March 1994
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,20 +23,34 @@
#
# General notes:
#
-# This table contains the data the Unicode Consortium has on how
-# JIS X 0212 (1983) characters map into Unicode.
#
+# This table contains one set of mappings from JIS X 0212 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of JIS X 0212 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# JIS X 0212 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between JIS X 0212 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
+#
# Format: Three tab-separated columns
# Column #1 is the JIS X 0212 code (in hex as 0xXXXX)
# Column #2 is the Unicode (in hex as 0xXXXX)
# Column #3 the Unicode name (follows a comment sign, '#')
-# The official names for Unicode characters U+4E00
-# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
-# where XXXX is the code point. Including all these
-# names in this file increases its size substantially
-# and needlessly. The token "<CJK>" is used for the
-# name of these characters. If necessary, it can be
-# expanded algorithmically by a parser or editor.
+# The official names for Unicode characters U+4E00
+# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
+# where XXXX is the code point. Including all these
+# names in this file increases its size substantially
+# and needlessly. The token "<CJK>" is used for the
+# name of these characters. If necessary, it can be
+# expanded algorithmically by a parser or editor.
#
# The entries are in JIS X 0212 order
#
1.3 +16 -3 XEmacs/xemacs/etc/unicode/unicode-consortium/KSC5601.TXT
Index: KSC5601.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/KSC5601.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- KSC5601.TXT 2002/03/13 08:51:52 1.2
+++ KSC5601.TXT 2007/01/27 18:29:05 1.3
@@ -4,9 +4,22 @@
# Table version: 1.0
# Table format: Format A
# Date: 07/24/95
-# Authors: Lori Hoerth <lorih at microsoft.com>
-# K.D.Chang <a-kchang at microsoft.com>
-# General notes: none
+#
+# This table contains one set of mappings from KSC5601-1992 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of KSC5601-1992 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# KSC5601-1992 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between KSC5601-1992 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
#
# Format: Three tab-separated columns
# Column #1 is the Unified Hangeul code (in hex)
1.3 +16 -4 XEmacs/xemacs/etc/unicode/unicode-consortium/OLD5601.TXT
Index: OLD5601.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/OLD5601.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- OLD5601.TXT 2002/03/13 08:51:54 1.2
+++ OLD5601.TXT 2007/01/27 18:29:06 1.3
@@ -4,8 +4,6 @@
# Table version: 0.0d2
# Table format: Format A
# Date: 6 December 1993
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,8 +23,22 @@
#
# General notes:
#
-# This table contains the data Taligent and Metis currently have on how
-# KSC5601 characters map into Unicode.
+#
+# This table contains one set of mappings from KSC5601 into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of KSC5601 and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# KSC5601 and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between KSC5601 and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
#
# A number of alternative mappings have been suggested by a
# reviewer. They are as follows:
1.3 +23 -11 XEmacs/xemacs/etc/unicode/unicode-consortium/SHIFTJIS.TXT
Index: SHIFTJIS.TXT
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/SHIFTJIS.TXT,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- SHIFTJIS.TXT 2002/03/13 08:51:55 1.2
+++ SHIFTJIS.TXT 2007/01/27 18:29:06 1.3
@@ -4,8 +4,6 @@
# Table version: 0.9
# Table format: Format A
# Date: 8 March 1994
-# Authors: Glenn Adams <glenn at metis.com>
-# John H. Jenkins <John_Jenkins at taligent.com>
#
# Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved.
#
@@ -25,20 +23,34 @@
#
# General notes:
#
-# This table contains the data the Unicode Consortium has on how
-# Shift-JIS (a combination of JIS 0201 and JIS 0208) maps into Unicode.
#
+# This table contains one set of mappings from Shift-JIS into Unicode.
+# Note that these data are *possible* mappings only and may not be the
+# same as those used by actual products, nor may they be the best suited
+# for all uses. For more information on the mappings between various code
+# pages incorporating the repertoire of Shift-JIS and Unicode, consult the
+# VENDORS mapping data. Normative information on the mapping between
+# Shift-JIS and Unicode may be found in the Unihan.txt file in the
+# latest Unicode Character Database.
+#
+# If you have carefully considered the fact that the mappings in
+# this table are only one possible set of mappings between Shift-JIS and
+# Unicode and have no normative status, but still feel that you
+# have located an error in the table that requires fixing, you may
+# report any such error to errata at unicode.org.
+#
+#
# Format: Three tab-separated columns
# Column #1 is the shift-JIS code (in hex)
# Column #2 is the Unicode (in hex as 0xXXXX)
# Column #3 the Unicode name (follows a comment sign, '#')
-# The official names for Unicode characters U+4E00
-# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
-# where XXXX is the code point. Including all these
-# names in this file increases its size substantially
-# and needlessly. The token "<CJK>" is used for the
-# name of these characters. If necessary, it can be
-# expanded algorithmically by a parser or editor.
+# The official names for Unicode characters U+4E00
+# to U+9FA5, inclusive, is "CJK UNIFIED IDEOGRAPH-XXXX",
+# where XXXX is the code point. Including all these
+# names in this file increases its size substantially
+# and needlessly. The token "<CJK>" is used for the
+# name of these characters. If necessary, it can be
+# expanded algorithmically by a parser or editor.
#
# The entries are ordered by their Shift-JIS codes as follows:
# Single-byte characters precede double-byte characters
1.1 XEmacs/xemacs/etc/unicode/unicode-consortium/COPYING
Index: COPYING
===================================================================
COPYING for Unicode Consortium mapping files in XEmacs.
Copyright (c) 2007 The Free Software Foundation, Inc.
This file is part of XEmacs. It is licensed to you under the
conditions of the GNU General Public License, version 2 or any later
version published by the FSF, at your option.
Other files in this directory are subject to O'Reilly Media and
Unicode Consortium licenses. The files oreilly.html and
unicode-consortium.html are not part of XEmacs; they are property of
O'Reilly Media, Inc. and Unicode, Inc. respectively. They are
included here for informational purposes only, and may be
redistributed in verbatim form only. These files were downloaded from
those vendors on January 28, 2007. If you can't read them easily
(they probably require network connections for full functionality),
report a bug to XEmacs at <xemacs-beta at xemacs.org>.
The following files were copied from locations below
http://www.unicode.org/Public/MAPPINGS/OBSOLETE/EASTASIA/
and are covered by the Unicode Consortium copying permission contained
in http://www.unicode.org/copying.html. A copy of that notice is in
unicode-consortium.html in this directory. We believe this notice
supersedes the following notice which appears in the files:
Recipient is granted the right to make copies in any form for
internal distribution and to freely use the information supplied
in the creation of products supporting Unicode. Unicode, Inc.
specifically excludes the right to re-distribute this file directly
to third parties or other organizations whether for profit or not.
We are consulting the Unicode Consortium for confirmation.
BIG5.TXT CNS11643.TXT
JIS0201.TXT JIS0208.TXT JIS0212.TXT SHIFTJIS.TXT
JOHAB.TXT KSX1001.TXT OLD5601.TXT
The following file was copied from
http://examples.oreilly.com/cjkvinfo/unicode/gb12345-90.txt
and is covered by the O'Reilly Media copying policy in
http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html.
A copy of that notice is in oreilly.html in this directory. This data
file is is an appendix to the book *Chinese, Japanese, Korean, and
Vietnamese Information Processing* by Ken Lunde, published by O'Reilly
Media (ISBN-13 978-1565922242).
GB12345.TXT
The following files are taken from locations below
http://www.unicode.org/Public/MAPPINGS/
and are covered by the conditions in Exhibit 1 of unicode.html in this
directory.
8859-1.TXT 8859-10.TXT 8859-13.TXT 8859-14.TXT 8859-15.TXT 8859-16.TXT
8859-2.TXT 8859-3.TXT 8859-4.TXT 8859-5.TXT 8859-6.TXT 8859-7.TXT
8859-8.TXT 8859-9.TXT CP1250.TXT CP1251.TXT CP1252.TXT CP1253.TXT
CP1254.TXT CP1255.TXT CP1256.TXT CP1257.TXT CP1258.TXT CP874.TXT
CP932.TXT CP936.TXT CP949.TXT CP950.TXT GB2312.TXT HANGUL.TXT
KOI8-R.TXT KSC5601.TXT
1.1 XEmacs/xemacs/etc/unicode/unicode-consortium/oreilly.html
Index: oreilly.html
===================================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>O'Reilly -- O'Reilly Policy on Re-Use of Code Examples from Books</title>
<meta name="keywords" content="O'Reilly,O'Reilly Network,oreillynet,oreillynet.com,O'Reilly,OREILLY,,Ask Tim,,Bruce Epstein,policy,re-use of code examples" />
<meta name="description" content="What is our policy with regard to programmers incorporating code examples from books into their work?" />
<meta name="date" content="Nov. 01, 2001" />
<meta name="pagename" content="O'Reilly Policy on Re-Use of Code Examples from Books" />
<meta name="site" content="O'Reilly" />
<meta name="author" content="" />
<meta name="safariu_url" content="" />
<!-- common javascript, css and hitbox -->
<link rel="stylesheet" rev="stylesheet" href="http://www.oreillynet.com/styles/all.css" type="text/css"/>
<script language="JavaScript" type="text/javascript" src="http://www.oreillynet.com/engine.js"></script>
<script language="JavaScript" type="text/javascript" src="http://www.oreillynet.com/common.js"></script>
<!--WEBSIDESTORY CODE HBX1.0 (Universal)-->
<!--COPYRIGHT 1997-2004 WEBSIDESTORY,INC. ALL RIGHTS RESERVED. U.S.PATENT No. 6,393,479B1. MORE INFO:http://websidestory.com / privacy-->
<script language="javascript" type="text/javascript">
var _hbEC=0,_hbE=new Array;function _hbEvent(a,b){b=_hbE[_hbEC++]=new Object();b._N=a;b._C=0;return b;}
var hbx=_hbEvent("pv");hbx.vpc="HBX0100u";hbx.gn="ehg-oreilly.hitbox.com";
//"BCB: oreilly.com,/a/oreilly/ask_tim/2001/codepolicy.html, DM52032830WV";
hbx.acct="DM52032830WV;DM520404M4ZR"; //ACCOUNT NUMBER(S)
hbx.pn="OReilly+Policy+on+Re-Use+of+Code+Examples+from+Books"; //PAGE NAME(S)
hbx.mlc="/a/oreilly/ask_tim/2001/;/oreilly.com/a/oreilly/ask_tim/2001/"; //MULTI-LEVEL CONTENT CATEGORY
hbx.pndef="title"; //DEFAULT PAGE NAME
hbx.ctdef="full"; //DEFAULT CONTENT CATEGORY
hbx.lt="auto"; //LINK TRACKING
hbx.dlf="n"; //DOWNLOAD FILTER
hbx.dft="n"; //DOWNLOAD FILE NAMING
hbx.elf="n"; //EXIT LINK FILTER
//SEGMENTS AND FUNNELS
hbx.seg=""; //VISITOR SEGMENTATION
hbx.fnl=""; //FUNNELS
//CAMPAIGNS
hbx.cmp=""; //CAMPAIGN ID
hbx.cmpn="CMP"; //CAMPAIGN ID IN QUERY
hbx.hra=""; //RESPONSE ATTRIBUTE
hbx.hqsr=""; //RESPONSE ATTRIBUTE IN REFERRAL QUERY
hbx.hqsp="ATT"; //RESPONSE ATTRIBUTE IN QUERY
hbx.hlt=""; //LEAD TRACKING
hbx.hla=""; //LEAD ATTRIBUTE
hbx.gp=""; //CAMPAIGN GOAL
hbx.gpn=""; //CAMPAIGN GOAL IN QUERY
hbx.hcn=""; //CONVERSION ATTRIBUTE
hbx.hcv=""; //CONVERSION VALUE
hbx.cp="null"; //LEGACY CAMPAIGN
hbx.cpd=""; //CAMPAIGN DOMAIN
//CUSTOM VARIABLES
hbx.ci="";//CUSTOMER ID
hbx.hc1="";//CUSTOM 1
hbx.hc2="";//CUSTOM 2
hbx.hc3="";//CUSTOM 3
hbx.hc4="";//CUSTOM 4
hbx.pec="";//ERROR CODES
</script><script language="javascript1.1" defer="defer" src="http://www.oreillynet.com/hbx.js" type="text/javascript"></script><!--//-->
<!-- END WEBSIDESTORY CODE -->
<link rel="stylesheet" rev="stylesheet" href="http://www.oreillynet.com/styles/about.css" />
<!-- feed autodiscovery links -->
</head>
<body onload="setMenu();" id="about">
<div id="page">
<div id="header">
<h1><a href="http://www.oreilly.com"><img src="/images/oreilly/oreilly.gif" width="228" height="67" alt="O'Reilly" /></a></h1>
<ul>
<li><a href="https://epoch.oreilly.com/account/default.orm" class="acct">My Account</a></li>
<li><a href="https://epoch.oreilly.com/shop/cart.orm" class="cart">View Cart</a></li>
</ul>
<span id="animal">
</span>
</div><!-- /#header -->
<div id="nav">
<ul>
<li><a href="http://www.oreilly.com/">Home</a></li>
<li><a href="http://www.oreillynet.com/">Network</a></li>
<li><a href="http://www.oreilly.com/store/">Store</a></li>
<li><a href="http://safari.oreilly.com">Safari Books Online</a></li>
<li><a href="http://conferences.oreillynet.com/">Conferences</a></li>
<li><a href="http://www.oreillylearning.com">Courses</a></li>
<li><a href="http://academic.oreilly.com/">Academic Solutions</a></li>
<li class="nav_selected"><a href="http://www.oreilly.com/about/">About</a></li>
</ul>
<div class="clear"></div>
</div><!-- /#nav -->
<div id="subnav">
<ul>
<li>
<a href="http://www.oreilly.com/contact.html">Contacts</a></li>
<li>
<a href="http://www.oreilly.com/history.html">History</a></li>
<li>
<a href="http://tim.oreilly.com">Tim O'Reilly</a></li>
<li>
<a href="http://labs.oreilly.com/">Labs</a></li>
<li>
<a href="http://press.oreilly.com/">Press Room</a></li>
<li>
<a href="http://jobs.oreilly.com/">Jobs</a></li>
<li>
<a href="http://www.oreillynet.com/cs/nl/home">Newsletters</a></li>
<li>
<a href="http://www.oreilly.com/oreilly/author/intro.csp">Writing for O'Reilly</a></li>
<li>
<a href="http://www.oreilly.com/feeds/">RSS Feeds</a></li>
</ul>
<div class="clear"></div>
</div><!-- /#subnav -->
<div id="content">
<!-- begin print-safariu-del.icio.us options -->
<div style="float:right;width:150px;margin: 0px 0px 6px 6px;">
<div style="padding-bottom:5px;"><a class="tool" title="Go to a print-friendly version of this page." href="/lpt/a/3883" class="secondary"><img src="/images/icons/print_18.gif" width="18" height="18" hspace="3" vspace="0" alt="Print." border="0" />Print</a></div>
<div style="padding: 5px 1px 5px 1px; border-top: 2px solid #ccc; border-bottom: 2px solid #ccc;" class="secondary"><a href='http://del.icio.us/post?url=http%3A%2F%2Fwww.oreilly.com%2Fpub%2Fa%2Foreilly%2Fask_tim%2F2001%2Fcodepolicy.html&title=O'Reilly%20Policy%20on%20Re-Use%20of%20Code%20Examples%20from%20Books'>Bookmark with del.icio.us</a></div>
</div>
<!-- end print-safariu-del.icio.us options -->
<!-- content here -->
<span id="intelliTxt">
<p> <font size="4"><b>O'Reilly Policy on Re-Use
of Code Examples from Books</b></font> </p>
<p> Bruce Epstein, author of <i>Director in a Nutshell</i>
(out of print) and <a href="http://www.oreilly.com/catalog/lingonut/">Lingo
in a Nutshell</a>, who is now working as a part-time
editor for O'Reilly (he is editor of Colin Moock's
recently published <a href="http://www.oreilly.com/catalog/actscript/">ActionScript:
The Definitive Guide</a>) sent in the following
question: </p>
<p> "What is our policy with regard to programmers
incorporating code examples from books into
their work? I get asked this all the time."
</p>
<p> The short answer is this: </p>
<p> You can use and redistribute example code from
our books for any non-commercial purpose (and
most commercial purposes) as long as you acknowledge
their source and authorship. The source of the
code should be noted in any documentation as
well as in the program code itself (as a comment).
The attribution should include author, title,
publisher, and ISBN. </p>
<p> As is often the case, there's a longer answer
as well. Bruce made it really easy for me to
put this response together, since he forwarded
an unofficial reply on this subject that he'd
sent to the FlashCoders mailing list. What appears
below is based on his message. (Hey, anyone
else who wants to send the answer as well as
the question to Ask Tim can make my job a lot
easier :-) Thanks, Bruce.) </p>
<p> As per the copyright notice in our books, O'Reilly
reserves all rights to the material in the book,
including the code examples. This literally
means that you can use the example code all
you like, but you can't publish or redistribute
it without our permission. In reality, we are
comfortable with any reasonable "fair use" of
the code, and you can assume permission is granted
without contacting us. The threshold of what
is reasonable (fair use) depends on a number
of factors. First, if the book is published
under an open source or open publication license,
you can use the code examples without any obligation
to us. Otherwise, use the following sanity tests:
</p>
<ol>
<li>
<p>If the code is incorporated into a software
product, Web site, or Web service, is
the product, site, or service a commercial
venture? We don't object to commercial
ventures, but if someone is looking
to profit from our work (or that of
our authors'), and the use is substantial,
we may want to consider a license fee.
(Send licensing queries to <a href="mailto:permissions at oreilly.com">permissions at oreilly.com</a>.)
</p>
</li>
<li>
<p>Is the O'Reilly material incidental to
the entire product? Are you using only
a small excerpt? For example, you can't
publish a CD-ROM of code examples from
O'Reilly books without our explicit
permission. But we aren't going to worry
if you use a routine taken from our
books as part of a huge software project,
in which the borrowed code is incidental.
</p>
</li>
<li>
<p>Does the work compete with O'Reilly?
For example, if you are a book publisher,
you can't use anything from our books
without our permission. </p>
</li>
<li>
<p>Is proper credit given? Such credit would
include a statement specifying the source
of the material, such as "Derived from
Example 10-2, <i>ActionScript: The Definitive
Guide</i> by Colin Moock. Copyright
2001 O'Reilly & Associates." Note
that giving credit does not insulate
you from prosecution if you improperly
use copyrighted material! </p>
</li>
<li>
<p>Does your use fall within fair use provisions
of copyright law? (Academic research,
commentary, etc.) For example, you don't
need O'Reilly's explicit permission
to post a snippet of code on a mailing
list if you are pointing out a bug,
asking a question, or answering one.
We especially like it when people answer
questions by pointing to our books,
quoting from them, and citing their
examples, as long as they acknowledge
the source! </p>
<p> Acknowledging the source is particularly
important. Bruce didn't mention this
in his posting to FlashCoders, but I
know that he personally was bit by this
one. Someone was routinely answering
Lingo questions on a mailing list by
supplying examples from Bruce's book,
without acknowledging the source (and
leading people to believe that the poster
had written them). </p>
</li>
</ol>
<p> We put the code from our books online because
we want it to be used. (Who wants to type it
in?) That's why we make it available in lots
of ways: for download from the Web (all examples
are linked from the book's catalog page on <i>oreilly.com</i>),
in our CD Bookshelf products, and in our new
Safari online service. </p>
<p> If you are interested in licensing O'Reilly
book content as a third party, send your request
to <a href="mailto:corporate at oreilly.com">corporate at oreilly.com</a>.
</p>
<p> --Tim </p>
<!-- End main text here -->
<p align="center"> <a href="http://www.oreilly.com/ask_tim/asktim_form.html"><b>Got
a question? Just ask!</b></a> </p>
<b>Return to: <a href="http://www.oreilly.com/ask_tim/">Ask Tim Archive</a></b>
</span>
<!-- end content -->
<img src="/images/trans.gif" alt=" " width="490" height="1" /><br />
<br /><br />
</div> <!-- /#content -->
<!-- navbar and footer -->
<div id="netnav">
<h3>Topics</h3>
<ul>
<li><a href="#" onclick="toggleSheet('business'); return true" id="businessButton" class="rollup">Business & Culture</a>
<ul id="business">
<li>
<a href="http://www.oreilly.com/pub/topic/business" class="showtopic">
Business</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/culture" class="showtopic">
Digital Culture</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/finance" class="showtopic">
Personal Finance</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/projectmanagement" class="showtopic">
Project & Career Management</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('databases'); return false" id="databasesButton" class="rollup">Databases</a>
<ul id="databases">
<li>
<a href="http://www.oreilly.com/pub/topic/access" class="showtopic">
Access</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/mysql" class="showtopic">
MySQL</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/oracle" class="showtopic">
Oracle</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/otherdatabases" class="showtopic">
Other Databases</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/sql" class="showtopic">
SQL</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/sqlserver" class="showtopic">
SQL Server</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/theory" class="showtopic">
Theory</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('design'); return false" id="designButton" class="rollup">Design & Graphics</a>
<ul id="design">
<li>
<a href="http://www.oreilly.com/pub/topic/flash" class="showtopic">
Flash & Actionscript</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/graphics" class="showtopic">
Illustration & Graphics</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/photomanipulation" class="showtopic">
Photoshop & Photomanipulation</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/printdesign" class="showtopic">
Print Design</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('audiovideo'); return false" id="audiovideoButton" class="rollup">Digital Audio & Video</a>
<ul id="audiovideo">
<li>
<a href="http://www.oreilly.com/pub/topic/digitalaudio" class="showtopic">
Digital Audio</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/digitalvideo" class="showtopic">
Digital Video</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('photography'); return false" id="photographyButton" class="rollup">Digital Photography</a>
<ul id="photography">
<li>
<a href="http://www.oreilly.com/pub/topic/digiphoto" class="showtopic">
Digital Photography</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/photomanipulation" class="showtopic">
Photoshop & Photomanipulation</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('hardware'); return false" id="hardwareButton" class="rollup">Hardware</a>
<ul id="hardware">
<li>
<a href="http://www.oreilly.com/pub/topic/devices" class="showtopic">
Devices & Peripherals</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/hardwarehacking" class="showtopic">
Hacks & Modifications</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/pchardware" class="showtopic">
PC Hardware</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('homeoffice'); return false" id="homeofficeButton" class="rollup">Home & Office</a>
<ul id="homeoffice">
<li>
<a href="http://www.oreilly.com/pub/topic/security" class="showtopic">
Computer Security & Privacy</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/games" class="showtopic">
Games</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/homeentertainment" class="showtopic">
Home Entertainment</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/homenetworking" class="showtopic">
Home Networking</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/mac" class="showtopic">
Mac OS X</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/macprograms" class="showtopic">
Macintosh Programs</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/pchardware" class="showtopic">
PC Hardware</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/finance" class="showtopic">
Personal Finance</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windows" class="showtopic">
Windows 2000 & earlier</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windowsprograms" class="showtopic">
Windows Programs</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windowsvista" class="showtopic">
Windows Vista</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windowsxp" class="showtopic">
Windows XP</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('sysadmin'); return false" id="sysadminButton" class="rollup">Networking & Sys Admin</a>
<ul id="sysadmin">
<li>
<a href="http://www.oreilly.com/pub/topic/apache" class="showtopic">
Apache</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/certification" class="showtopic">
Certification</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/cisco" class="showtopic">
Cisco & other Routers</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/email" class="showtopic">
Email</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/homenetworking" class="showtopic">
Home Networking</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/projectmanagement" class="showtopic">
Project & Career Management</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/protocols" class="showtopic">
Protocols</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/serveradmin" class="showtopic">
Server Administration</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/serversecurity" class="showtopic">
Server Security</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/spam" class="showtopic">
Spam</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/telephony" class="showtopic">
Telephony</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/wireless" class="showtopic">
Wireless</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('os'); return false" id="osButton" class="rollup">Operating Systems</a>
<ul id="os">
<li>
<a href="http://www.oreilly.com/pub/topic/linux" class="showtopic">
Linux/Unix</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/mac" class="showtopic">
Mac OS X</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windows" class="showtopic">
Windows 2000 & earlier</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windowsvista" class="showtopic">
Windows Vista</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/windowsxp" class="showtopic">
Windows XP</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('programming'); return false" id="programmingButton" class="rollup">Programming</a>
<ul id="programming">
<li>
<a href="http://www.oreilly.com/pub/topic/dotnet" class="showtopic">
.NET & Windows Programming</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/ajax" class="showtopic">
Ajax</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/csharp" class="showtopic">
C#</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/cprog" class="showtopic">
C/C++</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/certification" class="showtopic">
Certification</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/games" class="showtopic">
Games</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/java" class="showtopic">
Java</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/otherprogramming" class="showtopic">
Other Programming</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/perl" class="showtopic">
Perl</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/php" class="showtopic">
PHP</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/projectmanagement" class="showtopic">
Project & Career Management</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/python" class="showtopic">
Python</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/ruby" class="showtopic">
Ruby</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/secureprogramming" class="showtopic">
Secure Programming</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/vb" class="showtopic">
Visual Basic</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/webservices" class="showtopic">
Web Services</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/xml" class="showtopic">
XML</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('science'); return false" id="scienceButton" class="rollup">Science & Math</a>
<ul id="science">
<li>
<a href="http://www.oreilly.com/pub/topic/mapping" class="showtopic">
Mapping</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/math" class="showtopic">
Math</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/science" class="showtopic">
Science</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('security'); return false" id="securityButton" class="rollup">Security</a>
<ul id="security">
<li>
<a href="http://www.oreilly.com/pub/topic/security" class="showtopic">
Computer Security & Privacy</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/secureprogramming" class="showtopic">
Secure Programming</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/serversecurity" class="showtopic">
Server Security</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/spam" class="showtopic">
Spam</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('softwareengineering'); return false" id="softwareengineeringButton" class="rollup">Software Engineering</a>
<ul id="softwareengineering">
<li>
<a href="http://www.oreilly.com/pub/topic/designpatterns" class="showtopic">
Design Patterns</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/enterprisedev" class="showtopic">
Enterprise Development</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/projectmanagement" class="showtopic">
Project & Career Management</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/secureprogramming" class="showtopic">
Secure Programming</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/testing" class="showtopic">
Testing</a>
</li>
</ul>
</li>
<li><a href="#" onclick="toggleSheet('web'); return false" id="webButton" class="rollup">The Web</a>
<ul id="web">
<li>
<a href="http://www.oreilly.com/pub/topic/ajax" class="showtopic">
Ajax</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/flash" class="showtopic">
Flash & Actionscript</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/mapping" class="showtopic">
Mapping</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/webapplications" class="showtopic">
Web Applications</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/browsers" class="showtopic">
Web Browsers</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/webdesign" class="showtopic">
Web Design</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/webdev" class="showtopic">
Web Development</a>
</li><li>
<a href="http://www.oreilly.com/pub/topic/webservices" class="showtopic">
Web Services</a>
</li>
</ul>
</li>
</ul>
<h3>International Sites</h3>
<p><a href="http://www.oreilly.com.cn/"><img src="/images/oreilly/flags/new/china2.gif" alt="O'Reilly China" height="16" width="23" style="border: 1px solid black;" /></a> <a href="http://www.oreilly.fr/"><img src="/images/oreilly/flags/new/france2.gif" alt="O'Reilly France" height="16" width="23" style="border: 1px solid black;" /></a> <a href="http://www.oreilly.de/"><img src="/images/oreilly/flags/new/germany2.gif" alt="O'Reilly Germany" height="16" width="23" style="border: 1px solid black;" /></a> <a href="http://www.oreilly.co.jp/"><img src="/images/oreilly/flags/new/japan2.gif" alt="O'Reilly Japan" height="16" width="23" style="border: 1px solid black;" /></a> <a href="http://www.oreilly.com.tw/"><img src="/images/oreilly/flags/new/taiwan2.gif" alt="O'Reilly Taiwan" height="16" width="23" style="border: 1px solid black;" /></a></p>
<p> </p>
</div><!-- /#nav_net -->
<div class="clear"></div>
<div id="footer">
<p class="footer-links"><a href="http://www.oreilly.com/about/">About O'Reilly</a> | <a href="http://www.oreilly.com/oreilly/contact.html">Contact</a> | <a href="http://jobs.oreilly.com">Jobs</a> | <a href="http://press.oreilly.com">Press Room</a> | <a href="http://www.oreillynet.com/mediakit/">How to Advertise</a> | <a href="http://www.oreillynet.com/pub/a/mediakit/privacy.html">Privacy Policy</a>
</p>
<p>© 2006, O'Reilly Media, Inc.<br />
All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.</p>
</div><!-- /#footer -->
</div><!-- /#page -->
<!--WEBSIDESTORY CODE HBX1.0 (Universal)-->
<!--COPYRIGHT 1997-2004 WEBSIDESTORY,INC. ALL RIGHTS RESERVED. U.S.PATENT No. 6,393,479B1. MORE INFO:http://websidestory.com / privacy-->
<script language="javascript" type="text/javascript">
var _hbEC=0,_hbE=new Array;function _hbEvent(a,b){b=_hbE[_hbEC++]=new Object();b._N=a;b._C=0;return b;}
var hbx=_hbEvent("pv");hbx.vpc="HBX0100u";hbx.gn="ehg-oreilly.hitbox.com";
//"BCB: oreilly.com,/a/oreilly/ask_tim/2001/codepolicy.html, DM52032830WV";
hbx.acct="DM52032830WV;DM520404M4ZR"; //ACCOUNT NUMBER(S)
hbx.pn="OReilly+Policy+on+Re-Use+of+Code+Examples+from+Books"; //PAGE NAME(S)
hbx.mlc="/a/oreilly/ask_tim/2001/;/oreilly.com/a/oreilly/ask_tim/2001/"; //MULTI-LEVEL CONTENT CATEGORY
hbx.pndef="title"; //DEFAULT PAGE NAME
hbx.ctdef="full"; //DEFAULT CONTENT CATEGORY
hbx.lt="auto"; //LINK TRACKING
hbx.dlf="n"; //DOWNLOAD FILTER
hbx.dft="n"; //DOWNLOAD FILE NAMING
hbx.elf="n"; //EXIT LINK FILTER
//SEGMENTS AND FUNNELS
hbx.seg=""; //VISITOR SEGMENTATION
hbx.fnl=""; //FUNNELS
//CAMPAIGNS
hbx.cmp=""; //CAMPAIGN ID
hbx.cmpn="CMP"; //CAMPAIGN ID IN QUERY
hbx.hra=""; //RESPONSE ATTRIBUTE
hbx.hqsr=""; //RESPONSE ATTRIBUTE IN REFERRAL QUERY
hbx.hqsp="ATT"; //RESPONSE ATTRIBUTE IN QUERY
hbx.hlt=""; //LEAD TRACKING
hbx.hla=""; //LEAD ATTRIBUTE
hbx.gp=""; //CAMPAIGN GOAL
hbx.gpn=""; //CAMPAIGN GOAL IN QUERY
hbx.hcn=""; //CONVERSION ATTRIBUTE
hbx.hcv=""; //CONVERSION VALUE
hbx.cp="null"; //LEGACY CAMPAIGN
hbx.cpd=""; //CAMPAIGN DOMAIN
//CUSTOM VARIABLES
hbx.ci="";//CUSTOMER ID
hbx.hc1="";//CUSTOM 1
hbx.hc2="";//CUSTOM 2
hbx.hc3="";//CUSTOM 3
hbx.hc4="";//CUSTOM 4
hbx.pec="";//ERROR CODES
</script><script language="javascript1.1" defer="defer" src="http://www.oreillynet.com/hbx.js" type="text/javascript"></script><!--//-->
<!-- END WEBSIDESTORY CODE -->
</body>
</html>
1.1 XEmacs/xemacs/etc/unicode/unicode-consortium/unicode-consortium.html
Index: unicode-consortium.html
===================================================================
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Language" content="en-us">
<meta name="VI60_defaultClientScript" content="JavaScript">
<meta name="GENERATOR" content="Microsoft FrontPage 6.0">
<meta name="keywords" content="Unicode Standard, copyright">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Unicode Terms of Use</title>
<link rel="stylesheet" type="text/css"
href="http://www.unicode.org/webscripts/standard_styles.css">
</head>
<body text="#330000">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td colspan="2">
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="icon"><a href="http://www.unicode.org/"><img border="0"
src="http://www.unicode.org/webscripts/logo60s2.gif" align="middle"
alt="[Unicode]" width="34" height="33"></a> <a class="bar"
href="http://www.unicode.org/copyright.html"><font size="3">Terms of
Use</font></a></td>
<td class="bar"><a href="http://www.unicode.org" class="bar">Home</a>
| <a href="http://www.unicode.org/sitemap/" class="bar">Site Map</a> |
<a href="http://www.unicode.org/search" class="bar">Search </a></td>
</tr>
</table>
</td>
</tr>
<tr>
<td colspan="2" class="gray"> </td>
</tr>
<tr>
<td valign="top" width="25%" class="navCol">
<table class="navColTable" border="0" width="100%" cellspacing="4"
cellpadding="0">
<tr>
<td class="navColTitle">Contents</td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#1">Unicode Copyright</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#2">Restricted Rights
Legend</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#3">Warranties &
Disclaimers</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#4">Waiver of Damages</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#5">Trademarks</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#7">Miscellaneous</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"><a href="#Exhibit1">Data Files and
Software License Agreement (Exhibit 1)</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"> </td>
</tr>
</table>
<table class="navColTable" border="0" width="100%" cellspacing="4"
cellpadding="0">
<tr>
<td class="navColTitle">Related Links</td>
</tr>
<tr>
<td valign="top" class="navColCell">
<a href="http://www.unicode.org/policies/logo_policy.html">The
Unicode® Consortium Trademarks and Logo Policy</a></td>
</tr>
<tr>
<td valign="top" class="navColCell">
<a href="http://www.unicode.org/policies/policies.html">Unicode
Policies</a></td>
</tr>
<tr>
<td valign="top" class="navColCell"></td>
</tr>
</table>
<!-- BEGIN CONTENTS -->
<td>
<blockquote>
<h1>Unicode Terms of Use</h1>
<p>For the general privacy policy governing access to this site, see
the
<a href="http://www.unicode.org/policies/privacy_policy.html">
Unicode Privacy Policy</a>. For trademark usage, see
<a href="http://www.unicode.org/policies/logo_policy.html">the
Unicode Consortium® Trademarks and Logo Policy</a>.</p>
<table class="sidebar" align="right" width="50%" id="table1">
<tr>
<td class="sidebarTitle">Notice to End User: Terms of Use</td>
</tr>
<tr>
<td class="sidebar">Carefully read the following legal agreement
("Agreement"). Use or copying of the software and/or codes
provided with this agreement (The "Software") constitutes your
acceptance of these terms</td>
</tr>
</table>
<ol type="A">
<li><u><a name="1"></a>Unicode Copyright.</u>
<ol>
<li>Copyright © 1991-2007 Unicode, Inc. All rights reserved.</li>
<li>Certain documents and files on this website contain a legend
indicating that "Modification is permitted." Any person is
hereby authorized, without fee, to modify such documents and
files to create derivative works conforming to the Unicode®
Standard, subject to Terms and Conditions herein.</li>
<li>Any person is hereby authorized, without fee, to view, use,
reproduce, and distribute all documents and files solely for
informational purposes in the creation of products supporting
the Unicode Standard, subject to the Terms and Conditions
herein.</li>
<li>Further specifications of rights and restrictions pertaining
to the use of the particular set of data files known as the
"Unicode Character Database" can be found in <a href="#Exhibit1">
Exhibit 1</a>.</li>
<li>Each version of the Unicode Standard has further specifications of rights and restrictions
of use. For the book editions, these are found on the back of
the
<a href="http://www.unicode.org/versions/Unicode4.0.0/Title.pdf">
title page</a>. For the online edition, certain files (such as
the PDF files for book chapters and code charts) carry specific
restrictions. All other files are covered under these general
Terms of Use. To request a permission to reproduce any
part of the Unicode Standard, please
<a href="http://www.unicode.org/contacts.html">contact the
Unicode Consortium</a>.</li>
<li>No license is granted to "mirror" the Unicode website where
a fee is charged for access to the "mirror" site.</li>
<li>Modification is not permitted with respect to this document.
All copies of this document must be verbatim.</li>
</ol>
</li>
<li><u><a name="2"></a>Restricted Rights Legend</u>. Any technical
data or software which is licensed to the United States of
America, its agencies and/or instrumentalities under this
Agreement is commercial technical data or commercial computer
software developed exclusively at private expense as defined in
FAR 2.101, or DFARS 252.227-7014 (June 1995), as applicable. For
technical data, use, duplication, or disclosure by the Government
is subject to restrictions as set forth in DFARS 202.227-7015
Technical Data, Commercial and Items (Nov 1995) and this
Agreement. For Software, in accordance with FAR 12-212 or DFARS
227-7202, as applicable, use, duplication or disclosure by the
Government is subject to the restrictions set forth in this
Agreement.</li>
<li><u><a name="3"></a>Warranties and Disclaimers</u>.
<ol>
<li>This publication and/or website may include technical or
typographical errors or other inaccuracies . Changes are
periodically added to the information herein; these changes will
be incorporated in new editions of the publication and/or
website. Unicode may make improvements and/or changes in the
product(s) and/or program(s) described in this publication
and/or website at any time.</li>
<li>If this file has been purchased on magnetic or optical media
from Unicode, Inc. the sole and exclusive remedy for any claim
will be exchange of the defective media within ninety (90) days
of original purchase.</li>
<li>EXCEPT AS PROVIDED IN SECTION C.2, THIS PUBLICATION AND/OR
SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND EITHER
EXPRESS, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT. UNICODE AND ITS LICENSORS ASSUME
NO RESPONSIBILITY FOR ERRORS OR OMISSIONS IN THIS PUBLICATION
AND/OR SOFTWARE OR OTHER DOCUMENTS WHICH ARE REFERENCED BY OR
LINKED TO THIS PUBLICATION OR THE UNICODE WEBSITE.</li>
</ol>
</li>
<li><u><a name="4"></a>Waiver of Damages.</u> In no event shall
Unicode or its licensors be liable for any special, incidental,
indirect or consequential damages of any kind, or any damages
whatsoever, whether or not Unicode was advised of the possibility
of the damage, including, without limitation, those resulting from
the following: loss of use, data or profits, in connection with
the use, modification or distribution of this information or its
derivatives.</li>
<li><u><a name="5"></a>Trademarks.</u>
<ol>
<li>Unicode and the Unicode logo are registered trademarks of
Unicode, Inc. </li>
<li>This site contains product names and corporate names of
other companies. All product names and company names and logos
mentioned herein are the trademarks or registered trademarks of
their respective owners. Other products and corporate names
mentioned herein which are trademarks of a third party are used
only for explanation and for the owners' benefit and with no
intent to infringe.</li>
<li>Use of third party products or information referred to
herein is at the user’s risk.</li>
</ol>
</li>
<li><u><a name="7"></a>Miscellaneous</u>.
<ol>
<li><u>Jurisdiction and Venue</u>. This server is operated from
a location in the State of California, United States of America.
Unicode makes no representation that the materials are
appropriate for use in other locations. If you access this
server from other locations, you are responsible for compliance
with local laws. This Agreement, all use of this site and any
claims and damages resulting from use of this site are governed
solely by the laws of the State of California without regard to
any principles which would apply the laws of a different
jurisdiction. The user agrees that any disputes regarding this
site shall be resolved solely in the courts located in Santa
Clara County, California. The user agrees said courts have
personal jurisdiction and agree to waive any right to transfer
the dispute to any other forum. </li>
<li><u>Modification by Unicode </u>Unicode shall have the right
to modify this Agreement at any time by posting it to this site.
The user may not assign any part of this Agreement without
Unicode’s prior written consent.</li>
<li><u>Taxes.</u> The user agrees to pay any taxes arising from
access to this website or use of the information herein, except
for those based on Unicode’s net income.</li>
<li><u>Severability</u>. If any provision of this
Agreement is declared invalid or unenforceable, the remaining
provisions of this Agreement shall remain in effect.</li>
<li><u>Entire Agreement</u>. This Agreement constitutes the
entire agreement between the parties. </li>
</ol>
</li>
</ol>
</blockquote>
<hr width="95%">
<h3 align="center"><a name="Exhibit1">EXHIBIT 1</a><br>
UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE</h3>
<blockquote>
<p>Unicode Data Files include all data files under the directories
<a href="http://www.unicode.org/Public/">http://www.unicode.org/Public/</a>,
<a href="http://www.unicode.org/reports/">http://www.unicode.org/reports/</a>,
and
<a title="http://www.unicode.org/cldr/data/" onclick="return top.js.OpenExtLink(window,event,this)" target="_blank" href="http://www.unicode.org/cldr/data/">
http://www.unicode.org/cldr/data/ </a>. Unicode Software includes any source code
published in the Unicode Standard or under the directories
<a href="http://www.unicode.org/Public/">http://www.unicode.org/Public/</a>,
<a href="http://www.unicode.org/reports/">http://www.unicode.org/reports/</a>,
and
<a title="http://www.unicode.org/cldr/data/" onclick="return top.js.OpenExtLink(window,event,this)" target="_blank" href="http://www.unicode.org/cldr/data/">
http://www.unicode.org/cldr/data/.</a></p>
<p>NOTICE TO USER: Carefully read the following legal agreement. BY DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S DATA FILES ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE.</p>
<p>COPYRIGHT AND PERMISSION NOTICE</p>
<p>Copyright © 1991-2007 Unicode, Inc. All rights reserved. Distributed under the Terms of Use in
<a href="http://www.unicode.org/copyright.html">http://www.unicode.org/copyright.html</a>.</p>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and
any associated documentation (the "Data Files") or Unicode software and any associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear
with all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified.</p>
<p>THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THE DATA FILES OR SOFTWARE.</p>
<p>Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder.</p>
<hr width="80%">
<p>Unicode and the Unicode logo are trademarks of Unicode, Inc., and may be registered in some jurisdictions. All other trademarks and registered trademarks mentioned herein are the property of their respective owners.</p>
</blockquote>
<hr width="50%">
<div align="center">
<center>
<table cellspacing="0" cellpadding="0" border="0" id="table2">
<tr>
<td><a href="http://www.unicode.org/copyright.html">
<img src="http://www.unicode.org/img/hb_notice.gif"
border="0" alt="Access to Copyright and terms of use"
width="216" height="50"></a></td>
</tr>
</table>
<script language="Javascript" type="text/javascript"
src="http://www.unicode.org/webscripts/lastModified.js">
</script>
</center>
</div>
</td>
</tr>
</table>
</body>
</html>
More information about the XEmacs-CVS
mailing list