summaryrefslogtreecommitdiff
path: root/Build/source/texk/bibtex-x/csf
diff options
context:
space:
mode:
Diffstat (limited to 'Build/source/texk/bibtex-x/csf')
-rw-r--r--Build/source/texk/bibtex-x/csf/00readme.txt903
-rw-r--r--Build/source/texk/bibtex-x/csf/88591lat.csf313
-rw-r--r--Build/source/texk/bibtex-x/csf/88591sca.csf283
-rw-r--r--Build/source/texk/bibtex-x/csf/COPYING339
-rw-r--r--Build/source/texk/bibtex-x/csf/HISTORY61
-rw-r--r--Build/source/texk/bibtex-x/csf/ascii.csf242
-rw-r--r--Build/source/texk/bibtex-x/csf/cp437lat.csf281
-rw-r--r--Build/source/texk/bibtex-x/csf/cp850lat.csf272
-rw-r--r--Build/source/texk/bibtex-x/csf/cp850sca.csf279
-rw-r--r--Build/source/texk/bibtex-x/csf/cp866rus.csf296
-rw-r--r--Build/source/texk/bibtex-x/csf/csfile.txt318
-rw-r--r--Build/source/texk/bibtex-x/csf/file_id.diz13
12 files changed, 3600 insertions, 0 deletions
diff --git a/Build/source/texk/bibtex-x/csf/00readme.txt b/Build/source/texk/bibtex-x/csf/00readme.txt
new file mode 100644
index 00000000000..6322e51fcd3
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/00readme.txt
@@ -0,0 +1,903 @@
+******************************************************************************
+FILE: $RCSfile: 00readme.txt,v $
+ $Revision: 3.71 $
+ $Date: 1996/08/18 20:38:55 $
+******************************************************************************
+
+
+An 8-bit Implementation of BibTeX 0.99 with a Very Large Capacity
+=================================================================
+
+
+Contents
+--------
+
+ 0. Abstract
+
+ 1. Introduction
+ 1.1 8-bit Character Set Support
+ 1.2 Big and Customisable Capacity
+
+ 2. Distribution Kits and Where to Find Them
+ 2.1 bt371dos.zip
+ 2.2 bt371os2.zip
+ 2.3 bt371src.zip
+ 2.4 bt371csf.zip
+
+ 3. Running 8-bit BibTeX
+ 3.1 Command line options
+ 3.2 Finding Files
+ 3.3 Environment variables
+
+ 4. The Codepage and Sort Order (CS) File
+ 4.1 CS file syntax
+ 4.2 Testing a CS file
+ 4.3 Sharing your CS file
+
+ 5. Building 8-bit BibTeX from Source Code
+ 5.1 DOS
+ 5.2 OS/2
+ 5.3 Unix
+ 5.4 VMS
+
+ 6. Reporting Bugs and Requesting Improvements
+ 6.1 Contacting the authors
+ 6.2 Further enhancements
+
+ 7. Frequently Asked Questions
+
+ 8. Acknowledgements
+
+ 9. BibTeX Use and Copying Conditions
+
+ 10. Change Log
+
+
+
+0. Abstract
+-----------
+
+This abstract is in a format suitable for inclusion in BBS description files
+(file_id.diz):
+
+ (v3.71) "big" BibTeX with full 8-bit support
+
+ An enhanced, portable C version of BibTeX.
+ Enhanced by conversion to "big" (32-bit)
+ capacity, addition of run-time selectable
+ capacity and 8-bit support extensions.
+ National character set and sorting order
+ are controlled by an external configuration
+ file. Various examples are included.
+ Freeware / GNU Public Licence.
+
+ Niel Kempson <kempson@snowyowl.co.uk>
+ Alejandro Aguilar-Sierra <asierra@servidor.unam.mx>
+
+
+
+1. Introduction
+----------------
+
+8-bit BibTeX is an enhanced, portable C version of BibTeX 0.99. It has been
+enhanced in these areas:
+
+ - conversion to "big" (32-bit) capacity
+ - capacity selectable at run time
+ - flexible support for non-English languages using 8-bit character sets
+ - well matched to LateX2e and its "inputenc" package
+
+Oren Patashnik, the creator of BibTeX, is working on a new BibTeX 1.0 that
+will be a modern implementation supporting large capacities and non-English
+languages (see TUGboat, pages 269--274, volume 15, number 3, September 1994).
+He is content for this version to be released, but hopes that people will
+eventually migrate to BibTeX 1.0 when it is released. Its release date is
+uncertain at the moment.
+
+
+ 1.1 Big and Customisable Capacity
+ ---------------------------------
+
+ The original 16-bit code has been rewritten to use 32-bit data types
+ wherever possible. The result is a very large potential capacity. To
+ increase flexibility and to avoid BibTeX allocating all available memory,
+ the capacity of some key arrays can be set on the command line.
+
+ For convenience, several standard capacities have been predefined:
+ default, big and huge. The key capacities are set as follows:
+
+ Parameter Standard --big --huge --wolfgang
+ ------------------------------------------------------------
+ Hash_Prime 4,253 8,501 16,319 30,011
+ Hash_Size 5,000 10,000 19,000 35,000
+ Max_Cites 750 2,000 5,000 7,500
+ Max_Ent_Ints 3,000 4,000 5,000 7,500
+ Max_Ent_Strs 3,000 6,000 10,000 10,000
+ Max_Fields 17,250 30,000 85,000 125,000
+ Max_Strings 4,000 10,000 19,000 30,000
+ Pool_Size 65,530 130,000 500,000 750,000
+ Wiz_Fn_Space 3,000 6,000 10,000 10,000
+
+ If these parameter names mean nothing to you, don't worry, you've
+ probably never exceeded BibTeX's capacity.
+
+
+ 1.2 8-bit Character Set Support
+ -------------------------------
+
+ BibTeX now accepts 8-bit characters in its input files and writes 8-bit
+ characters to its output files. The character set is defined by an
+ external configuration text file - the codepage and sort order ("CS")
+ file.
+
+ The sort order can be defined for the language and character set. For
+ example, in German, the control sequence \"o (o umlaut) should be sorted
+ as if it were the letter "o", but after ordinary "o", leading to this
+ order:
+
+ Trofer, Tr\"ofer, Trufer
+
+ However, in Swedish, \"o (o umlaut) is treated as the 29th letter of the
+ alphabet and these entries would be sorted as:
+
+ Trofer, Trufer, Tr\"ofer
+
+ The sorting order is defined by an external configuration text file -
+ the codepage and sort order ("CS") file.
+
+ This version of BibTeX, coupled with LaTeX2e and its "inputenc" package
+ provide a robust means of handling 8-bit character sets.
+
+
+
+2. Distribution Kits and Where to Find Them
+--------------------------------------------
+
+8-bit BibTeX is distributed as a set of ZIP files created by the freely
+available implementation of ZIP by the Info-ZIP project. The files have all
+been compressed using the new "deflation" algorithm and can only be
+compressed using the Info-ZIP implementation of UNZIP, or PKUNZIP v2.04 or
+later. Ancient versions of PKUNZIP (e.g. v1.10) will not be able to unZIP
+the files and will complain with a message like: "PKUNZIP: Warning! I don't
+know how to handle: xxxxxxxx.xxx".
+
+The "official" version of 8-bit BibTeX will be available by anonymous FTP
+from the Comprehensive TeX Archive Network (CTAN) sites:
+
+ ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+ ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+
+There are four main ZIP files in the complete 8-bit BibTeX distribution:
+
+ bt###dos.zip bt###os2.zip bt###src.zip bt###csf.zip
+
+where ### is the latest version, currently 371 (for v3.71). Their contents
+and purpose are summarised below.
+
+
+ 2.1 bt371dos.zip
+ ----------------
+
+ The binary + documentation kit for MS-DOS users. It contains all you
+ need to run 8-bit BibTeX under MS-DOS, but no source code. The
+ executable program uses a 32-bit virtual memory extender called EMX to
+ run in 32-bit mode. emTeX is probably the most comprehensive and capable
+ implementation of TeX for DOS & OS/2 and it too uses EMX.
+
+ The kit contains these files:
+
+ 00readme.txt this file
+ COPYING GNU copyright notice
+ HISTORY summary of changes made so far
+ csfile.txt documentation for codepage and sort order
+ ("CS") files
+ msdos/bibtex.exe the 8-bit BibTeX program
+
+ EMX uses the VCPI mechanism to run in 32-bit mode and will therefore not
+ run in a DOS session under MS Windows. It will run under native DOS and
+ in a DOS session under OS/2. The EMX extender (v0.9b) is bound into
+ bibtex.exe, but you can always obtain the latest version of EMX by
+ anaonymous FTP from:
+
+ ftp.uni-stuttgart.de:/pub/systems/os2/emx-0.9b
+ ftp.leo.org:/pub/comp/os/os2/gnu/emx+gcc
+
+ If you want to run this version of BibTeX in a DOS session under MS
+ Windows, you have two choices:
+
+ - get and install the RSX extender. RSX is a DPMI-compliant DOS
+ extender which is more or less compatible with emx. It is compatible
+ with EMX, DPMI servers and DOS sessions under MS Windows. The
+ official site for the latest version of RSX is
+
+ ftp.uni-bielefeld.de:/pub/systems/msdos/misc
+
+ but you can also get it by anonymous FTP from the same CTAN sites as
+ BibTeX:
+
+ ftp.tex.ac.uk:/tex-archive/systems/msdos/dpmigcc
+ ftp.uni-stuttgart.de:/tex-archive/systems/msdos
+
+ The files to look for are dpmigcc5.zip and rsxwin3a.zip
+
+ If you use the emTeX implementation of TeX and friends, it may be
+ more convenient to get the "emxrsx" package - it's a minimal version
+ of RSX to allow emTeX to run in DOS sessions under MS Windows. It is
+ available by anonymous FTP from CTAN sites in the emTeX directory:
+
+ ftp.tex.ac.uk:/tex-archive/systems/msdos/emtex
+ ftp.uni-stuttgart.de:/tex-archive/systems/msdos/emtex
+
+ On the other hand, if you're using emTeX under MS Windows, you've
+ probably solved the problem already :-)
+
+ - get the djgpp GNU C compiler and DOS extender package and build
+ BibTeX from the source code. The master site for djgpp is
+ ftp.delorie.com.
+
+
+ 2.2 bt371os2.zip
+ ----------------
+
+ The binary + documentation kit for OS/2 2.x and 3.x users. It contains
+ all you need to run 8-bit BibTeX under OS/2, but no source code. The
+ executable program was developed using the EMX development system and has
+ its run-time library linked in - there is no need to install EMX just to
+ run BibTeX. If you already have EMX installed want a smaller executable,
+ you'll need to rebuild from sources.
+
+ The kit contains these files:
+
+ 00readme.txt this file
+ COPYING GNU copyright notice
+ HISTORY summary of changes made so far
+ csfile.txt documentation for codepage and sort order
+ ("CS") files
+ os2/bibtex.exe the 8-bit BibTeX program
+
+
+ 2.3 bt371src.zip
+ ----------------
+
+ The complete source code kit to build 8-bit BibTeX on all supported
+ systems. The source code is known to build easily under MS-DOS and OS/2
+ if you have the GNU C Compiler installed. The source code is quite
+ portable and contains almost no system-specific items - it should very
+ easily port to Unix or VMS. If you decide to port 8-bit BibTeX to
+ another platform, please let me know so that I can include your efforts
+ in the master distribution.
+
+ The source kit contains these files:
+
+ 00readme.txt this file
+ COPYING GNU copyright notice
+ HISTORY summary of changes made so far
+ csfile.txt documentation for codepage and sort order
+ ("CS") files
+
+ bibtex.h definition of global parameters and limits
+ datatype.h definition of custom data types
+ gblprocs.h forward declaration of all global functions
+ gblvars.h declaration of global variables
+ sysdep.h determine the compiler and environment
+
+ bibtex.c main source including system dependent code
+ bibtex-1.c part 1 of the system independent functions
+ bibtex-2.c part 2 of the system independent functions
+ bibtex-3.c part 3 of the system independent functions
+ bibtex-4.c part 4 of the system independent functions
+
+ utils.c nearly all of the enhancement code
+ utils.h
+
+ getopt.c the GNU getopt package for command line parsing
+ getopt1.c
+ getopt.h
+
+ dos-emx.mak makefile for EMX GNU C under MS-DOS
+ dos-dj.mak makefile for DJGPP GNU C under MS-DOS
+ os2.mak makefile for EMX GNU C under OS/2
+ unix.mak makefile for Unix variants
+
+
+ 2.4 bt371csf.zip
+ ----------------
+
+ The character set and sorting order is now defined by an external
+ configuration text file - the codepage and sort order ("CS") file. A
+ number of example files have been included with the master distribution,
+ but I hope that others will be written by 8-bit BibTeX users in due
+ course. To avoid the need to reissue to the master ZIP files every time
+ a new CS file is created, CS files will also be available as a separate
+ kit.
+
+ At the time of writing, the kit contains these CS files:
+
+ File Name Character Set Sorting Order
+ -------------------------------------------------------------
+ 88591lat.csf ISO 8859-1 Latin
+ 88591sca.csf ISO 8859-1 Scandinavean
+ ascii.csf US ASCII English
+ cp437lat.csf IBM codepage 437 Latin
+ cp850lat.csf IBM codepage 850 Latin
+ cp850sca.csf IBM codepage 850 Scandinavean
+ cp866rus.csf IBM codepage 866 Russian
+
+
+
+3. Running 8-bit BibTeX
+------------------------
+
+Running 8-bit BibTeX is superficially the same as running the original
+BibTeX, but there are quite a number of command line options that may be
+specified.
+
+
+ 3.1 Command line options
+ ------------------------
+
+ The command line syntax is:
+
+ bibtex [options] aux-file
+
+ where "aux-file" is the name of the TeX auxilliary output file to be
+ processed by BibTeX. The trailing ".aux" may be omitted.
+
+ Valid options are:
+
+ -? --help
+
+ Display some brief help text and then exit.
+
+ -7 --traditional
+
+ Operate in the original 7-bit mode. A CS file is not read:
+ only 7-bit ASCII characters are supported and sorting is
+ strictly by ASCII code value.
+
+ BibTeX will not allow you to specify --traditional with
+ either the --8bit or --csfile option.
+
+ -8 --8bit
+
+ Force 8-bit mode. A CS file is not read. All 8-bit
+ characters (code > 127) are treated as letters and sorting is
+ strictly by code page value.
+
+ BibTeX will not allow you to specify --8bit with either the
+ --csfile or --traditional option.
+
+ -c --csfile FILE
+
+ Read FILE as the BibTeX codepage and sort definition (CS)
+ file. The CS file is used to define the 8-bit character set
+ used by BibTeX and the order in which those characters should
+ be sorted.
+
+ BibTeX will not allow you to specify --csfile with either
+ the --8bit or --traditional option.
+
+ -d --debug TYPE
+
+ Report debugging information to the BibTeX log file and the
+ standard error device. The value TYPE controls the type of
+ debugging information reported. TYPE can be one or more of:
+
+ all - all debugging categories
+ csf - CS file processing
+ io - file I/O
+ mem - memory allocation and capacity
+ misc - other debugging information
+ search - path searching and file location
+
+ It is possible that your version of BibTeX has been compiled
+ with debugging support disabled. If this is the case, BibTeX
+ will issue a warning message when --debug is specified.
+
+ -s --statistics
+
+ Report internal statistics to the BibTeX log file.
+
+ It is possible that your version of BibTeX has been compiled
+ with statistics support disabled. If this is the case,
+ BibTeX will issue a warning message when --statistics is
+ specified.
+
+ -t --trace
+
+ Report execution tracing to the BibTeX log file.
+
+ It is possible that your version of BibTeX has been compiled
+ with tracing support disabled. If this is the case, BibTeX
+ will issue a warning message when --trace is specified.
+
+ -v --version
+
+ Report BibTeX's version and then exit.
+
+ -B --big
+
+ Set BibTeX's capacity to "big". The size of particular
+ parameters will be set as follows (the default sizes are
+ shown in brackets):
+
+ Hash_Prime 8,501 (4,253)
+ Hash_Size 10,000 (5,000)
+ Max_Cites 2,000 (750)
+ Max_Ent_Ints 4,000 (3,000)
+ Max_Ent_Strs 6,000 (3,000)
+ Max_Fields 30,000 (17,250)
+ Max_Strings 10,000 (4,000)
+ Pool_Size 130,000 (65,530)
+ Wiz_Fn_Space 6,000 (3,000)
+
+ -H --huge
+
+ Set BibTeX's capacity to "huge". The size of particular
+ parameters will be set as follows (the default sizes are
+ shown in brackets):
+
+ Hash_Prime 16,319 (4,253)
+ Hash_Size 19,000 (5,000)
+ Max_Cites 5,000 (750)
+ Max_Ent_Ints 5,000 (3,000)
+ Max_Ent_Strs 10,000 (3,000)
+ Max_Fields 85,000 (17,250)
+ Max_Strings 19,000 (4,000)
+ Pool_Size 500,000 (65,530)
+ Wiz_Fn_Space 10,000 (3,000)
+
+ -W --wolfgang
+
+ Set BibTeX's capacity to "really huge" - required for
+ Wolfgang's PhD thesis. The size of particular parameters
+ will be set as follows (the default sizes are shown in
+ brackets):
+
+ Hash_Prime 30,011 (4,253)
+ Hash_Size 35,000 (5,000)
+ Max_Cites 7,500 (750)
+ Max_Ent_Ints 7,500 (3,000)
+ Max_Ent_Strs 10,000 (3,000)
+ Max_Fields 125,000 (17,250)
+ Max_Strings 30,000 (4,000)
+ Pool_Size 750,000 (65,530)
+ Wiz_Fn_Space 10,000 (3,000)
+
+ -M --min_crossrefs ##
+
+ Set min_crossrefs to ##. If an item is cross-referenced at
+ least ## times, it will be placed in the list of citations,
+ even if it is not explicitly \cited as a reference. The
+ default value is 2.
+
+ --mcites ##
+
+ Allow a maximum of ## distinct \cites in the .aux files.
+ This number must be less than the maximum number of strings
+ (settable with --mstrings).
+
+ --mentints ##
+
+ Allow a maximum of ## integer entries in the .bib databases.
+
+ --mentstrs ##
+
+ Allow a maximum of ## string entries in the .bib databases.
+
+ --mfields ##
+
+ Allow a maximum of ## fields in the .bib databases.
+
+ --mpool ##
+
+ Set the string pool to ## bytes.
+
+ --mstrings ##
+
+ Allow a maximum of ## unique strings. This number must be
+ less than the hash size and greater than the maximum number
+ of \cites (settable with --mcites).
+
+ --mwizfuns ##
+
+ Allow a maximum of ## wizard functions.
+
+
+ 3.2 Finding Files
+ -----------------
+
+ 8-bit BibTeX looks for input files in three different steps as summarised
+ below. As soon as 8-bit BibTeX finds a matching file, it stops looking
+ (i.e. only the first matching file is used). In order, the three steps
+ are:
+
+ - look for the file in the current working directory.
+
+ - if the appropriate environment variable has been set (e.g. BSTINPUT),
+ treat its value as a list of directories to be searched. Look for the
+ file in each of the directories in the list.
+
+ - if the appropriate environment variable (e.g. BSTINPUT) has not been
+ set, use a predefined "fallback" path as a list of directories to be
+ searched.
+
+ A search list consists of a number of directories separated by a delimiter
+ (semicolons for MS-DOS & OS/2, colons for Unix and commas for VMS).
+
+ As distributed, the strategy adopted by 8-bit BibTeX for opening specific
+ file types is
+
+ .aux files
+
+ - look in current working directory only
+
+ .bib (BibTeX database) files
+
+ - look in current working directory
+ - search along path defined by environment variable BIBINPUT
+ - search along fallback path (empty by default)
+
+ .bst (BibTeX style) files
+
+ - look in current working directory
+ - search along path defined by environment variable BSTINPUT
+ - search along fallback path (empty by default)
+
+ .csf (CS) files
+
+ - look in current working directory
+ - search along path defined by environment variable CSFINPUT
+ - search along fallback path (empty by default)
+
+ The name of the CS file is determined using a number of steps
+
+ - use value of --csfile command line option,
+ - use value of the BIBTEX_CSFILE environment variable
+ - use fallback CS file name (empty by default)
+
+ Output files
+
+ All of BibTeX's output (.bbl, .blg) files are created in the
+ current working directory.
+
+
+ The environment variables and fallback paths used by 8-bit BibTeX are
+ defined in the Makefile and set at compile time, but you can determine
+ what your version of 8-bit BibTeX is using by starting it with the command
+ line
+
+ bibtex --debug=search non-existent-file-name
+
+ The debugging output (written to the standard error device) should look
+ something like:
+
+ D-SCH: Search strategy for .aux files:
+ D-SCH: search path environment variable: <undefined>
+ D-SCH: fallback search path: <undefined>
+ D-SCH: Search strategy for .bib files:
+ D-SCH: search path environment variable: BIBINPUT
+ D-SCH: BIBINPUT value: e:\usr\c\bibtex
+ D-SCH: fallback search path: e:/usr/latex/bibtex;e:/emtex/bibtex/bib
+ D-SCH: Search strategy for .bst files:
+ D-SCH: search path environment variable: BSTINPUT
+ D-SCH: BSTINPUT value: <undefined>
+ D-SCH: fallback search path: e:/usr/latex/bibtex;e:/emtex/bibtex/bst
+ D-SCH: Search strategy for .csf files:
+ D-SCH: search path environment variable: CSFINPUT
+ D-SCH: CSFINPUT value: e:\usr\c\bibtex
+ D-SCH: fallback search path: e:/usr/latex/bibtex;e:/emtex/bibtex/csf
+ D-SCH: Default .csf file:
+ D-SCH: file name environment variable: BIBTEX_CSFILE
+ D-SCH: BIBTEX_CSFILE value: e:/emtex/texinput/cp437lat.csf
+ D-SCH: fallback file name: cp850lat.csf
+
+ The current working directory will always be searched, even if the
+ environment variable and fallback paths have not been specified (e.g. as
+ for .aux files in the above example).
+
+ If the default behaviour is not to your liking, you will need to rebuild
+ 8-bit BibTeX from its source code (see section 5).
+
+
+ 3.3 Environment variables
+ -------------------------
+
+ As supplied, 8-bit BibTeX uses a number of environment variables:
+
+ BIBINPUT search path for database (.bib) files
+ BSTINPUT search path for style (.bst) files
+ CSFINPUT search path for CS (.csf) files
+ BIBTEX_CSFILE the default CS file
+ TMP directory for virtual memory files (DOS only)
+
+ The name of the environment variables used may be changed (in the
+ Makefile) when BibTeX is built. See the appropriate Makefile for your
+ environment and remember that you can use the "--debug=search" command
+ line option to reveal the environment variables used by your version of
+ 8-bit BibTeX (see previous section).
+
+ All environment variables used as a search list (BIBINPUT, BSTINPUT &
+ CSFINPUT) can be set to a number of separate directories, separated
+ by a delimiter (semicolons for MS-DOS & OS/2, colons for Unix and
+ commas for VMS).
+
+ Examples for MS-DOS and OS/2 are:
+
+ SET BIBINPUT=e:\data\tex\bibtex;c:\emtex\bibtex\bib
+ SET BSTINPUT=e:\data\tex\bibtex;c:\emtex\bibtex\bst
+ SET CSFINPUT=e:\data\tex\bibtex
+ SET BIBTEX_CSFILE=c:\data\tex\bibtex\cp850lat.csf
+
+ Examples for Unix:
+
+ setenv BIBINPUT /u/kempson/bibtex:/usr/local/lib/tex/bib-files
+ setenv BSTINPUT /u/kempson/bibtex:/usr/local/lib/tex/bst-files
+ setenv CSFINPUT /u/kempson/bibtex:/usr/local/lib/tex/csf-files
+ setenv BIBTEX_CSFILE /usr/local/lib/tex/csf-files/88591lat.csf
+
+ Examples for VMS:
+
+ define BIBINPUT "sys$login:,disk$tex:[bibtex.bib-files]"
+ define BSTINPUT "sys$login:,disk$tex:[bibtex.bst-files]"
+ define CSFINPUT "sys$login:,disk$tex:[bibtex.csf-files]"
+ define BIBTEX_CSFILE disk$tex:[bibtex.csf-files]88951lat.csf
+
+
+
+4. The Codepage and Sort Order (CS) File
+-----------------------------------------
+
+The Codepage and Sort definition (CS) file is used to define the 8-bit
+character set used by BibTeX and the order in which those characters should
+be sorted.
+
+Please see the associated csfile.txt for details of CS file syntax and
+guidelines for testing new CS files. NOTE: it contains many 8-bit characters
+and may cause problems if you try to display or print it on 7-bit systems
+(e.g. older versions of Unix).
+
+
+
+5. Building 8-bit BibTeX from Source Code
+------------------------------------------
+
+The 8-bit BibTeX source is fairly standard ANSI C with almost no system
+specific code. It should therefore be relatively straightforward to build it
+in a different environment if you have GNU C or an ANSI C compiler.
+
+A number of Makefiles have been provided to build 8-bit BibTeX from source
+code:
+
+ dos-emx.mak makefile for EMX GNU C under MS-DOS
+ dos-dj.mak makefile for DJGPP GNU C under MS-DOS
+ os2.mak makefile for EMX GNU C under OS/2
+ unix.mak makefile for Unix variants
+
+Whichever Makefile you use, you need to check that the "local definitions"
+are appropriate for your system. There are three small sections to
+customise:
+
+ BibTeX File Searching
+
+ - specifies the names of environment variables and paths to be used when
+ searching for input files
+
+ Utility Programs
+
+ - specifies the names of programs to be used for simple functions
+
+ Compiler/Linker
+
+ - specifies compiler/linker command lines
+
+If your system is already supported it should not be necessary to modify any
+part of the Makefile except these three sections.
+
+Brief notes for specific environments follow.
+
+
+ 5.1 DOS
+ -------
+
+ 8-bit BibTeX has been built and tested using the EMX and DJGPP
+ development environments. Both are based on GNU C with their own
+ custom 32-bit extenders.
+
+
+ 5.2 OS/2
+ --------
+
+ The EMX development environment is supported.
+
+
+ 5.3 Unix
+ --------
+
+ Most variants of Unix supporting GNU C should be capable of building
+ and running 8-bit BibTeX.
+
+
+ 5.4 VMS
+ -------
+
+ The authors have not built or tested this version of 8-bit BibTeX on
+ VMS, but see no reason why it shouldn't compile and run successfully
+ if GNU C is installed on the system. (The only system-dependent code
+ in 8-bit BibTeX concerns file opening and provision has been made for
+ VMS file modes.)
+
+ If you have GNU C installed, we recommend starting with a copy of the
+ unix.mak Makefile and customising it for VMS. If you successfully
+ get 8-bit BibTeX running under VMS, *please* let the authors know how
+ you did it.
+
+
+
+6. Reporting Bugs and Requesting Improvements
+----------------------------------------------
+
+Where possible, we will try to fix bugs and will consider requests for
+improvements. If you are reporting a bug, please provide as much information
+as possible (e.g. operating environment, 8-bit BibTeX version and source,
+exact error message and the offending files if possible).
+
+The most common message is of the form "BibTeX doesn't work on XXXX". This
+is generally of no help in debugging a problem so please provide as much
+information as possible.
+
+
+ 6.1 Contacting the authors
+ --------------------------
+
+ The authors are
+
+ Niel Kempson
+ Snowy Owl Systems Limited, Cheltenham, England
+ E-mail: kempson@snowyowl.co.uk
+
+ and
+
+ Alejandro Aguilar-Sierra
+ Centro de Ciencias de la Atm\'osfera,
+ Universidad Nacional Aut\'onoma de M\'exico, M\'exico
+ E-mail: asierra@servidor.unam.mx
+
+ Niel Kempson did the original manual translation from WEB to C,
+ conversion to "big" (32-bit) capacity, addition of run-time selectable
+ capacity and part of the 8-bit support extensions. He intermittently
+ maintains the master version of the source code.
+
+ Alejandro Aguilar-Sierra should take the credit for most of the 8-bit
+ function provided by this version of BibTeX.
+
+
+ 6.2 Further Enhancements
+ ------------------------
+
+ No program is perfect and this version of BibTeX is no exception to that
+ rule. Some known weaknesses are:
+
+ - the 8-bit support is currently limited to single 8-bit characters.
+ TeX control sequences (e.g. \'{A}) are not interpreted and treated in
+ the same way as the equivalent 8-bit character.
+
+ - it is not possible to redefine the lower 128 character codes. This
+ excludes support for character codes not built on ASCII (e.g. EBCDIC).
+
+ Future enhancements will be considered, but it may be time to build a
+ "proper" system built from the ground up to handle 8-bit character
+ sets. BibTeX 1.0 promises to be this system.
+
+ Other items that ought to be on the "to do" list:
+
+ - path searching using Karl Berry's kpathsea package
+ - TeX format documentation
+ - Unix man pages
+ - OS/2 .inf format documentation
+ - native 32-bit support for MS Windows 95/NT
+
+
+
+7. Frequently Asked Questions
+------------------------------
+
+When I run the DOS version 8-bit BibTeX in a DOS window under MS Windows 3.x,
+95 or NT, I get the message "DPMI not supported".
+
+ 8-bit BibTeX has been built using the EMX development environment. It
+ uses the VCPI mechanism to run in 32-bit mode and will therefore not run
+ in a DOS session under MS Windows.
+
+ If you want to run this version of 8-bit BibTeX in a DOS session under
+ MS Windows, you have two choices:
+
+ - get and install the RSX extender
+ - rebuild from sources using a suitable compiler
+
+ See section 2.1 for more information.
+
+
+8-bit BibTeX doesn't find my .bib/.bst files. How can I find out where it
+looks for them?
+
+ See section 3.2
+
+
+There isn't a CS file for my character set / language sorting order
+
+ Creating a new CS file should be relatively straightforward. If you'd
+ like to try, please contact the authors for assistance. If you don't
+ need assistance, *please* let us have a copy of your finished CS file so
+ we can include it in the distribution.
+
+
+
+8. Acknowledgement
+-------------------
+
+The original BibTeX was written by Oren Patashnik using Donald Knuth's WEB
+system. This format produces a PASCAL program for execution and a TeX
+documented version of the source code. This program started as a (manual)
+translation of the WEB source into C.
+
+
+
+9. BibTeX Use and Copying Conditions
+-------------------------------------
+
+The programs currently being distributed that relate to 8-bit BibTeX are
+*free*; this means that everyone may use them and redistribute them freely.
+The 8-bit BibTeX-related programs are not in the public domain; they are
+copyrighted and there are restrictions on their distribution, but these
+restrictions are designed to permit everything that a good cooperating
+citizen would want to do. What is not allowed is to try to prevent others
+from further sharing any version of these programs that they might get from
+you.
+
+Specifically, we want to make sure that you have the right to give away
+copies of the programs that relate to 8-bit BibTeX, that you receive source
+code or else can get it if you want it, that you can change these programs or
+use pieces of them in new free programs, and that you know you can do these
+things.
+
+To make sure that everyone has such rights, we have to forbid you to deprive
+anyone else of these rights. For example, if you distribute copies of the
+8-bit BibTeX related programs, you must give the recipients all the rights
+that you have. You must make sure that they, too, receive or can get the
+source code. And you must tell them their rights.
+
+Also, for our own protection, we must make certain that everyone finds out
+that there is no warranty for the programs that relate to 8-bit BibTeX. If
+these programs are modified by someone else and passed on, we want their
+recipients to know that what they have is not what we distributed, so that
+any problems introduced by others will not reflect on our reputation.
+
+The precise conditions of the licences for the programs currently being
+distributed that relate to 8-bit BibTeX are found in the General Public
+Licences that accompany them.
+
+
+
+10. Change Log
+---------------
+
+$Log: 00readme.txt,v $
+Revision 3.71 1996/08/18 20:38:55 kempson
+Official release 3.71 (see HISTORY for details).
+
+Revision 3.70 1996/04/29 20:17:53 kempson
+Final documentation & cosmetic changes for official release 3.70.
+
+Revision 1.2 1995/10/21 22:23:01 kempson
+Updated for v3.60 beta. Added description of --wolfgang option.
+Added some more information on running BibTeX in a Windows DOS session.
+Changed the example of CSF debugging output to something that is correct.
+
+Revision 1.1 1995/09/24 20:50:00 kempson
+Updated for the final beta test release.
+
+Revision 1.0 1995/09/24 20:42:30 kempson
+Placed under RCS control
+
+******************************** END OF FILE *******************************
diff --git a/Build/source/texk/bibtex-x/csf/88591lat.csf b/Build/source/texk/bibtex-x/csf/88591lat.csf
new file mode 100644
index 00000000000..0d324057f4c
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/88591lat.csf
@@ -0,0 +1,313 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: 88591lat.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:15 $
+%%
+%% CHARACTER SET: ISO 8859-1
+%%
+%% ISO 8859-1 is the system character set used by Unix/X Windows and
+%% MS Windows.
+%%
+%% SORTING ORDER: Latin countries
+%%
+%% Alphabetical sorting order of Aa..Zz (including accented characters).
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: 88591lat.csf,v $
+%% Revision 1.1 1996/08/04 20:48:15 kempson
+%% Added missing sort entries for 0..9 and 'd'.
+%%
+%% Revision 1.0 1995/10/21 22:10:28 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% The ISO 8859-1 code page contains an equal number of upper and lower
+%% case accented characters so we can use the \lowupcase{} section. The
+%% \lowercase{} and \uppercase{} sections are not used.
+%%
+\lowupcase{ % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ à À % ^^e0 \`{a} ^^c0 \`{A}
+ á Á % ^^e1 \'{a} ^^c1 \'{A}
+ â Â % ^^e2 \^{a} ^^c2 \^{A}
+ ã Ã % ^^e3 \~{a} ^^c3 \~{A}
+ ä Ä % ^^e4 \"{a} ^^c4 \"{A}
+ å Å % ^^e5 \aa ^^c5 \AA
+ æ Æ % ^^e6 \ae ^^c6 \AE
+ ç Ç % ^^e7 \c{c} ^^c7 \c{C}
+ è È % ^^e8 \`{e} ^^c8 \`{E}
+ é É % ^^e9 \'{e} ^^c9 \'{E}
+ ê Ê % ^^ea \^{e} ^^ca \^{E}
+ ë Ë % ^^eb \"{e} ^^cb \"{E}
+ ì Ì % ^^ec \`{\i} ^^cc \`{I}
+ í Í % ^^ed \'{\i} ^^cd \'{I}
+ î Î % ^^ee \^{\i} ^^ce \^{I}
+ ï Ï % ^^ef \"{\i} ^^cf \"{I}
+ ð Ð % ^^f0 eth ^^d0 ETH
+ ñ Ñ % ^^f1 \~{n} ^^d1 \~{N}
+ ò Ò % ^^f2 \`{o} ^^d2 \`{O}
+ ó Ó % ^^f3 \'{o} ^^d3 \'{O}
+ ô Ô % ^^f4 \^{o} ^^d4 \^{O}
+ õ Õ % ^^f5 \~{o} ^^d5 \~{O}
+ ö Ö % ^^f6 \"{o} ^^d6 \"{O}
+ ø Ø % ^^f8 \o ^^d8 \O
+ ù Ù % ^^f9 \`{u} ^^d9 \`{U}
+ ú Ú % ^^fa \'{u} ^^da \'{U}
+ û Û % ^^fb \^{u} ^^db \^{U}
+ ü Ü % ^^fc \"{u} ^^dc \"{U}
+ ý Ý % ^^fd \'{y} ^^dd \'{Y}
+ þ Þ % ^^fe thorn ^^de THORN
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is the natural language sorting order
+%% of 0..9Aa..Zz (including accented characters).
+%%
+\order{
+ 0-9
+ %
+ % The next line can be written in full or abbreviated using the "_"
+ % convention. The two equivalent alternatives are:
+ %
+ % A À Á Â Ã Ä Å a à á â ã ä å
+ % A À_Å a à_å
+ %
+ A À Á Â Ã Ä Å a à á â ã ä å
+ B b
+ C Ç c ç
+ D d
+
+ %
+ % The next line can be written in full or abbreviated using the "_"
+ % convention. The two equivalent alternatives are:
+ %
+ % E È É Ê Ë e è é ê ë
+ % E È_Ë e è_ë
+ %
+ E È É Ê Ë e è é ê ë
+ F f
+ G g
+ H h
+
+ %
+ % The next line can be written in full or abbreviated using the "_"
+ % convention. The two equivalent alternatives are:
+ %
+ % I Ì Í Î Ï i ì í î ï
+ % I Ì_Ï i ì_ï
+ %
+ I Ì Í Î Ï i ì í î ï
+ J j
+ K k
+ L l
+ M m
+ N n
+ Ñ ñ
+
+ %
+ % The next line can be written in full or abbreviated using the "_"
+ % convention. The two equivalent alternatives are:
+ %
+ % O Ò Ó Ô Õ Ö o ò ó ô õ ö
+ % O Ò_Ö o ò_ö
+ %
+ O Ò Ó Ô Õ Ö o ò ó ô õ ö
+ P p
+ Q q
+ R r
+ S s
+ T t
+
+ %
+ % The next line can be written in full or abbreviated using the "_"
+ % convention. The two equivalent alternatives are:
+ %
+ % U Ù Ú Û Ü u ù ú û ü
+ % U Ù_Ü u ù_ü
+ %
+ U Ù Ú Û Ü u ù ú û ü
+ V v
+ W w
+ X x
+ Y y
+ Z z
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/88591sca.csf b/Build/source/texk/bibtex-x/csf/88591sca.csf
new file mode 100644
index 00000000000..b2a524430e5
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/88591sca.csf
@@ -0,0 +1,283 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: 88591sca.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:52 $
+%%
+%% CHARACTER SET: ISO 8859-1
+%%
+%% ISO 8859-1 is the system character set used by Unix/X Windows and
+%% MS Windows.
+%%
+%% SORTING ORDER: Scandinavean countries
+%%
+%% The sorting order defined is a compromise between Norwegian/Danish
+%% and Swedish.
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: 88591sca.csf,v $
+%% Revision 1.1 1996/08/04 20:48:52 kempson
+%% Added missing sort entries for 0..9
+%%
+%% Revision 1.0 1995/10/21 22:10:29 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% The ISO 8859-1 code page contains an equal number of upper and lower
+%% case accented characters so we can use the \lowupcase{} section. The
+%% \lowercase{} and \uppercase{} sections are not used.
+%%
+\lowupcase{ % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ à À % ^^e0 \`{a} ^^c0 \`{A}
+ á Á % ^^e1 \'{a} ^^c1 \'{A}
+ â Â % ^^e2 \^{a} ^^c2 \^{A}
+ ã Ã % ^^e3 \~{a} ^^c3 \~{A}
+ ä Ä % ^^e4 \"{a} ^^c4 \"{A}
+ å Å % ^^e5 \aa ^^c5 \AA
+ æ Æ % ^^e6 \ae ^^c6 \AE
+ ç Ç % ^^e7 \c{c} ^^c7 \c{C}
+ è È % ^^e8 \`{e} ^^c8 \`{E}
+ é É % ^^e9 \'{e} ^^c9 \'{E}
+ ê Ê % ^^ea \^{e} ^^ca \^{E}
+ ë Ë % ^^eb \"{e} ^^cb \"{E}
+ ì Ì % ^^ec \`{\i} ^^cc \`{I}
+ í Í % ^^ed \'{\i} ^^cd \'{I}
+ î Î % ^^ee \^{\i} ^^ce \^{I}
+ ï Ï % ^^ef \"{\i} ^^cf \"{I}
+ ð Ð % ^^f0 eth ^^d0 ETH
+ ñ Ñ % ^^f1 \~{n} ^^d1 \~{N}
+ ò Ò % ^^f2 \`{o} ^^d2 \`{O}
+ ó Ó % ^^f3 \'{o} ^^d3 \'{O}
+ ô Ô % ^^f4 \^{o} ^^d4 \^{O}
+ õ Õ % ^^f5 \~{o} ^^d5 \~{O}
+ ö Ö % ^^f6 \"{o} ^^d6 \"{O}
+ ø Ø % ^^f8 \o ^^d8 \O
+ ù Ù % ^^f9 \`{u} ^^d9 \`{U}
+ ú Ú % ^^fa \'{u} ^^da \'{U}
+ û Û % ^^fb \^{u} ^^db \^{U}
+ ü Ü % ^^fc \"{u} ^^dc \"{U}
+ ý Ý % ^^fd \'{y} ^^dd \'{Y}
+ þ Þ % ^^fe thorn ^^de THORN
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is a compromise between Norwegian/Danish and
+%% Swedish.
+%%
+%% Norwegian/Danish sorting order: 0..9Aa..ZzÆæØøÅå
+%% Swedish sorting order: 0..9Aa..ZzÅåÄäÖö
+%% Compromise sorting order: 0..9Aa..ZzÆæØøÅåÄäÖö
+%%
+\order{
+ 0-9
+ A a
+ B b
+ C c
+ D d
+ E e
+ F f
+ G g
+ H h
+ I i
+ J j
+ K k
+ L l
+ M m
+ N n
+ O o
+ P p
+ Q q
+ R r
+ S s
+ T t
+ U u
+ V v
+ W w
+ X x
+ Y y
+ Z z
+ Æ æ
+ Ø ø
+ Å å
+ Ä ä
+ Ö ö
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/COPYING b/Build/source/texk/bibtex-x/csf/COPYING
new file mode 100644
index 00000000000..a43ea2126fb
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/COPYING
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/Build/source/texk/bibtex-x/csf/HISTORY b/Build/source/texk/bibtex-x/csf/HISTORY
new file mode 100644
index 00000000000..9a2d123c2c3
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/HISTORY
@@ -0,0 +1,61 @@
+******************************************************************************
+FILE: $RCSfile: HISTORY,v $
+ $Revision: 3.71 $
+ $Date: 1996/08/18 20:42:32 $
+******************************************************************************
+
+
+8-Bit BibTeX CHANGE HISTORY
+---------------------------
+
+v3.71 18-August-1996 Niel Kempson <snowyowl.co.uk>
+
+ - Changed default environment variables used for consistency across OS
+ implementations and better compatibility with emTeX. Now uses
+ BIBINPUT, BSTINPUT & CSFINPUT as the default environment variables
+ for .bib, .bst and .csf files respectively.
+
+ "Hard-coded" fallback search paths can now be specified for use if
+ the chosen environment variables are not defined. The environment
+ variables and the fallback paths are now defined in the Makefile
+ rather than in sysdep.h.
+
+ Thanks to Lars Frellesen <frelle@math-tech.dk> for spotting the
+ inconsistency and his Makefile suggestions.
+
+ - Fixed bug in handling of CSF \order section. Any alpha or numeric
+ character may now be specified in the sort order - previously only
+ alphas were allowed and BibTeX didn't correctly sort citations like
+ Knuth89, Knuth92 because the digits were ignored during sort
+ comparisons. Corrected example CS files to include digits in the
+ sort orders. Thanks to Andrei Grinkevitch <grin@bals.usr.pu.ru> for
+ spotting this one.
+
+ - Included the first contributed CS file: for codepage 866 with a Russian
+ sorting order. Thanks again to Andrei Grinkevitch <grin@bals.usr.pu.ru>.
+
+ - Added the missing 'd' to the sort section of 88591lat.csf. Thanks to
+ Tim Geisler <geisler@pms.informatik.uni-muenchen.de>.
+
+ - Removed CS files from all but the bt371csf.zip distribution file.
+
+ - Clarified 00readme.txt, specifically sections dealing with environment
+ variables and CS files. Moved 8-bit section describing CS files into
+ a separate csfile.txt because some people were having problems when
+ they tried to view the 8-bit 00readme.txt file on a 7-bit Unix
+ system. Thanks to Ken Smith <kgs@maths.uq.oz.au> for highlighting
+ this issue.
+
+ - Reinstated the -W option (--wolfgang did work). Thanks to Thomas
+ Plagwitz <tplagiwt@ix.urz.uni-heidelberg.de> for spotting this.
+
+ - Fixed str_lookup() to work with a hash size > 32767.
+
+ - Created new HISTORY file.
+
+
+v3.70 29-Apr-1996 Niel Kempson <snowyowl.co.uk>
+
+ Final documentation & cosmetic changes for official release 3.70.
+
+******************************** END OF FILE *******************************
diff --git a/Build/source/texk/bibtex-x/csf/ascii.csf b/Build/source/texk/bibtex-x/csf/ascii.csf
new file mode 100644
index 00000000000..30c180c0238
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/ascii.csf
@@ -0,0 +1,242 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: ascii.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:52 $
+%%
+%% CHARACTER SET: ASCII only
+%%
+%% No 8-bit characters are defined in this file. BibTeX will not accept
+%% characters with a value >= 128.
+%%
+%% SORTING ORDER: English
+%%
+%% BibTeX's standard sorting order is based simply on the codepage
+%% value of each character, resulting in an alphabetical sorting
+%% order of A..Za..z. We want a "normal" English sorting order of
+%% Aa..Zz.
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: ascii.csf,v $
+%% Revision 1.1 1996/08/04 20:48:52 kempson
+%% Added missing sort entries for 0..9
+%%
+%% Revision 1.0 1995/10/21 22:10:30 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% There are no character codes > 127 in ASCII, so we don't need \lowupcase,
+%% \lowercase or \uppercase sections.
+%%
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is the natural English language sorting order
+%% (i.e. 0..9AaBb..YyZz). Any other characters will be sorted after the
+%% characters in the \order section.
+%%
+\order{
+ 0-9
+ A a
+ B b
+ C c
+ D d
+ E e
+ F f
+ G g
+ H h
+ I i
+ J j
+ K k
+ L l
+ M m
+ N n
+ O o
+ P p
+ Q q
+ R r
+ S s
+ T t
+ U u
+ V v
+ W w
+ X x
+ Y y
+ Z z
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/cp437lat.csf b/Build/source/texk/bibtex-x/csf/cp437lat.csf
new file mode 100644
index 00000000000..dd69c90147f
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/cp437lat.csf
@@ -0,0 +1,281 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: cp437lat.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:52 $
+%%
+%% CHARACTER SET: IBM Code Page 437
+%%
+%% SORTING ORDER: Latin countries
+%%
+%% Alphabetical sorting order of Aa..Zz (including accented characters).
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: cp437lat.csf,v $
+%% Revision 1.1 1996/08/04 20:48:52 kempson
+%% Added missing sort entries for 0..9
+%%
+%% Revision 1.0 1995/10/21 22:10:31 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% The 437 code page does not contain an equal number of upper and lower
+%% case accented characters. There are a small number of characters where
+%% the upper and lower case pairs are present, but most accented characters
+%% are present in lower case form only.
+%%
+%% The pairs are defined in the \lowupcase section, and the unpaired lower
+%% case accented characters are given unaccented upper case equivalents in
+%% the \uppercase section.
+%%
+%% There are no unpaired upper case accented characters so a \lowercase
+%% section is not required.
+%%
+\lowupcase { % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ „ Ž % ^^84 \"{a} ^^8e \"{A}
+ † % ^^86 \aa ^^8f \AA
+ ‘ ’ % ^^91 \ae ^^92 \AE
+ ‡ € % ^^87 \c{c} ^^80 \c{C}
+ ‚ % ^^82 \'{e} ^^90 \'{E}
+ ¤ ¥ % ^^a4 \~{n} ^^a5 \~{N}
+ ” ™ % ^^94 \"{o} ^^99 \"{O}
+ š % ^^81 \"{u} ^^9a \"{U}
+}
+
+
+\uppercase{ % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ … A % ^^85 \`{a} A CP437 has no \`{A}
+   A % ^^a0 \'{a} A CP437 has no \'{A}
+ ƒ A % ^^83 \^{a} A CP437 has no \^{A}
+ Š E % ^^8a \`{e} E CP437 has no \`{E}
+ ˆ E % ^^88 \^{e} E CP437 has no \^{E}
+ ‰ E % ^^89 \"{e} E CP437 has no \"{E}
+ I % ^^8d \`{\i} I CP437 has no \`{I}
+ ¡ I % ^^a1 \'{\i} I CP437 has no \'{I}
+ ΠI % ^^8c \^{\i} I CP437 has no \^{I}
+ ‹ I % ^^8b \"{\i} I CP437 has no \"{I}
+ • O % ^^95 \`{o} O CP437 has no \`{O}
+ ¢ O % ^^a2 \'{o} O CP437 has no \'{O}
+ “ O % ^^93 \^{o} O CP437 has no \^{O}
+ — U % ^^97 \`{u} U CP437 has no \`{U}
+ £ U % ^^a3 \'{u} U CP437 has no \'{U}
+ – U % ^^96 \^{u} U CP437 has no \^{U}
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is the natural language sorting order
+%% of 0..9Aa..Zz (including accented characters).
+%%
+\order{
+ 0-9
+ A Ž a …   ƒ „ †
+ ’ ‘
+ B b
+ C € c ‡
+ D d
+ E e Š ‚ ˆ ‰
+ F f
+ G g
+ H h
+ I i ¡ Œ ‹
+ J j
+ K k
+ L l
+ M m
+ N n
+ ¥ ¤
+ O ™ o • ¢ “ ”
+ P p
+ Q q
+ R r
+ S s
+ á
+ T t
+ U š u — £ –
+ V v
+ W w
+ X x
+ Y y
+ Z z
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/cp850lat.csf b/Build/source/texk/bibtex-x/csf/cp850lat.csf
new file mode 100644
index 00000000000..2387da972f9
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/cp850lat.csf
@@ -0,0 +1,272 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: cp850lat.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:52 $
+%%
+%% CHARACTER SET: IBM Code Page 850
+%%
+%% SORTING ORDER: Latin countries
+%%
+%% Alphabetical sorting order of Aa..Zz (including accented characters).
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: cp850lat.csf,v $
+%% Revision 1.1 1996/08/04 20:48:52 kempson
+%% Added missing sort entries for 0..9
+%%
+%% Revision 1.0 1995/10/21 22:10:32 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% The 850 code page contains an equal number of upper and lower case
+%% accented characters so we can use the \lowupcase{} section. The
+%% \lowercase{} and \uppercase{} sections are not used.
+%%
+
+\lowupcase{ % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ … · % ^^85 \`{a} ^^b7 \`{A}
+   µ % ^^a0 \'{a} ^^b5 \'{A}
+ ƒ ¶ % ^^83 \^{a} ^^b6 \^{A}
+ Æ Ç % ^^c6 \~{a} ^^c7 \~{A}
+ „ Ž % ^^84 \"{a} ^^8e \"{A}
+ † % ^^86 \aa ^^8f \AA
+ ‘ ’ % ^^91 \ae ^^92 \AE
+ ‡ € % ^^87 \c{c} ^^80 \c{C}
+ Š Ô % ^^8a \`{e} ^^d4 \`{E}
+ ‚ % ^^82 \'{e} ^^90 \'{E}
+ ˆ Ò % ^^88 \^{e} ^^d2 \^{E}
+ ‰ Ó % ^^89 \"{e} ^^d3 \"{E}
+ Þ % ^^8d \`{\i} ^^de \`{I}
+ ¡ Ö % ^^a1 \'{\i} ^^d6 \'{I}
+ Œ × % ^^8c \^{\i} ^^d7 \^{I}
+ ‹ Ø % ^^8b \"{\i} ^^d8 \"{I}
+ ¤ ¥ % ^^a4 \~{n} ^^a5 \~{N}
+ • ã % ^^95 \`{o} ^^e3 \`{O}
+ ¢ à % ^^a2 \'{o} ^^e0 \'{O}
+ “ â % ^^93 \^{o} ^^e2 \^{O}
+ ä å % ^^e4 \~{o} ^^e5 \~{O}
+ ” ™ % ^^94 \"{o} ^^99 \"{O}
+ › % ^^9b \o ^^9d \O
+ — ë % ^^97 \`{u} ^^eb \`{U}
+ £ é % ^^a3 \'{u} ^^e9 \'{U}
+ – ê % ^^96 \^{u} ^^ea \^{U}
+ š % ^^81 \"{u} ^^9a \"{U}
+ ì í % ^^ec \'{y} ^^ed \'{Y}
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is the natural language sorting order
+%% of 0-9Aa..Zz (including accented characters).
+%%
+\order{
+ 0-9
+ A · µ ¶ Ç Ž a …   ƒ Æ „ †
+ ’ ‘
+ B b
+ C € c ‡
+ D d
+ E Ô Ò Ó e Š ‚ ˆ ‰
+ F f
+ G g
+ H h
+ I Þ Ö × Ø i ¡ Œ ‹
+ J j
+ K k
+ L l
+ M m
+ N n
+ ¥ ¤
+ O ã à â å ™ o • ¢ “ ä ”
+ P p
+ Q q
+ R r
+ S s
+ á
+ T t
+ U ë é ê š u — £ –
+ V v
+ W w
+ X x
+ Y y
+ Z z
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/cp850sca.csf b/Build/source/texk/bibtex-x/csf/cp850sca.csf
new file mode 100644
index 00000000000..3e51bc21a04
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/cp850sca.csf
@@ -0,0 +1,279 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: cp850sca.csf,v $
+%% $Revision: 1.1 $
+%% $Date: 1996/08/04 20:48:52 $
+%%
+%% CHARACTER SET: IBM Code Page 850
+%%
+%% SORTING ORDER: Scandinavean countries
+%%
+%% The sorting order defined is a compromise between Norwegian/Danish
+%% and Swedish.
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: cp850sca.csf,v $
+%% Revision 1.1 1996/08/04 20:48:52 kempson
+%% Added missing sort entries for 0..9
+%%
+%% Revision 1.0 1995/10/21 22:10:33 kempson
+%% Placed under RCS control
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+%% The 850 code page contains an equal number of upper and lower
+%% case accented characters so we can use the \lowupcase{} section. The
+%% \lowcase{} and \upcase{} sections are not used.
+%%
+
+\lowupcase{ % Lowercase Uppercase
+ % Code TeX Code TeX
+ %
+ … · % ^^85 \`{a} ^^b7 \`{A}
+   µ % ^^a0 \'{a} ^^b5 \'{A}
+ ƒ ¶ % ^^83 \^{a} ^^b6 \^{A}
+ Æ Ç % ^^c6 \~{a} ^^c7 \~{A}
+ „ Ž % ^^84 \"{a} ^^8e \"{A}
+ † % ^^86 \aa ^^8f \AA
+ ‘ ’ % ^^91 \ae ^^92 \AE
+ ‡ € % ^^87 \c{c} ^^80 \c{C}
+ Š Ô % ^^8a \`{e} ^^d4 \`{E}
+ ‚ % ^^82 \'{e} ^^90 \'{E}
+ ˆ Ò % ^^88 \^{e} ^^d2 \^{E}
+ ‰ Ó % ^^89 \"{e} ^^d3 \"{E}
+ Þ % ^^8d \`{\i} ^^de \`{I}
+ ¡ Ö % ^^a1 \'{\i} ^^d6 \'{I}
+ Œ × % ^^8c \^{\i} ^^d7 \^{I}
+ ‹ Ø % ^^8b \"{\i} ^^d8 \"{I}
+ ¤ ¥ % ^^a4 \~{n} ^^a5 \~{N}
+ • ã % ^^95 \`{o} ^^e3 \`{O}
+ ¢ à % ^^a2 \'{o} ^^e0 \'{O}
+ “ â % ^^93 \^{o} ^^e2 \^{O}
+ ä å % ^^e4 \~{o} ^^e5 \~{O}
+ ” ™ % ^^94 \"{o} ^^99 \"{O}
+ › % ^^9b \o ^^9d \O
+ — ë % ^^97 \`{u} ^^eb \`{U}
+ £ é % ^^a3 \'{u} ^^e9 \'{U}
+ – ê % ^^96 \^{u} ^^ea \^{U}
+ š % ^^81 \"{u} ^^9a \"{U}
+ ì í % ^^ec \'{y} ^^ed \'{Y}
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%% The sorting order defined is a compromise between Norwegian/Danish and
+%% Swedish.
+%%
+%% Norwegian/Danish sorting order: 0..9Aa..Zz’‘›†
+%% Swedish sorting order: 0..9Aa..Zz†Ž„™”
+%% Compromise sorting order: 0..9Aa..Zz’‘›†Ž„™”
+%%
+\order{
+ 0-9
+ A a
+ B b
+ C c
+ D d
+ E e
+ F f
+ G g
+ H h
+ I i
+ J j
+ K k
+ L l
+ M m
+ N n
+ O o
+ P p
+ Q q
+ R r
+ S s
+ T t
+ U u
+ V v
+ W w
+ X x
+ Y y
+ Z z
+ ’ ‘
+ ›
+ †
+ Ž „
+ ™ ”
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/cp866rus.csf b/Build/source/texk/bibtex-x/csf/cp866rus.csf
new file mode 100644
index 00000000000..54d950dec6e
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/cp866rus.csf
@@ -0,0 +1,296 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE: $RCSfile: cp866rus.csf,v $
+%% $Revision: 1.0 $
+%% $Date: 1996/08/04 20:59:12 $
+%%
+%% Date: 1996/05/03
+%% Author:-) Andrei Grinkevitch, grin@bals.usr.pu.ru
+%%
+%% CHARACTER SET: Russian (CP 866)
+%%
+%% SORTING ORDER: Russian
+%%
+%% WARNING
+%%
+%% This is a BibTeX Codepage and Sort definition file (CSF). It is
+%% used to define the 8-bit character set used by BibTeX and the
+%% order in which those characters should be sorted. The file
+%% format is documented below this header section.
+%%
+%% This file will only work with the 8-bit implementation of BibTeX
+%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
+%% available by anonymous FTP from these Comprehensive TeX Archive
+%% Network (CTAN) sites:
+%%
+%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
+%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
+%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
+%%
+%% CHANGE LOG
+%%
+%% $Log: cp866rus.csf,v $
+%% Revision 1.0 1996/08/04 20:59:12 kempson
+%% Initial revision
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%
+%% FILE FORMAT
+%%
+%% The codepage and sorting order (CS) file defines how BibTeX will treat an
+%% 8-bit character set, specifically which characters are to be treated as
+%% letters, the upper/lower case relationships between characters, and the
+%% sorting order of characters.
+%%
+%% The CS file may contain a number of sections, each presented in the
+%% form of a TeX macro:
+%%
+%% \section-name{
+%% <section definitions>
+%% }
+%%
+%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+%% and \order. The syntax of the four supported sections is summarised below.
+%%
+%% 8-bit characters may be entered naturally, but to avoid problems with
+%% character set translation or corruption, they can also be entered using
+%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+%% is the hexadecimal value ofthe character code.
+%%
+%% Reading of the sections ends when the first '}' character is reached, so
+%% '}' can't be included in a section. You can't use ^^7d either.
+%%
+%% The percent sign ('%') is used to introduce a trailing comment - it and
+%% all remaining characters on a line are ignored. ^^25 has the same effect.
+%%
+%%
+%% \lowupcase section
+%%
+%% The \lowupcase section of the CS file is used to define the lower
+%% /upper and upper/lower case relationship of pairs of specified
+%% characters. It is only used if the relationship is symmetrical - use
+%% \lowercase or \upcase if it isn't.
+%%
+%% The syntax of the \lowupcase section is:
+%%
+%% \lowupcase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+%% <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower or upper case equivalent of an ASCII
+%% character (code < 128), so all instances of <LC-n> and <UC-n>
+%% (i.e. both sides of the relationship) must have codes > 127.
+%%
+%%
+%% \lowercase section
+%%
+%% The \lowercase section of the CS file is used to define the lower case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \lowercase section is:
+%%
+%% \lowercase{
+%% <UC-1> <LC-1> % Comment begins with a percent sign
+%% <UC-2> <LC-2>
+%% ...
+%% <UC-N> <LC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the lower case
+%% equivalent of <UC-n> is <LC-n>.
+%%
+%% You cannot redefine the lower case equivalent of an ASCII character
+%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \uppercase section
+%%
+%% The \uppercase section of the CS file is used to define the upper case
+%% equivalent of specified characters. It should normally only be used
+%% if the relationship isn't symmetrical - use \lowupcase if it is.
+%%
+%% The syntax of the \uppercase section is:
+%%
+%% \uppercase{
+%% <LC-1> <UC-1> % Comment begins with a percent sign
+%% <LC-2> <UC-2>
+%% ...
+%% <LC-N> <UC-N>
+%% }
+%%
+%% Each <LC-n> <UC-n> pair of characters defines that the upper case
+%% case equivalent of <LC-n> is <UC-n>.
+%%
+%% You cannot redefine the upper case equivalent of an ASCII character
+%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
+%% of the relationship) must have codes > 127.
+%%
+%%
+%% \order section
+%%
+%% The \order section of the CS file is used to define the order in which
+%% characters are sorted.
+%%
+%% The syntax of the \order section is:
+%%
+%% \order{
+%% <char-1> % Comment begins with a percent sign
+%% <char-2> <char-3> % whitespace between the chars
+%% <char-4> - <char-5> % a hyphen between the chars
+%% <char-4> _ <char-5> % an underscore between the chars
+%% ...
+%% <char-n>
+%% }
+%%
+%% All characters on the same line are given the same sorting weight.
+%%
+%% The construct <char-1> <underscore> <char-2> is used to denote that
+%% all characters in the range <char-1> to <char-2> should be given the
+%% same sorting weight. For example, "A _ Z" would cause all ASCII
+%% upper case alphabetical characters to have the same sorting weight
+%% and would be equivalent to placing all 26 characters on the same line.
+%%
+%% The construct <char-1> <hyphen> <char-2> is used to denote that all
+%% characters in the range <char-1> to <char-2> should be given an
+%% ascending set of sorting weights, starting with <char-1> and ending
+%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
+%% alphabetical characters to be sorted in ascending order and would be
+%% equivalent to placing 'A' on the first line, 'B' on the second,
+%% through to 'Z' on the 26th line.
+%%
+%% The characters at the beginning of the order section are given a lower
+%% sorting weight than characters occuring later. When sorting
+%% alphabetically, characters with the lowest weight come first.
+%%
+%% All characters not in the \order section (including ASCII characters)
+%% are given the same very high sorting weight to ensure that they come
+%% last when sorting alphabetically.
+%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+
+
+%%
+%% CHARACTER SET
+%%
+\lowupcase{
+   €
+ ¡
+ ¢ ‚
+ £ ƒ
+ ¤ „
+ ¥ …
+ ñ ð
+ ¦ †
+ § ‡
+ ¨ ˆ
+ © ‰
+ ª Š
+ « ‹
+ ¬ Œ
+ ­
+ ® Ž
+ ¯
+ à
+ á ‘
+ â ’
+ ã “
+ ä ”
+ å •
+ æ –
+ ç —
+ è ˜
+ é ™
+ ê š
+ ë ›
+ ì œ
+ í
+ î ž
+ ï Ÿ
+}
+
+
+
+%%
+%% SORTING ORDER
+%%
+%%
+\order{
+ 0-9
+ A a
+ B b
+ C c
+ D d
+ E e
+ F f
+ G g
+ H h
+ I i
+ J j
+ K k
+ L l
+ M m
+ N n
+ O o
+ P p
+ Q q
+ R r
+ S s
+ T t
+ U u
+ V v
+ W w
+ X x
+ Y y
+ Z z
+ €  
+ ¡
+ ‚ ¢
+ ƒ £
+ „ ¤
+ … ¥
+ ð ñ
+ † ¦
+ ‡ §
+ ˆ ¨
+ ‰ ©
+ Š ª
+ ‹ «
+ Œ ¬
+ ­
+ Ž ®
+ ¯
+ à
+ ‘ á
+ ’ â
+ “ ã
+ ” ä
+ • å
+ – æ
+ — ç
+ ˜ è
+ ™ é
+ š ê
+ › ë
+ œ ì
+ í
+ ž î
+ Ÿ ï
+}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/Build/source/texk/bibtex-x/csf/csfile.txt b/Build/source/texk/bibtex-x/csf/csfile.txt
new file mode 100644
index 00000000000..9f112a466c3
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/csfile.txt
@@ -0,0 +1,318 @@
+******************************************************************************
+FILE: $RCSfile: csfile.txt,v $
+ $Revision: 3.71 $
+ $Date: 1996/08/18 20:41:31 $
+******************************************************************************
+
+
+An 8-bit Implementation of BibTeX 0.99 with a Very Large Capacity
+=================================================================
+
+
+Contents
+--------
+
+ 1. The Codepage and Sort Order (CS) File
+ 1.1 CS file syntax
+ 1.2 Testing a CS file
+ 1.3 Sharing your CS file
+
+ 2. Change Log
+
+
+
+1. The Codepage and Sort Order (CS) File
+-----------------------------------------
+
+The Codepage and Sort definition (CS) file is used to define the 8-bit
+character set used by BibTeX and the order in which those characters should
+be sorted.
+
+NOTE: this file contains many 8-bit characters and may cause problems
+ if you try to display or print it on 7-bit systems (e.g. older
+ versions of Unix).
+
+
+ 1.1 CS file syntax
+ ------------------
+
+ The codepage and sorting order (CS) file defines how BibTeX will treat an
+ 8-bit character set, specifically which characters are to be treated as
+ letters, the upper/lower case relationships between characters, and the
+ sorting order of characters.
+
+ The CS file may contain a number of sections, each presented in the form
+ of a TeX macro:
+
+ \section-name{
+ <section definitions>
+ }
+
+ Four sections are currently supported: \lowupcase, \lowercase, \uppercase
+ and \order. The syntax of the four supported sections is summarised
+ below.
+
+ 8-bit characters may be entered naturally, but to avoid problems with
+ character set translation or corruption, they can also be entered using
+ the TeX-style portable notation for character codes, i.e. ^^XX, where XX
+ is the hexadecimal value ofthe character code.
+
+ Reading of the sections ends when the first '}' character is reached, so
+ '}' can't be included in a section. You can, however, use ^^7d instead.
+
+ The percent sign ('%') is used to introduce a trailing comment - it and
+ all remaining characters on a line are ignored. If you need to insert a
+ percent character, you can use ^^25 instead.
+
+
+ \lowupcase section
+
+ The \lowupcase section of the CS file is used to define the lower
+ /upper and upper/lower case relationship of pairs of specified
+ characters. It is only used if the relationship is symmetrical - use
+ \lowercase or \upcase if it isn't.
+
+ The syntax of the \lowupcase section is:
+
+ \lowupcase{
+ <LC-1> <UC-1> % Comment begins with a percent sign
+ <LC-2> <UC-2>
+ ...
+ <LC-N> <UC-N>
+ }
+
+ Each <LC-n> <UC-n> pair of characters defines that the upper case
+ equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
+ <UC-n> is <LC-n>.
+
+ You cannot redefine the lower or upper case equivalent of an ASCII
+ character (code < 128), so all instances of <LC-n> and <UC-n> (i.e.
+ both sides of the relationship) must have codes > 127.
+
+
+ \lowercase section
+
+ The \lowercase section of the CS file is used to define the lower
+ case equivalent of specified characters. It should normally only be
+ used if the relationship isn't symmetrical - use \lowupcase if it is.
+
+ The syntax of the \lowercase section is:
+
+ \lowercase{
+ <UC-1> <LC-1> % Comment begins with a percent sign
+ <UC-2> <LC-2>
+ ...
+ <UC-N> <LC-N>
+ }
+
+ Each <LC-n> <UC-n> pair of characters defines that the lower case
+ equivalent of <UC-n> is <LC-n>.
+
+ You cannot redefine the lower case equivalent of an ASCII character
+ (code < 128), so all instances of <UC-n> (i.e. the left hand side of
+ the relationship) must have codes > 127.
+
+
+ \uppercase section
+
+ The \uppercase section of the CS file is used to define the upper
+ case equivalent of specified characters. It should normally only be
+ used if the relationship isn't symmetrical - use \lowupcase if it is.
+
+ The syntax of the \uppercase section is:
+
+ \uppercase{
+ <LC-1> <UC-1> % Comment begins with a percent sign
+ <LC-2> <UC-2>
+ ...
+ <LC-N> <UC-N>
+ }
+
+ Each <LC-n> <UC-n> pair of characters defines that the upper case
+ case equivalent of <LC-n> is <UC-n>.
+
+ You cannot redefine the upper case equivalent of an ASCII character
+ (code < 128), so all instances of <LC-n> (i.e. the left hand side of
+ the relationship) must have codes > 127.
+
+
+ \order section
+
+ The \order section of the CS file is used to define the order in
+ which characters are sorted.
+
+ The syntax of the \order section is:
+
+ \order{
+ <char-1> % Comment begins with a percent sign
+ <char-2> <char-3> % whitespace between the chars
+ <char-4> - <char-5> % a hyphen between the chars
+ <char-4> _ <char-5> % an underscore between the chars
+ ...
+ <char-n>
+ }
+
+ All characters on the same line are given the same sorting weight.
+
+ The construct <char-1> <underscore> <char-2> is used to denote that
+ all characters in the range <char-1> to <char-2> should be given the
+ same sorting weight. For example, "A _ Z" would cause all ASCII
+ upper case alphabetical characters to have the same sorting weight
+ and would be equivalent to placing all 26 characters on the same
+ line.
+
+ The construct <char-1> <hyphen> <char-2> is used to denote that all
+ characters in the range <char-1> to <char-2> should be given an
+ ascending set of sorting weights, starting with <char-1> and ending
+ with <char-2>. For example, "A - Z" would cause all upper case ASCII
+ alphabetical characters to be sorted in ascending order and would be
+ equivalent to placing 'A' on the first line, 'B' on the second,
+ through to 'Z' on the 26th line.
+
+ The characters at the beginning of the order section are given a
+ lower sorting weight than characters occuring later. When sorting
+ alphabetically, characters with the lowest weight come first.
+
+ All characters not in the \order section (including ASCII characters)
+ are given the same very high sorting weight to ensure that they come
+ last when sorting alphabetically.
+
+
+ 1.2 Testing a CS file
+ ---------------------
+
+ If you create a CS, you'll want a straightforward way of testing that
+ BibTeX is interpreting it as you expect it to. The --debug=csf option
+ will report the results of parsing the CS file. Specifically, BibTeX
+ will report:
+
+ o characters with codes > 127 that it has defined as type ALPHA
+ o characters with upper case equivalents
+ o characters with lower case equivalents
+ o characters in ascending sorting order
+
+ An example of the output when processing the cp437lat.csf CS file is
+ shown below. This output will only make sense if you are using a
+ computer that supports the IBM codepage 437.
+
+ D-CSF: c8read_csf: trying to open CS file `cp437lat.csf' ...
+ D-CSF: reading the \lowupcase section ...
+ D-CSF: finished reading the \lowupcase section.
+ D-CSF: reading the \uppercase section ...
+ D-CSF: finished reading the \uppercase section.
+ D-CSF: reading the \order section ...
+ D-CSF: finished reading the \order section.
+
+ D-CSF: 8-bit ALPHA characters
+ D-CSF: ----------------------
+ D-CSF: 80: € ‚ ƒ „ … † ‡ ˆ ‰ Š ‹ Œ Ž
+ D-CSF: 90: ‘ ’ “ ” • – — . ™ š . . . . .
+ D-CSF: a0:   ¡ ¢ £ ¤ ¥ . . . . . . . . . .
+ D-CSF: b0: . . . . . . . . . . . . . . . .
+ D-CSF: c0: . . . . . . . . . . . . . . . .
+ D-CSF: d0: . . . . . . . . . . . . . . . .
+ D-CSF: e0: . á . . . . . . . . . . . . . .
+ D-CSF: f0: . . . . . . . . . . . . . . . .
+
+ D-CSF: Characters with upper case equivalents
+ D-CSF: --------------------------------------
+ D-CSF: a [61] <<< A [41] b [62] <<< B [42] c [63] <<< C [43]
+ D-CSF: d [64] <<< D [44] e [65] <<< E [45] f [66] <<< F [46]
+ D-CSF: g [67] <<< G [47] h [68] <<< H [48] i [69] <<< I [49]
+ D-CSF: j [6a] <<< J [4a] k [6b] <<< K [4b] l [6c] <<< L [4c]
+ D-CSF: m [6d] <<< M [4d] n [6e] <<< N [4e] o [6f] <<< O [4f]
+ D-CSF: p [70] <<< P [50] q [71] <<< Q [51] r [72] <<< R [52]
+ D-CSF: s [73] <<< S [53] t [74] <<< T [54] u [75] <<< U [55]
+ D-CSF: v [76] <<< V [56] w [77] <<< W [57] x [78] <<< X [58]
+ D-CSF: y [79] <<< Y [59] z [7a] <<< Z [5a] [81] <<< š [9a]
+ D-CSF: ‚ [82] <<< [90] ƒ [83] <<< A [41] „ [84] <<< Ž [8e]
+ D-CSF: … [85] <<< A [41] † [86] <<< [8f] ‡ [87] <<< € [80]
+ D-CSF: ˆ [88] <<< E [45] ‰ [89] <<< E [45] Š [8a] <<< E [45]
+ D-CSF: ‹ [8b] <<< I [49] Œ [8c] <<< I [49] [8d] <<< I [49]
+ D-CSF: ‘ [91] <<< ’ [92] “ [93] <<< O [4f] ” [94] <<< ™ [99]
+ D-CSF: • [95] <<< O [4f] – [96] <<< U [55] — [97] <<< U [55]
+ D-CSF:   [a0] <<< A [41] ¡ [a1] <<< I [49] ¢ [a2] <<< O [4f]
+ D-CSF: £ [a3] <<< U [55] ¤ [a4] <<< ¥ [a5]
+
+ D-CSF: Characters with lower case equivalents
+ D-CSF: --------------------------------------
+ D-CSF: A [41] >>> a [61] B [42] >>> b [62] C [43] >>> c [63]
+ D-CSF: D [44] >>> d [64] E [45] >>> e [65] F [46] >>> f [66]
+ D-CSF: G [47] >>> g [67] H [48] >>> h [68] I [49] >>> i [69]
+ D-CSF: J [4a] >>> j [6a] K [4b] >>> k [6b] L [4c] >>> l [6c]
+ D-CSF: M [4d] >>> m [6d] N [4e] >>> n [6e] O [4f] >>> o [6f]
+ D-CSF: P [50] >>> p [70] Q [51] >>> q [71] R [52] >>> r [72]
+ D-CSF: S [53] >>> s [73] T [54] >>> t [74] U [55] >>> u [75]
+ D-CSF: V [56] >>> v [76] W [57] >>> w [77] X [58] >>> x [78]
+ D-CSF: Y [59] >>> y [79] Z [5a] >>> z [7a] € [80] >>> ‡ [87]
+ D-CSF: Ž [8e] >>> „ [84] [8f] >>> † [86] [90] >>> ‚ [82]
+ D-CSF: ’ [92] >>> ‘ [91] ™ [99] >>> ” [94] š [9a] >>> [81]
+ D-CSF: ¥ [a5] >>> ¤ [a4]
+
+ D-CSF: Characters in sorting order
+ D-CSF: ---------------------------
+ D-CSF: 00: 0 [30]
+ D-CSF: 01: 1 [31]
+ D-CSF: 02: 2 [32]
+ D-CSF: 03: 3 [33]
+ D-CSF: 04: 4 [34]
+ D-CSF: 05: 5 [35]
+ D-CSF: 06: 6 [36]
+ D-CSF: 07: 7 [37]
+ D-CSF: 08: 8 [38]
+ D-CSF: 09: 9 [39]
+ D-CSF: 0a: A [41] a [61] ƒ [83] „ [84] … [85] † [86] Ž [8e] [8f]   [a0]
+ D-CSF: 0b: ‘ [91] ’ [92]
+ D-CSF: 0c: B [42] b [62]
+ D-CSF: 0d: C [43] c [63] € [80] ‡ [87]
+ D-CSF: 0e: D [44] d [64]
+ D-CSF: 0f: E [45] e [65] ‚ [82] ˆ [88] ‰ [89] Š [8a] [90]
+ D-CSF: 10: F [46] f [66]
+ D-CSF: 11: G [47] g [67]
+ D-CSF: 12: H [48] h [68]
+ D-CSF: 13: I [49] i [69] ‹ [8b] Œ [8c] [8d] ¡ [a1]
+ D-CSF: 14: J [4a] j [6a]
+ D-CSF: 15: K [4b] k [6b]
+ D-CSF: 16: L [4c] l [6c]
+ D-CSF: 17: M [4d] m [6d]
+ D-CSF: 18: N [4e] n [6e]
+ D-CSF: 19: ¤ [a4] ¥ [a5]
+ D-CSF: 1a: O [4f] o [6f] “ [93] ” [94] • [95] ™ [99] ¢ [a2]
+ D-CSF: 1b: P [50] p [70]
+ D-CSF: 1c: Q [51] q [71]
+ D-CSF: 1d: R [52] r [72]
+ D-CSF: 1e: S [53] s [73]
+ D-CSF: 1f: á [e1]
+ D-CSF: 20: T [54] t [74]
+ D-CSF: 21: U [55] u [75] [81] – [96] — [97] š [9a] £ [a3]
+ D-CSF: 22: V [56] v [76]
+ D-CSF: 23: W [57] w [77]
+ D-CSF: 24: X [58] x [78]
+ D-CSF: 25: Y [59] y [79]
+ D-CSF: 26: Z [5a] z [7a]
+ D-CSF: (All other characters are sorted equally after any of the above.)
+
+
+ 1.3 Sharing your CS file
+ ------------------------
+
+ Although we have provided a limited number of CS files, we hope that
+ other will soon produce different examples for other character sets and
+ national sorting orders. We will also be happy to accept corrections to
+ the example files supplied.
+
+ If you'd like to contribute a CS file, please send it to one of the
+ authors or upload it to one of the CTAN FTP archives. If you e-mail a
+ copy please ZIP and encode (UU/MIME) it so that we can be confident that
+ the file has not become corrupted in transit.
+
+
+
+2. Change Log
+--------------
+
+$Log: csfile.txt,v $
+# Revision 3.71 1996/08/18 20:41:31 kempson
+# Placed under RCS control.
+#
+******************************** END OF FILE *******************************
diff --git a/Build/source/texk/bibtex-x/csf/file_id.diz b/Build/source/texk/bibtex-x/csf/file_id.diz
new file mode 100644
index 00000000000..b2379e717fc
--- /dev/null
+++ b/Build/source/texk/bibtex-x/csf/file_id.diz
@@ -0,0 +1,13 @@
+(v3.71) "big" BibTeX with full 8-bit support
+
+An enhanced, portable C version of BibTeX.
+Enhanced by conversion to "big" (32-bit)
+capacity, addition of run-time selectable
+capacity and 8-bit support extensions.
+National character set and sorting order
+are controlled by an external configuration
+file. Various examples are included.
+Freeware / GNU Public Licence.
+
+Niel Kempson <kempson@snowyowl.co.uk>
+Alejandro Aguilar-Sierra <asierra@servidor.unam.mx>