# HG changeset patch # User stephent # Date 1169922546 0 # Node ID e51807f9eedd45155666ee4b278cc6f5d7043193 # Parent d6f975442bd377adffc5a89d40d7d0d3b870f91c [xemacs-hg @ 2007-01-27 18:28:57 by stephent] Fix up copying situation in etc/unicode/unicode-consortium. <87mz4471zg.fsf@uwakimon.sk.tsukuba.ac.jp> diff -r d6f975442bd3 -r e51807f9eedd etc/ChangeLog --- a/etc/ChangeLog Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/ChangeLog Sat Jan 27 18:29:06 2007 +0000 @@ -1,3 +1,28 @@ +2007-01-28 Stephen J. Turnbull + + Thanks to Mike Fabian 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 * unicode/unicode-consortium/8859-7.TXT: diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/BIG5.TXT --- a/etc/unicode/unicode-consortium/BIG5.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/BIG5.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.0d3 # Table format: Format A # Date: 11 February 1994 -# Authors: Glenn Adams -# John H. Jenkins # # Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved. # @@ -25,8 +23,21 @@ # # 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@unicode.org. # # WARNING! It is currently impossible to provide round-trip compatibility # between BIG5 and Unicode. @@ -52,38 +63,34 @@ # # 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 "" 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 "" 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 -# # 0xA140 0x3000 # IDEOGRAPHIC SPACE 0xA141 0xFF0C # FULLWIDTH COMMA diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/CNS11643.TXT --- a/etc/unicode/unicode-consortium/CNS11643.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/CNS11643.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,7 +4,6 @@ # Table version: 0.0d1 # Table format: Format A # Date: 21 October 1994 -# Author: John H. Jenkins # # Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved. # @@ -24,8 +23,22 @@ # # 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@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,33 +63,29 @@ # 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 "" 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 "" 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 -# # 0x12121 0x3000 # IDEOGRAPHIC SPACE 0x12122 0xFF0C # FULLWIDTH COMMA diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/COPYING --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/etc/unicode/unicode-consortium/COPYING Sat Jan 27 18:29:06 2007 +0000 @@ -0,0 +1,60 @@ +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 . + +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 + diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/GB12345.TXT --- a/etc/unicode/unicode-consortium/GB12345.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/GB12345.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -7,21 +7,17 @@ # Author: Glenn Adams # John H. Jenkins # -# 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: # diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/JIS0201.TXT --- a/etc/unicode/unicode-consortium/JIS0201.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/JIS0201.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams -# John H. Jenkins # # Copyright (c) 1991-1994 Unicode, Inc. All Rights reserved. # @@ -25,9 +23,22 @@ # # 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@unicode.org. +# # # Format: Three tab-separated columns # Column #1 is the shift JIS code (in hex as 0xXX) @@ -36,11 +47,6 @@ # # The entries are in JIS order # -# These mappings are provisional, pending definition of -# official mappings by Japanese standards bodies. -# -# Any comments or problems, contact -# # 0x20 0x0020 # SPACE 0x21 0x0021 # EXCLAMATION MARK diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/JIS0208.TXT --- a/etc/unicode/unicode-consortium/JIS0208.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/JIS0208.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams -# John H. Jenkins # # 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@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 "" 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 "" 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 # diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/JIS0212.TXT --- a/etc/unicode/unicode-consortium/JIS0212.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/JIS0212.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams -# John H. Jenkins # # 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@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 "" 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 "" 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 # diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/KSC5601.TXT --- a/etc/unicode/unicode-consortium/KSC5601.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/KSC5601.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,9 +4,22 @@ # Table version: 1.0 # Table format: Format A # Date: 07/24/95 -# Authors: Lori Hoerth -# K.D.Chang -# 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@unicode.org. +# # # Format: Three tab-separated columns # Column #1 is the Unified Hangeul code (in hex) diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/OLD5601.TXT --- a/etc/unicode/unicode-consortium/OLD5601.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/OLD5601.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.0d2 # Table format: Format A # Date: 6 December 1993 -# Authors: Glenn Adams -# John H. Jenkins # # 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@unicode.org. +# # # A number of alternative mappings have been suggested by a # reviewer. They are as follows: diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/SHIFTJIS.TXT --- a/etc/unicode/unicode-consortium/SHIFTJIS.TXT Sat Jan 27 17:14:22 2007 +0000 +++ b/etc/unicode/unicode-consortium/SHIFTJIS.TXT Sat Jan 27 18:29:06 2007 +0000 @@ -4,8 +4,6 @@ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams -# John H. Jenkins # # 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@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 "" 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 "" 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 diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/oreilly.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/etc/unicode/unicode-consortium/oreilly.html Sat Jan 27 18:29:06 2007 +0000 @@ -0,0 +1,1072 @@ + + + + + + O'Reilly -- O'Reilly Policy on Re-Use of Code Examples from Books + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
+ + + + + + + + + + +

O'Reilly Policy on Re-Use + of Code Examples from Books

+

