January 2007 - XEmacs-Patches - XEmacs Mailing List Archives

[PATCH] respect CODESYS in `insert-file-contents-internal'. 17 years, 11 months

Nix

On 20 Jan 2007, David Kastrup outgrape: > For all that I know, specifying binary format image file names in an > image descriptor is _still_ blowing up XEmacs 21.4 (and likely 21.5, > too) once dired gets loaded. This bug was reported at least 4 years > ago IIRC. Let me take a look: Indeed. Here's the patch again, against fairly recent 21.5 CVS. 2005-02-04 Nix <nix(a)esperi.org.uk> * fileio.c (restore_read_coding_system_unwind): Pop the coding system. (Finsert_file_contents_internal): Use the CODESYS even for files read by a file-name-handler. Index: src/fileio.c =================================================================== --- src/fileio.c.orig 2006-12-16 21:20:49.000000000 +0000 +++ src/fileio.c 2006-12-16 21:46:42.000000000 +0000 ＠＠ -216,6 +216,15 ＠＠ return Fset_marker (point_marker, Qnil, Qnil); } +/* Restore coding-system-for-read. */ + +static Lisp_Object +restore_read_coding_system_unwind (Lisp_Object coding_system) +{ + Vcoding_system_for_read = coding_system; + return Qnil; +} + Lisp_Object Qexpand_file_name; Lisp_Object Qfile_truename; ＠＠ -3360,6 +3369,9 ＠＠ multiple return points make this a pain in the butt. ]] we do protect curbuf now. --ben */ + record_unwind_protect (restore_read_coding_system_unwind, Vcoding_system_for_read); + Vcoding_system_for_read = codesys; + codesys = get_coding_system_for_text_file (codesys, 0); if (current_buffer->base_buffer && ! NILP (visit)) -- `The serial comma, however, is correct and proper, and abandoning it will surely lead to chaos, anarchy, rioting in the streets, the Terrorists taking over, and possibly the complete collapse of Human Civilization.' _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

2 participants
4 comments

[AC21.5] Copyright rectification for Unicode 17 years, 11 months

Stephen J. Turnbull

