1
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
4
%% FILE: $RCSfile: 88591sca.csf,v $
6
%% $Date: 1996/08/04 20:48:52 $
8
%% CHARACTER SET: ISO 8859-1
10
%% ISO 8859-1 is the system character set used by Unix/X Windows and
13
%% SORTING ORDER: Scandinavean countries
15
%% The sorting order defined is a compromise between Norwegian/Danish
20
%% This is a BibTeX Codepage and Sort definition file (CSF). It is
21
%% used to define the 8-bit character set used by BibTeX and the
22
%% order in which those characters should be sorted. The file
23
%% format is documented below this header section.
25
%% This file will only work with the 8-bit implementation of BibTeX
26
%% written by Niel Kempson and Alejandro Aguilar-Sierra. It is
27
%% available by anonymous FTP from these Comprehensive TeX Archive
28
%% Network (CTAN) sites:
30
%% ftp.tex.ac.uk:/tex-archive/biblio/bibtex/8-bit
31
%% ftp.shsu.edu:/tex-archive/biblio/bibtex/8-bit
32
%% ftp.uni-stuttgart.de:/tex-archive/biblio/bibtex/8-bit
36
%% $Log: 88591sca.csf,v $
37
%% Revision 1.1 1996/08/04 20:48:52 kempson
38
%% Added missing sort entries for 0..9
40
%% Revision 1.0 1995/10/21 22:10:29 kempson
41
%% Placed under RCS control
43
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
44
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
47
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
48
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
52
%% The codepage and sorting order (CS) file defines how BibTeX will treat an
53
%% 8-bit character set, specifically which characters are to be treated as
54
%% letters, the upper/lower case relationships between characters, and the
55
%% sorting order of characters.
57
%% The CS file may contain a number of sections, each presented in the
58
%% form of a TeX macro:
61
%% <section definitions>
64
%% Four sections are currently supported: \lowupcase, \lowercase, \uppercase
65
%% and \order. The syntax of the four supported sections is summarised below.
67
%% 8-bit characters may be entered naturally, but to avoid problems with
68
%% character set translation or corruption, they can also be entered using
69
%% the TeX-style portable notation for character codes, i.e. ^^XX, where XX
70
%% is the hexadecimal value ofthe character code.
72
%% Reading of the sections ends when the first '}' character is reached, so
73
%% '}' can't be included in a section. You can't use ^^7d either.
75
%% The percent sign ('%') is used to introduce a trailing comment - it and
76
%% all remaining characters on a line are ignored. ^^25 has the same effect.
81
%% The \lowupcase section of the CS file is used to define the lower
82
%% /upper and upper/lower case relationship of pairs of specified
83
%% characters. It is only used if the relationship is symmetrical - use
84
%% \lowercase or \upcase if it isn't.
86
%% The syntax of the \lowupcase section is:
89
%% <LC-1> <UC-1> % Comment begins with a percent sign
95
%% Each <LC-n> <UC-n> pair of characters defines that the upper case
96
%% equivalent of <LC-n> is <UC-n> *and* the lower case equivalent of
99
%% You cannot redefine the lower or upper case equivalent of an ASCII
100
%% character (code < 128), so all instances of <LC-n> and <UC-n>
101
%% (i.e. both sides of the relationship) must have codes > 127.
104
%% \lowercase section
106
%% The \lowercase section of the CS file is used to define the lower case
107
%% equivalent of specified characters. It should normally only be used
108
%% if the relationship isn't symmetrical - use \lowupcase if it is.
110
%% The syntax of the \lowercase section is:
113
%% <UC-1> <LC-1> % Comment begins with a percent sign
119
%% Each <LC-n> <UC-n> pair of characters defines that the lower case
120
%% equivalent of <UC-n> is <LC-n>.
122
%% You cannot redefine the lower case equivalent of an ASCII character
123
%% (code < 128), so all instances of <UC-n> (i.e. the left hand side
124
%% of the relationship) must have codes > 127.
127
%% \uppercase section
129
%% The \uppercase section of the CS file is used to define the upper case
130
%% equivalent of specified characters. It should normally only be used
131
%% if the relationship isn't symmetrical - use \lowupcase if it is.
133
%% The syntax of the \uppercase section is:
136
%% <LC-1> <UC-1> % Comment begins with a percent sign
142
%% Each <LC-n> <UC-n> pair of characters defines that the upper case
143
%% case equivalent of <LC-n> is <UC-n>.
145
%% You cannot redefine the upper case equivalent of an ASCII character
146
%% (code < 128), so all instances of <LC-n> (i.e. the left hand side
147
%% of the relationship) must have codes > 127.
152
%% The \order section of the CS file is used to define the order in which
153
%% characters are sorted.
155
%% The syntax of the \order section is:
158
%% <char-1> % Comment begins with a percent sign
159
%% <char-2> <char-3> % whitespace between the chars
160
%% <char-4> - <char-5> % a hyphen between the chars
161
%% <char-4> _ <char-5> % an underscore between the chars
166
%% All characters on the same line are given the same sorting weight.
168
%% The construct <char-1> <underscore> <char-2> is used to denote that
169
%% all characters in the range <char-1> to <char-2> should be given the
170
%% same sorting weight. For example, "A _ Z" would cause all ASCII
171
%% upper case alphabetical characters to have the same sorting weight
172
%% and would be equivalent to placing all 26 characters on the same line.
174
%% The construct <char-1> <hyphen> <char-2> is used to denote that all
175
%% characters in the range <char-1> to <char-2> should be given an
176
%% ascending set of sorting weights, starting with <char-1> and ending
177
%% with <char-2>. For example, "A - Z" would cause all upper case ASCII
178
%% alphabetical characters to be sorted in ascending order and would be
179
%% equivalent to placing 'A' on the first line, 'B' on the second,
180
%% through to 'Z' on the 26th line.
182
%% The characters at the beginning of the order section are given a lower
183
%% sorting weight than characters occuring later. When sorting
184
%% alphabetically, characters with the lowest weight come first.
186
%% All characters not in the \order section (including ASCII characters)
187
%% are given the same very high sorting weight to ensure that they come
188
%% last when sorting alphabetically.
190
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
191
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
198
%% The ISO 8859-1 code page contains an equal number of upper and lower
199
%% case accented characters so we can use the \lowupcase{} section. The
200
%% \lowercase{} and \uppercase{} sections are not used.
202
\lowupcase{ % Lowercase Uppercase
205
� � % ^^e0 \`{a} ^^c0 \`{A}
206
� � % ^^e1 \'{a} ^^c1 \'{A}
207
� � % ^^e2 \^{a} ^^c2 \^{A}
208
� � % ^^e3 \~{a} ^^c3 \~{A}
209
� � % ^^e4 \"{a} ^^c4 \"{A}
210
� � % ^^e5 \aa ^^c5 \AA
211
� � % ^^e6 \ae ^^c6 \AE
212
� � % ^^e7 \c{c} ^^c7 \c{C}
213
� � % ^^e8 \`{e} ^^c8 \`{E}
214
� � % ^^e9 \'{e} ^^c9 \'{E}
215
� � % ^^ea \^{e} ^^ca \^{E}
216
� � % ^^eb \"{e} ^^cb \"{E}
217
� � % ^^ec \`{\i} ^^cc \`{I}
218
� � % ^^ed \'{\i} ^^cd \'{I}
219
� � % ^^ee \^{\i} ^^ce \^{I}
220
� � % ^^ef \"{\i} ^^cf \"{I}
221
� � % ^^f0 eth ^^d0 ETH
222
� � % ^^f1 \~{n} ^^d1 \~{N}
223
� � % ^^f2 \`{o} ^^d2 \`{O}
224
� � % ^^f3 \'{o} ^^d3 \'{O}
225
� � % ^^f4 \^{o} ^^d4 \^{O}
226
� � % ^^f5 \~{o} ^^d5 \~{O}
227
� � % ^^f6 \"{o} ^^d6 \"{O}
228
� � % ^^f8 \o ^^d8 \O
229
� � % ^^f9 \`{u} ^^d9 \`{U}
230
� � % ^^fa \'{u} ^^da \'{U}
231
� � % ^^fb \^{u} ^^db \^{U}
232
� � % ^^fc \"{u} ^^dc \"{U}
233
� � % ^^fd \'{y} ^^dd \'{Y}
234
� � % ^^fe thorn ^^de THORN
242
%% The sorting order defined is a compromise between Norwegian/Danish and
245
%% Norwegian/Danish sorting order: 0..9Aa..Zz������
246
%% Swedish sorting order: 0..9Aa..Zz������
247
%% Compromise sorting order: 0..9Aa..Zz����������
283
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% END OF FILE %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%