diff options
| author | Karl Berry <karl@freefriends.org> | 2008-09-09 17:37:57 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2008-09-09 17:37:57 +0000 |
| commit | 065c68d929443ad4a1c9fa87fccbc529a5390915 (patch) | |
| tree | db01feeb2577ed7a73d3160fce7d042eabfe8d5a /Master | |
| parent | 9184473b15ef7df52bc1597191130d69e1bf5acd (diff) | |
include CTAN:biblio/bibtex/8-bit/bt371csf.zip contents, olli 08 Sep 2008 23:20:06
git-svn-id: svn://tug.org/texlive/trunk@10521 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master')
14 files changed, 2291 insertions, 0 deletions
diff --git a/Master/texmf-dist/bibtex/csf/base/88591lat.csf b/Master/texmf-dist/bibtex/csf/base/88591lat.csf new file mode 100644 index 00000000000..0d324057f4c --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/88591sca.csf b/Master/texmf-dist/bibtex/csf/base/88591sca.csf new file mode 100644 index 00000000000..b2a524430e5 --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/README.TEXLIVE b/Master/texmf-dist/bibtex/csf/base/README.TEXLIVE new file mode 100644 index 00000000000..8303e60114d --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/README.TEXLIVE @@ -0,0 +1,5 @@ +This is the unpacked archive CTAN:biblio/bibtex/8-bit/bt371csf.zip, +except the generic 00readme.txt, COPYING, HISTORY, and file_id.diz files +have been removed. + +--karl, 9sep08 (this file public domain :) diff --git a/Master/texmf-dist/bibtex/csf/base/ascii.csf b/Master/texmf-dist/bibtex/csf/base/ascii.csf new file mode 100644 index 00000000000..30c180c0238 --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/cp437lat.csf b/Master/texmf-dist/bibtex/csf/base/cp437lat.csf new file mode 100644 index 00000000000..dd69c90147f --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/cp850lat.csf b/Master/texmf-dist/bibtex/csf/base/cp850lat.csf new file mode 100644 index 00000000000..2387da972f9 --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/cp850sca.csf b/Master/texmf-dist/bibtex/csf/base/cp850sca.csf new file mode 100644 index 00000000000..3e51bc21a04 --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/cp866rus.csf b/Master/texmf-dist/bibtex/csf/base/cp866rus.csf new file mode 100644 index 00000000000..54d950dec6e --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/csfile.txt b/Master/texmf-dist/bibtex/csf/base/csfile.txt new file mode 100644 index 00000000000..9f112a466c3 --- /dev/null +++ b/Master/texmf-dist/bibtex/csf/base/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/Master/texmf-dist/bibtex/csf/base/88592pl.csf b/Master/texmf-dist/bibtex/csf/polish-csf/88592pl.csf index 9d0856ee52b..9d0856ee52b 100644 --- a/Master/texmf-dist/bibtex/csf/base/88592pl.csf +++ b/Master/texmf-dist/bibtex/csf/polish-csf/88592pl.csf diff --git a/Master/texmf-dist/bibtex/csf/base/cp1250pl.csf b/Master/texmf-dist/bibtex/csf/polish-csf/cp1250pl.csf index c1047203ded..c1047203ded 100644 --- a/Master/texmf-dist/bibtex/csf/base/cp1250pl.csf +++ b/Master/texmf-dist/bibtex/csf/polish-csf/cp1250pl.csf diff --git a/Master/texmf-dist/bibtex/csf/base/cp852pl.csf b/Master/texmf-dist/bibtex/csf/polish-csf/cp852pl.csf index cbb8136bfb0..cbb8136bfb0 100644 --- a/Master/texmf-dist/bibtex/csf/base/cp852pl.csf +++ b/Master/texmf-dist/bibtex/csf/polish-csf/cp852pl.csf diff --git a/Master/texmf-dist/bibtex/csf/base/iso8859-7.csf b/Master/texmf-dist/bibtex/csf/polish-csf/iso8859-7.csf index 5984e51fc25..5984e51fc25 100644 --- a/Master/texmf-dist/bibtex/csf/base/iso8859-7.csf +++ b/Master/texmf-dist/bibtex/csf/polish-csf/iso8859-7.csf diff --git a/Master/tlpkg/tlpsrc/bin-bibtex8.tlpsrc b/Master/tlpkg/tlpsrc/bin-bibtex8.tlpsrc index 28be1ad6591..ceabbb888c8 100644 --- a/Master/tlpkg/tlpsrc/bin-bibtex8.tlpsrc +++ b/Master/tlpkg/tlpsrc/bin-bibtex8.tlpsrc @@ -1,5 +1,7 @@ name bin-bibtex8 category TLCore runpattern d texmf-dist/bibtex/csf/base +# this should be its own package, but didn't seem worth it. --karl, 9sep08 +runpattern d texmf-dist/bibtex/csf/polish-csf docpattern f texmf/doc/bibtex8/* binpattern f bin/${ARCH}/bibtex8 |