Mike Fabian <mfabian(a)suse.de> kindly informed me of some issues discovered by the legal department of SuSE, and per their suggestions I've downloaded what should be legit copies (see COPYING below for what the remaining doubt is) of several Unicode Consortium files, added information about the upstream permissions, and added the COPYING file. I'm in contact with O'Reilly re copying permissions on their copying policy. Unicode explicitly allows verbatim-only redistribution. ------------------------------------------------------------------------ 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(a)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 ------------------------------------------------------------------------ Here's the patch (which doesn't include COPYING): Index: etc/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/ChangeLog,v retrieving revision 1.77 diff -u -u -r1.77 ChangeLog --- etc/ChangeLog 29 Dec 2006 18:09:38 -0000 1.77 +++ etc/ChangeLog 27 Jan 2007 18:21:18 -0000 ＠＠ -0,0 +1,25 ＠＠ +2007-01-28 Stephen J. Turnbull <stephen(a)xemacs.org> + + Thanks to Mike Fabian <mfabian(a)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. + Index: etc/unicode/unicode-consortium/BIG5.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/BIG5.TXT,v retrieving revision 1.2 diff -u -u -r1.2 BIG5.TXT --- etc/unicode/unicode-consortium/BIG5.TXT 13 Mar 2002 08:51:40 -0000 1.2 +++ etc/unicode/unicode-consortium/BIG5.TXT 27 Jan 2007 18:21:19 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.0d3 # Table format: Format A # Date: 11 February 1994 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)taligent.com> # # 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(a)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(a)taligent.com> # # 0xA140 0x3000 # IDEOGRAPHIC SPACE Index: etc/unicode/unicode-consortium/CNS11643.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/CNS11643.TXT,v retrieving revision 1.2 diff -u -u -r1.2 CNS11643.TXT --- etc/unicode/unicode-consortium/CNS11643.TXT 13 Mar 2002 08:51:41 -0000 1.2 +++ etc/unicode/unicode-consortium/CNS11643.TXT 27 Jan 2007 18:21:20 -0000 ＠＠ -4,7 +4,6 ＠＠ # Table version: 0.0d1 # Table format: Format A # Date: 21 October 1994 -# Author: John H. Jenkins <John_Jenkins(a)taligent.com> # # 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(a)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(a)taligent.com> # # 0x12121 0x3000 # IDEOGRAPHIC SPACE Index: etc/unicode/unicode-consortium/GB12345.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/GB12345.TXT,v retrieving revision 1.2 diff -u -u -r1.2 GB12345.TXT --- etc/unicode/unicode-consortium/GB12345.TXT 13 Mar 2002 08:51:48 -0000 1.2 +++ etc/unicode/unicode-consortium/GB12345.TXT 27 Jan 2007 18:21:20 -0000 ＠＠ -7,21 +7,17 ＠＠ # Author: Glenn Adams <glenn(a)metis.com> # John H. Jenkins <John_Jenkins(a)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: # Index: etc/unicode/unicode-consortium/JIS0201.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0201.TXT,v retrieving revision 1.2 diff -u -u -r1.2 JIS0201.TXT --- etc/unicode/unicode-consortium/JIS0201.TXT 13 Mar 2002 08:51:50 -0000 1.2 +++ etc/unicode/unicode-consortium/JIS0201.TXT 27 Jan 2007 18:21:22 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)taligent.com> # # 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(a)unicode.org. +# # # Format: Three tab-separated columns # Column #1 is the shift JIS code (in hex as 0xXX) ＠＠ -35,11 +46,6 ＠＠ # 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(a)taligent.com> # # 0x20 0x0020 # SPACE Index: etc/unicode/unicode-consortium/JIS0208.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0208.TXT,v retrieving revision 1.2 diff -u -u -r1.2 JIS0208.TXT --- etc/unicode/unicode-consortium/JIS0208.TXT 13 Mar 2002 08:51:50 -0000 1.2 +++ etc/unicode/unicode-consortium/JIS0208.TXT 27 Jan 2007 18:21:23 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)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(a)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 # Index: etc/unicode/unicode-consortium/JIS0212.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/JIS0212.TXT,v retrieving revision 1.2 diff -u -u -r1.2 JIS0212.TXT --- etc/unicode/unicode-consortium/JIS0212.TXT 13 Mar 2002 08:51:50 -0000 1.2 +++ etc/unicode/unicode-consortium/JIS0212.TXT 27 Jan 2007 18:21:23 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)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(a)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 # Index: etc/unicode/unicode-consortium/KSC5601.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/KSC5601.TXT,v retrieving revision 1.2 diff -u -u -r1.2 KSC5601.TXT --- etc/unicode/unicode-consortium/KSC5601.TXT 13 Mar 2002 08:51:52 -0000 1.2 +++ etc/unicode/unicode-consortium/KSC5601.TXT 27 Jan 2007 18:21:26 -0000 ＠＠ -4,9 +4,22 ＠＠ # Table version: 1.0 # Table format: Format A # Date: 07/24/95 -# Authors: Lori Hoerth <lorih(a)microsoft.com> -# K.D.Chang <a-kchang(a)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(a)unicode.org. +# # # Format: Three tab-separated columns # Column #1 is the Unified Hangeul code (in hex) Index: etc/unicode/unicode-consortium/OLD5601.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/OLD5601.TXT,v retrieving revision 1.2 diff -u -u -r1.2 OLD5601.TXT --- etc/unicode/unicode-consortium/OLD5601.TXT 13 Mar 2002 08:51:54 -0000 1.2 +++ etc/unicode/unicode-consortium/OLD5601.TXT 27 Jan 2007 18:21:28 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.0d2 # Table format: Format A # Date: 6 December 1993 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)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(a)unicode.org. +# # # A number of alternative mappings have been suggested by a # reviewer. They are as follows: Index: etc/unicode/unicode-consortium/SHIFTJIS.TXT =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/etc/unicode/unicode-consortium/SHIFTJIS.TXT,v retrieving revision 1.2 diff -u -u -r1.2 SHIFTJIS.TXT --- etc/unicode/unicode-consortium/SHIFTJIS.TXT 13 Mar 2002 08:51:55 -0000 1.2 +++ etc/unicode/unicode-consortium/SHIFTJIS.TXT 27 Jan 2007 18:21:28 -0000 ＠＠ -4,8 +4,6 ＠＠ # Table version: 0.9 # Table format: Format A # Date: 8 March 1994 -# Authors: Glenn Adams <glenn(a)metis.com> -# John H. Jenkins <John_Jenkins(a)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(a)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 Index: etc/unicode/unicode-consortium/oreilly.html =================================================================== RCS file: etc/unicode/unicode-consortium/oreilly.html diff -N etc/unicode/unicode-consortium/oreilly.html --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ etc/unicode/unicode-consortium/oreilly.html 27 Jan 2007 18:21:28 -0000 ＠＠ -0,0 +1,1072 ＠＠ +<!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="" /> + + + +<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> + +  +  + <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> +  + + +<link rel="stylesheet" rev="stylesheet" href="http://www.oreillynet.com/styles/about.css" /> + + + + + + + + +</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> + +<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> + +<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> + + +<div id="content"> + + + + +<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> + + + + +<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＠oreilly.com">permissions＠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＠oreilly.com">corporate＠oreilly.com</a>. + </p> + <p> --Tim </p> +  + <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> + + + +<img src="/images/trans.gif" alt=" " width="490" height="1" /><br /> + + + + + + + + + +<br /><br /> + + + +</div>  + + + +<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> + +<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> + +</div> +  +  + <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> +  + </body> + +</html> Index: etc/unicode/unicode-consortium/unicode-consortium.html =================================================================== RCS file: etc/unicode/unicode-consortium/unicode-consortium.html diff -N etc/unicode/unicode-consortium/unicode-consortium.html --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ etc/unicode/unicode-consortium/unicode-consortium.html 27 Jan 2007 18:21:28 -0000 ＠＠ -0,0 +1,330 ＠＠ +<!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,AB.(B 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> + + +  + + <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,AB.(B 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 ,AB)(B 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,AB.(B + 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,Ab��(Bs 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,Ab��(Bs 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,Ab��(Bs 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 ,AB)(B 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/copyr...> + +<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> _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

[AC] Unbreak non-MULE Xft build 17 years, 11 months

Michael Sperber

I've committed this one. 2007-01-27 Mike Sperber <mike(a)xemacs.org> * faces.c (complex_vars_of_faces): Move declarations of fontptr and fonts out of #ifdef MULE, unbreaking the non-MULE Xft build. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla Index: src/faces.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/faces.c,v retrieving revision 1.53 diff -u -r1.53 faces.c --- src/faces.c 17 Dec 2006 11:26:09 -0000 1.53 +++ src/faces.c 27 Jan 2007 17:01:09 -0000 ＠＠ -2258,7 +2258,7 ＠＠ Lisp_Object device_symbol = Qx; #endif -#ifdef MULE + const Ascbyte **fontptr; const Ascbyte *fonts[] = { ＠＠ -2287,7 +2287,8 ＠＠ "-*-*-medium-r-*-*-*-170-*-*-c-*-*-*", #endif }; - const Ascbyte **fontptr; + +#ifdef MULE /* Define some specifier tags for classes of character sets. Combining these allows for distinct fallback fonts for distinct dimensions of _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

Re: [PATCH (mail-lib)] Add freedesktop.org's xdg-open support to browse-url 17 years, 11 months

Ville Skyttä

COMMIT mail-lib On Sunday 21 January 2007 22:37, Simon Josefsson wrote: > Ville Skyttä <scop(a)xemacs.org> writes: > > This patch adds support for freedesktop.org's xdg-open to browse-url and > > adds SeaMonkey to browse-url-xemacs. Simon, let me know if you'd like me > > to commit this. > > Seems fine to me, please install! Thanks, done. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

[PATCH (mail-lib)] Add freedesktop.org's xdg-open support to browse-url 17 years, 11 months

Ville Skyttä

This patch adds support for freedesktop.org's xdg-open to browse-url and adds SeaMonkey to browse-url-xemacs. Simon, let me know if you'd like me to commit this. For more info about xdg-open, see http://portland.freedesktop.org/wiki/XdgUtils 2007-01-21 Ville Skyttä <scop(a)xemacs.org> * browse-url.el: Add support for freedesktop.org xdg-open. (browse-url-xdg-open-program): New. (browse-url-default-xdg-browser): New. (browse-url-browser-function): Add item for freedesktop.org browser. (browse-url-default-browser): Try freedesktop.org browser first, fix order of other tried browsers. * browse-url-xemacs.el (browse-url-menu): Add SeaMonkey and freedesktop.org items. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

2 participants
1 comments

Re: [Q21.5] Make the X11 font menu work again. 17 years, 11 months

Aidan Kehoe

Ar an naoú lá déag de mí Eanair, scríobh Stephen J. Turnbull: > Aidan Kehoe writes: > > > > I don't understand why you changed the code rather than the > > > docstring. > > > > The code that called it relied on it not reverting the default > > face. > > IMO, the calling code is broken, then. It’s relying on the documented behaviour of the function it calls! It’s not broken. Maybe the API is wrong, but the code isn’t. > The functionality provided by `(reset-face 'default)' is useful (to me, > when hacking, at least), (remove-specifier (face-font 'default)) is equivalent. > and reset-face is fairly rarely called. Once again: > > > If people want a font to be controlled by Custom, let them set > > > it via Custom, no? Is this needed to make the font-menu work? > > > > The font-menu uses Custom to change the face family and size, which > > is well and good, duplicating the frobbing Custom does would be a > > waste. If, however, a face specifier doesn’t have 'custom in its > > specifier tag list, as will be the case if it was initialised from > > X resources or from the corresponding fallback, Custom won’t > > modify a faces. > > I don't understand what you're saying. I've never had trouble > Customizing any face, but AFAIK no face is initialized with 'custom > tags on any of the instantiators. Start XEmacs 21.4. Click on Options -> Font, choose a font. Click on Options -> Save Options to Custom File. Exit XEmacs. Start XEmacs again. (face-font 'default) will show that the face has custom tags on the instantiators. > > > I guess you can recover the resource settings by reinitializing > > > the face, but wouldn't it be preferable to keep the > > > resource-based instantiators and implement reset-to-default by > > > clearing instantiators with the Custom tag-set? > > > > That’s the current situation, and it has the disadvantage that the > > font menu doesn’t work. > > Well, it *did* work at one time. AFAIK it does work in 21.4, I'll > need to check. That's basically the same font-menu code IIRC, except > for the Xft-related kludges in recent 21.5. There were changes, and I don’t understand them in detail. I suspect it’s a question of the relative order of instantiators, which would have been fragile even when it worked. > More important, I don't see how neutralizing X resources makes it > "really work"; there are other ways of editing face specifications. > According to the logic you've presented, to placate Custom you're > going to need to deprecate the whole set-specifier UI as well as > set-face-font and friends. Am I missing something special about X > resources? > > Can you explain why we want to go there? It seems to me that what we > want to do is to turn Custom into a convenient front-end to the > specifier API, rather than to remove the specifier API. I’m not making a complete API, and I don’t want to. I want clicking on Options -> Font to do something useful. It’s important. It’s the first thing lots of new users do. -- When I was in the scouts, the leader told me to pitch a tent. I couldn't find any pitch, so I used creosote. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

