Debian Codegraph @

jadedoc/dsssl2.htm

raw
1 <!-- -*- sgml -*- -->
2 <html>
3
4 <head>
5 <meta http-equiv="Content-Type"
6 content="text/html; charset=iso-8859-1">
7 <meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
8 <title>Experimental DSSSL extensions for XSL</title>
9 </head>
10
11 <body background="images/background.gif" bgcolor="#FFFFFF">
12
13 <p><font face="Arial"><img src="images/dsssltitle.gif"
14 alt="OpenJade" vspace="10" width="750" height="60"> </font></p>
15 <div align="left">
16
17 <table border="0" width="780">
18 <tr>
19 <td valign="top"><font face="Arial"><img
20 src="images/space.gif" alt="" width="145" height="10"></font></td>
21 <td><h1><font face="Arial">Experimental DSSSL extensions</font></h1>
22 <h2><font face="Arial">Contents</font></h2>
23 <ul>
24 <li><a href="#Introduction"><font face="Arial">Introduction</font></a><font
25 face="Arial"> </font></li>
26 <li><a href="#Imperative programming"><font
27 face="Arial">Imperative programming</font></a><font
28 face="Arial"> </font></li>
29 <li><a href="#Style rules"><font face="Arial">Style
30 rules</font></a><font face="Arial"> </font></li>
31 <li><a href="#ExtendedPatterns"><font face="Arial">Extended
32 Patterns</font></a><font face="Arial"> </font></li>
33 <li><a href="#Multiple patterns per rule"><font
34 face="Arial">Multiple patterns per rule</font></a><font
35 face="Arial"> </font></li>
36 <li><a href="#Flow object macros"><font face="Arial">Flow
37 object macros</font></a><font face="Arial"> </font></li>
38 <li><a href="#Characteristic value conversion"><font
39 face="Arial">Characteristic value convertion</font></a><font
40 face="Arial"> </font></li>
41 <li><a href="#Characteristic names"><font
42 face="Arial">Characteristic names</font></a><font
43 face="Arial"> </font></li>
44 <li><a href="#char-map""><font face="Arial">
45 The char-map characteristic</font></a></li>
46 </ul>
47 <h2><a name="Introduction"><font face="Arial">Introduction</font></a></h2>
48 <p><font face="Arial">This document descibes some
49 experimental extensions to DSSSL that are implemented in OpenJade.
50 These are designed so that, with these
51 extensions, DSSSL provides a superset of the semantics </font><a
52 href="http://www.w3.org/TR/NOTE-XSL-970910"><font
53 face="Arial">XSL</font></a><font face="Arial"> for flow
54 object tree construction. OpenJade has a <code>-2</code>
55 option that enables these extensions. </font></p>
56 <p><font face="Arial">These extensions do not include the
57 additional flow object classes and characteristics that
58 will be needed for XSL; in particular they do not include
59 the HTML/CSS flow object classes. </font></p>
60 <p><a href="#top"><font face="Arial"><img
61 src="images/top-of-page.gif" alt="Up" border="0"
62 width="11" height="15"></font></a><a href="#top"><font
63 size="2" face="Arial">Back to top</font></a><font
64 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
65 <h2><a name="Imperative programming"><font face="Arial">Imperative
66 programming</font></a></h2>
67 <p><font face="Arial">The following features come from R4RS:
68 </font></p>
69 <ul>
70 <li><font face="Arial">assignment (<code>set!</code>)
71 expressions (with </font><a href="#read-only"><font
72 face="Arial">restrictions</font></a><font
73 face="Arial">) </font></li>
74 <li><font face="Arial">vectors (with </font><a
75 href="#read-only"><font face="Arial">restrictions</font></a><font
76 face="Arial">) </font></li>
77 <li><font face="Arial"><code>call-with-current-continuation</code>
78 (with </font><a href="#call/cc"><font
79 face="Arial">restrictions</font></a><font
80 face="Arial">) </font></li>
81 <li><font face="Arial"><code>begin</code> expressions
82 </font></li>
83 <li><font face="Arial">multiple expressions in
84 procedure bodies, <code>cond</code> clauses </font></li>
85 <li><font face="Arial">alternate in <code>if</code>
86 expression optional </font></li>
87 <li><font face="Arial">it is not an error when
88 nothing matches in <code>cond</code> or <code>case</code>
89 expression </font></li>
90 <li><font face="Arial"><code>eqv?</code> and <code>memv</code>
91 procedures; these behave as specified in R4RS for
92 vectors but behave the same as <code>equal?</code>
93 for strings and lists </font><p><font
94 face="Arial">This is so that case expressions can
95 use <code>eqv?</code> as required by R4RS without
96 breaking compatibility with existing DSSSL code
97 which assumes case expressions with strings and
98 lists will use <code>equal?</code>. R4RS
99 specifies that <code>eqv?</code> should return #t
100 when its arguments &quot;should normally be
101 regarded as the same object&quot;. R4RS treats
102 strings and lists as mutable and its
103 specification of <code>eqv?</code> for strings
104 and lists is consistent with this. So long as
105 DSSSL keeps strings and lists as immutable data-types
106 with value semantics, it is more consistent to
107 define <code>eqv?</code> to behave like <code>equal?</code>
108 for them. </font></p>
109 </li>
110 </ul>
111 <p><font face="Arial">The use of side-effects is
112 restricted. Assignment to top-level variables is not
113 allowed. There is also the concept that a memory location
114 can be read-only. When a memory location is read-only, it
115 is an error to change that location. An memory location
116 can be recursively marked as read-only; this means that
117 the memory location along with all memory locations
118 reachable from that memory location become read-only. A
119 memory location is recursively marked as read-only when: </font></p>
120 <ul>
121 <li><font face="Arial">an object stored in that
122 memory location is bound to a top-level variable </font></li>
123 <li><font face="Arial">an expression specifying a
124 characteristic is evaluated and a variable that
125 names that memory location occurs free in that
126 expression; for example, this would be an error: </font><pre><font
127 face="Arial">
128 (let ((x 10pt))
129 (make paragraph
130 font-size: (begin (set! x 12pt) x)))
131 </font></pre>
132 </li>
133 <li><font face="Arial">an object stored in that
134 memory location is returned by a <code>(inherited-</code><code><var>C</var></code><code>)</code>
135 or <code>(actual-</code><code><var>C</var></code><code>)</code>
136 procedure </font></li>
137 <li><font face="Arial">an object stored in that
138 memory location is passed as the first argument
139 to the <code>node-list-map</code> procedure </font></li>
140 </ul>
141 <p><font face="Arial">A continuation created with <code>call-with-current-continuation</code>
142 cannot be called if it is read-only, and can only be used
143 to return to a stack frame in the current call chain (sometimes
144 referred to as upwards only). </font></p>
145 <p><font face="Arial">There's a <code>void</code> data
146 type with a single value which can be written as <code>#v</code>.
147 This is returned by <code>cond</code>, <code>case</code>
148 and <code>if</code> expressions which don't match. </font></p>
149 <p><a href="#top"><font face="Arial"><img
150 src="images/top-of-page.gif" alt="Up" border="0"
151 width="11" height="15"></font></a><a href="#top"><font
152 size="2" face="Arial">Back to top</font></a><font
153 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
154 <h2><a name="Style rules"><font face="Arial">Style rules</font></a></h2>
155 <p><font face="Arial">When a construction rule has a
156 keyword argument list instead of a construct expression
157 it is treated as a style rule. For example, </font></p>
158 <pre><font face="Arial">
159 (element H1
160 font-size: 14pt
161 font-weight: 'bold)
162 </font></pre>
163 <p><font face="Arial">The keyword argument list can
164 include a <code>use:</code> keyword just as with <code>style</code>
165 expressions. See the </font><a
166 href="http://www.w3.org/TR/NOTE-XSL-970910"><font
167 face="Arial">XSL proposal</font></a><font face="Arial">
168 for the semantics of style rules. </font></p>
169 <p><a href="#top"><font face="Arial"><img
170 src="images/top-of-page.gif" alt="Up" border="0"
171 width="11" height="15"></font></a><a href="#top"><font
172 size="2" face="Arial">Back to top</font></a><font
173 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
174 <h2><a name="ExtendedPatterns"><font face="Arial">Extended
175 patterns</font></a></h2>
176 <p><font face="Arial">The syntax for element patterns is
177 extended. These provide provide a superset of the
178 semantics of XSL patterns. They are allowed both in
179 element construction rules and in contexts where a <code>match-element?</code>
180 pattern is currently allowed (eg <code>select-elements</code>,
181 <code>process-matching-children</code>, <code>process-first-descendant</code>).
182 </font></p>
183 <p><font face="Arial">A pattern is either a single gi or
184 a list. A list consists of a sequence of gis, where each
185 gi can be followed by one or more keyword/value pairs (where
186 the value is always a single datum). A gi can be #t, a
187 string or a symbol. The following keywords are allowed: </font></p>
188 <dl>
189 <dt><font face="Arial"><code>id:</code> </font></dt>
190 <dd><font face="Arial">followed by a string or symbol
191 </font></dd>
192 <dt><font face="Arial"><code>class:</code> </font></dt>
193 <dd><font face="Arial">followed by a string or symbol
194 </font></dd>
195 <dt><font face="Arial"><code>repeat:</code> </font></dt>
196 <dd><font face="Arial">followed by one of the symbols
197 <code>*</code>, <code>+</code>, <code>?</code> </font></dd>
198 <dt><font face="Arial"><code>only:</code> </font></dt>
199 <dd><font face="Arial">followed by one of the symbols
200 <code>of-type</code>, <code>of-any</code> </font></dd>
201 <dt><font face="Arial"><code>position:</code> </font></dt>
202 <dd><font face="Arial">followed by one of the symbols
203 <code>first-of-type</code>, <code>first-of-any</code>,
204 <code>last-of-type</code>, <code>last-of-any</code>
205 </font></dd>
206 <dt><font face="Arial"><code>attributes:</code> </font></dt>
207 <dd><font face="Arial">followed by a list of name/value
208 pairs; for backward compatibility with <code>match-element?</code>
209 patterns in the current DSSSL standard the <code>attributes:</code>
210 keyword can be omitted; #t and #f can be used as
211 a value to test for presence or absence of
212 attributes. </font></dd>
213 <dt><font face="Arial"><code>children:</code> </font></dt>
214 <dd><font face="Arial">followed by a pattern; each of
215 the elements in the pattern must occur as child; <code>repeat:</code>
216 is not allowed in children patterns; the <code>children:</code>
217 qualifier is allowed on any gi in a pattern not
218 just the last element </font></dd>
219 <dt><font face="Arial"><code>priority:</code> </font></dt>
220 <dd><font face="Arial">followed by an integer;
221 multiple <code>priority:</code> qualifiers are
222 allowed in a pattern and will be added together </font></dd>
223 <dt><font face="Arial"><code>importance:</code> </font></dt>
224 <dd><font face="Arial">followed by an integer;
225 multiple <code>importance:</code> qualifiers are
226 allowed and will be added together </font></dd>
227 </dl>
228 <p><font face="Arial">Class attribute names are declared
229 using </font></p>
230 <pre><font face="Arial">
231 (declare-class-attribute &quot;<var>class</var>&quot;)
232 </font></pre>
233 <p><font face="Arial">or </font></p>
234 <pre><font face="Arial">
235 (declare-class-attribute <var>class</var>)
236 </font></pre>
237 <p><font face="Arial">Id attribute names can be declared
238 similarily using <code>declare-id-attribute</code>. </font></p>
239 <p><font face="Arial">Some examples: </font></p>
240 <pre><font face="Arial">
241 (element (E importance: 42) <var>...</var>)
242
243 (element (E attributes: (A1 V1)) <var>...</var>)
244
245 (element (P E children: C) <var>...</var>)
246
247 (element (P children: C priority: -11
248 E children: C attributes: (A1 V1 A2 V2))
249 <var>...</var>)
250
251 (element (P E children: (A children: C B children: C)) <var>...</var>)
252 </font></pre>
253 <p><font face="Arial">The last is equivalent to the
254 following in XSL syntax: </font></p>
255 <pre><font face="Arial">
256 &lt;element type=&quot;P&quot;&gt;
257 &lt;target-element type=&quot;E&quot;&gt;
258 &lt;element type=&quot;A&quot;&gt;
259 &lt;element type=&quot;C&quot;/&gt;
260 &lt;/element&gt;
261 &lt;element type=&quot;B&quot;&gt;
262 &lt;element type=&quot;C&quot;/&gt;
263 &lt;/element&gt;
264 &lt;/target-element&gt;
265 &lt;/element&gt;
266 </font></pre>
267 <pre><a href="#top"><font face="Arial"><img
268 src="images/top-of-page.gif" alt="Up" border="0" width="11"
269 height="15"></font></a><a href="#top"><font size="3" face="Arial">Back to top</font></a><font
270 size="3" face="Arial">&nbsp;</font></pre>
271 <h2><a name="Multiple patterns per rule"><font
272 face="Arial">Multiple patterns per rule</font></a></h2>
273 <p><font face="Arial">An <code>or-element</code>
274 construction rule has the syntax </font></p>
275 <pre><font face="Arial">
276 (or-element (<var>pattern</var>+) <var>expression</var>)
277 </font></pre>
278 <p><font face="Arial">where <code><var>pattern</var></code>
279 is any pattern that could be allowed in an element
280 construction rule. It is equivalent to a sequence of
281 element construction rules. </font></p>
282 <p><font face="Arial">For example, </font></p>
283 <pre><font face="Arial">
284 (or-element (H1 H2 H3)
285 font-weight: 'bold)
286
287 (or-element ((H1 TITLE) (H2 TITLE) (H3 TITLE))
288 font-weight: 'bold)
289 </font></pre>
290 <p><font face="Arial">is equivalent to </font></p>
291 <pre><font face="Arial">
292 (element H1
293 font-weight: 'bold)
294
295 (element H2
296 font-weight: 'bold)
297
298 (element H3
299 font-weight: 'bold)
300
301 (element (H1 TITLE)
302 font-weight: 'bold)
303
304 (element (H2 TITLE)
305 font-weight: 'bold)
306
307 (element (H3 TITLE)
308 font-weight: 'bold)
309 </font></pre>
310 <pre><a href="#top"><font face="Arial"><img
311 src="images/top-of-page.gif" alt="Up" border="0" width="11"
312 height="15"></font></a><a href="#top"><font size="3" face="Arial">Back to top</font></a><font
313 size="2" face="Arial">&nbsp;</font></pre>
314 <h2><a name="Flow object macros"><font face="Arial">Flow
315 object macros</font></a></h2>
316 <p><font face="Arial">A flow object macro can be defined
317 like this: </font></p>
318 <p align="left"><font face="Arial">&nbsp; </font></p>
319 <div align="left"><table border="0" width="546"
320 bgcolor="#FFFFBB">
321 <tr>
322 <td width="542"><dl>
323 <dt><font face="Arial">(declare-flow-object-macro
324 list-item ((indent 1in) (marker &quot;\bullet&quot;)
325 #!contents contents)<br>
326 &nbsp; (make paragraph<br>
327 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
328 first-line-start-indent: (- indent)<br>
329 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
330 start-indent: (+ indent (inherited-start-indent))<br>
331 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (make
332 line-field<br>
333 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
334 field-width: indent<br>
335 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
336 (literal marker)</font></dt>
337 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
338 )<br>
339 &nbsp; contents</font></dt>
340 <dt><font face="Arial">&nbsp; )</font></dt>
341 <dt><font face="Arial">)<br>
342 <br>
343 (root<br>
344 &nbsp;&nbsp;&nbsp; (make simple-page-sequence<br>
345 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
346 (make paragraph<br>
347 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
348 (literal &quot;Para 1&quot;)</font></dt>
349 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
350 )<br>
351 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
352 (make list-item<br>
353 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
354 (literal &quot;Item 1&quot;)<br>
355 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
356 (make list-item<br>
357 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
358 indent: .5in<br>
359 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
360 marker: &quot;\black-circle&quot;<br>
361 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
362 (literal &quot;Sub item 1.1&quot;)</font></dt>
363 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
364 )</font></dt>
365 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
366 )<br>
367 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
368 (make list-item<br>
369 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
370 font-weight: 'bold<br>
371 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
372 (literal &quot;Item 2&quot;)<br>
373 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
374 (make list-item<br>
375 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
376 (literal &quot;Sub item 2.1&quot;)</font></dt>
377 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
378 )</font></dt>
379 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
380 )<br>
381 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
382 (make paragraph<br>
383 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
384 (literal &quot;Para 2&quot;)</font></dt>
385 <dt><font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
386 )</font></dt>
387 <dt><font face="Arial">&nbsp;&nbsp;&nbsp; )</font></dt>
388 <dt><font face="Arial">)</font></dt>
389 </dl>
390 </td>
391 </tr>
392 </table>
393 </div><p><font face="Arial">If the formal argument list
394 includes <code>#!contents</code> the flow object behaves
395 like a compound flow object, otherwise like an atomic
396 flow object. Inherited characteristics can be specified;
397 these are applied to a sequence flow object which is
398 automatically wrapped around what is returned by the body
399 of the flow object macro. The preceding formal arguments
400 are the non-inherited characteristics; like keyword
401 arguments they can be specified either as <code><var>id</var></code>
402 (in which case they default to #f), or as <code>(</code><code><var>id</var></code><code>
403 </code><code><var>init-expression</var></code><code>)</code>.
404 </font></p>
405 <p><font face="Arial">Note that flow object macros are
406 quite different from ordinary procedures in that the
407 macro body is not evaluated when the make expression is
408 evaluated, but rather when the flow object is to be added
409 to the tree; this allows <code>(inherited-</code><code><var>c</var></code><code>)</code>
410 and <code>(actual-</code><code><var>c</var></code><code>)</code>
411 procedures to be used in flow object macro
412 characteristics, non-inherited as well as inherited, just
413 as with normal flow objects. It is also possible to use <code>(inherited-</code><code><var>c</var></code><code>)</code>
414 and <code>(actual-</code><code><var>c</var></code><code>)</code>
415 procedures in the body of the flow object macro; they
416 will return the same result as if they were used in the
417 specification of a characteristic on the invocation of
418 the flow object macro. </font></p>
419 <p><font face="Arial">For an example of a library built
420 with the macro facility read: </font><a
421 href="../DSSSL/HTML%20Sample.html"><font face="Arial">Simple
422 XML to HTML Conversion and Rendition Example</font></a><font
423 face="Arial"> </font></p>
424 <p><a href="#top"><font face="Arial"><img
425 src="images/top-of-page.gif" alt="Up" border="0"
426 width="11" height="15"></font></a><a href="#top"><font
427 size="2" face="Arial">Back to top</font></a><font
428 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
429 <h2><a name="Characteristic value conversion"><font
430 face="Arial">Characteristic value conversion</font></a></h2>
431 <p><font face="Arial">Most characteristic values can now
432 be specified as strings and will be converted
433 appropriately. For boolean valued characteristics any of
434 the strings <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>,
435 <code>&quot;yes&quot;</code> and <code>&quot;no&quot;</code>
436 are acceptable. </font></p>
437 <p><a href="#top"><font face="Arial"><img
438 src="images/top-of-page.gif" alt="Up" border="0"
439 width="11" height="15"></font></a><a href="#top"><font
440 size="2" face="Arial">Back to top</font></a><font
441 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
442 <h2><a name="Characteristic names"><font face="Arial">Characteristic
443 names</font></a></h2>
444 <p><font face="Arial">The question mark that can be
445 omitted from those DSSSL characteristic names that end
446 with a question mark. This is because the question mark
447 is not (and cannot reasonably be made) a legal XML name
448 character. </font></p>
449 <p><a href="#top"><font face="Arial"><img
450 src="images/top-of-page.gif" alt="Up" border="0"
451 width="11" height="15"></font></a><a href="#top"><font
452 size="2" face="Arial">Back to top</font></a><font
453 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
454
455 <h2><a name="char-map"><font face="Arial">
456 The char-map characteristic</font></a></h2>
457 <p><font face="Arial">
458 The char-map inherited characteristic accept, in addition to #f and
459 a procedure, the symbols uppercase, lowercase and capitalize.
460 uppercase means to convert every character to upper case, lowercase
461 means to convert every character to lower case and capitalize means
462 that the first character in every word is converterd to upper case.
463 The country: and language: characteristics will determine how
464 the case conversion is done.</font></p>
465
466 <p><a href="#top"><font face="Arial"><img
467 src="images/top-of-page.gif" alt="Up" border="0"
468 width="11" height="15"></font></a><a href="#top"><font
469 size="2" face="Arial">Back to top</font></a><font
470 size="2" face="Arial">&nbsp;</font><font face="Arial"> </font></p>
471 </td>
472 </tr>
473 </table>
474 </div>
475 </body>
476 </html>