Bruce Epstein, author of Director in a Nutshell + (out of print) and Lingo + in a Nutshell, who is now working as a part-time + editor for O'Reilly (he is editor of Colin Moock's + recently published ActionScript: + The Definitive Guide) sent in the following + question:

+

"What is our policy with regard to programmers + incorporating code examples from books into + their work? I get asked this all the time." +

+

The short answer is this:

+

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.

+

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.)

+

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: +

+
    +
  1. +

    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 permissions@oreilly.com.) +

    +
    2. +
  2. +

    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. +

    +
    3. +
  3. +

    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.

    +
    4. +
  4. +

    Is proper credit given? Such credit would + include a statement specifying the source + of the material, such as "Derived from + Example 10-2, ActionScript: The Definitive + Guide by Colin Moock. Copyright + 2001 O'Reilly & Associates." Note + that giving credit does not insulate + you from prosecution if you improperly + use copyrighted material!

    +
    5. +
  5. +

    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!

    +

    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).

    +
    6. +
+

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 oreilly.com), + in our CD Bookshelf products, and in our new + Safari online service.

+

If you are interested in licensing O'Reilly + book content as a third party, send your request + to corporate@oreilly.com. +

+

--Tim

+ +

Got + a question? Just ask!

+ Return to: Ask Tim Archive + + + + +
+ + + + + + + + + +

+ + + +
+ + + +
+

Topics

+ + +

International Sites

+

O'Reilly China O'Reilly France O'Reilly Germany O'Reilly Japan O'Reilly Taiwan

+ +

 

+ +
+ +
+ + + + +
+ + + + + + + diff -r d6f975442bd3 -r e51807f9eedd etc/unicode/unicode-consortium/unicode-consortium.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/etc/unicode/unicode-consortium/unicode-consortium.html Sat Jan 27 18:29:06 2007 +0000 @@ -0,0 +1,330 @@ + + + + + + + + + + + + + + + + + + +Unicode Terms of Use + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + +
[Unicode]  Terms of + UseHome + | Site Map | + Search
+
 
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Contents
Unicode Copyright
Restricted Rights + Legend
Warranties & + Disclaimers
Waiver of Damages
Trademarks
Miscellaneous
Data Files and + Software License Agreement (Exhibit 1)
 
+ + + + + + + + + + + + + +
Related Links
+ The + Unicode® Consortium Trademarks and Logo Policy
+ Unicode + Policies
+ + + + + 		+ +
+

Unicode Terms of Use

+ +

For the general privacy policy governing access to this site, see + the  + + Unicode Privacy Policy. For trademark usage, see + the + Unicode Consortium® Trademarks and Logo Policy.

+ + + + + + + + + +
    +
  1. Unicode Copyright. +
      +
    1. Copyright © 1991-2007 Unicode, Inc. All rights reserved.
      2. +
    2. 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.
      3. +
    3. 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.
      4. +
    4. 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 + Exhibit 1.
      5. +
    5. 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 + + title page. 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 + contact the + Unicode Consortium.
      6. +
    6. No license is granted to "mirror" the Unicode website where + a fee is charged for access to the "mirror" site.
      7. +
    7. Modification is not permitted with respect to this document. + All copies of this document must be verbatim.
      8. +
    +
    2. +
  2. Restricted Rights Legend. 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.
    3. +
  3. Warranties and Disclaimers. +
      +
    1. 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.
      2. +
    2. 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.
      3. +
    3. 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.
      4. +
    +
    4. +
  4. Waiver of Damages. 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.
    5. +
  5. Trademarks. +
      +
    1. Unicode and the Unicode logo are registered trademarks of + Unicode, Inc. 
      2. +
    2. 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.
      3. +
    3. Use of third party products or information referred to + herein is at the user’s risk.
      4. +
    +
    6. + +
  6. Miscellaneous. +
      +
    1. Jurisdiction and Venue. 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.
      2. +
    2. Modification by Unicode 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.
      3. +
    3. Taxes. 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.
      4. +
    4. Severability.  If any provision of this + Agreement is declared invalid or unenforceable, the remaining + provisions of this Agreement shall remain in effect.
      5. +
    5. Entire Agreement. This Agreement constitutes the + entire agreement between the parties. 
      6. +
    +
    7. +
+
+
+ +

EXHIBIT 1
+UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE

+
+

Unicode Data Files include all data files under the directories +http://www.unicode.org/Public/, +http://www.unicode.org/reports/, +and + +http://www.unicode.org/cldr/data/ . Unicode Software includes any source code +published in the Unicode Standard or under the directories +http://www.unicode.org/Public/, +http://www.unicode.org/reports/, +and + +http://www.unicode.org/cldr/data/.

+ +

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.

+

COPYRIGHT AND PERMISSION NOTICE

+ +

Copyright © 1991-2007 Unicode, Inc. All rights reserved. Distributed under the Terms of Use in +http://www.unicode.org/copyright.html.

+ +

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.

+ +

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.

+ +

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.

+ +
+ +

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.

+ + +
+ + +
+
+
+ + + + +
+ Access to Copyright and terms of use
+ + + +
+
+ +
+ +