[COMMIT] Fill out docstrings fo `function,' `quote' and `require.' 17 years, 11 months

Aidan Kehoe

APPROVE COMMIT NOTE: This patch has been committed. src/ChangeLog addition: 2007-01-20 Aidan Kehoe <kehoea(a)parhasard.net> * eval.c: Document in more detail what happens with byte-compilation, `function', and `quote'. * fns.c: Mention that `require' is evaluated both at byte-compile time and at runtime. XEmacs Trunk source patch: Diff command: cvs -q diff -Nu Files affected: src/fns.c =================================================================== RCS src/eval.c =================================================================== RCS Index: src/eval.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/eval.c,v retrieving revision 1.93 diff -u -u -r1.93 eval.c --- src/eval.c 2006/08/29 14:10:54 1.93 +++ src/eval.c 2007/01/20 16:51:06 ＠＠ -1177,6 +1177,15 ＠＠ DEFUN ("quote", Fquote, 1, UNEVALLED, 0, /* Return the argument, without evaluating it. `(quote x)' yields `x'. + +There is an alternative and more used reader syntax for `quote'. Precede +any Lisp object with a single apostrophe, and that Lisp object will be +returned unevaluated. 'x is thus equivalent to (quote x). + +Do not use `quote' or the single apostrophe for lambda expressions that you +would prefer to be byte-compiled. Use `function', which see, or take +advantage of the fact that lambda expressions are self-quoting and such +lambda expressions will be automatically byte-compiled. */ (args)) { ＠＠ -1185,8 +1194,16 ＠＠ DEFUN ("function", Ffunction, 1, UNEVALLED, 0, /* Like `quote', but preferred for objects which are functions. -In byte compilation, `function' causes its argument to be compiled. -`quote' cannot do that. + +As with `quote' there is an alternative reader syntax for `function' which +in practice is used more often. Writing #'OBJECT is equivalent to writing +\(function OBJECT), where OBJECT is some Lisp object. + +In byte compilation, `function' causes a lambda expression argument to be +compiled. `quote' cannot do that. lambda expressions are, however, +self-quoting, and self-quoted lambda expressions will be byte-compiled. +Only lambda expressions explicitly quoted with `quote' or that occur in +nested data lists will not be byte-compiled. */ (args)) { Index: src/fns.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/fns.c,v retrieving revision 1.64 diff -u -u -r1.64 fns.c --- src/fns.c 2005/10/25 11:16:24 1.64 +++ src/fns.c 2007/01/20 16:51:08 ＠＠ -3582,6 +3582,13 ＠＠ If FILENAME is omitted, the printname of FEATURE is used as the file name. If optional third argument NOERROR is non-nil, then return nil if the file is not found instead of signaling an error. +Normally the return value is FEATURE. +The normal messages at start and end of loading FILENAME are suppressed. + +In order to make it possible for a required package to provide macros to be +expanded at byte-compilation time, top level calls of `require' are +evaluated both at byte-compile time and at run time. That is, any top-level +call to `require' is wrapped in an implicit \(eval-and-compile ...\) block. */ (feature, filename, noerror)) { -- When I was in the scouts, the leader told me to pitch a tent. I couldn't find any pitch, so I used creosote. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

Re: [Q21.5] Make the X11 font menu work again. 17 years, 11 months

Aidan Kehoe

Ar an t-ochtú lá déag de mí Eanair, scríobh Stephen J. Turnbull: > QUERY > > Aidan Kehoe writes: > > > lisp/ChangeLog addition: > > > > 2007-01-02 Aidan Kehoe <kehoea(a)parhasard.net> > > > > * cus-face.el (custom-set-face-update-spec): > > Fix some formatting. > > * faces.el (reset-face): > > reset-face resets other faces to behave like the default face--it > > shouldn't do anything if it's handed the default face. > > I don't understand why you changed the code rather than the docstring. The code that called it relied on it not reverting the default face. > Ie, it makes sense to reset the default face, which results in it > behaving according to its fallbacks. `reset-face' is marked as a > dangerous, irreversible function; isn't that enough? > > > * font-menu.el: > > * font-menu.el (font-menu-set-font): > > If the font was initialised from X resources (the tag-set > > contains 'x-resource) pretend to Custom that it has > > responsibility for those settings. > > I don't understand the logic for this. If people want a font to be > controlled by Custom, let them set it via Custom, no? Is this needed > to make the font-menu work? The font-menu uses Custom to change the face family and size, which is well and good, duplicating the frobbing Custom does would be a waste. If, however, a face specifier doesn’t have 'custom in its specifier tag list, as will be the case if it was initialised from X resources or from the corresponding fallback, Custom won’t modify a faces. > I guess you can recover the resource settings by reinitializing the face, > but wouldn't it be preferable to keep the resource-based instantiators > and implement reset-to-default by clearing instantiators with the Custom > tag-set? That’s the current situation, and it has the disadvantage that the font menu doesn’t work. > In general: > > Brief testing indicates that the font menu is still very broken under > Xft. That's expected, right? I haven't tried a non-Xft build yet. That’s expected, yes--haven’t got to it yet. -- When I was in the scouts, the leader told me to pitch a tent. I couldn't find any pitch, so I used creosote. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

[PATCH COMMIT] Tramp doesn't depend on edebug 17 years, 11 months

Michael Albinus

Hi, I've committed a patch which fixes the dependency on edebug. Best regards, Michael. _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

1 participants
0 comments

[PATCH21.5] Support readonly bit under Windows 17 years, 11 months

Vin Shelton

This is the 21.5 version of the readonly-bit patch that Benson posted for 21.4. src/ChangeLog addition: 2007-01-06 Vin Shelton <acs(a)xemacs.org> * fileio.c (check_writable): Check old-style readonly bit first. 21.5 source patch: Diff command: cvs -q diff -u Files affected: src/fileio.c Index: src/fileio.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/fileio.c,v retrieving revision 1.109 diff -a -u -u -r1.109 fileio.c --- src/fileio.c 2006/12/08 02:22:01 1.109 +++ src/fileio.c 2007/01/07 02:42:39 ＠＠ -2311,8 +2311,8 ＠＠ PRIVILEGE_SET PrivilegeSet; DWORD dwPrivSetSize = sizeof( PRIVILEGE_SET ); BOOL fAccessGranted = FALSE; - DWORD dwAccessAllowed; - Extbyte *fnameext; + DWORD dwAccessAllowed; + Extbyte *fnameext; #ifdef CYGWIN cygwin_conv_to_full_win32_path(filename, filename_buffer); ＠＠ -2320,12 +2320,18 ＠＠ #endif C_STRING_TO_TSTR(filename, fnameext); + + // First check for a normal file with the old-style readonly bit + attributes = qxeGetFileAttributes(fnameext); + if (FILE_ATTRIBUTE_READONLY == (attributes & (FILE_ATTRIBUTE_DIRECTORY|FILE_ATTRIBUTE_READONLY))) + return 0; + /* Win32 prototype lacks const. */ error = qxeGetNamedSecurityInfo(fnameext, SE_FILE_OBJECT, - DACL_SECURITY_INFORMATION|GROUP_SECURITY_INFORMATION|OWNER_SECURITY_INFORMATION, - &psidOwner, &psidGroup, &pDacl, &pSacl, &pDesc); + DACL_SECURITY_INFORMATION|GROUP_SECURITY_INFORMATION|OWNER_SECURITY_INFORMATION, + &psidOwner, &psidGroup, &pDacl, &pSacl, &pDesc); if(error != ERROR_SUCCESS) { // FAT? - attributes = qxeGetFileAttributes((Extbyte *)filename); + attributes = qxeGetFileAttributes(fnameext); return (attributes & FILE_ATTRIBUTE_DIRECTORY) || (0 == (attributes & FILE_ATTRIBUTE_READONLY)); } _______________________________________________ XEmacs-Patches mailing list XEmacs-Patches(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches

2 participants
1 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

XEmacs-Patches January 2007