1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516 9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818 9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890 9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957 9958 9959 9960 9961 9962 9963 9964 9965 9966 9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10093 10094 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121 10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198 10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264 10265 10266 10267 10268 10269 10270 10271 10272 10273 10274 10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10287 10288 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351 10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424 10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454 10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498 10499 10500 10501 10502 10503 10504 10505 10506 10507 10508 10509 10510 10511 10512 10513 10514 10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546 10547 10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576 10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589 10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639 10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657 10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695 10696 10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715 10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794 10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871 10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948 10949 10950 10951 10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024 11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101 11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152 11153 11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176 11177 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224 11225 11226 11227 11228 11229 11230 11231 11232 11233 11234 11235 11236 11237 11238 11239 11240 11241 11242 11243 11244 11245 11246 11247 11248 11249 11250 11251 11252 11253 11254 11255 11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 11273 11274 11275 11276 11277 11278 11279 11280 11281 11282 11283 11284 11285 11286 11287 11288 11289 11290 11291 11292 11293 11294 11295 11296 11297 11298 11299 11300 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314 11315 11316 11317 11318 11319 11320 11321 11322 11323 11324 11325 11326 11327 11328 11329 11330 11331 11332 11333 11334 11335 11336 11337 11338 11339 11340 11341 11342 11343 11344 11345 11346 11347 11348 11349 11350 11351 11352 11353 11354 11355 11356 11357 11358 11359 11360 11361 11362 11363 11364 11365 11366 11367 11368 11369 11370 11371 11372 11373 11374 11375 11376 11377 11378 11379 11380 11381 11382 11383 11384 11385 11386 11387 11388 11389 11390 11391 11392 11393 11394 11395 11396 11397 11398 11399 11400 11401 11402 11403 11404 11405 11406 11407 11408 11409 11410 11411 11412 11413 11414 11415 11416 11417 11418 11419 11420 11421 11422 11423 11424 11425 11426 11427 11428 11429 11430 11431 11432 11433 11434 11435 11436 11437 11438 11439 11440 11441 11442 11443 11444 11445 11446 11447 11448 11449 11450 11451 11452 11453 11454 11455 11456 11457 11458 11459 11460 11461 11462 11463 11464 11465 11466 11467 11468 11469 11470 11471 11472 11473 11474 11475 11476 11477 11478 11479 11480 11481 11482 11483 11484 11485 11486 11487
|
<?xml version="1.0" encoding="ASCII"?><book version="5.0">
<info>
<title>HTML Parameter Reference</title>
<releaseinfo role="meta">
</releaseinfo>
<author>
<personname>
<surname>Walsh</surname>
<firstname>Norman</firstname>
</personname>
</author>
<copyright>
<year>1999</year>
<year>2000</year>
<year>2001</year>
<year>2002</year>
<year>2003</year>
<year>2004</year>
<year>2005</year>
<year>2006</year>
<year>2007</year>
<year>2008</year>
<year>2009</year>
<year>2010</year>
<year>2011</year>
<holder>Norman Walsh</holder>
</copyright>
<abstract>
<para>This is reference documentation for all user-configurable
parameters in the DocBook XSL HTML stylesheets (for generating
HTML output).</para>
</abstract>
</info>
<reference xml:id="admons"><title>Admonitions</title>
<refentry version="5.0" xml:id="admon.graphics.extension">
<refmeta>
<refentrytitle>admon.graphics.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>admon.graphics.extension</refname>
<refpurpose>Filename extension for admonition graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="admon.graphics.extension.frag">
<xsl:param name="admon.graphics.extension">.png</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the filename extension to use on admonition graphics.</para>
<itemizedlist>
<para>The DocBook XSL distribution provides admonition graphics in the following formats:</para>
<listitem><para>GIF (extension: <filename class="extension">.gif</filename>)</para></listitem>
<listitem><para>PNG (extension: <filename class="extension">.png</filename>)</para></listitem>
<listitem><para>SVG (extension: <filename class="extension">.svg</filename>)</para></listitem>
<listitem><para>TIFF (extension: <filename class="extension">.tif</filename>)</para></listitem>
</itemizedlist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="admon.graphics.path">
<refmeta>
<refentrytitle>admon.graphics.path</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>admon.graphics.path</refname>
<refpurpose>Path to admonition graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="admon.graphics.path.frag"><xsl:param name="admon.graphics.path">images/</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the path to the directory containing the admonition graphics
(caution.png, important.png etc). This location is normally relative
to the output html directory. See <parameter>base.dir</parameter></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="admon.graphics">
<refmeta>
<refentrytitle>admon.graphics</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>admon.graphics</refname>
<refpurpose>Use graphics in admonitions?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="admon.graphics.frag">
<xsl:param name="admon.graphics" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true (non-zero), admonitions are presented in an alternate style that uses
a graphic. Default graphics are provided in the distribution.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="admon.textlabel">
<refmeta>
<refentrytitle>admon.textlabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>admon.textlabel</refname>
<refpurpose>Use text label in admonitions?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="admon.textlabel.frag">
<xsl:param name="admon.textlabel" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true (non-zero), admonitions are presented with a generated
text label such as Note or Warning in the appropriate language.
If zero, such labels are turned off, but any title child
of the admonition element are still output.
The default value is 1.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="admon.style">
<refmeta>
<refentrytitle>admon.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>admon.style</refname>
<refpurpose>Specifies the CSS style attribute that should be added to
admonitions.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="admon.style.frag"><xsl:param name="admon.style">
<xsl:value-of select="concat('margin-', $direction.align.start, ': 0.5in; margin-', $direction.align.end, ': 0.5in;')"></xsl:value-of>
</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the value of the CSS <tag class="attribute">style</tag>
attribute that should be added to admonitions.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="callouts"><title>Callouts</title>
<refentry version="5.0" xml:id="callout.defaultcolumn">
<refmeta>
<refentrytitle>callout.defaultcolumn</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.defaultcolumn</refname>
<refpurpose>Indicates what column callouts appear in by default</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.defaultcolumn.frag">
<xsl:param name="callout.defaultcolumn">60</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If a callout does not identify a column (for example, if it uses
the <literal>linerange</literal> <tag class="attribute">unit</tag>),
it will appear in the default column.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.graphics.extension">
<refmeta>
<refentrytitle>callout.graphics.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.graphics.extension</refname>
<refpurpose>Filename extension for callout graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.graphics.extension.frag">
<xsl:param name="callout.graphics.extension">.png</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the filename extension to use on callout graphics. </para>
<itemizedlist>
<para>The Docbook XSL distribution provides callout graphics in the following formats:</para>
<listitem><para>SVG (extension: <filename class="extension">.svg</filename>)</para></listitem>
<listitem><para>PNG (extension: <filename class="extension">.png</filename>)</para></listitem>
<listitem><para>GIF (extension: <filename class="extension">.gif</filename>)</para></listitem>
</itemizedlist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.graphics.number.limit">
<refmeta>
<refentrytitle>callout.graphics.number.limit</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.graphics.number.limit</refname>
<refpurpose>Number of the largest callout graphic</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.graphics.number.limit.frag">
<xsl:param name="callout.graphics.number.limit">15</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>callout.graphics</parameter> is non-zero, graphics
are used to represent callout numbers instead of plain text. The value
of <parameter>callout.graphics.number.limit</parameter> is the largest
number for which a graphic exists. If the callout number exceeds this
limit, the default presentation "(plain text instead of a graphic)"
will be used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.graphics.path">
<refmeta>
<refentrytitle>callout.graphics.path</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.graphics.path</refname>
<refpurpose>Path to callout graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.graphics.path.frag">
<xsl:param name="callout.graphics.path">images/callouts/</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the path to the directory holding the callout graphics. his
location is normally relative to the output html directory. see
base.dir. Always terminate the directory with / since the graphic file
is appended to this string, hence needs the separator.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.graphics">
<refmeta>
<refentrytitle>callout.graphics</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.graphics</refname>
<refpurpose>Use graphics for callouts?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.graphics.frag">
<xsl:param name="callout.graphics" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, callouts are presented with graphics (e.g., reverse-video
circled numbers instead of "(1)", "(2)", etc.).
Default graphics are provided in the distribution.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.list.table">
<refmeta>
<refentrytitle>callout.list.table</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.list.table</refname>
<refpurpose>Present callout lists using a table?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.list.table.frag">
<xsl:param name="callout.list.table" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The default presentation of <tag>calloutlist</tag>s uses
an HTML <tag>DL</tag> element. Some browsers don't align DLs very well
if <parameter>callout.graphics</parameter> is used. With this option
turned on, <tag>calloutlist</tag>s are presented in an HTML
<tag>TABLE</tag>, which usually results in better alignment
of the callout number with the callout description.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.unicode.number.limit">
<refmeta>
<refentrytitle>callout.unicode.number.limit</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.unicode.number.limit</refname>
<refpurpose>Number of the largest unicode callout character</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.unicode.number.limit.frag">
<xsl:param name="callout.unicode.number.limit">10</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>callout.unicode</parameter>
is non-zero, unicode characters are used to represent
callout numbers. The value of
<parameter>callout.unicode.number.limit</parameter>
is
the largest number for which a unicode character exists. If the callout number
exceeds this limit, the default presentation "(nnn)" will always
be used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.unicode.start.character">
<refmeta>
<refentrytitle>callout.unicode.start.character</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.unicode.start.character</refname>
<refpurpose>First Unicode character to use, decimal value.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.unicode.start.character.frag">
<xsl:param name="callout.unicode.start.character">10102</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>callout.graphics</parameter> is zero and <parameter>callout.unicode</parameter>
is non-zero, unicode characters are used to represent
callout numbers. The value of
<parameter>callout.unicode.start.character</parameter>
is the decimal unicode value used for callout number one. Currently,
only values 9312 and 10102 are supported in the stylesheets for this parameter.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callout.unicode">
<refmeta>
<refentrytitle>callout.unicode</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callout.unicode</refname>
<refpurpose>Use Unicode characters rather than images for callouts.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callout.unicode.frag"><xsl:param name="callout.unicode" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The stylesheets can use either an image of the numbers one to ten, or the single Unicode character which represents the numeral, in white on a black background. Use this to select the Unicode character option.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="callouts.extension">
<refmeta>
<refentrytitle>callouts.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>callouts.extension</refname>
<refpurpose>Enable the callout extension</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="callouts.extension.frag">
<xsl:param name="callouts.extension" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The callouts extension processes <tag>areaset</tag>
elements in <tag>programlistingco</tag> and other text-based
callout elements.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="ebnf"><title>EBNF</title>
<refentry version="5.0" xml:id="ebnf.table.bgcolor">
<refmeta>
<refentrytitle>ebnf.table.bgcolor</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">color</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ebnf.table.bgcolor</refname>
<refpurpose>Background color for EBNF tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ebnf.table.bgcolor.frag">
<xsl:param name="ebnf.table.bgcolor">#F5DCB3</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the background color for EBNF tables (a pale brown). No
<tag>bgcolor</tag> attribute is output if
<parameter>ebnf.table.bgcolor</parameter> is set to the null string. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="ebnf.table.border">
<refmeta>
<refentrytitle>ebnf.table.border</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ebnf.table.border</refname>
<refpurpose>Selects border on EBNF tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ebnf.table.border.frag"><xsl:param name="ebnf.table.border" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Selects the border on EBNF tables. If non-zero, the tables have
borders, otherwise they don't.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="ebnf.assignment">
<refmeta>
<refentrytitle>ebnf.assignment</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">rtf</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ebnf.assignment</refname>
<refpurpose>The EBNF production assignment operator</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ebnf.assignment.frag">
<xsl:param name="ebnf.assignment">
<code>::=</code>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>ebnf.assignment</parameter> parameter determines what
text is used to show <quote>assignment</quote> in <tag>production</tag>s
in <tag>productionset</tag>s.</para>
<para>While <quote><literal>::=</literal></quote> is common, so are several
other operators.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="ebnf.statement.terminator">
<refmeta>
<refentrytitle>ebnf.statement.terminator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">rtf</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ebnf.statement.terminator</refname>
<refpurpose>Punctuation that ends an EBNF statement.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ebnf.statement.terminator.frag">
<xsl:param name="ebnf.statement.terminator"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>ebnf.statement.terminator</parameter> parameter determines what
text is used to terminate each <tag>production</tag>
in <tag>productionset</tag>.</para>
<para>Some notations end each statement with a period.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="toc_index"><title>ToC/LoT/Index Generation</title>
<refentry version="5.0" xml:id="annotate.toc">
<refmeta>
<refentrytitle>annotate.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotate.toc</refname>
<refpurpose>Annotate the Table of Contents?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotate.toc.frag"><xsl:param name="annotate.toc" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true, TOCs will be annotated. At present, this just means
that the <tag>refpurpose</tag> of <tag>refentry</tag>
TOC entries will be displayed.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="autotoc.label.separator">
<refmeta>
<refentrytitle>autotoc.label.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>autotoc.label.separator</refname>
<refpurpose>Separator between labels and titles in the ToC</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="autotoc.label.separator.frag">
<xsl:param name="autotoc.label.separator">. </xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>String used to separate labels and titles in a table of contents.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="autotoc.label.in.hyperlink">
<refmeta>
<refentrytitle>autotoc.label.in.hyperlink</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>autotoc.label.in.hyperlink</refname>
<refpurpose>Include label in hyperlinked titles in TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="autotoc.label.in.hyperlink.frag"><xsl:param name="autotoc.label.in.hyperlink" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If the value of
<parameter>autotoc.label.in.hyperlink</parameter> is non-zero, labels
are included in hyperlinked titles in the TOC. If it is instead zero,
labels are still displayed prior to the hyperlinked titles, but
are not hyperlinked along with the titles.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="process.source.toc">
<refmeta>
<refentrytitle>process.source.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>process.source.toc</refname>
<refpurpose>Process a non-empty <tag>toc</tag> element if it occurs in a source document?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="process.source.toc.frag"><xsl:param name="process.source.toc" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies that the contents of a non-empty "hard-coded"
<tag>toc</tag> element in a source document are processed to
generate a TOC in output.
<note>
<para>This parameter has no effect on automated generation of
TOCs. An automated TOC may still be generated along with the
"hard-coded" TOC. To suppress automated TOC generation, adjust the
value of the <parameter>generate.toc</parameter> paramameter.</para>
<para>The <tag>process.source.toc</tag> parameter also has
no effect if the <tag>toc</tag> element is empty; handling
for empty <tag>toc</tag> is controlled by the
<parameter>process.empty.source.toc</parameter> parameter.</para>
</note>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="process.empty.source.toc">
<refmeta>
<refentrytitle>process.empty.source.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>process.empty.source.toc</refname>
<refpurpose>Generate automated TOC if <tag>toc</tag> element occurs in a source document?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="process.empty.source.toc.frag"><xsl:param name="process.empty.source.toc" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies that if an empty <tag>toc</tag> element is found in a
source document, an automated TOC is generated at this point in the
document.
<note>
<para>Depending on what the value of the
<parameter>generate.toc</parameter> parameter is, setting this
parameter to <literal>1</literal> could result in generation of
duplicate automated TOCs. So the
<parameter>process.empty.source.toc</parameter> is primarily useful
as an "override": by placing an empty <tag>toc</tag> in your
document and setting this parameter to <literal>1</literal>, you can
force a TOC to be generated even if <tag>generate.toc</tag>
says not to.</para>
</note>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="bridgehead.in.toc">
<refmeta>
<refentrytitle>bridgehead.in.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>bridgehead.in.toc</refname>
<refpurpose>Should bridgehead elements appear in the TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="bridgehead.in.toc.frag"><xsl:param name="bridgehead.in.toc" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, <tag>bridgehead</tag>s appear in the TOC. Note that
this option is not fully supported and may be removed in a future
version of the stylesheets.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="simplesect.in.toc">
<refmeta>
<refentrytitle>simplesect.in.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>simplesect.in.toc</refname>
<refpurpose>Should <tag>simplesect</tag> elements appear in the TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="simplesect.in.toc.frag"><xsl:param name="simplesect.in.toc" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, <tag>simplesect</tag>s will be included in the TOC.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="manual.toc">
<refmeta>
<refentrytitle>manual.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>manual.toc</refname>
<refpurpose>An explicit TOC to be used for the TOC</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="manual.toc.frag">
<xsl:param name="manual.toc"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>manual.toc</parameter> identifies an explicit TOC that
will be used for building the printed TOC.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="toc.list.type">
<refmeta>
<refentrytitle>toc.list.type</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">dl</refmiscinfo>
<refmiscinfo class="other" otherclass="value">ul</refmiscinfo>
<refmiscinfo class="other" otherclass="value">ol</refmiscinfo>
</refmeta>
<refnamediv>
<refname>toc.list.type</refname>
<refpurpose>Type of HTML list element to use for Tables of Contents</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="toc.list.type.frag"><xsl:param name="toc.list.type">dl</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When an automatically generated Table of Contents (or List of Titles)
is produced, this HTML element will be used to make the list.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="toc.section.depth">
<refmeta>
<refentrytitle>toc.section.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>toc.section.depth</refname>
<refpurpose>How deep should recursive <tag>section</tag>s appear
in the TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="toc.section.depth.frag"><xsl:param name="toc.section.depth">2</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the depth to which recursive sections should appear in the
TOC.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="toc.max.depth">
<refmeta>
<refentrytitle>toc.max.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>toc.max.depth</refname>
<refpurpose>How many levels should be created for each TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="toc.max.depth.frag"><xsl:param name="toc.max.depth">8</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the maximal depth of TOC on all levels.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.toc">
<refmeta>
<refentrytitle>generate.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">table</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.toc</refname>
<refpurpose>Control generation of ToCs and LoTs</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.toc.frag">
<xsl:param name="generate.toc">
appendix toc,title
article/appendix nop
article toc,title
book toc,title,figure,table,example,equation
chapter toc,title
part toc,title
preface toc,title
qandadiv toc
qandaset toc
reference toc,title
sect1 toc
sect2 toc
sect3 toc
sect4 toc
sect5 toc
section toc
set toc,title
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter has a structured value. It is a table of space-delimited
path/value pairs. Each path identifies some element in the source document
using a restricted subset of XPath (only the implicit child axis, no wildcards,
no predicates). Paths can be either relative or absolute.</para>
<para>When processing a particular element, the stylesheets consult this table to
determine if a ToC (or LoT(s)) should be generated.</para>
<para>For example, consider the entry:</para>
<screen>book toc,figure</screen>
<para>This indicates that whenever a <tag>book</tag> is formatted, a
Table Of Contents and a List of Figures should be generated. Similarly,</para>
<screen>/chapter toc</screen>
<para>indicates that whenever a document <emphasis>that has a root
of</emphasis> <tag>chapter</tag> is formatted, a Table of
Contents should be generated. The entry <literal>chapter</literal> would match
all chapters, but <literal>/chapter</literal> matches only <tag>chapter</tag>
document elements.</para>
<para>Generally, the longest match wins. So, for example, if you want to distinguish
articles in books from articles in parts, you could use these two entries:</para>
<screen>book/article toc,figure
part/article toc</screen>
<para>Note that an article in a part can never match a <literal>book/article</literal>,
so if you want nothing to be generated for articles in parts, you can simply leave
that rule out.</para>
<para>If you want to leave the rule in, to make it explicit that you're turning
something off, use the value <quote>nop</quote>. For example, the following
entry disables ToCs and LoTs for articles:</para>
<screen>article nop</screen>
<para>Do not simply leave the word <quote>article</quote> in the file
without a matching value. That'd be just begging the silly little
path/value parser to get confused.</para>
<para>Section ToCs are further controlled by the
<parameter>generate.section.toc.level</parameter> parameter.
For a given section level to have a ToC, it must have both an entry in
<parameter>generate.toc</parameter> and be within the range enabled by
<parameter>generate.section.toc.level</parameter>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.section.toc.level">
<refmeta>
<refentrytitle>generate.section.toc.level</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.section.toc.level</refname>
<refpurpose>Control depth of TOC generation in sections</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.section.toc.level.frag">
<xsl:param name="generate.section.toc.level" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>generate.section.toc.level</parameter> parameter
controls the depth of <tag>section</tag> in which TOCs will be generated. Note
that this is related to, but not the same as
<parameter>toc.section.depth</parameter>, which controls the depth to
which TOC entries will be generated in a given TOC.</para>
<para>If, for example, <parameter>generate.section.toc.level</parameter>
is <literal>3</literal>, TOCs will be generated in first, second, and third
level sections, but not in fourth level sections.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.index">
<refmeta>
<refentrytitle>generate.index</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.index</refname>
<refpurpose>Do you want an index?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.index.frag"><xsl:param name="generate.index" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specify if an index should be generated. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.method">
<refmeta>
<refentrytitle>index.method</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">basic</refmiscinfo>
<refmiscinfo class="other" otherclass="value">kosek</refmiscinfo>
<refmiscinfo class="other" otherclass="value">kimber</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.method</refname>
<refpurpose>Select method used to group index entries in an index</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.method.frag">
<xsl:param name="index.method">basic</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter lets you select which method to use for sorting and grouping
index entries in an index.
Indexes in Latin-based languages that have accented characters typically
sort together accented words and unaccented words.
Thus <quote>Á</quote> (U+00C1 LATIN CAPITAL LETTER A WITH ACUTE) would sort together
with <quote>A</quote> (U+0041 LATIN CAPITAL LETTER A), so both would appear in the <quote>A</quote>
section of the index.
Languages using other alphabets (such as Russian, which is written in the Cyrillic alphabet)
and languages using ideographic chararacters (such as Japanese)
require grouping specific to the languages and alphabets.
</para>
<para>The default indexing method is limited.
It can group accented characters in Latin-based languages only.
It cannot handle non-Latin alphabets or ideographic languages.
The other indexing methods require extensions of one type or
another, and do not work with
all XSLT processors, which is why they are not used by default.</para>
<para>The three choices for indexing method are:</para>
<variablelist>
<varlistentry>
<term><literal>basic</literal></term>
<listitem>
<para>
(default) Sort and groups words based only on the Latin alphabet.
Words with accented Latin letters will group and sort with
their respective primary letter, but
words in non-Latin alphabets will be
put in the <quote>Symbols</quote> section of the index.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>kosek</literal></term>
<listitem>
<para>
This method sorts and groups words based on letter groups configured in
the DocBook locale file for the given language.
See, for example, the French locale file <filename>common/fr.xml</filename>.
This method requires that the XSLT processor
supports the EXSLT extensions (most do).
It also requires support for using
user-defined functions in xsl:key (xsltproc does not).
</para>
<para>This method is suitable for any language for which you can
list all the individual characters that should appear
in each letter group in an index.
It is probably not practical to use it for ideographic languages
such as Chinese that have hundreds or thousands of characters.
</para>
<para>To use the kosek method, you must:</para>
<orderedlist>
<listitem>
<para>Use a processor that supports its extensions, such as
Saxon 6 or Xalan (xsltproc and Saxon 8 do not).
</para>
</listitem>
<listitem>
<para>Set the index.method parameter's value to <quote>kosek</quote>.
</para>
</listitem>
<listitem>
<para>Import the appropriate index extensions stylesheet module
<filename>fo/autoidx-kosek.xsl</filename> or
<filename>html/autoidx-kosek.xsl</filename> into your
customization.
</para>
</listitem>
</orderedlist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>kimber</literal></term>
<listitem>
<para>
This method uses extensions to the Saxon processor to implement
sophisticated indexing processes. It uses its own
configuration file, which can include information for any number of
languages. Each language's configuration can group
words using one of two processes. In the
enumerated process similar to that used in the kosek method,
you indicate the groupings character-by-character.
In the between-key process, you specify the
break-points in the sort order that should start a new group.
The latter configuration is useful for ideographic languages
such as Chinese, Japanese, and Korean.
You can also define your own collation algorithms and how you
want mixed Latin-alphabet words sorted.</para>
<itemizedlist>
<listitem>
<para>For a whitepaper describing the extensions, see:
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.innodata-isogen.com/knowledge_center/white_papers/back_of_book_for_xsl_fo.pdf">http://www.innodata-isogen.com/knowledge_center/white_papers/back_of_book_for_xsl_fo.pdf</link>.
</para>
</listitem>
<listitem>
<para>To download the extension library, see
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.innodata-isogen.com/knowledge_center/tools_downloads/i18nsupport">http://www.innodata-isogen.com/knowledge_center/tools_downloads/i18nsupport</link>.
</para>
</listitem>
</itemizedlist>
<para>To use the kimber method, you must:</para>
<orderedlist>
<listitem>
<para>Use Saxon (version 6 or 8) as your XSLT processor.
</para>
</listitem>
<listitem>
<para>Install and configure the Innodata Isogen library, using
the documentation that comes with it.
</para>
</listitem>
<listitem>
<para>Set the index.method parameter's value to <quote>kimber</quote>.
</para>
</listitem>
<listitem>
<para>Import the appropriate index extensions stylesheet module
<filename>fo/autoidx-kimber.xsl</filename> or
<filename>html/autoidx-kimber.xsl</filename> into your
customization.
</para>
</listitem>
</orderedlist>
</listitem>
</varlistentry>
</variablelist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.on.type">
<refmeta>
<refentrytitle>index.on.type</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.on.type</refname>
<refpurpose>Select indexterms based on <tag class="attribute">type</tag>
attribute value</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.on.type.frag">
<xsl:param name="index.on.type" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If non-zero,
then an <tag>index</tag> element that has a
<tag class="attribute">type</tag> attribute
value will contain only those <tag>indexterm</tag>
elements with a matching <tag class="attribute">type</tag> attribute value.
If an <tag>index</tag> has no <tag class="attribute">type</tag>
attribute or it is blank, then the index will contain
all <tag>indexterm</tag>s in the current scope.
</para>
<para>
If <literal>index.on.type</literal> is zero, then the
<tag class="attribute">type</tag> attribute has no effect
on selecting indexterms for an index.
</para>
<para>For those using DocBook version 4.2 or earlier,
the <tag class="attribute">type</tag> attribute is not available
for index terms. However, you can achieve the same
effect by using the <tag class="attribute">role</tag> attribute
in the same manner on <tag>indexterm</tag>
and <tag>index</tag>, and setting the stylesheet parameter
<parameter>index.on.role</parameter> to a nonzero value.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.on.role">
<refmeta>
<refentrytitle>index.on.role</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.on.role</refname>
<refpurpose>Select indexterms based on <tag class="attribute">role</tag> value</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.on.role.frag">
<xsl:param name="index.on.role" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If non-zero,
then an <tag>index</tag> element that has a
<tag class="attribute">role</tag> attribute
value will contain only those <tag>indexterm</tag>
elements with a matching role value.
If an <tag>index</tag> has no <tag class="attribute">role</tag>
attribute or it is blank, then the index will contain
all <tag>indexterm</tag>s in the current scope.
</para>
<para>
If <literal>index.on.role</literal> is zero, then the
<tag class="attribute">role</tag> attribute has no effect
on selecting indexterms for an index.
</para>
<para>If you are using DocBook version 4.3 or later, you should
use the <tag class="attribute">type</tag> attribute instead of <tag class="attribute">role</tag>
on <tag>indexterm</tag> and <tag>index</tag>,
and set the <parameter>index.on.type</parameter> to a nonzero
value.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.links.to.section">
<refmeta>
<refentrytitle>index.links.to.section</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.links.to.section</refname>
<refpurpose>HTML index entries link to container section title</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.links.to.section.frag">
<xsl:param name="index.links.to.section" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If zero, then an index entry in an index links
directly to the location of the
generated <tag>anchor</tag> that is output
for the indexterm. If two identical indexterm elements
exist in the same section, then both entries appear
in the index with the same title but link to different
locations.</para>
<para>If non-zero, then an index entry in an index links to the
section title containing the <tag>indexterm</tag>, rather than
directly to the <tag>anchor</tag> output for the indexterm.
Duplicate indexterm entries in the same section are dropped.
</para>
<para>The default value is 1, so index entries link to
section titles by default.</para>
<para>In both cases, the link text in an index entry is the
title of the section containing the indexterm.
That is because HTML does not have numbered pages.
It also provides the reader with context information
for each link.</para>
<para>This parameter lets you choose which style of
index linking you want. </para>
<itemizedlist>
<listitem>
<para>When set to 0, an index entry takes you
to the precise location of its corresponding indexterm.
However, if you have a lot of duplicate
entries in sections, then you have a lot of duplicate
titles in the index, which makes it more cluttered.
The reader may not recognize why duplicate titles
appear until they follow the links. Also, the links
may land the reader in the middle of a section where the
section title is not visible, which may also be
confusing to the reader.</para>
</listitem>
<listitem>
<para>When set to 1, an index entry link is
less precise, but duplicate titles in the
index entries are eliminated.
Landing on the section title location may confirm the reader's
expectation that a link that
shows a section title will take them to that section title,
not a location within the section.
</para>
</listitem>
</itemizedlist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.prefer.titleabbrev">
<refmeta>
<refentrytitle>index.prefer.titleabbrev</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.prefer.titleabbrev</refname>
<refpurpose>Should abbreviated titles be used as back references?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.prefer.titleabbrev.frag">
<xsl:param name="index.prefer.titleabbrev" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, and if a <tag>titleabbrev</tag> is defined, the abbreviated title
is used as the link text of a back reference in the index.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="autolink.index.see">
<refmeta>
<refentrytitle>autolink.index.see</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>autolink.index.see</refname>
<refpurpose>Link index see and seealso to index primary</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="autolink.index.see.frag"><xsl:param name="autolink.index.see" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If this param is set to a non-zero value,
(default = 1), then the
stylesheet will attempt for form a link between a
<tag>see</tag> or <tag>seealso</tag> element
and a matching indexterm <tag>primary</tag> element.
</para>
<para>The stylesheet uses an exact text match after
applying the <literal>normalize-space()</literal> function.
If the <tag>see</tag> or <tag>seealso</tag> text contains a comma,
then only the text prior to the comma is used.
This assumes the author is using the convention "see primary, secondary"
to specify a subentry. Automatic links always land on the primary
entry in the index, so the reader has to look down to see the
secondary entry.</para>
<para>If there is no match on a
<tag>primary</tag>, no link is formed, but the text
still displays.</para>
<para>No attempt is made to automatically link to text in
<tag>secondary</tag> or <tag>tertiary</tag> elements.
If you want to link to such elements, you can form a
manual link by adding a linkend attribute to the
<tag>see</tag> or <tag>seealso</tag> element, where
the linkend references an id or xml:id attribute on
such a subelement. Such manual links take precedence over
any automatic links.
</para>
<para>If this parameter is zero, then
no automatic links from see and seealso
are formed within the index. Any manual links are
still processed, however.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.term.separator">
<refmeta>
<refentrytitle>index.term.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.term.separator</refname>
<refpurpose>Override for punctuation separating an index term
from its list of page references in an index</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.term.separator.frag">
<xsl:param name="index.term.separator"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter permits you to override
the text to insert between
the end of an index term and its list of page references.
Typically that might be a comma and a space.
</para>
<para>Because this text may be locale dependent,
this parameter's value is normally taken from a gentext
template named 'term-separator' in the
context 'index' in the stylesheet
locale file for the language
of the current document.
This parameter can be used to override the gentext string,
and would typically be used on the command line.
This parameter would apply to all languages.
</para>
<para>So this text string can be customized in two ways.
You can reset the default gentext string using
the <parameter>local.l10n.xml</parameter> parameter, or you can
fill in the content for this normally empty
override parameter.
The content can be a simple string, or it can be
something more complex such as a call-template.
For fo output, it could be an <tag>fo:leader</tag>
element to provide space of a specific length, or a dot leader.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.number.separator">
<refmeta>
<refentrytitle>index.number.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.number.separator</refname>
<refpurpose>Override for punctuation separating page numbers in index</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.number.separator.frag">
<xsl:param name="index.number.separator"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter permits you to override the text to insert between
page references in a formatted index entry. Typically
that would be a comma and a space.
</para>
<para>Because this text may be locale dependent,
this parameter's value is normally taken from a gentext
template named 'number-separator' in the
context 'index' in the stylesheet
locale file for the language
of the current document.
This parameter can be used to override the gentext string,
and would typically be used on the command line.
This parameter would apply to all languages.
</para>
<para>So this text string can be customized in two ways.
You can reset the default gentext string using
the <parameter>local.l10n.xml</parameter> parameter, or you can
override the gentext with the content of this parameter.
The content can be a simple string, or it can be
something more complex such as a call-template.
</para>
<para>In HTML index output, section title references are used instead of
page number references. This punctuation appears between
such section titles in an HTML index.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="index.range.separator">
<refmeta>
<refentrytitle>index.range.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>index.range.separator</refname>
<refpurpose>Override for punctuation separating the two numbers
in a page range in index</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="index.range.separator.frag">
<xsl:param name="index.range.separator"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter permits you
to override the text to insert between
the two numbers of a page range in an index.
This parameter is only used by those XSL-FO processors
that support an extension for generating such page ranges
(such as XEP).</para>
<para>Because this text may be locale dependent,
this parameter's value is normally taken from a gentext
template named 'range-separator' in the
context 'index' in the stylesheet
locale file for the language
of the current document.
This parameter can be used to override the gentext string,
and would typically be used on the command line.
This parameter would apply to all languages.
</para>
<para>So this text string can be customized in two ways.
You can reset the default gentext string using
the <parameter>local.l10n.xml</parameter> parameter, or you can
override the gentext with the content of this parameter.
The content can be a simple string, or it can be
something more complex such as a call-template.
</para>
<para>In HTML index output, section title references are used instead of
page number references. So there are no page ranges
and this parameter has no effect.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="dbk_ext"><title>Stylesheet Extensions</title>
<refentry version="5.0" xml:id="linenumbering.everyNth">
<refmeta>
<refentrytitle>linenumbering.everyNth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>linenumbering.everyNth</refname>
<refpurpose>Indicate which lines should be numbered</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="linenumbering.everyNth.frag">
<xsl:param name="linenumbering.everyNth">5</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If line numbering is enabled, everyNth line will be
numbered. Note that numbering is one based, not zero based.
</para>
<para>See also <parameter>linenumbering.extension</parameter>,
<parameter>linenumbering.separator</parameter>,
<parameter>linenumbering.width</parameter> and
<parameter>use.extensions</parameter></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="linenumbering.extension">
<refmeta>
<refentrytitle>linenumbering.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>linenumbering.extension</refname>
<refpurpose>Enable the line numbering extension</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="linenumbering.extension.frag">
<xsl:param name="linenumbering.extension" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, verbatim environments (<tag>address</tag>, <tag>literallayout</tag>,
<tag>programlisting</tag>, <tag>screen</tag>, <tag>synopsis</tag>) that specify line numbering will
have line numbers.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="linenumbering.separator">
<refmeta>
<refentrytitle>linenumbering.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>linenumbering.separator</refname>
<refpurpose>Specify a separator between line numbers and lines</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="linenumbering.separator.frag">
<xsl:param name="linenumbering.separator"><xsl:text> </xsl:text></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The separator is inserted between line numbers and lines in the
verbatim environment. The default value is a single white space.
Note the interaction with <parameter>linenumbering.width</parameter>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="linenumbering.width">
<refmeta>
<refentrytitle>linenumbering.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>linenumbering.width</refname>
<refpurpose>Indicates the width of line numbers</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="linenumbering.width.frag">
<xsl:param name="linenumbering.width">3</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If line numbering is enabled, line numbers will appear right
justified in a field "width" characters wide.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="tablecolumns.extension">
<refmeta>
<refentrytitle>tablecolumns.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>tablecolumns.extension</refname>
<refpurpose>Enable the table columns extension function</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="tablecolumns.extension.frag">
<xsl:param name="tablecolumns.extension" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The table columns extension function adjusts the widths of table
columns in the HTML result to more accurately reflect the specifications
in the CALS table.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="textinsert.extension">
<refmeta>
<refentrytitle>textinsert.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>textinsert.extension</refname>
<refpurpose>Enables the textinsert extension element</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="textinsert.extension.frag">
<xsl:param name="textinsert.extension" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The textinsert extension element inserts the contents of
a file into the result tree (as text).</para>
<note>
<para>To use the textinsert extension element, you must use
either Saxon or Xalan as your XSLT processor (it doesn’t
work with xsltproc), along with either the DocBook Saxon
extensions or DocBook Xalan extensions (for more
information about those extensions, see <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="InstallingAProcessor.html#SaxonExtensions">DocBook Saxon Extensions</link> and <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="InstallingAProcessor.html#XalanExtensions">DocBook Xalan Extensions</link>), and you must set both
the <parameter>use.extensions</parameter> and
<parameter>textinsert.extension</parameter> parameters to
<literal>1</literal>.</para>
<para>As an alternative to using the textinsert element,
consider using an Xinclude element with the
<literal>parse="text"</literal> attribute and value
specified, as detailed in <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="ExternalCode.html#XIncludeCode">Using XInclude for text inclusions</link>.</para>
</note>
</refsection>
<refsection><info><title>See Also</title></info>
<para>You can also use the <tag class="xmlpi">dbhtml-include href</tag> processing
instruction to insert external files — both files containing
plain text and files with markup content (including HTML
content).</para>
</refsection>
<refsection><info><title>More information</title></info>
<para>For how-to documentation on inserting contents of
external code files and other text files into output, see
<link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="ExternalCode.html">External code files</link>.</para>
<para>For guidelines on inserting contents of
HTML files into output, see <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="InsertExtHtml.html">Inserting external HTML code</link>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="textdata.default.encoding">
<refmeta>
<refentrytitle>textdata.default.encoding</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>textdata.default.encoding</refname>
<refpurpose>Default encoding of external text files which are included
using textdata element</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="textdata.default.encoding.frag">
<xsl:param name="textdata.default.encoding"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the encoding of any external text files included using
<tag>textdata</tag> element. This value is used only when you do
not specify encoding by the appropriate attribute
directly on textdata. An empty string is interpreted as the system
default encoding.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="graphicsize.extension">
<refmeta>
<refentrytitle>graphicsize.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>graphicsize.extension</refname>
<refpurpose>Enable the getWidth()/getDepth() extension functions</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="graphicsize.extension.frag">
<xsl:param name="graphicsize.extension" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero (and if <parameter>use.extensions</parameter> is non-zero
and if you're using a processor that supports extension functions), the
<function>getWidth</function> and <function>getDepth</function> functions
will be used to extract image sizes from graphics.</para>
<para>The main supported image formats are GIF, JPEG, and PNG. Somewhat cruder
support for EPS and PDF images is also available.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="graphicsize.use.img.src.path">
<refmeta>
<refentrytitle>graphicsize.use.img.src.path</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>graphicsize.use.img.src.path</refname>
<refpurpose>Prepend <parameter>img.src.path</parameter> before
filenames passed to extension functions</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="graphicsize.use.img.src.path.frag">
<xsl:param name="graphicsize.use.img.src.path" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero <parameter>img.src.path</parameter> parameter will
be appended before filenames passed to extension functions for
measuring image dimensions.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.extensions">
<refmeta>
<refentrytitle>use.extensions</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.extensions</refname>
<refpurpose>Enable extensions</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.extensions.frag">
<xsl:param name="use.extensions" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, extensions may be used. Each extension is
further controlled by its own parameter. But if
<parameter>use.extensions</parameter> is zero, no extensions will
be used.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="labels"><title>Automatic labelling</title>
<refentry version="5.0" xml:id="chapter.autolabel">
<refmeta>
<refentrytitle>chapter.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">0<alt>none</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>chapter.autolabel</refname>
<refpurpose>Specifies the labeling format for Chapter titles</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chapter.autolabel.frag">
<xsl:param name="chapter.autolabel" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, then chapters will be numbered using the parameter
value as the number format if the value matches one of the following:
</para>
<variablelist>
<varlistentry>
<term>1 or arabic</term>
<listitem>
<para>Arabic numeration (1, 2, 3 ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>A or upperalpha</term>
<listitem>
<para>Uppercase letter numeration (A, B, C ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>a or loweralpha</term>
<listitem>
<para>Lowercase letter numeration (a, b, c ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I or upperroman</term>
<listitem>
<para>Uppercase roman numeration (I, II, III ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>i or lowerroman</term>
<listitem>
<para>Lowercase roman letter numeration (i, ii, iii ...).</para>
</listitem>
</varlistentry>
</variablelist>
<para>Any nonzero value other than the above will generate
the default number format (arabic).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="appendix.autolabel">
<refmeta>
<refentrytitle>appendix.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">0<alt>none</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>appendix.autolabel</refname>
<refpurpose>Specifies the labeling format for Appendix titles</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="appendix.autolabel.frag">
<xsl:param name="appendix.autolabel">A</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, then appendices will be numbered using the
parameter value as the number format if the value matches one of the
following:
</para>
<variablelist>
<varlistentry>
<term>1 or arabic</term>
<listitem>
<para>Arabic numeration (1, 2, 3 ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>A or upperalpha</term>
<listitem>
<para>Uppercase letter numeration (A, B, C ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>a or loweralpha</term>
<listitem>
<para>Lowercase letter numeration (a, b, c ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I or upperroman</term>
<listitem>
<para>Uppercase roman numeration (I, II, III ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>i or lowerroman</term>
<listitem>
<para>Lowercase roman letter numeration (i, ii, iii ...).</para>
</listitem>
</varlistentry>
</variablelist>
<para>Any nonzero value other than the above will generate
the default number format (upperalpha).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="part.autolabel">
<refmeta>
<refentrytitle>part.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">0<alt>none</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>part.autolabel</refname>
<refpurpose>Specifies the labeling format for Part titles</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="part.autolabel.frag">
<xsl:param name="part.autolabel">I</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, then parts will be numbered using the parameter
value as the number format if the value matches one of the following:
</para>
<variablelist>
<varlistentry>
<term>1 or arabic</term>
<listitem>
<para>Arabic numeration (1, 2, 3 ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>A or upperalpha</term>
<listitem>
<para>Uppercase letter numeration (A, B, C ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>a or loweralpha</term>
<listitem>
<para>Lowercase letter numeration (a, b, c ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I or upperroman</term>
<listitem>
<para>Uppercase roman numeration (I, II, III ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>i or lowerroman</term>
<listitem>
<para>Lowercase roman letter numeration (i, ii, iii ...).</para>
</listitem>
</varlistentry>
</variablelist>
<para>Any nonzero value other than the above will generate
the default number format (upperroman).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="reference.autolabel">
<refmeta>
<refentrytitle>reference.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">0<alt>none</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>reference.autolabel</refname>
<refpurpose>Specifies the labeling format for Reference titles</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="reference.autolabel.frag">
<xsl:param name="reference.autolabel">I</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, references will be numbered using the parameter
value as the number format if the value matches one of the
following:
</para>
<variablelist>
<varlistentry>
<term>1 or arabic</term>
<listitem>
<para>Arabic numeration (1, 2, 3 ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>A or upperalpha</term>
<listitem>
<para>Uppercase letter numeration (A, B, C ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>a or loweralpha</term>
<listitem>
<para>Lowercase letter numeration (a, b, c ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I or upperroman</term>
<listitem>
<para>Uppercase roman numeration (I, II, III ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>i or lowerroman</term>
<listitem>
<para>Lowercase roman letter numeration (i, ii, iii ...).</para>
</listitem>
</varlistentry>
</variablelist>
<para>Any non-zero value other than the above will generate
the default number format (upperroman).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="preface.autolabel">
<refmeta>
<refentrytitle>preface.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">0<alt>none</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>preface.autolabel</refname>
<refpurpose>Specifices the labeling format for Preface titles</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="preface.autolabel.frag"><xsl:param name="preface.autolabel" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero then prefaces will be numbered using the parameter
value as the number format if the value matches one of the following:
</para>
<variablelist>
<varlistentry>
<term>1 or arabic</term>
<listitem>
<para>Arabic numeration (1, 2, 3 ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>A or upperalpha</term>
<listitem>
<para>Uppercase letter numeration (A, B, C ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>a or loweralpha</term>
<listitem>
<para>Lowercase letter numeration (a, b, c ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>I or upperroman</term>
<listitem>
<para>Uppercase roman numeration (I, II, III ...).</para>
</listitem>
</varlistentry>
<varlistentry>
<term>i or lowerroman</term>
<listitem>
<para>Lowercase roman letter numeration (i, ii, iii ...).</para>
</listitem>
</varlistentry>
</variablelist>
<para>Any nonzero value other than the above will generate
the default number format (arabic).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="qandadiv.autolabel">
<refmeta>
<refentrytitle>qandadiv.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>qandadiv.autolabel</refname>
<refpurpose>Are divisions in QAndASets enumerated?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="qandadiv.autolabel.frag"><xsl:param name="qandadiv.autolabel" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, unlabeled qandadivs will be enumerated.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="section.autolabel">
<refmeta>
<refentrytitle>section.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>section.autolabel</refname>
<refpurpose>Are sections enumerated?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="section.autolabel.frag"><xsl:param name="section.autolabel" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true (non-zero), unlabeled sections will be enumerated.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="section.autolabel.max.depth">
<refmeta>
<refentrytitle>section.autolabel.max.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>section.autolabel.max.depth</refname>
<refpurpose>The deepest level of sections that are numbered.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="section.autolabel.max.depth.frag">
<xsl:param name="section.autolabel.max.depth">8</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When section numbering is turned on by the
<parameter>section.autolabel</parameter> parameter, then this
parameter controls the depth of <tag>section</tag> nesting that is
numbered. Sections nested to a level deeper than this value will not
be numbered.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="section.label.includes.component.label">
<refmeta>
<refentrytitle>section.label.includes.component.label</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>section.label.includes.component.label</refname>
<refpurpose>Do section labels include the component label?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="section.label.includes.component.label.frag"><xsl:param name="section.label.includes.component.label" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, section labels are prefixed with the label of the
component that contains them.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="label.from.part">
<refmeta>
<refentrytitle>label.from.part</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>label.from.part</refname>
<refpurpose>Renumber components in each part?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="label.from.part.frag">
<xsl:param name="label.from.part" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>label.from.part</parameter> is non-zero, then
numbering of components — <tag>preface</tag>,
<tag>chapter</tag>, <tag>appendix</tag>, and
<tag>reference</tag> (when <tag>reference</tag> occurs at the
component level) — is re-started within each
<tag>part</tag>.</para>
<para>If <parameter>label.from.part</parameter> is zero (the
default), numbering of components is <emphasis>not</emphasis>
re-started within each <tag>part</tag>; instead, components are
numbered sequentially throughout each <tag>book</tag>,
regardless of whether or not they occur within <tag>part</tag>
instances.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="component.label.includes.part.label">
<refmeta>
<refentrytitle>component.label.includes.part.label</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>component.label.includes.part.label</refname>
<refpurpose>Do component labels include the part label?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="component.label.includes.part.label.frag"><xsl:param name="component.label.includes.part.label" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, number labels for <tag>chapter</tag>,
<tag>appendix</tag>, and other component elements are prefixed with
the label of the part element that contains them. So you might see
Chapter II.3 instead of Chapter 3. Also, the labels for formal
elements such as <tag>table</tag> and <tag>figure</tag> will include
the part label. If there is no part element container, then no prefix
is generated.
</para>
<para>
This feature is most useful when the
<parameter>label.from.part</parameter> parameter is turned on.
In that case, there would be more than one <tag>chapter</tag>
<quote>1</quote>, and the extra part label prefix will identify
each chapter unambiguously.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="html"><title>HTML</title>
<refentry version="5.0" xml:id="html.base">
<refmeta>
<refentrytitle>html.base</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.base</refname>
<refpurpose>An HTML base URI</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.base.frag">
<xsl:param name="html.base"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If html.base is set, it is used for the <tag>base</tag> element
in the <tag>head</tag> of the html documents. The parameter specifies
the base URL for all relative URLs in the document. This is useful
for dynamically served html where the base URI needs to be
shifted.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.stylesheet">
<refmeta>
<refentrytitle>html.stylesheet</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.stylesheet</refname>
<refpurpose>Name of the stylesheet(s) to use in the generated HTML</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.stylesheet.frag">
<xsl:param name="html.stylesheet"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>html.stylesheet</parameter> parameter is either
empty, indicating that no stylesheet <tag>link</tag> tag should be
generated in the html output, or it is a list of one or more
stylesheet files.</para>
<para>Multiple stylesheets are space-delimited. If you need to
reference a stylesheet URI that includes a space, encode it with
<literal>%20</literal>. A separate html <literal>link</literal> element will
be generated for each stylesheet in the order they are listed in the
parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.stylesheet.type">
<refmeta>
<refentrytitle>html.stylesheet.type</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.stylesheet.type</refname>
<refpurpose>The type of the stylesheet used in the generated HTML</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.stylesheet.type.frag"><xsl:param name="html.stylesheet.type">text/css</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The type of the stylesheet to place in the HTML <tag>link</tag> tag.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="css.decoration">
<refmeta>
<refentrytitle>css.decoration</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>css.decoration</refname>
<refpurpose>Enable CSS decoration of elements</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="css.decoration.frag">
<xsl:param name="css.decoration" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If non-zero, then html elements produced by the stylesheet may be
decorated with <literal>style</literal> attributes. For example, the
<literal>li</literal> tags produced for list items may include a
fragment of CSS in the <literal>style</literal> attribute which sets
the CSS property "list-style-type".
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.script">
<refmeta>
<refentrytitle>html.script</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.script</refname>
<refpurpose>Name of the script(s) to use in the generated HTML</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.script.frag">
<xsl:param name="html.script"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>html.script</parameter> parameter is either
empty (default), indicating that no <tag>script</tag> element should be
generated in the html output, or it is a list of one or more
script locations.</para>
<para>Multiple script locations are space-delimited. If you need to
reference a script URI that includes a space, encode it with
<literal>%20</literal>. A separate html <literal>script</literal> element will
be generated for each script in the order they are listed in the
parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.script.type">
<refmeta>
<refentrytitle>html.script.type</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.script.type</refname>
<refpurpose>The type of script used in the generated HTML</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.script.type.frag"><xsl:param name="html.script.type">text/javascript</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The type of script to place in the HTML <tag>script</tag> element.
Specifically, the value of the <tag>script</tag> element's <tag>type</tag>
attribute.
The default value is <literal>text/javascript</literal>.
This param is used only when the stylesheet parameter
<tag>html.script</tag> is non-blank and specifies the location of a script.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="spacing.paras">
<refmeta>
<refentrytitle>spacing.paras</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>spacing.paras</refname>
<refpurpose>Insert additional <p> elements for spacing?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="spacing.paras.frag">
<xsl:param name="spacing.paras" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When non-zero, additional, empty paragraphs are inserted in
several contexts (for example, around informal figures), to create a
more pleasing visual appearance in many browsers.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="emphasis.propagates.style">
<refmeta>
<refentrytitle>emphasis.propagates.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>emphasis.propagates.style</refname>
<refpurpose>Pass emphasis role attribute through to HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="emphasis.propagates.style.frag">
<xsl:param name="emphasis.propagates.style" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the <literal>role</literal> attribute of
<tag>emphasis</tag> elements will be passed through to the HTML as a
class attribute on a <literal>span</literal> that surrounds the
emphasis.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="para.propagates.style">
<refmeta>
<refentrytitle>para.propagates.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>para.propagates.style</refname>
<refpurpose>Pass para role attribute through to HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="para.propagates.style.frag">
<xsl:param name="para.propagates.style" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true, the role attribute of <tag>para</tag> elements
will be passed through to the HTML as a class attribute on the
<tag>p</tag> generated for the paragraph.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="phrase.propagates.style">
<refmeta>
<refentrytitle>phrase.propagates.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>phrase.propagates.style</refname>
<refpurpose>Pass phrase role attribute through to HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="phrase.propagates.style.frag">
<xsl:param name="phrase.propagates.style" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the role attribute of <tag>phrase</tag> elements
will be passed through to the HTML as a <literal>class</literal>
attribute on a <literal>span</literal> that surrounds the
phrase.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="entry.propagates.style">
<refmeta>
<refentrytitle>entry.propagates.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>entry.propagates.style</refname>
<refpurpose>Pass entry role attribute through to HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="entry.propagates.style.frag">
<xsl:param name="entry.propagates.style" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true, the role attribute of <tag>entry</tag> elements
will be passed through to the HTML as a class attribute on the
<tag>td</tag> or <tag>th</tag> generated for the table
cell.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.longdesc">
<refmeta>
<refentrytitle>html.longdesc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.longdesc</refname>
<refpurpose>Should longdesc URIs be created?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.longdesc.frag">
<xsl:param name="html.longdesc" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, HTML files will be created for the
<literal>longdesc</literal> attribute. These files
are created from the <tag>textobject</tag>s in
<tag>mediaobject</tag>s and
<tag>inlinemediaobject</tag>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.longdesc.link">
<refmeta>
<refentrytitle>html.longdesc.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.longdesc.link</refname>
<refpurpose>Should a link to the longdesc be included in the HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.longdesc.link.frag">
<xsl:param name="html.longdesc.link" select="$html.longdesc"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, links will be created to the
HTML files created for the
<literal>longdesc</literal> attribute. It makes no
sense to enable this option without also enabling the
<parameter>html.longdesc</parameter> parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="make.valid.html">
<refmeta>
<refentrytitle>make.valid.html</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>make.valid.html</refname>
<refpurpose>Attempt to make sure the HTML output is valid HTML</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="make.valid.html.frag">
<xsl:param name="make.valid.html" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>make.valid.html</parameter> is true, the stylesheets take
extra effort to ensure that the resulting HTML is valid. This may mean that some
<tag>para</tag> tags are translated into HTML <tag>div</tag>s or
that other substitutions occur.</para>
<para>This parameter is different from <parameter>html.cleanup</parameter>
because it changes the resulting markup; it does not use extension functions
to manipulate result-tree-fragments and is therefore applicable to any
XSLT processor.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.cleanup">
<refmeta>
<refentrytitle>html.cleanup</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.cleanup</refname>
<refpurpose>Attempt to clean up the resulting HTML?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.cleanup.frag">
<xsl:param name="html.cleanup" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, and if the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.exslt.org/">EXSLT</link>
extensions are supported by your processor, the resulting HTML will be
<quote>cleaned up</quote>. This improves the chances that the
resulting HTML will be valid. It may also improve the formatting of
some elements.</para>
<para>This parameter is different from <parameter>make.valid.html</parameter>
because it uses extension functions to manipulate result-tree-fragments.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.append">
<refmeta>
<refentrytitle>html.append</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.append</refname>
<refpurpose>Specifies content to append to HTML output</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.append.frag"><xsl:param name="html.append"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies content to append to the end of HTML files output by
the <filename>html/docbook.xsl</filename> stylesheet, after the
closing <code><html></code> tag. You probably don’t want to set any
value for this parameter; but if you do, the only value it should ever
be set to is a newline character: <code>&#x0a;</code> or
<code>&#10;</code></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="draft.mode">
<refmeta>
<refentrytitle>draft.mode</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
</refmeta>
<refnamediv>
<refname>draft.mode</refname>
<refpurpose>Select draft mode</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="draft.mode.frag">
<xsl:param name="draft.mode">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Selects draft mode. If <parameter>draft.mode</parameter> is
<quote><literal>yes</literal></quote>, the entire document will be treated
as a draft. If it is <quote><literal>no</literal></quote>, the entire document
will be treated as a final copy. If it is <quote><literal>maybe</literal></quote>,
individual sections will be treated as draft or final independently, depending
on how their <literal>status</literal> attribute is set.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="draft.watermark.image">
<refmeta>
<refentrytitle>draft.watermark.image</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>draft.watermark.image</refname>
<refpurpose>The URI of the image to be used for draft watermarks</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="draft.watermark.image.frag">
<xsl:param name="draft.watermark.image">images/draft.png</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The image to be used for draft watermarks.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.id.attributes">
<refmeta>
<refentrytitle>generate.id.attributes</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.id.attributes</refname>
<refpurpose>Generate ID attributes on container elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.id.attributes.frag">
<xsl:param name="generate.id.attributes" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the HTML stylesheet will generate ID attributes on
containers. For example, the markup:</para>
<screen><section id="foo"><title>Some Title</title>
<para>Some para.</para>
</section></screen>
<para>might produce:</para>
<screen><div class="section" id="foo">
<h2>Some Title</h2>
<p>Some para.</p>
</div></screen>
<para>The alternative is to generate anchors:</para>
<screen><div class="section">
<h2><a name="foo"></a>Some Title</h2>
<p>Some para.</p>
</div></screen>
<para>Because the <tag class="attribute">name</tag> attribute of
the <tag>a</tag> element and the <tag class="attribute">id</tag>
attribute of other tags are both of type <quote>ID</quote>, producing both
generates invalid documents.</para>
<para>As of version 1.50, you can use this switch to control which type of
identifier is generated. For backwards-compatibility, generating
<tag>a</tag> anchors is preferred.</para>
<para>Note: at present, this switch is incompletely implemented.
Disabling ID attributes will suppress them, but enabling ID attributes
will not suppress the anchors.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.consistent.ids">
<refmeta>
<refentrytitle>generate.consistent.ids</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.consistent.ids</refname>
<refpurpose>Generate consistent id values if document is unchanged</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.consistent.ids.frag">
<xsl:param name="generate.consistent.ids" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When the stylesheet assigns an id value to an output element,
the generate-id() function may be used. That function may not
produce consistent values between runs. Version control
systems may misidentify the changing id values as changes
to the document.</para>
<para>If you set this parameter's value to 1, then the
template named <literal>object.id</literal> will replace
the use of the function generate-id() with
<literal><xsl:number level="multiple" count="*"/></literal>.
This counts preceding elements to generate a unique number for
the id value.</para>
<caution>
<para>This param does not associate permanent unique id values
with particular elements.
The id values are consistent only as long as the document
structure does not change.
If the document structure changes, then the counting
of elements changes, and all id values after
the first such change may be different, even when there is
no change to the element itself or its output.
</para>
</caution>
<para>The default value of this parameter is zero, so generate-id() is used
by default.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.meta.abstract">
<refmeta>
<refentrytitle>generate.meta.abstract</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.meta.abstract</refname>
<refpurpose>Generate HTML <tag>META</tag> element from <tag>abstract</tag>?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.meta.abstract.frag">
<xsl:param name="generate.meta.abstract" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, document abstracts will be reproduced in the HTML
<literal>head</literal>, with <literal>>meta name="description" content="..."</literal></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="make.clean.html">
<refmeta>
<refentrytitle>make.clean.html</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>make.clean.html</refname>
<refpurpose>Make HTML conform to modern coding standards</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="make.clean.html.frag">
<xsl:param name="make.clean.html" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>make.clean.html</parameter> is true, the stylesheets take
extra effort to ensure that the resulting HTML is conforms to
modern HTML coding standards. In addition to eliminating
excessive and noncompliant coding, it moves presentation
HTML coding to a CSS stylesheet.</para>
<para>The resulting HTML is dependent on
CSS for formatting, and so the stylesheet is capable of
generating a supporting CSS file. The <parameter>docbook.css.source</parameter>
and <parameter>custom.css.source</parameter> parameters control
how a CSS file is generated.</para>
<para>If you require your CSS to reside in the HTML
<tag>head</tag> element, then the <parameter>generate.css.header</parameter>
can be used to do that.</para>
<para>The <parameter>make.clean.html</parameter> parameter is
different from <parameter>html.cleanup</parameter>
because the former changes the resulting markup; it does not use extension functions
like the latter to manipulate result-tree-fragments,
and is therefore applicable to any XSLT processor.</para>
<para>If <parameter>make.clean.html</parameter> is set to zero (the default),
then the stylesheet retains its original
<quote>old style</quote>
HTML formatting features.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="docbook.css.source">
<refmeta>
<refentrytitle>docbook.css.source</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>docbook.css.source</refname>
<refpurpose>Name of the default CSS input file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="docbook.css.source.frag"><xsl:param name="docbook.css.source">docbook.css.xml</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>docbook.css.source</parameter> parameter
specifies the name of the file containing the default DocBook
CSS styles. Those styles are necessary when the
<parameter>make.clean.html</parameter> parameter is nonzero.</para>
<para>The file is a well-formed XML file that
must consist of a single <tag>style</tag> root
element that contains CSS styles as its text content.
The default value of the parameter (and filename)
is <literal>docbook.css.xml</literal>.
The stylesheets ship with the default file. You can substitute
your own and specify its path in this parameter.</para>
<para>If <parameter>docbook.css.source</parameter> is not blank,
and <parameter>make.clean.html</parameter> is nonzero, then
the stylesheet takes the following actions:</para>
<orderedlist>
<listitem>
<para>The stylesheet uses the XSLT <literal>document()</literal>
function to open the file specified by the parameter and
load it into a variable.</para>
</listitem>
<listitem>
<para>The stylesheet forms an output pathname consisting of the
value of the <parameter>base.dir</parameter> parameter (if it is set)
and the value of <parameter>docbook.css.source</parameter>,
with the <literal>.xml</literal> suffix stripped off.
</para>
</listitem>
<listitem>
<para>The stylesheet removes the <tag>style</tag>
wrapper element and writes just the CSS text content to the output file.</para>
</listitem>
<listitem>
<para>The stylesheet adds a <tag>link</tag> element to the
HTML <tag>HEAD</tag> element to reference the external CSS stylesheet.
For example:</para>
<programlisting><link rel="stylesheet" href="docbook.css" type="text/css">
</programlisting>
<para>However, if the <parameter>docbook.css.link</parameter>
parameter is set to zero, then no <tag>link</tag> is written
for the default CSS file. That is useful if a custom
CSS file will import the default CSS stylesheet to ensure
proper cascading of styles.</para>
</listitem>
</orderedlist>
<para>If the <parameter>docbook.css.source</parameter> parameter
is changed from its default <literal>docbook.css.xml</literal> to blank,
then no default CSS is generated. Likewise if the
<parameter>make.clean.html</parameter> parameter is set to zero,
then no default CSS is generated. The
<parameter>custom.css.source</parameter> parameter can be used
instead to generate a complete custom CSS file.</para>
<para>You can use the <parameter>generate.css.header</parameter>
parameter to instead write the CSS to each HTML <tag>HEAD</tag>
element in a <tag>style</tag> tag instead of an external CSS file.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="docbook.css.link">
<refmeta>
<refentrytitle>docbook.css.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>docbook.css.link</refname>
<refpurpose>Insert a link referencing the default CSS stylesheet</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="docbook.css.link.frag">
<xsl:param name="docbook.css.link" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The stylesheets are capable of generating a default
CSS stylesheet file. The parameters
<parameter>make.clean.html</parameter> and
<parameter>docbook.css.source</parameter> control that feature.</para>
<para>Normally if a default CSS file is generated, then
the stylesheet inserts a <tag>link</tag> tag in the HTML
<tag>HEAD</tag> element to reference it.
However, you can omit that <tag>link</tag> reference if
you set the <parameter>docbook.css.link</parameter> to zero
(1 is the default).</para>
<para>This parameter is useful when you want to import the
default CSS into a custom CSS file generated using the
<parameter>custom.css.source</parameter> parameter.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="custom.css.source">
<refmeta>
<refentrytitle>custom.css.source</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>custom.css.source</refname>
<refpurpose>Name of a custom CSS input file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="custom.css.source.frag"><xsl:param name="custom.css.source"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>custom.css.source</parameter>
parameter enables you to add CSS styles to DocBook's
HTML output.</para>
<para>The parameter
specifies the name of a file containing custom
CSS styles. The file must be a well-formed XML file that
consists of a single <tag>style</tag> root
element that contains CSS styles as its text content.
For example:</para>
<programlisting><?xml version="1.0"?>
<style>
h2 {
font-weight: bold;
color: blue;
}
...
</style>
</programlisting>
<para>The filename specified by the parameter
should have a <literal>.xml</literal>
filename suffix, although that is not required.
The default value of this parameter is blank.</para>
<para>If <parameter>custom.css.source</parameter> is not blank, then
the stylesheet takes the following actions.
These actions take place regardless of the value of
the <parameter>make.clean.html</parameter> parameter.</para>
<orderedlist>
<listitem>
<para>The stylesheet uses the XSLT <literal>document()</literal>
function to open the file specified by the parameter and
load it into a variable.</para>
</listitem>
<listitem>
<para>The stylesheet forms an output pathname consisting of the
value of the <parameter>base.dir</parameter> parameter (if it is set)
and the value of <parameter>custom.css.source</parameter>,
with the <literal>.xml</literal> suffix stripped off.
</para>
</listitem>
<listitem>
<para>The stylesheet removes the <tag>style</tag>
wrapper element and writes just the CSS text content to the output file.</para>
</listitem>
<listitem>
<para>The stylesheet adds a <tag>link</tag> element to the
HTML <tag>HEAD</tag> element to reference this external CSS stylesheet.
For example:
<programlisting><link rel="stylesheet" href="custom.css" type="text/css">
</programlisting>
</para>
</listitem>
</orderedlist>
<para>If the <parameter>make.clean.html</parameter> parameter is nonzero
(the default is zero),
and if the <parameter>docbook.css.source</parameter> parameter
is not blank (the default is not blank),
then the stylesheet will also generate a default CSS file
and add a <tag>link</tag> tag to reference it.
The <tag>link</tag> to the custom CSS comes after the
<tag>link</tag> to the default, so it should cascade properly
in most browsers.
If you do not want two <tag>link</tag> tags, and
instead want your custom CSS to import the default generated
CSS file, then do the following:
</para>
<orderedlist>
<listitem>
<para>Add a line like the following to your custom CSS source file:</para>
<programlisting>@import url("docbook.css")
</programlisting>
</listitem>
<listitem>
<para>Set the <parameter>docbook.css.link</parameter> parameter
to zero. This will omit the <tag>link</tag> tag
that references the default CSS file.</para>
</listitem>
</orderedlist>
<para>If you set <parameter>make.clean.html</parameter> to nonzero but
you do not want the default CSS generated, then also set
the <parameter>docbook.css.source</parameter> parameter to blank.
Then no default CSS will be generated, and so
all CSS styles must come from your custom CSS file.</para>
<para>You can use the <parameter>generate.css.header</parameter>
parameter to instead write the CSS to each HTML <tag>HEAD</tag>
element in a <tag>style</tag> tag instead of an external CSS file.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.css.header">
<refmeta>
<refentrytitle>generate.css.header</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.css.header</refname>
<refpurpose>Insert generated CSS styles in HEAD element</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.css.header.frag">
<xsl:param name="generate.css.header" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The stylesheets are capable of generating both default
and custom CSS stylesheet files. The parameters
<parameter>make.clean.html</parameter>,
<parameter>docbook.css.source</parameter>, and
<parameter>custom.css.source</parameter> control that feature.</para>
<para>If you require that CSS styles reside in the HTML
<tag>HEAD</tag> element instead of external CSS files,
then set the <parameter>generate.css.header</parameter>
parameter to nonzero (it is zero by default).
Then instead of generating the CSS in external files,
they are wrapped in <tag>style</tag> elements in
the <tag>HEAD</tag> element of each HTML output file.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="xslt"><title>XSLT Processing</title>
<refentry version="5.0" xml:id="rootid">
<refmeta>
<refentrytitle>rootid</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>rootid</refname>
<refpurpose>Specify the root element to format</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="rootid.frag">
<xsl:param name="rootid"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>rootid</parameter> is not empty, it must be the
value of an ID that occurs in the document being formatted. The entire
document will be loaded and parsed, but formatting will begin at the
element identified, rather than at the root. For example, this allows
you to process only <tag>chapter</tag> 4 of a <tag>book</tag>.</para>
<para>Because the entire document is available to the processor, automatic
numbering, cross references, and other dependencies are correctly
resolved.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="suppress.navigation">
<refmeta>
<refentrytitle>suppress.navigation</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>suppress.navigation</refname>
<refpurpose>Disable header and footer navigation</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="suppress.navigation.frag">
<xsl:param name="suppress.navigation" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If non-zero, header and footer navigation will be suppressed.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="suppress.header.navigation">
<refmeta>
<refentrytitle>suppress.header.navigation</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>suppress.header.navigation</refname>
<refpurpose>Disable header navigation</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="suppress.header.navigation.frag">
<xsl:param name="suppress.header.navigation" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, header navigation will be suppressed.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="suppress.footer.navigation">
<refmeta>
<refentrytitle>suppress.footer.navigation</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>suppress.footer.navigation</refname>
<refpurpose>Disable footer navigation</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="suppress.footer.navigation.frag"><xsl:param name="suppress.footer.navigation">0</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If non-zero, footer navigation will be suppressed.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="header.rule">
<refmeta>
<refentrytitle>header.rule</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>header.rule</refname>
<refpurpose>Rule under headers?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="header.rule.frag">
<xsl:param name="header.rule" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a rule will be drawn below the page headers.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="footer.rule">
<refmeta>
<refentrytitle>footer.rule</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>footer.rule</refname>
<refpurpose>Rule over footers?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="footer.rule.frag">
<xsl:param name="footer.rule" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a rule will be drawn above the page footers.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="id.warnings">
<refmeta>
<refentrytitle>id.warnings</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>id.warnings</refname>
<refpurpose>Should warnings be generated for titled elements without IDs?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="id.warnings.frag">
<xsl:param name="id.warnings" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the stylesheet will issue a warning for any element
(other than the root element) which has a <tag>title</tag> but does not have an
ID.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="meta"><title>Meta/*Info and Titlepages</title>
<refentry version="5.0" xml:id="inherit.keywords">
<refmeta>
<refentrytitle>inherit.keywords</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>inherit.keywords</refname>
<refpurpose>Inherit keywords from ancestor elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="inherit.keywords.frag">
<xsl:param name="inherit.keywords" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>inherit.keywords</parameter>
is non-zero, the keyword <literal>meta</literal> for each HTML
<literal>head</literal> element will include all of the keywords from
ancestor elements. Otherwise, only the keywords from the current section
will be used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="make.single.year.ranges">
<refmeta>
<refentrytitle>make.single.year.ranges</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>make.single.year.ranges</refname>
<refpurpose>Print single-year ranges (e.g., 1998-1999)</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="make.single.year.ranges.frag">
<xsl:param name="make.single.year.ranges" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, year ranges that span a single year will be printed
in range notation (1998-1999) instead of discrete notation
(1998, 1999).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="make.year.ranges">
<refmeta>
<refentrytitle>make.year.ranges</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>make.year.ranges</refname>
<refpurpose>Collate copyright years into ranges?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="make.year.ranges.frag"><xsl:param name="make.year.ranges" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, multiple copyright <tag>year</tag> elements will be
collated into ranges.
This works only if each year number is put into a separate
year element. The copyright element permits multiple
year elements. If a year element contains a dash or
a comma, then that year element will not be merged into
any range.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="author.othername.in.middle">
<refmeta>
<refentrytitle>author.othername.in.middle</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>author.othername.in.middle</refname>
<refpurpose>Is <tag>othername</tag> in <tag>author</tag> a
middle name?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="author.othername.in.middle.frag">
<xsl:param name="author.othername.in.middle" select="1"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the <tag>othername</tag> of an <tag>author</tag>
appears between the <tag>firstname</tag> and
<tag>surname</tag>. Otherwise, <tag>othername</tag>
is suppressed.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="blurb.on.titlepage.enabled">
<refmeta>
<refentrytitle>blurb.on.titlepage.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>blurb.on.titlepage.enabled</refname>
<refpurpose>Display personblurb and authorblurb on title pages?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="blurb.on.titlepage.enabled.frag">
<xsl:param name="blurb.on.titlepage.enabled" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, output from <tag>authorblurb</tag> and
<tag>personblurb</tag> elements is displayed on title pages. If zero
(the default), output from those elements is suppressed on title pages
(unless you are using a <literal>titlepage</literal> customization
that causes them to be included).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="contrib.inline.enabled">
<refmeta>
<refentrytitle>contrib.inline.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>contrib.inline.enabled</refname>
<refpurpose>Display contrib output inline?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="contrib.inline.enabled.frag"><xsl:param name="contrib.inline.enabled">1</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero (the default), output of the <tag>contrib</tag> element is
displayed as inline content rather than as block content.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="editedby.enabled">
<refmeta>
<refentrytitle>editedby.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>editedby.enabled</refname>
<refpurpose>Display “Edited by” heading above editor name?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="editedby.enabled.frag"><xsl:param name="editedby.enabled">1</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a localized <emphasis role="bold">Edited
by</emphasis> heading is displayed above editor names in output of the
<tag>editor</tag> element.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="abstract.notitle.enabled">
<refmeta>
<refentrytitle>abstract.notitle.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>abstract.notitle.enabled</refname>
<refpurpose>Suppress display of abstract titles?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="abstract.notitle.enabled.frag"><xsl:param name="abstract.notitle.enabled" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, in output of the <tag>abstract</tag> element on titlepages,
display of the abstract title is suppressed.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="othercredit.like.author.enabled">
<refmeta>
<refentrytitle>othercredit.like.author.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>othercredit.like.author.enabled</refname>
<refpurpose>Display othercredit in same style as author?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="othercredit.like.author.enabled.frag"><xsl:param name="othercredit.like.author.enabled">0</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, output of the
<tag>othercredit</tag> element on titlepages is displayed in
the same style as <tag>author</tag> and
<tag>editor</tag> output. If zero then
<tag>othercredit</tag> output is displayed using a style
different than that of <tag>author</tag> and
<tag>editor</tag>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.legalnotice.link">
<refmeta>
<refentrytitle>generate.legalnotice.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.legalnotice.link</refname>
<refpurpose>Write legalnotice to separate chunk and generate link?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.legalnotice.link.frag"><xsl:param name="generate.legalnotice.link" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If the value of <parameter>generate.legalnotice.link</parameter>
is non-zero, the stylesheet:
<itemizedlist>
<listitem>
<para>writes the contents of <tag>legalnotice</tag> to a separate
HTML file</para>
</listitem>
<listitem>
<para>inserts a hyperlink to the <tag>legalnotice</tag> file</para>
</listitem>
<listitem>
<para>adds (in the HTML <literal>head</literal>) either a single
<literal>link</literal> or element or multiple
<literal>link</literal> elements (depending on the value of the
<parameter>html.head.legalnotice.link.multiple</parameter>
parameter), with the value or values derived from the
<parameter>html.head.legalnotice.link.types</parameter>
parameter</para>
</listitem>
</itemizedlist>
Otherwise, if <parameter>generate.legalnotice.link</parameter> is
zero, <tag>legalnotice</tag> contents are rendered on the title
page.</para>
<para>The name of the separate HTML file is computed as follows:
<orderedlist>
<listitem>
<para>If a filename is given by the <tag class="xmlpi">dbhtml filename</tag>
processing instruction, that filename is used.</para>
</listitem>
<listitem>
<para>If the legalnotice has an <tag class="attribute">id</tag>/<tag class="attribute">xml:id</tag>
attribute, and if <parameter>use.id.as.filename</parameter> != 0, the filename
is the concatenation of the id value and the value of the <parameter>html.ext</parameter>
parameter.</para>
</listitem>
<listitem>
<para>If the legalnotice does not have an <tag class="attribute">id</tag>/<tag class="attribute">xml:id</tag>
attribute, or if <parameter>use.id.as.filename</parameter> = 0, the filename is the concatenation of "ln-",
auto-generated id value, and <parameter>html.ext</parameter> value.
</para>
</listitem>
</orderedlist>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.revhistory.link">
<refmeta>
<refentrytitle>generate.revhistory.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.revhistory.link</refname>
<refpurpose>Write revhistory to separate chunk and generate link?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.revhistory.link.frag"><xsl:param name="generate.revhistory.link" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the contents of <tag>revhistory</tag> are written
to a separate HTML file and a link to the file is
generated. Otherwise, <tag>revhistory</tag> contents are rendered on
the title page.</para>
<para>The name of the separate HTML file is computed as follows:
<orderedlist>
<listitem>
<para>If a filename is given by the <tag class="xmlpi">dbhtml filename</tag> processing instruction,
that filename is used.</para>
</listitem>
<listitem>
<para>If the revhistory has an <tag class="attribute">id</tag>/<tag class="attribute">xml:id</tag>
attribute, and if <parameter>use.id.as.filename</parameter> != 0, the filename is the concatenation of
the id value and the value of the <parameter>html.ext</parameter> parameter.</para>
</listitem>
<listitem>
<para>If the revhistory does not have an <tag class="attribute">id</tag>/<tag class="attribute">xml:id</tag>
attribute, or if <parameter>use.id.as.filename</parameter> = 0, the filename is the concatenation of "rh-",
auto-generated id value, and <parameter>html.ext</parameter> value.
</para>
</listitem>
</orderedlist>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.head.legalnotice.link.types">
<refmeta>
<refentrytitle>html.head.legalnotice.link.types</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.head.legalnotice.link.types</refname>
<refpurpose>Specifies link types for legalnotice link in html head</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.head.legalnotice.link.types.frag">
<xsl:param name="html.head.legalnotice.link.types">copyright</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of
<parameter>html.head.legalnotice.link.types</parameter> is a
space-separated list of link types, as described in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/html401/types.html#type-links">Section 6.12
of the HTML 4.01 specification</link>. If the value of the
<parameter>generate.legalnotice.link</parameter> parameter is
non-zero, then the stylesheet generates (in the
<literal>head</literal> section of the HTML source) either a single
HTML <literal>link</literal> element or, if the value of the
<parameter>html.head.legalnotice.link.multiple</parameter> is
non-zero, one <literal>link</literal> element for each link type
specified. Each <literal>link</literal> has the following attributes:
<itemizedlist>
<listitem>
<para>a <tag class="attribute">rel</tag> attribute whose
value is derived from the value of
<parameter>html.head.legalnotice.link.types</parameter></para>
</listitem>
<listitem>
<para>an <tag class="attribute">href</tag> attribute whose
value is set to the URL of the file containing the
<tag>legalnotice</tag></para>
</listitem>
<listitem>
<para>a <tag class="attribute">title</tag> attribute whose
value is set to the title of the corresponding
<tag>legalnotice</tag> (or a title programatically
determined by the stylesheet)</para>
</listitem>
</itemizedlist>
For example:
<screen> <link rel="license" href="ln-id2524073.html" title="Legal Notice"></screen>
</para>
<refsection><info><title>About the default value</title></info>
<para>In an ideal world, the default value of
<parameter>html.head.legalnotice.link.types</parameter> would
probably be “<literal>license</literal>”, since the content of the
DocBook <tag>legalnotice</tag> is typically license
information, not copyright information. However, the default value
is “<literal>copyright</literal>” for pragmatic reasons: because
that’s among the set of “recognized link types” listed in <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/html401/types.html#type-links">Section
6.12 of the HTML 4.01 specification</link>, and because certain
browsers and browser extensions are preconfigured to recognize that
value.</para>
</refsection>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.head.legalnotice.link.multiple">
<refmeta>
<refentrytitle>html.head.legalnotice.link.multiple</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.head.legalnotice.link.multiple</refname>
<refpurpose>Generate multiple link instances in html head for legalnotice?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.head.legalnotice.link.multiple.frag">
<xsl:param name="html.head.legalnotice.link.multiple" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>html.head.legalnotice.link.multiple</parameter> is
non-zero and the value of
<parameter>html.head.legalnotice.link.types</parameter> contains
multiple link types, then the stylesheet generates (in the
<literal>head</literal> section of the HTML source) one
<literal>link</literal> element for each link type specified. For
example, if the value of
<parameter>html.head.legalnotice.link.types</parameter> is
“<literal>copyright license</literal>”:
<screen> <link rel="copyright" href="ln-id2524073.html" title="Legal Notice">
<link rel="license" href="ln-id2524073.html" title="Legal Notice"></screen>
Otherwise, the stylesheet generates generates a single
<literal>link</literal> instance; for example:
<screen> <link rel="copyright license" href="ln-id2524073.html" title="Legal Notice"></screen>
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="refentry"><title>Reference Pages</title>
<refentry version="5.0" xml:id="funcsynopsis.decoration">
<refmeta>
<refentrytitle>funcsynopsis.decoration</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>funcsynopsis.decoration</refname>
<refpurpose>Decorate elements of a <tag>funcsynopsis</tag>?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="funcsynopsis.decoration.frag">
<xsl:param name="funcsynopsis.decoration" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, elements of the <tag>funcsynopsis</tag> will be
decorated (e.g. rendered as bold or italic text). The decoration is controlled by
templates that can be redefined in a customization layer.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="funcsynopsis.style">
<refmeta>
<refentrytitle>funcsynopsis.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">ansi</refmiscinfo>
<refmiscinfo class="other" otherclass="value">kr</refmiscinfo>
</refmeta>
<refnamediv>
<refname>funcsynopsis.style</refname>
<refpurpose>What style of <tag>funcsynopsis</tag> should be generated?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="funcsynopsis.style.frag"><xsl:param name="funcsynopsis.style">kr</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>funcsynopsis.style</parameter> is <literal>ansi</literal>,
ANSI-style function synopses are generated for a
<tag>funcsynopsis</tag>, otherwise K&R-style
function synopses are generated.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="function.parens">
<refmeta>
<refentrytitle>function.parens</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>function.parens</refname>
<refpurpose>Generate parens after a function?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="function.parens.frag">
<xsl:param name="function.parens" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the formatting of a <tag>function</tag> element
will include generated parentheses.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="refentry.generate.name">
<refmeta>
<refentrytitle>refentry.generate.name</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>refentry.generate.name</refname>
<refpurpose>Output NAME header before <tag>refname</tag>s?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="refentry.generate.name.frag">
<xsl:param name="refentry.generate.name" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a "NAME" section title is output before the list
of <tag>refname</tag>s. This parameter and
<parameter>refentry.generate.title</parameter> are mutually
exclusive. This means that if you change this parameter to zero, you
should set <parameter>refentry.generate.title</parameter> to non-zero unless
you want get quite strange output.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="refentry.generate.title">
<refmeta>
<refentrytitle>refentry.generate.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>refentry.generate.title</refname>
<refpurpose>Output title before <tag>refname</tag>s?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="refentry.generate.title.frag">
<xsl:param name="refentry.generate.title" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the reference page title or first name is
output before the list of <tag>refname</tag>s. This parameter and
<parameter>refentry.generate.name</parameter> are mutually exclusive.
This means that if you change this parameter to non-zero, you
should set <parameter>refentry.generate.name</parameter> to zero unless
you want get quite strange output.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="refentry.xref.manvolnum">
<refmeta>
<refentrytitle>refentry.xref.manvolnum</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>refentry.xref.manvolnum</refname>
<refpurpose>Output <tag>manvolnum</tag> as part of
<tag>refentry</tag> cross-reference?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="refentry.xref.manvolnum.frag">
<xsl:param name="refentry.xref.manvolnum" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>if non-zero, the <tag>manvolnum</tag> is used when cross-referencing
<tag>refentry</tag>s, either with <tag>xref</tag>
or <tag>citerefentry</tag>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="citerefentry.link">
<refmeta>
<refentrytitle>citerefentry.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>citerefentry.link</refname>
<refpurpose>Generate URL links when cross-referencing RefEntrys?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="citerefentry.link.frag">
<xsl:param name="citerefentry.link" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a web link will be generated, presumably
to an online man->HTML gateway. The text of the link is
generated by the <literal>generate.citerefentry.link</literal> template.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="refentry.separator">
<refmeta>
<refentrytitle>refentry.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>refentry.separator</refname>
<refpurpose>Generate a separator between consecutive RefEntry elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="refentry.separator.frag">
<xsl:param name="refentry.separator" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true, a separator will be generated between consecutive
reference pages.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="refclass.suppress">
<refmeta>
<refentrytitle>refclass.suppress</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>refclass.suppress</refname>
<refpurpose>Suppress display of refclass contents?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="refclass.suppress.frag">
<xsl:param name="refclass.suppress" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If the value of <parameter>refclass.suppress</parameter> is
non-zero, then display of <tag>refclass</tag> contents is
suppressed in output.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="tables"><title>Tables</title>
<refentry version="5.0" xml:id="default.table.width">
<refmeta>
<refentrytitle>default.table.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>default.table.width</refname>
<refpurpose>The default width of tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="default.table.width.frag">
<xsl:param name="default.table.width"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, this value will be used for the
<literal>width</literal> attribute on <tag>table</tag>s that do not specify an
alternate width (with the <tag class="xmlpi">dbhtml table-width</tag> or
<tag class="xmlpi">dbfo table-width</tag> processing instruction).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="nominal.table.width">
<refmeta>
<refentrytitle>nominal.table.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>nominal.table.width</refname>
<refpurpose>The (absolute) nominal width of tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="nominal.table.width.frag">
<xsl:param name="nominal.table.width">6in</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>In order to convert CALS column widths into HTML column widths, it
is sometimes necessary to have an absolute table width to use for conversion
of mixed absolute and relative widths. This value must be an absolute
length (not a percentage).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.borders.with.css">
<refmeta>
<refentrytitle>table.borders.with.css</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.borders.with.css</refname>
<refpurpose>Use CSS to specify table, row, and cell borders?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.borders.with.css.frag">
<xsl:param name="table.borders.with.css" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, CSS will be used to draw table borders.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.cell.border.style">
<refmeta>
<refentrytitle>table.cell.border.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">none</refmiscinfo>
<refmiscinfo class="other" otherclass="value">solid</refmiscinfo>
<refmiscinfo class="other" otherclass="value">dotted</refmiscinfo>
<refmiscinfo class="other" otherclass="value">dashed</refmiscinfo>
<refmiscinfo class="other" otherclass="value">double</refmiscinfo>
<refmiscinfo class="other" otherclass="value">groove</refmiscinfo>
<refmiscinfo class="other" otherclass="value">ridge</refmiscinfo>
<refmiscinfo class="other" otherclass="value">inset</refmiscinfo>
<refmiscinfo class="other" otherclass="value">outset</refmiscinfo>
<refmiscinfo class="other" otherclass="value">solid</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.cell.border.style</refname>
<refpurpose>Specifies the border style of table cells</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.cell.border.style.frag">
<xsl:param name="table.cell.border.style">solid</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the border style of table cells.</para>
<note>
<para>To control properties of cell borders in HTML output, you must also turn on the
<parameter>table.borders.with.css</parameter> parameter.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.cell.border.thickness">
<refmeta>
<refentrytitle>table.cell.border.thickness</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.cell.border.thickness</refname>
<refpurpose>Specifies the thickness of table cell borders</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.cell.border.thickness.frag">
<xsl:param name="table.cell.border.thickness">
<xsl:choose>
<xsl:when test="contains($stylesheet.result.type,'html')">1px</xsl:when>
<xsl:otherwise>0.5pt</xsl:otherwise>
</xsl:choose>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, specifies the thickness of borders on table
cells. See <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/CSS21/box.html#border-width-properties">
CSS</link></para>
<note>
<para>To control properties of cell borders in HTML output, you must also turn on the
<parameter>table.borders.with.css</parameter> parameter.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.cell.border.color">
<refmeta>
<refentrytitle>table.cell.border.color</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">color</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.cell.border.color</refname>
<refpurpose>Specifies the border color of table cells</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.cell.border.color.frag">
<xsl:param name="table.cell.border.color"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set the color of table cell borders. If non-zero, the value is used
for the border coloration. See <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/CSS21/syndata.html#value-def-color">CSS</link>. A
<literal>color</literal> is either a keyword or a numerical RGB specification.
Keywords are aqua, black, blue, fuchsia, gray, green, lime, maroon,
navy, olive, orange, purple, red, silver, teal, white, and
yellow.</para>
<note>
<para>To control properties of cell borders in HTML output, you must also turn on the
<parameter>table.borders.with.css</parameter> parameter.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.frame.border.style">
<refmeta>
<refentrytitle>table.frame.border.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">none</refmiscinfo>
<refmiscinfo class="other" otherclass="value">solid</refmiscinfo>
<refmiscinfo class="other" otherclass="value">dotted</refmiscinfo>
<refmiscinfo class="other" otherclass="value">dashed</refmiscinfo>
<refmiscinfo class="other" otherclass="value">double</refmiscinfo>
<refmiscinfo class="other" otherclass="value">groove</refmiscinfo>
<refmiscinfo class="other" otherclass="value">ridge</refmiscinfo>
<refmiscinfo class="other" otherclass="value">inset</refmiscinfo>
<refmiscinfo class="other" otherclass="value">outset</refmiscinfo>
<refmiscinfo class="other" otherclass="value">solid</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.frame.border.style</refname>
<refpurpose>Specifies the border style of table frames</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.frame.border.style.frag">
<xsl:param name="table.frame.border.style">solid</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the border style of table frames.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.frame.border.thickness">
<refmeta>
<refentrytitle>table.frame.border.thickness</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.frame.border.thickness</refname>
<refpurpose>Specifies the thickness of the frame border</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.frame.border.thickness.frag">
<xsl:param name="table.frame.border.thickness">
<xsl:choose>
<xsl:when test="contains($stylesheet.result.type,'html')">1px</xsl:when>
<xsl:otherwise>0.5pt</xsl:otherwise>
</xsl:choose>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the thickness of the border on the table's frame.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.frame.border.color">
<refmeta>
<refentrytitle>table.frame.border.color</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">color</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.frame.border.color</refname>
<refpurpose>Specifies the border color of table frames</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.frame.border.color.frag">
<xsl:param name="table.frame.border.color"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the border color of table frames.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="default.table.frame">
<refmeta>
<refentrytitle>default.table.frame</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>default.table.frame</refname>
<refpurpose>The default framing of tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="default.table.frame.frag">
<xsl:param name="default.table.frame">all</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This value will be used when there is no frame attribute on the
table. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.cellspacing">
<refmeta>
<refentrytitle>html.cellspacing</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.cellspacing</refname>
<refpurpose>Default value for cellspacing in HTML tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.cellspacing.frag">
<xsl:param name="html.cellspacing"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, this value will be used as the default cellspacing
value in HTML tables. nn for pixels or nn% for percentage
length. E.g. 5 or 5%</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.cellpadding">
<refmeta>
<refentrytitle>html.cellpadding</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.cellpadding</refname>
<refpurpose>Default value for cellpadding in HTML tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.cellpadding.frag">
<xsl:param name="html.cellpadding"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, this value will be used as the default cellpadding value
in HTML tables. nn for pixels or nn% for percentage length. E.g. 5 or
5%</para>
</refsection>
</refentry>
</reference>
<reference xml:id="qa"><title>QAndASet</title>
<refentry version="5.0" xml:id="qanda.defaultlabel">
<refmeta>
<refentrytitle>qanda.defaultlabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">number</refmiscinfo>
<refmiscinfo class="other" otherclass="value">qanda</refmiscinfo>
<refmiscinfo class="other" otherclass="value">none</refmiscinfo>
</refmeta>
<refnamediv>
<refname>qanda.defaultlabel</refname>
<refpurpose>Sets the default for defaultlabel on QandASet.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="qanda.defaultlabel.frag">
<xsl:param name="qanda.defaultlabel">number</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If no <literal>defaultlabel</literal> attribute is specified on
a <tag>qandaset</tag>, this value is used. It is generally one of the legal
values for the defaultlabel attribute (<literal>none</literal>,
<literal>number</literal> or
<literal>qanda</literal>), or one of the additional stylesheet-specific values
(<literal>qnumber</literal> or <literal>qnumberanda</literal>).
The default value is 'number'.
</para>
<para>The values are rendered as follows:</para>
<variablelist>
<varlistentry><term><literal>qanda</literal></term>
<listitem>
<para><tag>question</tag>s are labeled "Q:" and
<tag>answer</tag>s are labeled "A:". </para>
</listitem>
</varlistentry>
<varlistentry><term><literal>number</literal></term>
<listitem>
<para>The questions are enumerated and the answers
are not labeled. </para>
</listitem>
</varlistentry>
<varlistentry><term><literal>qnumber</literal></term>
<listitem>
<para>The questions are labeled "Q:" followed by a number, and answers are not
labeled.
When sections are numbered, adding a label
to the number distinguishes the question numbers
from the section numbers.
This value is not allowed in the
<tag class="attribute">defaultlabel</tag> attribute
of a <tag>qandaset</tag> element.</para>
</listitem>
</varlistentry>
<varlistentry><term><literal>qnumberanda</literal></term>
<listitem>
<para>The questions are labeled "Q:" followed by a number, and
the answers are labeled "A:".
When sections are numbered, adding a label
to the number distinguishes the question numbers
from the section numbers.
This value is not allowed in the
<tag class="attribute">defaultlabel</tag> attribute
of a <tag>qandaset</tag> element.</para>
</listitem>
</varlistentry>
<varlistentry><term><literal>none</literal></term>
<listitem>
<para>No distinguishing label precedes Questions or Answers.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="qanda.inherit.numeration">
<refmeta>
<refentrytitle>qanda.inherit.numeration</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>qanda.inherit.numeration</refname>
<refpurpose>Does enumeration of QandASet components inherit the numeration of parent elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="qanda.inherit.numeration.frag">
<xsl:param name="qanda.inherit.numeration" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, numbered <tag>qandadiv</tag> elements and
<tag>question</tag> and <tag>answer</tag> inherit the enumeration of
the ancestors of the <tag>qandaset</tag>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="qanda.in.toc">
<refmeta>
<refentrytitle>qanda.in.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>qanda.in.toc</refname>
<refpurpose>Should qandaentry questions appear in
the document table of contents?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="qanda.in.toc.frag"><xsl:param name="qanda.in.toc" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If true (non-zero), then the generated table of contents
for a document will include <tag>qandaset</tag> titles,
<tag>qandadiv</tag> titles,
and <tag>question</tag> elements. The default value (zero) excludes
them from the TOC.
</para>
<para>This parameter does not affect any tables of contents
that may be generated inside a qandaset or qandadiv.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="qanda.nested.in.toc">
<refmeta>
<refentrytitle>qanda.nested.in.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>qanda.nested.in.toc</refname>
<refpurpose>Should nested answer/qandaentry instances appear in TOC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="qanda.nested.in.toc.frag">
<xsl:param name="qanda.nested.in.toc" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, instances of <tag>qandaentry</tag>
that are children of <tag>answer</tag> elements are shown in
the TOC.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="links"><title>Linking</title>
<refentry version="5.0" xml:id="target.database.document">
<refmeta>
<refentrytitle>target.database.document</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>target.database.document</refname>
<refpurpose>Name of master database file for resolving
olinks</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="target.database.document.frag">
<xsl:param name="target.database.document">olinkdb.xml</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
To resolve olinks between documents, the stylesheets use a master
database document that identifies the target datafiles for all the
documents within the scope of the olinks. This parameter value is the
URI of the master document to be read during processing to resolve
olinks. The default value is <filename>olinkdb.xml</filename>.</para>
<para>The data structure of the file is defined in the
<filename>targetdatabase.dtd</filename> DTD. The database file
provides the high level elements to record the identifiers, locations,
and relationships of documents. The cross reference data for
individual documents is generally pulled into the database using
system entity references or XIncludes. See also
<parameter>targets.filename</parameter>. </para> </refsection>
</refentry>
<refentry version="5.0" xml:id="targets.filename">
<refmeta>
<refentrytitle>targets.filename</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>targets.filename</refname>
<refpurpose>Name of cross reference targets data file</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="targets.filename.frag">
<xsl:param name="targets.filename">target.db</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
In order to resolve olinks efficiently, the stylesheets can
generate an external data file containing information about
all potential cross reference endpoints in a document.
This parameter lets you change the name of the generated
file from the default name <filename>target.db</filename>.
The name must agree with that used in the target database
used to resolve olinks during processing.
See also <parameter>target.database.document</parameter>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="olink.base.uri">
<refmeta>
<refentrytitle>olink.base.uri</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>olink.base.uri</refname>
<refpurpose>Base URI used in olink hrefs</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="olink.base.uri.frag">
<xsl:param name="olink.base.uri"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When cross reference data is collected for resolving olinks, it
may be necessary to prepend a base URI to each target's href. This
parameter lets you set that base URI when cross reference data is
collected. This feature is needed when you want to link to a document
that is processed without chunking. The output filename for such a
document is not known to the XSL stylesheet; the only target
information consists of fragment identifiers such as
<literal>#idref</literal>. To enable the resolution of olinks between
documents, you should pass the name of the HTML output file as the
value of this parameter. Then the hrefs recorded in the cross
reference data collection look like
<literal>outfile.html#idref</literal>, which can be reached as links
from other documents.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.local.olink.style">
<refmeta>
<refentrytitle>use.local.olink.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.local.olink.style</refname>
<refpurpose>Process olinks using xref style of current
document</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="use.local.olink.style.frag">
<xsl:param name="use.local.olink.style" select="0"></xsl:param> </programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When cross reference data is collected for use by olinks, the data for each potential target includes one field containing a completely assembled cross reference string, as if it were an xref generated in that document. Other fields record the separate title, number, and element name of each target. When an olink is formed to a target from another document, the olink resolves to that preassembled string by default. If the <parameter>use.local.olink.style</parameter> parameter is set to non-zero, then instead the cross
reference string is formed again from the target title, number, and
element name, using the stylesheet processing the targeting document.
Then olinks will match the xref style in the targeting document
rather than in the target document. If both documents are processed
with the same stylesheet, then the results will be the same.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="current.docid">
<refmeta>
<refentrytitle>current.docid</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>current.docid</refname>
<refpurpose>targetdoc identifier for the document being
processed</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="current.docid.frag">
<xsl:param name="current.docid"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When olinks between documents are resolved for HTML output, the stylesheet can compute the relative path between the current document and the target document. The stylesheet needs to know the <literal>targetdoc</literal> identifiers for both documents, as they appear in the <parameter>target.database.document</parameter> database file. This parameter passes to the stylesheet
the targetdoc identifier of the current document, since that
identifier does not appear in the document itself. </para>
<para>This parameter can also be used for print output. If an olink's <literal>targetdoc</literal> id differs from the <literal>current.docid</literal>, then the stylesheet can append the target document's title to the generated olink text. That identifies to the reader that the link is to a different document, not the current document. See also <parameter>olink.doctitle</parameter> to enable that feature.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="olink.doctitle">
<refmeta>
<refentrytitle>olink.doctitle</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
</refmeta>
<refnamediv>
<refname>olink.doctitle</refname>
<refpurpose>show the document title for external olinks?</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="olink.doctitle.frag">
<xsl:param name="olink.doctitle">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When olinks between documents are resolved, the generated text
may not make it clear that the reference is to another document.
It is possible for the stylesheets to append the other document's
title to external olinks. For this to happen, two parameters must
be set.</para>
<itemizedlist>
<listitem>
<para>This <parameter>olink.doctitle</parameter> parameter
should be set to either <literal>yes</literal> or <literal>maybe</literal>
to enable this feature.
</para>
</listitem>
<listitem>
<para>And you should also set the <parameter>current.docid</parameter>
parameter to the document id for the document currently
being processed for output.
</para>
</listitem>
</itemizedlist>
<para>
Then if an olink's <literal>targetdoc</literal> id differs from
the <literal>current.docid</literal> value, the stylesheet knows
that it is a reference to another document and can
append the target document's
title to the generated olink text. </para>
<para>The text for the target document's title is copied from the
olink database from the <tag>ttl</tag> element
of the top-level <tag>div</tag> for that document.
If that <tag>ttl</tag> element is missing or empty,
no title is output.
</para>
<para>The supported values for <parameter>olink.doctitle</parameter> are:
</para>
<variablelist>
<varlistentry>
<term><literal>yes</literal></term>
<listitem>
<para>
Always insert the title to the target document if it is not
the current document.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>no</literal></term>
<listitem>
<para>
Never insert the title to the target document, even if requested
in an <tag class="attribute">xrefstyle</tag> attribute.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>maybe</literal></term>
<listitem>
<para>
Only insert the title to the target document, if requested
in an <tag class="attribute">xrefstyle</tag> attribute.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>An <tag class="attribute">xrefstyle</tag> attribute
may override the global setting for individual olinks.
The following values are supported in an
<tag class="attribute">xrefstyle</tag>
attribute using the <literal>select:</literal> syntax:
</para>
<variablelist>
<varlistentry>
<term><literal>docname</literal></term>
<listitem>
<para>
Insert the target document name for this olink using the
<literal>docname</literal> gentext template, but only
if the value of <parameter>olink.doctitle</parameter>
is not <literal>no</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>docnamelong</literal></term>
<listitem>
<para>
Insert the target document name for this olink using the
<literal>docnamelong</literal> gentext template, but only
if the value of <parameter>olink.doctitle</parameter>
is not <literal>no</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>nodocname</literal></term>
<listitem>
<para>
Omit the target document name even if
the value of <parameter>olink.doctitle</parameter>
is <literal>yes</literal>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>Another way of inserting the target document name
for a single olink is to employ an
<tag class="attribute">xrefstyle</tag>
attribute using the <literal>template:</literal> syntax.
The <literal>%o</literal> placeholder (the letter o, not zero)
in such a template
will be filled in with the target document's title when it is processed.
This will occur regardless of
the value of <parameter>olink.doctitle</parameter>.
</para>
<para>Note that prior to version 1.66 of the XSL stylesheets,
the allowed values for this parameter were 0 and 1. Those
values are still supported and mapped to 'no' and 'yes', respectively.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="activate.external.olinks">
<refmeta>
<refentrytitle>activate.external.olinks</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>activate.external.olinks</refname>
<refpurpose>Make external olinks into active links</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="activate.external.olinks.frag">
<xsl:param name="activate.external.olinks" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>activate.external.olinks</parameter> is nonzero
(the default), then any olinks that reference another document
become active links that can be clicked on to follow the link.
If the parameter is set to zero, then external olinks
will have the appropriate link text generated, but the link is
not made active. Olinks to destinations in
the current document remain active.</para>
<para>To make an external olink active for HTML
outputs, the link text is wrapped in an <tag>a</tag>
element with an <tag>href</tag> attribute. To
make an external olink active for FO outputs, the link text is
wrapped in an <tag>fo:basic-link</tag> element with an
<tag>external-destination</tag> attribute.</para>
<para>This parameter is useful when you need external olinks
to resolve but not be clickable. For example, if documents
in a collection are available independently of each other,
then having active links between them could lead to
unresolved links when a given target document is missing.</para>
<para>The epub stylesheets set this parameter to zero by default
because there is no standard linking mechanism between Epub documents.</para>
<para>If external links are made inactive, you should
consider setting the
stylesheet parameter <parameter>olink.doctitle</parameter>
to <literal>yes</literal>. That will append the external document's
title to the link text, making it easier for the user to
locate the other document.</para>
<para>An olink is considered external when the
<parameter>current.docid</parameter> stylesheet parameter
is set to some value, and the olink's <tag>targetdoc</tag>
attribute has a different value. If the two values
match, then the link is considered internal. If the
<parameter>current.docid</parameter> parameter is blank, or
the <tag>olink</tag> element does not have a <tag>targetdoc</tag> attribute,
then the link is considered to be internal and will become
an active link.</para>
<para>See also <parameter>olink.doctitle</parameter>,
<parameter>prefer.internal.olink</parameter>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="olink.debug">
<refmeta>
<refentrytitle>olink.debug</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>olink.debug</refname>
<refpurpose>Turn on debugging messages for olinks</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="olink.debug.frag">
<xsl:param name="olink.debug" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, then each olink will generate several
messages about how it is being resolved during processing.
This is useful when an olink does not resolve properly
and the standard error messages are not sufficient to
find the problem.
</para>
<para>You may need to read through the olink XSL templates
to understand the context for some of the debug messages.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="olink.properties">
<refmeta>
<refentrytitle>olink.properties</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">attribute set</refmiscinfo>
</refmeta>
<refnamediv>
<refname>olink.properties</refname>
<refpurpose>Properties associated with the cross-reference
text of an olink.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="olink.properties.frag">
<xsl:attribute-set name="olink.properties">
<xsl:attribute name="show-destination">replace</xsl:attribute>
</xsl:attribute-set>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This <literal>attribute set</literal> is applied to the
<literal>fo:basic-link</literal> element of an olink. It is not applied to the
optional page number or optional title of the external
document.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="olink.lang.fallback.sequence">
<refmeta>
<refentrytitle>olink.lang.fallback.sequence</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>olink.lang.fallback.sequence</refname>
<refpurpose>look up translated documents if olink not found?</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="olink.lang.fallback.sequence.frag">
<xsl:param name="olink.lang.fallback.sequence"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter defines a list of lang values
to search among to resolve olinks.
</para>
<para>Normally an olink tries to resolve to a document in the same
language as the olink itself. The language of an olink
is determined by its nearest ancestor element with a
<tag class="attribute">lang</tag> attribute, otherwise the
value of the <parameter>l10n.gentext.default.lang</parameter>
parameter.
</para>
<para>An olink database can contain target data for the same
document in multiple languages. Each set of data has the
same value for the <tag>targetdoc</tag> attribute in
the <tag>document</tag> element in the database, but with a
different <tag>lang</tag> attribute value.
</para>
<para>When an olink is being resolved, the target is first
sought in the document with the same language as the olink.
If no match is found there, then this parameter is consulted
for additional languages to try.</para>
<para>The <parameter>olink.lang.fallback.sequence</parameter>
must be a whitespace separated list of lang values to
try. The first one with a match in the olink database is used.
The default value is empty.</para>
<para>For example, a document might be written in German
and contain an olink with
<literal>targetdoc="adminguide"</literal>.
When the document is processed, the processor
first looks for a target dataset in the
olink database starting with:</para>
<literallayout><literal><document targetdoc="adminguide" lang="de"></literal>.
</literallayout>
<para>If there is no such element, then the
<parameter>olink.lang.fallback.sequence</parameter>
parameter is consulted.
If its value is, for example, <quote>fr en</quote>, then the processor next
looks for <literal>targetdoc="adminguide" lang="fr"</literal>, and
then for <literal>targetdoc="adminguide" lang="en"</literal>.
If there is still no match, it looks for
<literal>targetdoc="adminguide"</literal> with no
lang attribute.
</para>
<para>This parameter is useful when a set of documents is only
partially translated, or is in the process of being translated.
If a target of an olink has not yet been translated, then this
parameter permits the processor to look for the document in
other languages. This assumes the reader would rather have
a link to a document in a different language than to have
a broken link.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="insert.olink.page.number">
<refmeta>
<refentrytitle>insert.olink.page.number</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
</refmeta>
<refnamediv>
<refname>insert.olink.page.number</refname>
<refpurpose>Turns page numbers in olinks on and off</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="insert.olink.page.number.frag">
<xsl:param name="insert.olink.page.number">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter determines if
cross references made between documents with
<tag>olink</tag> will
include page number citations.
In most cases this is only applicable to references in printed output.
</para>
<para>The parameter has three possible values.
</para>
<variablelist>
<varlistentry>
<term>no</term>
<listitem><para>No page number references will be generated for olinks.
</para></listitem>
</varlistentry>
<varlistentry>
<term>yes</term>
<listitem><para>Page number references will be generated
for all <tag>olink</tag> references.
The style of page reference may be changed
if an <tag class="attribute">xrefstyle</tag>
attribute is used.
</para></listitem>
</varlistentry>
<varlistentry>
<term>maybe</term>
<listitem><para>Page number references will not be generated
for an <tag>olink</tag> element unless
it has an
<tag class="attribute">xrefstyle</tag>
attribute whose value specifies a page reference.
</para></listitem>
</varlistentry>
</variablelist>
<para>Olinks that point to targets within the same document
are treated as <tag>xref</tag>s, and controlled by
the <parameter>insert.xref.page.number</parameter> parameter.
</para>
<para>Page number references for olinks to
external documents can only be inserted if the
information exists in the olink database.
This means each olink target element
(<tag>div</tag> or <tag>obj</tag>)
must have a <tag class="attribute">page</tag> attribute
whose value is its page number in the target document.
The XSL stylesheets are not able to extract that information
during processing because pages have not yet been created in
XSLT transformation. Only the XSL-FO processor knows what
page each element is placed on.
Therefore some postprocessing must take place to populate
page numbers in the olink database.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="insert.olink.pdf.frag">
<refmeta>
<refentrytitle>insert.olink.pdf.frag</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>insert.olink.pdf.frag</refname>
<refpurpose>Add fragment identifiers for links into PDF files</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="insert.olink.pdf.frag.frag">
<xsl:param name="insert.olink.pdf.frag" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter determines whether
the cross reference URIs to PDF documents made with
<tag>olink</tag> will
include fragment identifiers.
</para>
<para>When forming a URI to link to a PDF document,
a fragment identifier (typically a '#' followed by an
id value) appended to the PDF filename can be used by
the PDF viewer to open
the PDF file to a location within the document instead of
the first page.
However, not all PDF files have id
values embedded in them, and not all PDF viewers can
handle fragment identifiers.
</para>
<para>If <parameter>insert.olink.pdf.frag</parameter> is set
to a non-zero value, then any olink targeting a
PDF file will have the fragment identifier appended to the URI.
The URI is formed by concatenating the value of the
<parameter>olink.base.uri</parameter> parameter, the
value of the <tag class="attribute">baseuri</tag>
attribute from the <tag class="element">document</tag>
element in the olink database with the matching
<tag class="attribute">targetdoc</tag> value,
and the value of the <tag class="attribute">href</tag>
attribute for the targeted element in the olink database.
The <tag class="attribute">href</tag> attribute
contains the fragment identifier.
</para>
<para>If <parameter>insert.olink.pdf.frag</parameter> is set
to zero (the default value), then
the <tag class="attribute">href</tag> attribute
from the olink database
is not appended to PDF olinks, so the fragment identifier is left off.
A PDF olink is any olink for which the
<tag class="attribute">baseuri</tag> attribute
from the matching <tag class="element">document</tag>
element in the olink database ends with '.pdf'.
Any other olinks will still have the fragment identifier added.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="prefer.internal.olink">
<refmeta>
<refentrytitle>prefer.internal.olink</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>prefer.internal.olink</refname>
<refpurpose>Prefer a local olink reference to an external reference</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="prefer.internal.olink.frag">
<xsl:param name="prefer.internal.olink" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you are re-using XML content modules in multiple documents,
you may want to redirect some of your olinks. This parameter
permits you to redirect an olink to the current document.
</para>
<para>For example: you are writing documentation for a product,
which includes 3 manuals: a little installation
booklet (booklet.xml), a user
guide (user.xml), and a reference manual (reference.xml).
All 3 documents begin with the same introduction section (intro.xml) that
contains a reference to the customization section (custom.xml) which is
included in both user.xml and reference.xml documents.
</para>
<para>How do you write the link to custom.xml in intro.xml
so that it is interpreted correctly in all 3 documents?</para>
<itemizedlist>
<listitem><para>If you use xref, it will fail in booklet.xml.</para>
</listitem>
<listitem><para>If you use olink (pointing to reference.xml),
the reference in user.xml
will point to the customization section of the reference manual, while it is
actually available in user.xml.</para>
</listitem>
</itemizedlist>
<para>If you set the <parameter>prefer.internal.olink</parameter>
parameter to a non-zero value, then the processor will
first look in the olink database
for the olink's <tag>targetptr</tag> attribute value
in document matching the <parameter>current.docid</parameter>
parameter value. If it isn't found there, then
it tries the document in the database
with the <tag>targetdoc</tag>
value that matches the olink's <tag>targetdoc</tag>
attribute.
</para>
<para>This feature permits an olink reference to resolve to
the current document if there is an element
with an id matching the olink's <tag>targetptr</tag>
value. The current document's olink data must be
included in the target database for this to work.</para>
<caution>
<para>There is a potential for incorrect links if
the same <tag>id</tag> attribute value is used for different
content in different documents.
Some of your olinks may be redirected to the current document
when they shouldn't be. It is not possible to control
individual olink instances.</para>
</caution>
</refsection>
</refentry>
<refentry version="5.0" xml:id="link.mailto.url">
<refmeta>
<refentrytitle>link.mailto.url</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>link.mailto.url</refname>
<refpurpose>Mailto URL for the LINK REL=made HTML HEAD element</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="link.mailto.url.frag">
<xsl:param name="link.mailto.url"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If not the empty string, this address will be used for the
rel=made <literal>link</literal> element in the html <literal>head</literal>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="ulink.target">
<refmeta>
<refentrytitle>ulink.target</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ulink.target</refname>
<refpurpose>The HTML anchor target for ULinks</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ulink.target.frag">
<xsl:param name="ulink.target">_top</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>ulink.target</parameter> is non-zero, its value will
be used for the <literal>target</literal> attribute
on anchors generated for <tag>ulink</tag>s.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="xrefs"><title>Cross References</title>
<refentry version="5.0" xml:id="collect.xref.targets">
<refmeta>
<refentrytitle>collect.xref.targets</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">only</refmiscinfo>
</refmeta>
<refnamediv>
<refname>collect.xref.targets</refname>
<refpurpose>Controls whether cross reference data is
collected</refpurpose>
</refnamediv>
<refsynopsisdiv> <programlisting xml:id="collect.xref.targets.frag">
<xsl:param name="collect.xref.targets">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
In order to resolve olinks efficiently, the stylesheets can
generate an external data file containing information about
all potential cross reference endpoints in a document.
This parameter determines whether the collection process is run when the document is processed by the stylesheet. The default value is <literal>no</literal>, which means the data file is not generated during processing. The other choices are <literal>yes</literal>, which means the data file is created and the document is processed for output, and <literal>only</literal>, which means the data file is created but the document is not processed for output.
See also <parameter>targets.filename</parameter>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="insert.xref.page.number">
<refmeta>
<refentrytitle>insert.xref.page.number</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
</refmeta>
<refnamediv>
<refname>insert.xref.page.number</refname>
<refpurpose>Turns page numbers in xrefs on and off</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="insert.xref.page.number.frag">
<xsl:param name="insert.xref.page.number">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter determines if
cross references (<tag>xref</tag>s) in
printed output will
include page number citations.
It has three possible values.
</para>
<variablelist>
<varlistentry>
<term>no</term>
<listitem><para>No page number references will be generated.
</para></listitem>
</varlistentry>
<varlistentry>
<term>yes</term>
<listitem><para>Page number references will be generated
for all <tag>xref</tag> elements.
The style of page reference may be changed
if an <tag class="attribute">xrefstyle</tag>
attribute is used.
</para></listitem>
</varlistentry>
<varlistentry>
<term>maybe</term>
<listitem><para>Page number references will not be generated
for an <tag>xref</tag> element unless
it has an
<tag class="attribute">xrefstyle</tag>
attribute whose value specifies a page reference.
</para></listitem>
</varlistentry>
</variablelist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="insert.xref.page.number.para">
<refmeta>
<refentrytitle>insert.xref.page.number.para</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">maybe</refmiscinfo>
</refmeta>
<refnamediv>
<refname>insert.xref.page.number.para</refname>
<refpurpose>Turns page numbers in xrefs to paragraphs on and off</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="insert.xref.page.number.para.frag">
<xsl:param name="insert.xref.page.number.para">yes</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter determines if
cross references (<tag>xref</tag>s) to paragraphs in
printed output will include page number citations.
</para>
<para>Historically, cross references to paragraphs
included page number citations unconditionally, regardless
of the <parameter>insert.xref.page.number</parameter>
value.</para>
<variablelist>
<varlistentry>
<term>yes</term>
<listitem><para>Page number references will be generated
for paragraphs.</para></listitem>
</varlistentry>
<varlistentry>
<term>maybe</term>
<listitem><para>Whether page number references are generated
for an <tag>xref</tag> element referring to a paragraph will
be controlled by the <parameter>insert.xref.page.number</parameter>
rules.</para></listitem>
</varlistentry>
</variablelist>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.role.as.xrefstyle">
<refmeta>
<refentrytitle>use.role.as.xrefstyle</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.role.as.xrefstyle</refname>
<refpurpose>Use <tag class="attribute">role</tag> attribute for
<tag class="attribute">xrefstyle</tag> on <tag>xref</tag>?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.role.as.xrefstyle.frag">
<xsl:param name="use.role.as.xrefstyle" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>In DocBook documents that conform to a schema older than V4.3, this parameter allows
<tag class="attribute">role</tag> to serve the purpose of specifying the cross reference style.</para>
<para>If non-zero, the <tag class="attribute">role</tag> attribute on
<tag>xref</tag> will be used to select the cross reference style.
In DocBook V4.3, the <tag class="attribute">xrefstyle</tag> attribute was added for this purpose.
If the <tag class="attribute">xrefstyle</tag> attribute is present,
<tag class="attribute">role</tag> will be ignored, regardless of the setting
of this parameter.</para>
</refsection>
<refsection><info><title>Example</title></info>
<para>The following small stylesheet shows how to configure the
stylesheets to make use of the cross reference style:</para>
<programlisting><?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:import href="../xsl/html/docbook.xsl"/>
<xsl:output method="html"/>
<xsl:param name="local.l10n.xml" select="document('')"/>
<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
<l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="en">
<l:context name="xref">
<l:template name="chapter" style="title" text="Chapter %n, %t"/>
<l:template name="chapter" text="Chapter %n"/>
</l:context>
</l:l10n>
</l:i18n>
</xsl:stylesheet></programlisting>
<para>With this stylesheet, the cross references in the following document:</para>
<programlisting><?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<book id="book"><title>Book</title>
<preface>
<title>Preface</title>
<para>Normal: <xref linkend="ch1"/>.</para>
<para>Title: <xref xrefstyle="title" linkend="ch1"/>.</para>
</preface>
<chapter id="ch1">
<title>First Chapter</title>
<para>Irrelevant.</para>
</chapter>
</book></programlisting>
<para>will appear as:</para>
<informalexample>
<para>Normal: Chapter 1.</para>
<para>Title: Chapter 1, <emphasis>First Chapter</emphasis>.</para>
</informalexample>
</refsection>
</refentry>
<refentry version="5.0" xml:id="xref.with.number.and.title">
<refmeta>
<refentrytitle>xref.with.number.and.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>xref.with.number.and.title</refname>
<refpurpose>Use number and title in cross references</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="xref.with.number.and.title.frag">
<xsl:param name="xref.with.number.and.title" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>A cross reference may include the number (for example, the number of
an example or figure) and the <tag>title</tag> which is a required child of some
targets. This parameter inserts both the relevant number as well as
the title into the link. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="xref.label-page.separator">
<refmeta>
<refentrytitle>xref.label-page.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>xref.label-page.separator</refname>
<refpurpose>Punctuation or space separating label from page number in xref</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="xref.label-page.separator.frag"><xsl:param name="xref.label-page.separator"><xsl:text> </xsl:text></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
This parameter allows you to control the punctuation of certain
types of generated cross reference text.
When cross reference text is generated for an
<tag class="element">xref</tag> or
<tag class="element">olink</tag> element
using an <tag class="attribute">xrefstyle</tag> attribute
that makes use of the <literal>select:</literal> feature,
and the selected components include both label and page
but no title,
then the value of this parameter is inserted between
label and page number in the output.
If a title is included, then other separators are used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="xref.label-title.separator">
<refmeta>
<refentrytitle>xref.label-title.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>xref.label-title.separator</refname>
<refpurpose>Punctuation or space separating label from title in xref</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="xref.label-title.separator.frag"><xsl:param name="xref.label-title.separator">: </xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
This parameter allows you to control the punctuation of certain
types of generated cross reference text.
When cross reference text is generated for an
<tag class="element">xref</tag> or
<tag class="element">olink</tag> element
using an <tag class="attribute">xrefstyle</tag> attribute
that makes use of the <literal>select:</literal> feature,
and the selected components include both label and title,
then the value of this parameter is inserted between
label and title in the output.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="xref.title-page.separator">
<refmeta>
<refentrytitle>xref.title-page.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>xref.title-page.separator</refname>
<refpurpose>Punctuation or space separating title from page number in xref</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="xref.title-page.separator.frag"><xsl:param name="xref.title-page.separator"><xsl:text> </xsl:text></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
This parameter allows you to control the punctuation of certain
types of generated cross reference text.
When cross reference text is generated for an
<tag class="element">xref</tag> or
<tag class="element">olink</tag> element
using an <tag class="attribute">xrefstyle</tag> attribute
that makes use of the <literal>select:</literal> feature,
and the selected components include both title and page number,
then the value of this parameter is inserted between
title and page number in the output.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="lists"><title>Lists</title>
<refentry version="5.0" xml:id="segmentedlist.as.table">
<refmeta>
<refentrytitle>segmentedlist.as.table</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>segmentedlist.as.table</refname>
<refpurpose>Format segmented lists as tables?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="segmentedlist.as.table.frag">
<xsl:param name="segmentedlist.as.table" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, <tag>segmentedlist</tag>s will be formatted as
tables.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="variablelist.as.table">
<refmeta>
<refentrytitle>variablelist.as.table</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>variablelist.as.table</refname>
<refpurpose>Format <tag>variablelist</tag>s as tables?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="variablelist.as.table.frag">
<xsl:param name="variablelist.as.table" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, <tag>variablelist</tag>s will be formatted as
tables. A processing instruction exists to specify a particular width for the
column containing the <tag>term</tag>s:
<tag class="xmlpi">dbhtml term-width=".25in"</tag></para>
<para>You can override this setting with a processing instruction as the
child of <tag>variablelist</tag>: <tag class="xmlpi">dbhtml
list-presentation="table"</tag> or <tag class="xmlpi">dbhtml
list-presentation="list"</tag>.</para>
<para>This parameter only applies to the HTML transformations. In the
FO case, proper list markup is robust enough to handle the formatting.
But see also <parameter>variablelist.as.blocks</parameter>.</para>
<programlisting> <variablelist>
<?dbhtml list-presentation="table"?>
<?dbhtml term-width="1.5in"?>
<?dbfo list-presentation="list"?>
<?dbfo term-width="1in"?>
<varlistentry>
<term>list</term>
<listitem>
<para>
Formatted as a table even if variablelist.as.table is set to 0.
</para>
</listitem>
</varlistentry>
</variablelist></programlisting>
</refsection>
</refentry>
<refentry version="5.0" xml:id="variablelist.term.separator">
<refmeta>
<refentrytitle>variablelist.term.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>variablelist.term.separator</refname>
<refpurpose>Text to separate <tag>term</tag>s within a multi-term
<tag>varlistentry</tag></refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="variablelist.term.separator.frag">
<xsl:param name="variablelist.term.separator">, </xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When a <tag>varlistentry</tag> contains multiple <tag>term</tag>
elements, the string specified in the value of the
<parameter>variablelist.term.separator</parameter> parameter is placed
after each <tag>term</tag> except the last.</para>
<note>
<para>To generate a line break between multiple <tag>term</tag>s in
a <tag>varlistentry</tag>, set a non-zero value for the
<parameter>variablelist.term.break.after</parameter> parameter. If
you do so, you may also want to set the value of the
<parameter>variablelist.term.separator</parameter> parameter to an
empty string (to suppress rendering of the default comma and space
after each <tag>term</tag>).</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="variablelist.term.break.after">
<refmeta>
<refentrytitle>variablelist.term.break.after</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>variablelist.term.break.after</refname>
<refpurpose>Generate line break after each <tag>term</tag> within a
multi-term <tag>varlistentry</tag>?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="variablelist.term.break.after.frag">
<xsl:param name="variablelist.term.break.after">0</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set a non-zero value for the
<parameter>variablelist.term.break.after</parameter> parameter to
generate a line break between <tag>term</tag>s in a
multi-term <tag>varlistentry</tag>.</para>
<note>
<para>If you set a non-zero value for
<parameter>variablelist.term.break.after</parameter>, you may also
want to set the value of the
<parameter>variablelist.term.separator</parameter> parameter to an
empty string (to suppress rendering of the default comma and space
after each <tag>term</tag>).</para>
</note>
</refsection>
</refentry>
</reference>
<reference xml:id="biblio"><title>Bibliography</title>
<refentry version="5.0" xml:id="bibliography.style">
<refmeta>
<refentrytitle>bibliography.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">normal</refmiscinfo>
<refmiscinfo class="other" otherclass="value">iso690</refmiscinfo>
</refmeta>
<refnamediv>
<refname>bibliography.style</refname>
<refpurpose>Style used for formatting of biblioentries.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="bibliography.style.frag">
<xsl:param name="bibliography.style">normal</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Currently only <literal>normal</literal> and
<literal>iso690</literal> styles are supported.</para>
<para>In order to use ISO690 style to the full extent you might need
to use additional markup described on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://wiki.docbook.org/topic/ISO690Bibliography">the
following WiKi page</link>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="biblioentry.item.separator">
<refmeta>
<refentrytitle>biblioentry.item.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>biblioentry.item.separator</refname>
<refpurpose>Text to separate bibliography entries</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="biblioentry.item.separator.frag"><xsl:param name="biblioentry.item.separator">. </xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Text to separate bibliography entries
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="bibliography.collection">
<refmeta>
<refentrytitle>bibliography.collection</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>bibliography.collection</refname>
<refpurpose>Name of the bibliography collection file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="bibliography.collection.frag">
<xsl:param name="bibliography.collection">http://cdn.docbook.org/release/xsl/bibliography/bibliography.xml</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Maintaining bibliography entries across a set of documents is tedious, time
consuming, and error prone. It makes much more sense, usually, to store all of
the bibliography entries in a single place and simply <quote>extract</quote>
the ones you need in each document.</para>
<para>That's the purpose of the
<parameter>bibliography.collection</parameter> parameter. To setup a global
bibliography <quote>database</quote>, follow these steps:</para>
<para>First, create a stand-alone bibliography document that contains all of
the documents that you wish to reference. Make sure that each bibliography
entry (whether you use <tag>biblioentry</tag> or <tag>bibliomixed</tag>)
has an ID.</para>
<para>My global bibliography, <filename>~/bibliography.xml</filename> begins
like this:</para>
<informalexample>
<programlisting><!DOCTYPE bibliography
PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<bibliography><title>References</title>
<bibliomixed id="xml-rec"><abbrev>XML 1.0</abbrev>Tim Bray,
Jean Paoli, C. M. Sperberg-McQueen, and Eve Maler, editors.
<citetitle><ulink url="http://www.w3.org/TR/REC-xml">Extensible Markup
Language (XML) 1.0 Second Edition</ulink></citetitle>.
World Wide Web Consortium, 2000.
</bibliomixed>
<bibliomixed id="xml-names"><abbrev>Namespaces</abbrev>Tim Bray,
Dave Hollander,
and Andrew Layman, editors.
<citetitle><ulink url="http://www.w3.org/TR/REC-xml-names/">Namespaces in
XML</ulink></citetitle>.
World Wide Web Consortium, 1999.
</bibliomixed>
<!-- ... -->
</bibliography>
</programlisting>
</informalexample>
<para>When you create a bibliography in your document, simply
provide <emphasis>empty</emphasis> <tag>bibliomixed</tag>
entries for each document that you wish to cite. Make sure that these
elements have the same ID as the corresponding <quote>real</quote>
entry in your global bibliography.</para>
<para>For example:</para>
<informalexample>
<programlisting><bibliography><title>Bibliography</title>
<bibliomixed id="xml-rec"/>
<bibliomixed id="xml-names"/>
<bibliomixed id="DKnuth86">Donald E. Knuth. <citetitle>Computers and
Typesetting: Volume B, TeX: The Program</citetitle>. Addison-Wesley,
1986. ISBN 0-201-13437-3.
</bibliomixed>
<bibliomixed id="relaxng"/>
</bibliography></programlisting>
</informalexample>
<para>Note that it's perfectly acceptable to mix entries from your
global bibliography with <quote>normal</quote> entries. You can use
<tag>xref</tag> or other elements to cross-reference your
bibliography entries in exactly the same way you do now.</para>
<para>Finally, when you are ready to format your document, simply set the
<parameter>bibliography.collection</parameter> parameter (in either a
customization layer or directly through your processor's interface) to
point to your global bibliography.</para>
<para>A relative path in the parameter is interpreted in one
of two ways:</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>If your document contains no links to empty bibliographic elements,
then the path is relative to the file containing
the first <tag>bibliomixed</tag> element in the document.</para>
</listitem>
<listitem>
<para>If your document does contain links to empty bibliographic elements,
then the path is relative to the file containing
the first such link element in the document.</para>
</listitem>
</orderedlist>
<para>Once the collection file is opened by the first instance described
above, it stays open for the current document
and the relative path is not reinterpreted again.</para>
<para>The stylesheets will format the bibliography in your document as if
all of the entries referenced appeared there literally.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="bibliography.numbered">
<refmeta>
<refentrytitle>bibliography.numbered</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>bibliography.numbered</refname>
<refpurpose>Should bibliography entries be numbered?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="bibliography.numbered.frag">
<xsl:param name="bibliography.numbered" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero bibliography entries will be numbered</para>
</refsection>
</refentry>
</reference>
<reference xml:id="glossary"><title>Glossary</title>
<refentry version="5.0" xml:id="glossterm.auto.link">
<refmeta>
<refentrytitle>glossterm.auto.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>glossterm.auto.link</refname>
<refpurpose>Generate links from glossterm to glossentry automatically?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="glossterm.auto.link.frag">
<xsl:param name="glossterm.auto.link" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, links from inline <tag>glossterm</tag>s to the corresponding
<tag>glossentry</tag> elements in a <tag>glossary</tag> or <tag>glosslist</tag>
will be automatically generated. This is useful when your glossterms are consistent
and you don't want to add links manually.</para>
<para>The automatic link generation feature is not used on <tag>glossterm</tag> elements
that have a <tag class="attribute">linkend</tag> attribute.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="firstterm.only.link">
<refmeta>
<refentrytitle>firstterm.only.link</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>firstterm.only.link</refname>
<refpurpose>Does automatic glossterm linking only apply to firstterms?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="firstterm.only.link.frag">
<xsl:param name="firstterm.only.link" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, only <tag>firstterm</tag>s will be automatically linked
to the glossary. If glossary linking is not enabled, this parameter
has no effect.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="glossary.collection">
<refmeta>
<refentrytitle>glossary.collection</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>glossary.collection</refname>
<refpurpose>Name of the glossary collection file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="glossary.collection.frag">
<xsl:param name="glossary.collection"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Glossaries maintained independently across a set of documents
are likely to become inconsistent unless considerable effort is
expended to keep them in sync. It makes much more sense, usually, to
store all of the glossary entries in a single place and simply
<quote>extract</quote> the ones you need in each document.</para>
<para>That's the purpose of the
<parameter>glossary.collection</parameter> parameter. To setup a global
glossary <quote>database</quote>, follow these steps:</para>
<refsection><info><title>Setting Up the Glossary Database</title></info>
<para>First, create a stand-alone glossary document that contains all of
the entries that you wish to reference. Make sure that each glossary
entry has an ID.</para>
<para>Here's an example glossary:</para>
<informalexample>
<programlisting>
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glossary
PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<glossary>
<glossaryinfo>
<editor><firstname>Eric</firstname><surname>Raymond</surname></editor>
<title>Jargon File 4.2.3 (abridged)</title>
<releaseinfo>Just some test data</releaseinfo>
</glossaryinfo>
<glossdiv><title>0</title>
<glossentry>
<glossterm>0</glossterm>
<glossdef>
<para>Numeric zero, as opposed to the letter `O' (the 15th letter of
the English alphabet). In their unmodified forms they look a lot
alike, and various kluges invented to make them visually distinct have
compounded the confusion. If your zero is center-dotted and letter-O
is not, or if letter-O looks almost rectangular but zero looks more
like an American football stood on end (or the reverse), you're
probably looking at a modern character display (though the dotted zero
seems to have originated as an option on IBM 3270 controllers). If
your zero is slashed but letter-O is not, you're probably looking at
an old-style ASCII graphic set descended from the default typewheel on
the venerable ASR-33 Teletype (Scandinavians, for whom /O is a letter,
curse this arrangement). (Interestingly, the slashed zero long
predates computers; Florian Cajori's monumental "A History of
Mathematical Notations" notes that it was used in the twelfth and
thirteenth centuries.) If letter-O has a slash across it and the zero
does not, your display is tuned for a very old convention used at IBM
and a few other early mainframe makers (Scandinavians curse <emphasis>this</emphasis>
arrangement even more, because it means two of their letters collide).
Some Burroughs/Unisys equipment displays a zero with a <emphasis>reversed</emphasis>
slash. Old CDC computers rendered letter O as an unbroken oval and 0
as an oval broken at upper right and lower left. And yet another
convention common on early line printers left zero unornamented but
added a tail or hook to the letter-O so that it resembled an inverted
Q or cursive capital letter-O (this was endorsed by a draft ANSI
standard for how to draw ASCII characters, but the final standard
changed the distinguisher to a tick-mark in the upper-left corner).
Are we sufficiently confused yet?</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>1TBS</glossterm>
<glossdef>
<para role="accidence">
<phrase role="pronounce"></phrase>
<phrase role="partsofspeach">n</phrase>
</para>
<para>The "One True Brace Style"</para>
<glossseealso>indent style</glossseealso>
</glossdef>
</glossentry>
<!-- ... -->
</glossdiv>
<!-- ... -->
</glossary></programlisting>
</informalexample>
</refsection>
<refsection><info><title>Marking Up Glossary Terms</title></info>
<para>That takes care of the glossary database, now you have to get the entries
into your document. Unlike bibliography entries, which can be empty, creating
<quote>placeholder</quote> glossary entries would be very tedious. So instead,
support for <parameter>glossary.collection</parameter> relies on implicit linking.</para>
<para>In your source document, simply use <tag>firstterm</tag> and
<tag>glossterm</tag> to identify the terms you wish to have included
in the glossary. The stylesheets assume that you will either set the
<tag class="attribute">baseform</tag> attribute correctly, or that the
content of the element exactly matches a term in your glossary.</para>
<para>If you're using a <parameter>glossary.collection</parameter>, don't
make explicit links on the terms in your document.</para>
<para>So, in your document, you might write things like this:</para>
<informalexample>
<programlisting><para>This is dummy text, without any real meaning.
The point is simply to reference glossary terms like <glossterm>0</glossterm>
and the <firstterm baseform="1TBS">One True Brace Style (1TBS)</firstterm>.
The <glossterm>1TBS</glossterm>, as you can probably imagine, is a nearly
religious issue.</para></programlisting>
</informalexample>
<para>If you set the <parameter>firstterm.only.link</parameter> parameter,
only the terms marked with <tag>firstterm</tag> will be links.
Otherwise, all the terms will be linked.</para>
</refsection>
<refsection><info><title>Marking Up the Glossary</title></info>
<para>The glossary itself has to be identified for the stylesheets. For lack
of a better choice, the <tag class="attribute">role</tag> is used.
To identify the glossary as the target for automatic processing, set
the role to <quote><literal>auto</literal></quote>. The title of this
glossary (and any other information from the <tag>glossaryinfo</tag>
that's rendered by your stylesheet) will be displayed, but the entries will
come from the database.
</para>
<para>Unfortunately, the glossary can't be empty, so you must put in
at least one <tag>glossentry</tag>. The content of this entry
is irrelevant, it will not be rendered:</para>
<informalexample>
<programlisting><glossary role="auto">
<glossentry>
<glossterm>Irrelevant</glossterm>
<glossdef>
<para>If you can see this, the document was processed incorrectly. Use
the <parameter>glossary.collection</parameter> parameter.</para>
</glossdef>
</glossentry>
</glossary></programlisting>
</informalexample>
<para>What about glossary divisions? If your glossary database has glossary
divisions <emphasis>and</emphasis> your automatic glossary contains at least
one <tag>glossdiv</tag>, the automic glossary will have divisions.
If the <tag>glossdiv</tag> is missing from either location, no divisions
will be rendered.</para>
<para>Glossary entries (and divisions, if appropriate) in the glossary will
occur in precisely the order they occur in your database.</para>
</refsection>
<refsection><info><title>Formatting the Document</title></info>
<para>Finally, when you are ready to format your document, simply set the
<parameter>glossary.collection</parameter> parameter (in either a
customization layer or directly through your processor's interface) to
point to your global glossary.</para>
<para>A relative path in the parameter is interpreted in one
of two ways:</para>
<orderedlist numeration="loweralpha">
<listitem>
<para>If the parameter <literal>glossterm.auto.link</literal>
is set to zero, then the path is relative to the file containing
the empty <tag>glossary</tag> element in the document.</para>
</listitem>
<listitem>
<para>If the parameter <literal>glossterm.auto.link</literal>
is set to non-zero, then the path is relative to the file containing
the first inline <tag>glossterm</tag> or
<tag>firstterm</tag> in the document to be linked.</para>
</listitem>
</orderedlist>
<para>Once the collection file is opened by the first instance described
above, it stays open for the current document
and the relative path is not reinterpreted again.</para>
<para>The stylesheets will format the glossary in your document as if
all of the entries implicilty referenced appeared there literally.</para>
</refsection>
<refsection><info><title>Limitations</title></info>
<para>Glossary cross-references <emphasis>within the glossary</emphasis> are
not supported. For example, this <emphasis>will not</emphasis> work:</para>
<informalexample>
<programlisting><glossentry>
<glossterm>gloss-1</glossterm>
<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
<glossseealso>gloss-2</glossseealso>
</glossdef>
</glossentry></programlisting>
</informalexample>
<para>If you put glossary cross-references in your glossary that way,
you'll get the cryptic error: <computeroutput>Warning:
glossary.collection specified, but there are 0 automatic
glossaries</computeroutput>.</para>
<para>Instead, you must do two things:</para>
<orderedlist>
<listitem>
<para>Markup your glossary using <tag>glossseealso</tag>:</para>
<informalexample>
<programlisting><glossentry>
<glossterm>gloss-1</glossterm>
<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
<glossseealso>gloss-2</glossseealso>
</glossdef>
</glossentry></programlisting>
</informalexample>
</listitem>
<listitem>
<para>Make sure there is at least one <tag>glossterm</tag> reference to
<glossterm>gloss-2</glossterm> <emphasis>in your document</emphasis>. The
easiest way to do that is probably within a <tag>remark</tag> in your
automatic glossary:</para>
<informalexample>
<programlisting><glossary role="auto">
<remark>Make sure there's a reference to <glossterm>gloss-2</glossterm>.</remark>
<glossentry>
<glossterm>Irrelevant</glossterm>
<glossdef>
<para>If you can see this, the document was processed incorrectly. Use
the <parameter>glossary.collection</parameter> parameter.</para>
</glossdef>
</glossentry>
</glossary></programlisting>
</informalexample>
</listitem>
</orderedlist>
</refsection>
</refsection>
</refentry>
<refentry version="5.0" xml:id="glossary.sort">
<refmeta>
<refentrytitle>glossary.sort</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>glossary.sort</refname>
<refpurpose>Sort glossentry elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="glossary.sort.frag">
<xsl:param name="glossary.sort" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, then the glossentry elements within a
glossary, glossdiv, or glosslist are sorted on the glossterm, using
the current lang setting. If zero (the default), then
glossentry elements are not sorted and are presented
in document order.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="glossentry.show.acronym">
<refmeta>
<refentrytitle>glossentry.show.acronym</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">no</refmiscinfo>
<refmiscinfo class="other" otherclass="value">yes</refmiscinfo>
<refmiscinfo class="other" otherclass="value">primary</refmiscinfo>
</refmeta>
<refnamediv>
<refname>glossentry.show.acronym</refname>
<refpurpose>Display <tag>glossentry</tag> acronyms?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="glossentry.show.acronym.frag">
<xsl:param name="glossentry.show.acronym">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>A setting of <quote>yes</quote> means they should be displayed;
<quote>no</quote> means they shouldn't. If <quote>primary</quote> is used,
then they are shown as the primary text for the entry.</para>
<note>
<para>This setting controls both <tag>acronym</tag> and
<tag>abbrev</tag> elements in the <tag>glossentry</tag>.</para>
</note>
</refsection>
</refentry>
</reference>
<reference xml:id="misc"><title>Miscellaneous</title>
<refentry version="5.0" xml:id="formal.procedures">
<refmeta>
<refentrytitle>formal.procedures</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>formal.procedures</refname>
<refpurpose>Selects formal or informal procedures</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="formal.procedures.frag">
<xsl:param name="formal.procedures" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Formal procedures are numbered and always have a title.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="formal.title.placement">
<refmeta>
<refentrytitle>formal.title.placement</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">table</refmiscinfo>
</refmeta>
<refnamediv>
<refname>formal.title.placement</refname>
<refpurpose>Specifies where formal object titles should occur</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="formal.title.placement.frag">
<xsl:param name="formal.title.placement">
figure before
example before
equation before
table before
procedure before
task before
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies where formal object titles should occur. For each formal object
type (<tag>figure</tag>,
<tag>example</tag>,
<tag>equation</tag>,
<tag>table</tag>, and <tag>procedure</tag>)
you can specify either the keyword
<quote><literal>before</literal></quote> or
<quote><literal>after</literal></quote>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="runinhead.default.title.end.punct">
<refmeta>
<refentrytitle>runinhead.default.title.end.punct</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>runinhead.default.title.end.punct</refname>
<refpurpose>Default punctuation character on a run-in-head</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="runinhead.default.title.end.punct.frag"><xsl:param name="runinhead.default.title.end.punct">.</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, For a <tag>formalpara</tag>, use the specified
string as the separator between the title and following text. The period is the default value.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="runinhead.title.end.punct">
<refmeta>
<refentrytitle>runinhead.title.end.punct</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>runinhead.title.end.punct</refname>
<refpurpose>Characters that count as punctuation on a run-in-head</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="runinhead.title.end.punct.frag">
<xsl:param name="runinhead.title.end.punct">.!?:</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specify which characters are to be counted as punctuation. These
characters are checked for a match with the last character of the
title. If no match is found, the
<parameter>runinhead.default.title.end.punct</parameter> contents are
inserted. This is to avoid duplicated punctuation in the output.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="show.comments">
<refmeta>
<refentrytitle>show.comments</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>show.comments</refname>
<refpurpose>Display <tag>remark</tag> elements?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="show.comments.frag">
<xsl:param name="show.comments" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, comments will be displayed, otherwise they
are suppressed. Comments here refers to the <tag>remark</tag> element
(which was called <literal>comment</literal> prior to DocBook
4.0), not XML comments (<-- like this -->) which are
unavailable.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="show.revisionflag">
<refmeta>
<refentrytitle>show.revisionflag</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>show.revisionflag</refname>
<refpurpose>Enable decoration of elements that have a revisionflag</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="show.revisionflag.frag">
<xsl:param name="show.revisionflag" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>
If <parameter>show.revisionflag</parameter> is turned on, then the stylesheets
may produce additional markup designed to allow a CSS stylesheet to
highlight elements that have specific revisionflag settings.</para>
<para>The markup inserted will be usually be either a <span> or
<div> with an appropriate <literal>class</literal>
attribute. (The value of the class attribute will be the same as the
value of the revisionflag attribute). In some contexts, for example
tables, where extra markup would be structurally illegal, the class
attribute will be added to the appropriate container element.</para>
<para>In general, the stylesheets only test for revisionflag in contexts
where an importing stylesheet would have to redefine whole templates.
Most of the revisionflag processing is expected to be done by another
stylesheet, for example <filename>changebars.xsl</filename>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="shade.verbatim">
<refmeta>
<refentrytitle>shade.verbatim</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>shade.verbatim</refname>
<refpurpose>Should verbatim environments be shaded?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="shade.verbatim.frag"><xsl:param name="shade.verbatim" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>In the FO stylesheet, if this parameter is non-zero then the
<property>shade.verbatim.style</property> properties will be applied
to verbatim environments.</para>
<para>In the HTML stylesheet, this parameter is now deprecated. Use
CSS instead.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="shade.verbatim.style">
<refmeta>
<refentrytitle>shade.verbatim.style</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">attribute set</refmiscinfo>
</refmeta>
<refnamediv>
<refname>shade.verbatim.style</refname>
<refpurpose>Properties that specify the style of shaded verbatim listings</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="shade.verbatim.style.frag">
<xsl:attribute-set name="shade.verbatim.style">
<xsl:attribute name="border">0</xsl:attribute>
<xsl:attribute name="bgcolor">#E0E0E0</xsl:attribute>
</xsl:attribute-set>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Properties that specify the style of shaded verbatim listings. The
parameters specified (the border and background color) are added to
the styling of the xsl-fo output. A border might be specified as "thin
black solid" for example. See <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/2004/WD-xsl11-20041216/#border">xsl-fo</link></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="punct.honorific">
<refmeta>
<refentrytitle>punct.honorific</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>punct.honorific</refname>
<refpurpose>Punctuation after an honorific in a personal name.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="punct.honorific.frag">
<xsl:param name="punct.honorific">.</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the punctuation that should be added after an
honorific in a personal name.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="tex.math.in.alt">
<refmeta>
<refentrytitle>tex.math.in.alt</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">plain</refmiscinfo>
<refmiscinfo class="other" otherclass="value">latex</refmiscinfo>
</refmeta>
<refnamediv>
<refname>tex.math.in.alt</refname>
<refpurpose>TeX notation used for equations</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="tex.math.in.alt.frag">
<xsl:param name="tex.math.in.alt"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want type math directly in TeX notation in equations,
this parameter specifies notation used. Currently are supported two
values -- <literal>plain</literal> and <literal>latex</literal>. Empty
value means that you are not using TeX math at all.</para>
<para>Preferred way for including TeX alternative of math is inside of
<tag>textobject</tag> element. Eg.:</para>
<programlisting><inlineequation>
<inlinemediaobject>
<imageobject>
<imagedata fileref="eq1.gif"/>
</imageobject>
<textobject><phrase>E=mc squared</phrase></textobject>
<textobject role="tex"><phrase>E=mc^2</phrase></textobject>
</inlinemediaobject>
</inlineequation></programlisting>
<para>If you are using <tag>graphic</tag> element, you can
store TeX inside <tag>alt</tag> element:</para>
<programlisting><inlineequation>
<alt role="tex">a^2+b^2=c^2</alt>
<graphic fileref="a2b2c2.gif"/>
</inlineequation></programlisting>
<para>If you want use this feature, you should process your FO with
PassiveTeX, which only supports TeX math notation. When calling
stylsheet, don't forget to specify also
passivetex.extensions=1.</para>
<para>If you want equations in HTML, just process generated file
<filename>tex-math-equations.tex</filename> by TeX or LaTeX. Then run
dvi2bitmap program on result DVI file. You will get images for
equations in your document.</para>
<warning>
<para>This feature is useful for print/PDF output only if you
use the obsolete and now unsupported PassiveTeX XSL-FO
engine.</para>
</warning>
</refsection>
<refsection><info><title>Related Parameters</title></info>
<para><parameter>tex.math.delims</parameter>,
<parameter>passivetex.extensions</parameter>,
<parameter>tex.math.file</parameter></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="tex.math.file">
<refmeta>
<refentrytitle>tex.math.file</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>tex.math.file</refname>
<refpurpose>Name of temporary file for generating images from equations</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="tex.math.file.frag">
<xsl:param name="tex.math.file">tex-math-equations.tex</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Name of auxiliary file for TeX equations. This file can be
processed by dvi2bitmap to get bitmap versions of equations for HTML
output.</para>
</refsection>
<refsection><info><title>Related Parameters</title></info>
<para><parameter>tex.math.in.alt</parameter>,
<parameter>tex.math.delims</parameter>,
</para>
</refsection>
<refsection><info><title>More information</title></info>
<para>For how-to documentation on embedding TeX equations and
generating output from them, see
<link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="TexMath.html">DBTeXMath</link>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="tex.math.delims">
<refmeta>
<refentrytitle>tex.math.delims</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>tex.math.delims</refname>
<refpurpose>Should equations output for processing by TeX be
surrounded by math mode delimiters?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="tex.math.delims.frag">
<xsl:param name="tex.math.delims" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>For compatibility with DSSSL based DBTeXMath from Allin Cottrell
you should set this parameter to 0.</para>
<warning>
<para>This feature is useful for print/PDF output only if you
use the obsolete and now unsupported PassiveTeX XSL-FO
engine.</para>
</warning>
</refsection>
<refsection><info><title>Related Parameters</title></info>
<para><parameter>tex.math.in.alt</parameter>,
<parameter>passivetex.extensions</parameter></para>
</refsection>
<refsection><info><title>See Also</title></info>
<para>You can also use the <tag class="xmlpi">dbtex delims</tag> processing
instruction to control whether delimiters are output.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="pixels.per.inch">
<refmeta>
<refentrytitle>pixels.per.inch</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>pixels.per.inch</refname>
<refpurpose>How many pixels are there per inch?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="pixels.per.inch.frag">
<xsl:param name="pixels.per.inch">90</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When lengths are converted to pixels, this value is used to
determine the size of a pixel. The default value is taken from the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/2004/WD-xsl11-20041216/">XSL
Recommendation</link>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="points.per.em">
<refmeta>
<refentrytitle>points.per.em</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">number</refmiscinfo>
</refmeta>
<refnamediv>
<refname>points.per.em</refname>
<refpurpose>Specify the nominal size of an em-space in points</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="points.per.em.frag">
<xsl:param name="points.per.em">10</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The fixed value used for calculations based upon the size of a
character. The assumption made is that ten point font is in use. This
assumption may not be valid.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.svg">
<refmeta>
<refentrytitle>use.svg</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.svg</refname>
<refpurpose>Allow SVG in the result tree?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.svg.frag">
<xsl:param name="use.svg" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, SVG will be considered an acceptable image format. SVG
is passed through to the result tree, so correct rendering of the resulting
diagram depends on the formatter (FO processor or web browser) that is used
to process the output from the stylesheet.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="menuchoice.separator">
<refmeta>
<refentrytitle>menuchoice.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>menuchoice.separator</refname>
<refpurpose>Separator between items of a <tag>menuchoice</tag>
other than <tag>guimenuitem</tag> and
<tag>guisubmenu</tag></refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="menuchoice.separator.frag">
<xsl:param name="menuchoice.separator">+</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Separator used to connect items of a <tag>menuchoice</tag> other
than <tag>guimenuitem</tag> and <tag>guisubmenu</tag>. The latter
elements are linked with <parameter>menuchoice.menu.separator</parameter>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="menuchoice.menu.separator">
<refmeta>
<refentrytitle>menuchoice.menu.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>menuchoice.menu.separator</refname>
<refpurpose>Separator between items of a <tag>menuchoice</tag>
with <tag>guimenuitem</tag> or
<tag>guisubmenu</tag></refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="menuchoice.menu.separator.frag">
<xsl:param name="menuchoice.menu.separator"> → </xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Separator used to connect items of a <tag>menuchoice</tag> with
<tag>guimenuitem</tag> or <tag>guisubmenu</tag>. Other elements
are linked with <parameter>menuchoice.separator</parameter>.
</para>
<para>The default value is &#x2192;, which is the
&rarr; (right arrow) character entity.
The current FOP (0.20.5) requires setting the font-family
explicitly.
</para>
<para>The default value also includes spaces around the arrow,
which will allow a line to break. Replace the spaces with
&#xA0; (nonbreaking space) if you don't want those
spaces to break.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="default.float.class">
<refmeta>
<refentrytitle>default.float.class</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>default.float.class</refname>
<refpurpose>Specifies the default float class</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="default.float.class.frag">
<xsl:param name="default.float.class">
<xsl:choose>
<xsl:when test="contains($stylesheet.result.type,'html')">left</xsl:when>
<xsl:otherwise>before</xsl:otherwise>
</xsl:choose>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Selects the direction in which a float should be placed. for
xsl-fo this is before, for html it is left. For Western texts, the
before direction is the top of the page.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="footnote.number.format">
<refmeta>
<refentrytitle>footnote.number.format</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>footnote.number.format</refname>
<refpurpose>Identifies the format used for footnote numbers</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="footnote.number.format.frag">
<xsl:param name="footnote.number.format">1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>footnote.number.format</parameter> specifies the format
to use for footnote numeration (1, i, I, a, or A).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.footnote.number.format">
<refmeta>
<refentrytitle>table.footnote.number.format</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">1<alt>1,2,3...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">A<alt>A,B,C...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">a<alt>a,b,c...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">i<alt>i,ii,iii...</alt></refmiscinfo>
<refmiscinfo class="other" otherclass="value">I<alt>I,II,III...</alt></refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.footnote.number.format</refname>
<refpurpose>Identifies the format used for footnote numbers in tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.footnote.number.format.frag">
<xsl:param name="table.footnote.number.format">a</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>table.footnote.number.format</parameter> specifies the format
to use for footnote numeration (1, i, I, a, or A) in tables.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="footnote.number.symbols">
<refmeta>
<refentrytitle>footnote.number.symbols</refentrytitle>
<refmiscinfo class="other" otherclass="datatype"/>
</refmeta>
<refnamediv>
<refname>footnote.number.symbols</refname>
<refpurpose>Special characters to use as footnote markers</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="footnote.number.symbols.frag">
<xsl:param name="footnote.number.symbols"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>footnote.number.symbols</parameter> is not the empty string,
footnotes will use the characters it contains as footnote symbols. For example,
<quote>*&#x2020;&#x2021;&#x25CA;&#x2720;</quote> will identify
footnotes with <quote>*</quote>, <quote>†</quote>, <quote>‡</quote>,
<quote>◊</quote>, and <quote>✠</quote>. If there are more footnotes
than symbols, the stylesheets will fall back to numbered footnotes using
<parameter>footnote.number.format</parameter>.</para>
<para>The use of symbols for footnotes depends on the ability of your
processor (or browser) to render the symbols you select. Not all systems are
capable of displaying the full range of Unicode characters. If the quoted characters
in the preceding paragraph are not displayed properly, that's a good indicator
that you may have trouble using those symbols for footnotes.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="table.footnote.number.symbols">
<refmeta>
<refentrytitle>table.footnote.number.symbols</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>table.footnote.number.symbols</refname>
<refpurpose>Special characters to use a footnote markers in tables</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="table.footnote.number.symbols.frag">
<xsl:param name="table.footnote.number.symbols"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>table.footnote.number.symbols</parameter> is not the empty string,
table footnotes will use the characters it contains as footnote symbols. For example,
<quote>*&#x2020;&#x2021;&#x25CA;&#x2720;</quote> will identify
footnotes with <quote>*</quote>, <quote>†</quote>, <quote>‡</quote>,
<quote>◊</quote>, and <quote>✠</quote>. If there are more footnotes
than symbols, the stylesheets will fall back to numbered footnotes using
<parameter>table.footnote.number.format</parameter>.</para>
<para>The use of symbols for footnotes depends on the ability of your
processor (or browser) to render the symbols you select. Not all systems are
capable of displaying the full range of Unicode characters. If the quoted characters
in the preceding paragraph are not displayed properly, that's a good indicator
that you may have trouble using those symbols for footnotes.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="highlight.source">
<refmeta>
<refentrytitle>highlight.source</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>highlight.source</refname>
<refpurpose>Should the content of <tag>programlisting</tag>
be syntactically highlighted?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="highlight.source.frag">
<xsl:param name="highlight.source" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When this parameter is non-zero, the stylesheets will try to do syntax highlighting of the
content of <tag>programlisting</tag> elements. You specify the language for each programlisting
by using the <tag class="attribute">language</tag> attribute. The <parameter>highlight.default.language</parameter>
parameter can be used to specify the language for programlistings without a <tag class="attribute">language</tag>
attribute. Syntax highlighting also works for <tag>screen</tag> and <tag>synopsis</tag> elements.</para>
<para>The actual highlighting work is done by the XSLTHL extension module. This is an external Java library that has to be
downloaded separately (see below).</para>
<itemizedlist>
<para>In order to use this extension, you must</para>
<listitem><para>add <filename>xslthl-2.x.x.jar</filename> to your Java classpath. The latest version is available
from <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://sourceforge.net/projects/xslthl">the XSLT syntax highlighting project</link>
at SourceForge.</para>
</listitem>
<listitem>
<para>use a customization layer in which you import one of the following stylesheet modules:
<itemizedlist>
<listitem>
<para><filename>html/highlight.xsl</filename>
</para>
</listitem>
<listitem>
<para><filename>xhtml/highlight.xsl</filename>
</para>
</listitem>
<listitem>
<para><filename>xhtml-1_1/highlight.xsl</filename>
</para>
</listitem>
<listitem>
<para><filename>fo/highlight.xsl</filename>
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem><para>let either the <literal>xslthl.config</literal> Java system property or the
<parameter>highlight.xslthl.config</parameter> parameter point to the configuration file for syntax
highlighting (using URL syntax). DocBook XSL comes with a ready-to-use configuration file,
<filename>highlighting/xslthl-config.xml</filename>.</para>
</listitem>
</itemizedlist>
<para>The extension works with Saxon 6.5.x and Xalan-J. (Saxon 8.5 or later is also supported, but since it is
an XSLT 2.0 processor it is not guaranteed to work with DocBook XSL in all circumstances.)</para>
<para>The following is an example of a Saxon 6 command adapted for syntax highlighting, to be used on Windows:</para>
<informalexample>
<para><command>java -cp c:/Java/saxon.jar;c:/Java/xslthl-2.0.1.jar
-Dxslthl.config=file:///c:/docbook-xsl/highlighting/xslthl-config.xml com.icl.saxon.StyleSheet
-o test.html test.xml myhtml.xsl</command></para>
</informalexample>
</refsection>
</refentry>
<refentry version="5.0" xml:id="highlight.xslthl.config">
<refmeta>
<refentrytitle>highlight.xslthl.config</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>highlight.xslthl.config</refname>
<refpurpose>Location of XSLTHL configuration file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="highlight.xslthl.config.frag">
<xsl:param name="highlight.xslthl.config"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This location has precedence over the corresponding Java property.</para>
<para>Please note that usually you have to specify location as URL not
just as a simple path on the local
filesystem. E.g. <filename>file:///home/user/xslthl/my-xslthl-config.xml</filename>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="highlight.default.language">
<refmeta>
<refentrytitle>highlight.default.language</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>highlight.default.language</refname>
<refpurpose>Default language of programlisting</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="highlight.default.language.frag">
<xsl:param name="highlight.default.language"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This language is used when there is no language attribute on programlisting.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="email.delimiters.enabled">
<refmeta>
<refentrytitle>email.delimiters.enabled</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>email.delimiters.enabled</refname>
<refpurpose>Generate delimiters around email addresses?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="email.delimiters.enabled.frag">
<xsl:param name="email.delimiters.enabled" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, delimiters
<footnote><para>For delimiters, the
stylesheets are currently hard-coded to output angle
brackets.</para></footnote>
are generated around e-mail addresses
(the output of the <tag>email</tag> element).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="exsl.node.set.available">
<refmeta>
<refentrytitle>exsl.node.set.available</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>exsl.node.set.available</refname>
<refpurpose>Is the test function-available('exsl:node-set') true?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="exsl.node.set.available.frag"><xsl:param name="exsl.node.set.available">
<xsl:choose>
<xsl:when exsl:foo="" test="function-available('exsl:node-set') or contains(system-property('xsl:vendor'), 'Apache Software Foundation')">1</xsl:when>
<xsl:otherwise>0</xsl:otherwise>
</xsl:choose>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero,
then the exsl:node-set() function is available to be used in
the stylesheet.
If zero, then the function is not available.
This param automatically detects the presence of
the function and does not normally need to be set manually.</para>
<para>This param was created to handle a long-standing
bug in the Xalan processor that fails to detect the
function even though it is available.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="annos"><title>Annotations</title>
<refentry version="5.0" xml:id="annotation.support">
<refmeta>
<refentrytitle>annotation.support</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotation.support</refname>
<refpurpose>Enable annotations?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotation.support.frag">
<xsl:param name="annotation.support" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the stylesheets will attempt to support annotation
elements in HTML by including some JavaScript (see
<parameter>annotation.js</parameter>).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="annotation.js">
<refmeta>
<refentrytitle>annotation.js</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotation.js</refname>
<refpurpose>URIs identifying JavaScript files with support for annotation popups</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotation.js.frag">
<xsl:param name="annotation.js">
<xsl:text>http://cdn.docbook.org/release/xsl/script/AnchorPosition.js http://cdn.docbook.org/release/xsl/script/PopupWindow.js</xsl:text></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <property>annotation.support</property> is enabled and the
document contains <tag>annotation</tag>s, then the URIs listed
in this parameter will be included. These JavaScript files are required
for popup annotation support.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="annotation.css">
<refmeta>
<refentrytitle>annotation.css</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotation.css</refname>
<refpurpose>CSS rules for annotations</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotation.css.frag">
<xsl:param name="annotation.css">
/* ======================================================================
Annotations
*/
div.annotation-list { visibility: hidden;
}
div.annotation-nocss { position: absolute;
visibility: hidden;
}
div.annotation-popup { position: absolute;
z-index: 4;
visibility: hidden;
padding: 0px;
margin: 2px;
border-style: solid;
border-width: 1px;
width: 200px;
background-color: white;
}
div.annotation-title { padding: 1px;
font-weight: bold;
border-bottom-style: solid;
border-bottom-width: 1px;
color: white;
background-color: black;
}
div.annotation-body { padding: 2px;
}
div.annotation-body p { margin-top: 0px;
padding-top: 0px;
}
div.annotation-close { position: absolute;
top: 2px;
right: 2px;
}
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>annotation.support</parameter> is enabled and the
document contains <tag>annotation</tag>s, then the CSS in this
parameter will be included in the document.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="annotation.graphic.open">
<refmeta>
<refentrytitle>annotation.graphic.open</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotation.graphic.open</refname>
<refpurpose>Image for identifying a link that opens an annotation popup</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotation.graphic.open.frag">
<xsl:param name="annotation.graphic.open">http://cdn.docbook.org/release/xsl/images/annot-open.png</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This image is used inline to identify the location of
annotations. It may be replaced by a user provided graphic. The size should be approximately 10x10 pixels.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="annotation.graphic.close">
<refmeta>
<refentrytitle>annotation.graphic.close</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>annotation.graphic.close</refname>
<refpurpose>Image for identifying a link that closes an annotation popup</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="annotation.graphic.close.frag">
<xsl:param name="annotation.graphic.close">
http://cdn.docbook.org/release/xsl/images/annot-close.png</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This image is used on popup annotations as the “x” that the
user can click to dismiss the popup.</para>
<para>This image is used on popup annotations as the “x” that the user can
click to dismiss the popup. It may be replaced by a user provided graphic. The size should be approximately 10x10 pixels.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="graphics"><title>Graphics</title>
<refentry version="5.0" xml:id="img.src.path">
<refmeta>
<refentrytitle>img.src.path</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>img.src.path</refname>
<refpurpose>Path to HTML/FO image files</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="img.src.path.frag"><xsl:param name="img.src.path"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Add a path prefix to the value of the <tag class="attribute">fileref</tag>
attribute of <tag>graphic</tag>, <tag>inlinegraphic</tag>, and <tag>imagedata</tag> elements. The resulting
compound path is used in the output as the value of the <tag class="attribute">src</tag>
attribute of <tag class="element">img</tag> (HTML) or <tag class="element">external-graphic</tag> (FO).
</para>
<para>
The path given by <literal>img.src.path</literal> could be relative to the directory where the HTML/FO
files are created, or it could be an absolute URI.
The default value is empty.
Be sure to include a trailing slash if needed.
</para>
<para>This prefix is not applied to any filerefs that start
with "/" or contain "//:".
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="keep.relative.image.uris">
<refmeta>
<refentrytitle>keep.relative.image.uris</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>keep.relative.image.uris</refname>
<refpurpose>Should image URIs be resolved against xml:base?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="keep.relative.image.uris.frag">
<xsl:param name="keep.relative.image.uris" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, relative URIs (in, for example
<literal>fileref</literal> attributes) will be used in the generated
output. Otherwise, the URIs will be made absolute with respect to the
base URI.</para>
<para>Note that the stylesheets calculate (and use) the absolute form
for some purposes, this only applies to the resulting output.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="graphic.default.extension">
<refmeta>
<refentrytitle>graphic.default.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>graphic.default.extension</refname>
<refpurpose>Default extension for graphic filenames</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="graphic.default.extension.frag"><xsl:param name="graphic.default.extension"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If a <tag>graphic</tag> or <tag>mediaobject</tag>
includes a reference to a filename that does not include an extension,
and the <tag class="attribute">format</tag> attribute is
<emphasis>unspecified</emphasis>, the default extension will be used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="default.image.width">
<refmeta>
<refentrytitle>default.image.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>default.image.width</refname>
<refpurpose>The default width of images</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="default.image.width.frag">
<xsl:param name="default.image.width"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If specified, this value will be used for the
<tag class="attribute">width</tag> attribute on images that do not specify any
<emphasis xmlns:xlink="http://www.w3.org/1999/xlink" xlink:title="DocBook 5: The Definitive Guide" xlink:href="http://docbook.org/tdg5/en/html/imagedata.html#viewport.area">viewport dimensions</emphasis>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="nominal.image.width">
<refmeta>
<refentrytitle>nominal.image.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>nominal.image.width</refname>
<refpurpose>The nominal image width</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="nominal.image.width.frag">
<xsl:param name="nominal.image.width" select="6 * $pixels.per.inch"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Graphic widths expressed as a percentage are problematic. In the
following discussion, we speak of width and contentwidth, but
the same issues apply to depth and contentdepth.</para>
<para>A width of 50% means "half of the available space for the image."
That's fine. But note that in HTML, this is a dynamic property and
the image size will vary if the browser window is resized.</para>
<para>A contentwidth of 50% means "half of the actual image width".
But what does that mean if the stylesheets cannot assess the image's
actual size? Treating this as a width of 50% is one possibility, but
it produces behavior (dynamic scaling) that seems entirely out of
character with the meaning.</para>
<para>Instead, the stylesheets define a
<parameter>nominal.image.width</parameter> and convert percentages to
actual values based on that nominal size.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="nominal.image.depth">
<refmeta>
<refentrytitle>nominal.image.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">length</refmiscinfo>
</refmeta>
<refnamediv>
<refname>nominal.image.depth</refname>
<refpurpose>Nominal image depth</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="nominal.image.depth.frag">
<xsl:param name="nominal.image.depth" select="4 * $pixels.per.inch"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>See <parameter>nominal.image.width</parameter>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.embed.for.svg">
<refmeta>
<refentrytitle>use.embed.for.svg</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.embed.for.svg</refname>
<refpurpose>Use HTML <tag>embed</tag> for SVG?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.embed.for.svg.frag">
<xsl:param name="use.embed.for.svg" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, an <tag>embed</tag> element will be created for
SVG figures. An <tag>object</tag> is <emphasis>always</emphasis> created,
this parameter merely controls whether or not an additional <tag>embed</tag>
is generated inside the <tag>object</tag>.</para>
<para>On the plus side, this may be more portable among browsers and plug-ins.
On the minus side, it isn't valid HTML.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="make.graphic.viewport">
<refmeta>
<refentrytitle>make.graphic.viewport</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>make.graphic.viewport</refname>
<refpurpose>Use tables in HTML to make viewports for graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="make.graphic.viewport.frag">
<xsl:param name="make.graphic.viewport" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The HTML <tag>img</tag> element only supports the notion
of content-area scaling; it doesn't support the distinction between a
content-area and a viewport-area, so we have to make some compromises.</para>
<para>If <parameter>make.graphic.viewport</parameter> is non-zero, a table
will be used to frame the image. This creates an effective viewport-area.
</para>
<para>Tables and alignment don't work together, so this parameter is ignored
if alignment is specified on an image.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="preferred.mediaobject.role">
<refmeta>
<refentrytitle>preferred.mediaobject.role</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>preferred.mediaobject.role</refname>
<refpurpose>Select which mediaobject to use based on
this value of an object's <tag class="attribute">role</tag> attribute.
</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="preferred.mediaobject.role.frag">
<xsl:param name="preferred.mediaobject.role"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>A mediaobject may contain several objects such as imageobjects.
If the parameter <parameter>use.role.for.mediaobject</parameter> is
non-zero, then the <literal>role</literal> attribute on
<tag>imageobject</tag>s and other objects within a
<tag>mediaobject</tag> container will be used to select which object
will be used. If one of the objects has a role value that matches the
<parameter>preferred.mediaobject.role</parameter> parameter, then it
has first priority for selection. If more than one has such a role
value, the first one is used.
</para>
<para>
See the <parameter>use.role.for.mediaobject</parameter> parameter
for the sequence of selection.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="link.to.self.for.mediaobject">
<refmeta>
<refentrytitle>link.to.self.for.mediaobject</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>link.to.self.for.mediaobject</refname>
<refpurpose>Include <tag>a</tag> element to image objects itself to go to a full-size, freely-zoomable version</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="link.to.self.for.mediaobject.frag">
<xsl:param name="link.to.self.for.mediaobject" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection>
<info>
<title>Description</title>
</info>
<para>In some cases, it can be very helpful to be able to click on an embedded <tag>figure</tag>
or <tag>informalfigure</tag> to get a full-size, freely-zoomable version of an image, for
instance when targeting readers on smartphones. This is implemented for images only, but not
for audio or video objects. </para>
<para>If non-zero, the image will be wrapped in an <tag>a</tag> element, using the <tag class="attribute">href</tag>
attribute pointing to the image itself: </para>
<screen><a href="source/image">
<!-- the image object -->
</a></screen>
<para> If the value of <parameter>link.to.self.for.mediaobject.xml</parameter> is zero
(default), then no <tag>a</tag> container is added. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.role.for.mediaobject">
<refmeta>
<refentrytitle>use.role.for.mediaobject</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.role.for.mediaobject</refname>
<refpurpose>Use <tag class="attribute">role</tag> attribute
value for selecting which of several objects within a mediaobject to use.
</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.role.for.mediaobject.frag">
<xsl:param name="use.role.for.mediaobject" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the <tag class="attribute">role</tag> attribute on
<tag>imageobject</tag>s or other objects within a <tag>mediaobject</tag> container will be used to select which object will be
used.
</para>
<para>
The order of selection when then parameter is non-zero is:
</para>
<orderedlist>
<listitem>
<para>If the stylesheet parameter <parameter>preferred.mediaobject.role</parameter> has a value, then the object whose role equals that value is selected.</para>
</listitem>
<listitem>
<para>Else if an object's role attribute has a value of
<literal>html</literal> for HTML processing or
<literal>fo</literal> for FO output, then the first
of such objects is selected.
</para>
</listitem>
<listitem>
<para>Else the first suitable object is selected.</para>
</listitem>
</orderedlist>
<para>
If the value of
<parameter>use.role.for.mediaobject</parameter>
is zero, then role attributes are not considered
and the first suitable object
with or without a role value is used.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="ignore.image.scaling">
<refmeta>
<refentrytitle>ignore.image.scaling</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>ignore.image.scaling</refname>
<refpurpose>Tell the stylesheets to ignore the author's image scaling attributes</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="ignore.image.scaling.frag">
<xsl:param name="ignore.image.scaling" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the scaling attributes on graphics and media objects are
ignored.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="chunking"><title>Chunking</title>
<refentry version="5.0" xml:id="chunker.output.cdata-section-elements">
<refmeta>
<refentrytitle>chunker.output.cdata-section-elements</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.cdata-section-elements</refname>
<refpurpose>List of elements to escape with CDATA sections</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.cdata-section-elements.frag">
<xsl:param name="chunker.output.cdata-section-elements"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the list of elements that should be escaped
as CDATA sections by the chunking stylesheet. Not all processors support
specification of this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.doctype-public">
<refmeta>
<refentrytitle>chunker.output.doctype-public</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.doctype-public</refname>
<refpurpose>Public identifer to use in the document type of generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.doctype-public.frag">
<xsl:param name="chunker.output.doctype-public"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the public identifier that should be used by
the chunking stylesheet in the document type declaration of chunked pages.
Not all processors support specification of
this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.doctype-system">
<refmeta>
<refentrytitle>chunker.output.doctype-system</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.doctype-system</refname>
<refpurpose>System identifier to use for the document type in generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.doctype-system.frag">
<xsl:param name="chunker.output.doctype-system"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the system identifier that should be used by
the chunking stylesheet in the document type declaration of chunked pages.
Not all processors support specification of
this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.encoding">
<refmeta>
<refentrytitle>chunker.output.encoding</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.encoding</refname>
<refpurpose>Encoding used in generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.encoding.frag">
<xsl:param name="chunker.output.encoding">ISO-8859-1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the encoding to be used in files
generated by the chunking stylesheet. Not all processors support
specification of this parameter.
</para>
<para>This parameter used to be named <literal>default.encoding</literal>.</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.indent">
<refmeta>
<refentrytitle>chunker.output.indent</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.indent</refname>
<refpurpose>Specification of indentation on generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.indent.frag">
<xsl:param name="chunker.output.indent">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the value of the indent
specification for generated pages. Not all processors support
specification of this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.media-type">
<refmeta>
<refentrytitle>chunker.output.media-type</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.media-type</refname>
<refpurpose>Media type to use in generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.media-type.frag">
<xsl:param name="chunker.output.media-type"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the media type that should be used by
the chunking stylesheet. Not all processors support specification of
this parameter.
</para>
<para>This parameter specifies the media type that should be used by the
chunking stylesheet. This should be one from those defined in
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.ietf.org/rfc/rfc2045.txt">[RFC2045]</link> and
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.ietf.org/rfc/rfc2046.txt">[RFC2046]</link> </para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
<para>It must be one from html, xml or text</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.method">
<refmeta>
<refentrytitle>chunker.output.method</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">list</refmiscinfo>
<refmiscinfo class="other" otherclass="value">html</refmiscinfo>
<refmiscinfo class="other" otherclass="value">xml</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.method</refname>
<refpurpose>Method used in generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.method.frag">
<xsl:param name="chunker.output.method">html</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the output method to be used in files
generated by the chunking stylesheet.
</para>
<para>This parameter used to be named <literal>output.method</literal>.</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.omit-xml-declaration">
<refmeta>
<refentrytitle>chunker.output.omit-xml-declaration</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.omit-xml-declaration</refname>
<refpurpose>Omit-xml-declaration for generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.omit-xml-declaration.frag">
<xsl:param name="chunker.output.omit-xml-declaration">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the value of the omit-xml-declaration
specification for generated pages. Not all processors support
specification of this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunker.output.standalone">
<refmeta>
<refentrytitle>chunker.output.standalone</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunker.output.standalone</refname>
<refpurpose>Standalone declaration for generated pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunker.output.standalone.frag">
<xsl:param name="chunker.output.standalone">no</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the value of the standalone
specification for generated pages. It must be either
<literal>yes</literal> or <literal>no</literal>. Not all
processors support specification of this parameter.
</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="saxon.character.representation">
<refmeta>
<refentrytitle>saxon.character.representation</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>saxon.character.representation</refname>
<refpurpose>Saxon character representation used in generated HTML pages</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="saxon.character.representation.frag"><xsl:param name="saxon.character.representation" select="'entity;decimal'"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter has effect only when Saxon 6 is used (version 6.4.2 or later).
It sets the character representation in files generated by the chunking stylesheets.
If you want to suppress entity references for characters with direct representations in
<parameter>chunker.output.encoding</parameter>, set the parameter value to <literal>native</literal>.
</para>
<para> For more information, see <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="OutputEncoding.html#SaxonCharacter">Saxon output character representation</link>.</para>
<note>
<para>This parameter is documented here, but the declaration is actually
in the <filename>chunker.xsl</filename> stylesheet module.</para>
</note>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.ext">
<refmeta>
<refentrytitle>html.ext</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.ext</refname>
<refpurpose>Identifies the extension of generated HTML files</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.ext.frag">
<xsl:param name="html.ext">.html</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The extension identified by <parameter>html.ext</parameter> will
be used as the filename extension for chunks created by this
stylesheet. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="use.id.as.filename">
<refmeta>
<refentrytitle>use.id.as.filename</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>use.id.as.filename</refname>
<refpurpose>Use ID value of chunk elements as the filename?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="use.id.as.filename.frag">
<xsl:param name="use.id.as.filename" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If <parameter>use.id.as.filename</parameter>
is non-zero, the filename of chunk elements that have IDs will be
derived from the ID value.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="html.extra.head.links">
<refmeta>
<refentrytitle>html.extra.head.links</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>html.extra.head.links</refname>
<refpurpose>Toggle extra HTML head link information</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="html.extra.head.links.frag">
<xsl:param name="html.extra.head.links" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, extra <tag>link</tag> elements will be
generated in the <tag>head</tag> of chunked HTML files. These
extra links point to chapters, appendixes, sections, etc. as supported
by the <quote>Site Navigation Bar</quote> in Mozilla 1.0 (as of CR1, at least).
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="root.filename">
<refmeta>
<refentrytitle>root.filename</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>root.filename</refname>
<refpurpose>Identifies the name of the root HTML file when chunking</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="root.filename.frag">
<xsl:param name="root.filename">index</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>root.filename</parameter> is the base filename for
the chunk created for the root of each document processed.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="base.dir">
<refmeta>
<refentrytitle>base.dir</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">uri</refmiscinfo>
</refmeta>
<refnamediv>
<refname>base.dir</refname>
<refpurpose>The base directory of chunks</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="base.dir.frag">
<xsl:param name="base.dir"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If specified, the <parameter>base.dir</parameter> parameter identifies
the output directory for chunks. (If not specified, the output directory
is system dependent.)</para>
<para>Starting with version 1.77 of the stylesheets,
the param's value will have a trailing slash added if it does
not already have one.</para>
<caution><para>Do not use <parameter>base.dir</parameter>
to add a filename prefix string to chunked files.
Instead, use the <parameter>chunked.filename.prefix</parameter>
parameter.</para></caution>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunked.filename.prefix">
<refmeta>
<refentrytitle>chunked.filename.prefix</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunked.filename.prefix</refname>
<refpurpose>Filename prefix for chunked files</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunked.filename.prefix.frag">
<xsl:param name="chunked.filename.prefix"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If specified, the <parameter>chunked.filename.prefix</parameter>
parameter specifies a prefix string to add to each generated chunk filename.
For example:</para>
<programlisting><xsl:param name="chunked.filename.prefix">admin-<xsl:param></programlisting>
<para>will produce chunked filenames like:</para>
<programlisting>admin-index.html
admin-ch01.html
admin-ch01s01.html
...
</programlisting>
<caution><para>Trying to use the <parameter>base.dir</parameter>
parameter to add a string prefix (by omitting the trailing slash)
no longer works (it never worked completely anyway). That parameter
value should contain only a directory path, and
now gets a trailing slash appended if it was omitted from the param.</para></caution>
</refsection>
</refentry>
<refentry version="5.0" xml:id="generate.manifest">
<refmeta>
<refentrytitle>generate.manifest</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>generate.manifest</refname>
<refpurpose>Generate a manifest file?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="generate.manifest.frag"><xsl:param name="generate.manifest" select="0"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a list of HTML files generated by the
stylesheet transformation is written to the file named by
the <parameter>manifest</parameter> parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="manifest">
<refmeta>
<refentrytitle>manifest</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>manifest</refname>
<refpurpose>Name of manifest file</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="manifest.frag">
<xsl:param name="manifest">HTML.manifest</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The name of the file to which a manifest is written (if the
value of the <parameter>generate.manifest</parameter> parameter
is non-zero).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="manifest.in.base.dir">
<refmeta>
<refentrytitle>manifest.in.base.dir</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>manifest.in.base.dir</refname>
<refpurpose>Should the manifest file be written into <parameter>base.dir</parameter>?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="manifest.in.base.dir.frag">
<xsl:param name="manifest.in.base.dir" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the manifest file as well as project files for HTML Help and
Eclipse Help are written into <parameter>base.dir</parameter> instead
of the current directory.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.toc">
<refmeta>
<refentrytitle>chunk.toc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.toc</refname>
<refpurpose>An explicit TOC to be used for chunking</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.toc.frag">
<xsl:param name="chunk.toc"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The <parameter>chunk.toc</parameter> identifies an explicit TOC that
will be used for chunking. This parameter is only used by the
<filename>chunktoc.xsl</filename> stylesheet (and customization layers built
from it).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.tocs.and.lots">
<refmeta>
<refentrytitle>chunk.tocs.and.lots</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.tocs.and.lots</refname>
<refpurpose>Should ToC and LoTs be in separate chunks?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.tocs.and.lots.frag">
<xsl:param name="chunk.tocs.and.lots" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, ToC and LoT (List of Examples, List of Figures, etc.)
will be put in a separate chunk. At the moment, this chunk is not in the
normal forward/backward navigation list. Instead, a new link is added to the
navigation footer.</para>
<para>This feature is still somewhat experimental. Feedback welcome.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.separate.lots">
<refmeta>
<refentrytitle>chunk.separate.lots</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.separate.lots</refname>
<refpurpose>Should each LoT be in its own separate chunk?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.separate.lots.frag">
<xsl:param name="chunk.separate.lots" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, each of the ToC and LoTs
(List of Examples, List of Figures, etc.)
will be put in its own separate chunk.
The title page includes generated links to each of the separate files.
</para>
<para>
This feature depends on the
<parameter>chunk.tocs.and.lots</parameter>
parameter also being non-zero.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.tocs.and.lots.has.title">
<refmeta>
<refentrytitle>chunk.tocs.and.lots.has.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.tocs.and.lots.has.title</refname>
<refpurpose>Should ToC and LoTs in a separate chunks have title?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.tocs.and.lots.has.title.frag">
<xsl:param name="chunk.tocs.and.lots.has.title" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero title of document is shown before ToC/LoT in
separate chunk.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.section.depth">
<refmeta>
<refentrytitle>chunk.section.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.section.depth</refname>
<refpurpose>Depth to which sections should be chunked</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.section.depth.frag">
<xsl:param name="chunk.section.depth" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter sets the depth of section chunking.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.first.sections">
<refmeta>
<refentrytitle>chunk.first.sections</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.first.sections</refname>
<refpurpose>Chunk the first top-level section?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.first.sections.frag">
<xsl:param name="chunk.first.sections" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, a chunk will be created for the first top-level
<tag>sect1</tag> or <tag>section</tag> elements in
each component. Otherwise, that section will be part of the chunk for
its parent.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.quietly">
<refmeta>
<refentrytitle>chunk.quietly</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.quietly</refname>
<refpurpose>Omit the chunked filename messages.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.quietly.frag">
<xsl:param name="chunk.quietly" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If zero (the default), the XSL processor emits a message naming
each separate chunk filename as it is being output.
If nonzero, then the messages are suppressed.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="chunk.append">
<refmeta>
<refentrytitle>chunk.append</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>chunk.append</refname>
<refpurpose>Specifies content to append to chunked HTML output</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="chunk.append.frag"><xsl:param name="chunk.append"></xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies content to append to the end of HTML files output by
the <filename>html/chunk.xsl</filename> stylesheet, after the closing
<code><html></code> tag. You probably don’t want to set any value
for this parameter; but if you do, the only value it should ever be
set to is a newline character: <code>&#x0a;</code> or
<code>&#10;</code></para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="navig.graphics">
<refmeta>
<refentrytitle>navig.graphics</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>navig.graphics</refname>
<refpurpose>Use graphics in navigational headers and footers?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="navig.graphics.frag">
<xsl:param name="navig.graphics" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the navigational headers and footers in chunked
HTML are presented in an alternate style that uses graphical icons for
Next, Previous, Up, and Home. Default graphics are provided in the
distribution. If zero, text is used instead of graphics.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="navig.graphics.extension">
<refmeta>
<refentrytitle>navig.graphics.extension</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>navig.graphics.extension</refname>
<refpurpose>Extension for navigational graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="navig.graphics.extension.frag">
<xsl:param name="navig.graphics.extension">.gif</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the filename extension to use on navigational graphics used
in the headers and footers of chunked HTML.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="navig.graphics.path">
<refmeta>
<refentrytitle>navig.graphics.path</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>navig.graphics.path</refname>
<refpurpose>Path to navigational graphics</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="navig.graphics.path.frag">
<xsl:param name="navig.graphics.path">images/</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets the path, probably relative to the directory where the HTML
files are created, to the navigational graphics used in the
headers and footers of chunked HTML.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="navig.showtitles">
<refmeta>
<refentrytitle>navig.showtitles</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>navig.showtitles</refname>
<refpurpose>Display titles in HTML headers and footers?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="navig.showtitles.frag"><xsl:param name="navig.showtitles">1</xsl:param></programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero,
the headers and footers of chunked HTML
display the titles of the next and previous chunks,
along with the words 'Next' and 'Previous' (or the
equivalent graphical icons if navig.graphics is true).
If false (zero), then only the words 'Next' and 'Previous'
(or the icons) are displayed.
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="profiling"><title>Profiling</title>
<partintro xml:id="partintro">
<para>The following parameters can be used for attribute-based
profiling of your document. For more information about profiling, see
<link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="Profiling.html">Profiling (conditional text)</link>.</para>
</partintro>
<refentry version="5.0" xml:id="profile.arch">
<refmeta>
<refentrytitle>profile.arch</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.arch</refname>
<refpurpose>Target profile for <tag class="attribute">arch</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.arch.frag">
<xsl:param name="profile.arch"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.audience">
<refmeta>
<refentrytitle>profile.audience</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.audience</refname>
<refpurpose>Target profile for <tag class="attribute">audience</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.audience.frag">
<xsl:param name="profile.audience"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.condition">
<refmeta>
<refentrytitle>profile.condition</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.condition</refname>
<refpurpose>Target profile for <tag class="attribute">condition</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.condition.frag">
<xsl:param name="profile.condition"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.conformance">
<refmeta>
<refentrytitle>profile.conformance</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.conformance</refname>
<refpurpose>Target profile for <tag class="attribute">conformance</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.conformance.frag">
<xsl:param name="profile.conformance"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.lang">
<refmeta>
<refentrytitle>profile.lang</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.lang</refname>
<refpurpose>Target profile for <tag class="attribute">lang</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.lang.frag">
<xsl:param name="profile.lang"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.os">
<refmeta>
<refentrytitle>profile.os</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.os</refname>
<refpurpose>Target profile for <tag class="attribute">os</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.os.frag">
<xsl:param name="profile.os"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.outputformat">
<refmeta>
<refentrytitle>profile.outputformat</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.outputformat</refname>
<refpurpose>Target profile for <tag class="attribute">outputformat</tag> attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.outputformat.frag">
<xsl:param name="profile.outputformat"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.revision">
<refmeta>
<refentrytitle>profile.revision</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.revision</refname>
<refpurpose>Target profile for <tag class="attribute">revision</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.revision.frag">
<xsl:param name="profile.revision"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.revisionflag">
<refmeta>
<refentrytitle>profile.revisionflag</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.revisionflag</refname>
<refpurpose>Target profile for <tag class="attribute">revisionflag</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.revisionflag.frag">
<xsl:param name="profile.revisionflag"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.role">
<refmeta>
<refentrytitle>profile.role</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.role</refname>
<refpurpose>Target profile for <tag class="attribute">role</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.role.frag">
<xsl:param name="profile.role"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
<warning>
<para>Note that <tag class="attribute">role</tag> is often
used for other purposes than profiling. For example it is commonly
used to get emphasize in bold font:</para>
<programlisting><emphasis role="bold">very important</emphasis></programlisting>
<para>If you are using <tag class="attribute">role</tag> for
these purposes do not forget to add values like <literal>bold</literal> to
value of this parameter. If you forgot you will get document with
small pieces missing which are very hard to track.</para>
<para>For this reason it is not recommended to use <tag class="attribute">role</tag> attribute for profiling. You should
rather use profiling specific attributes like <tag class="attribute">userlevel</tag>, <tag class="attribute">os</tag>, <tag class="attribute">arch</tag>, <tag class="attribute">condition</tag>, etc.</para>
</warning>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.security">
<refmeta>
<refentrytitle>profile.security</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.security</refname>
<refpurpose>Target profile for <tag class="attribute">security</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.security.frag">
<xsl:param name="profile.security"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.status">
<refmeta>
<refentrytitle>profile.status</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.status</refname>
<refpurpose>Target profile for <tag class="attribute">status</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.status.frag">
<xsl:param name="profile.status"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.userlevel">
<refmeta>
<refentrytitle>profile.userlevel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.userlevel</refname>
<refpurpose>Target profile for <tag class="attribute">userlevel</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.userlevel.frag">
<xsl:param name="profile.userlevel"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.vendor">
<refmeta>
<refentrytitle>profile.vendor</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.vendor</refname>
<refpurpose>Target profile for <tag class="attribute">vendor</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.vendor.frag">
<xsl:param name="profile.vendor"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.wordsize">
<refmeta>
<refentrytitle>profile.wordsize</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.wordsize</refname>
<refpurpose>Target profile for <tag class="attribute">wordsize</tag>
attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.wordsize.frag">
<xsl:param name="profile.wordsize"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.attribute">
<refmeta>
<refentrytitle>profile.attribute</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.attribute</refname>
<refpurpose>Name of user-specified profiling attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.attribute.frag">
<xsl:param name="profile.attribute"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter is used in conjuction with
<parameter>profile.value</parameter>.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.value">
<refmeta>
<refentrytitle>profile.value</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.value</refname>
<refpurpose>Target profile for user-specified attribute</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.value.frag">
<xsl:param name="profile.value"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When you are using this parameter you must also specify name of
profiling attribute with parameter
<parameter>profile.attribute</parameter>.</para>
<para>The value of this parameter specifies profiles which should be
included in the output. You can specify multiple profiles by
separating them by semicolon. You can change separator character by
<parameter>profile.separator</parameter>
parameter.</para>
<para>This parameter has effect only when you are using profiling
stylesheets (<filename>profile-docbook.xsl</filename>,
<filename>profile-chunk.xsl</filename>, …) instead of normal
ones (<filename>docbook.xsl</filename>,
<filename>chunk.xsl</filename>, …).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="profile.separator">
<refmeta>
<refentrytitle>profile.separator</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>profile.separator</refname>
<refpurpose>Separator character for compound profile values</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="profile.separator.frag">
<xsl:param name="profile.separator">;</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Separator character used for compound profile values. See <parameter>profile.arch</parameter></para>
</refsection>
</refentry>
</reference>
<reference xml:id="htmlhelp"><title>HTML Help</title>
<refentry version="5.0" xml:id="htmlhelp.encoding">
<refmeta>
<refentrytitle>htmlhelp.encoding</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.encoding</refname>
<refpurpose>Character encoding to use in files for HTML Help compiler.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.encoding.frag">
<xsl:param name="htmlhelp.encoding">iso-8859-1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The HTML Help Compiler is not UTF-8 aware, so you should always use an
appropriate single-byte encoding here. See also <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="HtmlHelp.html#HelpProcOptions" role="tcg">Processing options</link>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.autolabel">
<refmeta>
<refentrytitle>htmlhelp.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.autolabel</refname>
<refpurpose>Should tree-like ToC use autonumbering feature?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.autolabel.frag">
<xsl:param name="htmlhelp.autolabel" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set this to non-zero to include chapter and section numbers into ToC
in the left panel.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.chm">
<refmeta>
<refentrytitle>htmlhelp.chm</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.chm</refname>
<refpurpose>Filename of output HTML Help file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.chm.frag">
<xsl:param name="htmlhelp.chm">htmlhelp.chm</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set the name of resulting CHM file</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.default.topic">
<refmeta>
<refentrytitle>htmlhelp.default.topic</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.default.topic</refname>
<refpurpose>Name of file with default topic</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.default.topic.frag">
<xsl:param name="htmlhelp.default.topic"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Normally first chunk of document is displayed when you open HTML
Help file. If you want to display another topic, simply set its
filename by this parameter.</para>
<para>This is useful especially if you don't generate ToC in front of
your document and you also hide root element in ToC. E.g.:</para>
<programlisting><xsl:param name="generate.book.toc" select="0"/>
<xsl:param name="htmlhelp.hhc.show.root" select="0"/>
<xsl:param name="htmlhelp.default.topic">pr01.html</xsl:param>
</programlisting>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.display.progress">
<refmeta>
<refentrytitle>htmlhelp.display.progress</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.display.progress</refname>
<refpurpose>Display compile progress?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.display.progress.frag">
<xsl:param name="htmlhelp.display.progress" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to to display compile progress
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhp">
<refmeta>
<refentrytitle>htmlhelp.hhp</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhp</refname>
<refpurpose>Filename of project file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhp.frag">
<xsl:param name="htmlhelp.hhp">htmlhelp.hhp</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Change this parameter if you want different name of project
file than htmlhelp.hhp.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc">
<refmeta>
<refentrytitle>htmlhelp.hhc</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc</refname>
<refpurpose>Filename of TOC file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.frag">
<xsl:param name="htmlhelp.hhc">toc.hhc</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set the name of the TOC file. The default is <filename>toc.hhc</filename>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhk">
<refmeta>
<refentrytitle>htmlhelp.hhk</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhk</refname>
<refpurpose>Filename of index file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhk.frag">
<xsl:param name="htmlhelp.hhk">index.hhk</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>set the name of the index file. The default is <filename>index.hhk</filename>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhp.tail">
<refmeta>
<refentrytitle>htmlhelp.hhp.tail</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhp.tail</refname>
<refpurpose>Additional content for project file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhp.tail.frag">
<xsl:param name="htmlhelp.hhp.tail"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want to include some additional parameters into project file,
store appropriate part of project file into this parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhp.window">
<refmeta>
<refentrytitle>htmlhelp.hhp.window</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhp.window</refname>
<refpurpose>Name of default window.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhp.window.frag">
<xsl:param name="htmlhelp.hhp.window">Main</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Name of default window. If empty no [WINDOWS] section will be
added to project file.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhp.windows">
<refmeta>
<refentrytitle>htmlhelp.hhp.windows</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhp.windows</refname>
<refpurpose>Definition of additional windows</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhp.windows.frag">
<xsl:param name="htmlhelp.hhp.windows"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Content of this parameter is placed at the end of [WINDOWS]
section of project file. You can use it for defining your own
addtional windows.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.enhanced.decompilation">
<refmeta>
<refentrytitle>htmlhelp.enhanced.decompilation</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.enhanced.decompilation</refname>
<refpurpose>Allow enhanced decompilation of CHM?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.enhanced.decompilation.frag">
<xsl:param name="htmlhelp.enhanced.decompilation" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>When non-zero this parameter enables enhanced decompilation of CHM.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.enumerate.images">
<refmeta>
<refentrytitle>htmlhelp.enumerate.images</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.enumerate.images</refname>
<refpurpose>Should the paths to all used images be added to the project file?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.enumerate.images.frag">
<xsl:param name="htmlhelp.enumerate.images" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero if you insert images into your documents as
external binary entities or if you are using absolute image paths.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.force.map.and.alias">
<refmeta>
<refentrytitle>htmlhelp.force.map.and.alias</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.force.map.and.alias</refname>
<refpurpose>Should [MAP] and [ALIAS] sections be added to the project file unconditionally?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.force.map.and.alias.frag">
<xsl:param name="htmlhelp.force.map.and.alias" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero if you have your own
<literal>alias.h</literal> and <literal>context.h</literal>
files and you want to include references to them in the project
file.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.map.file">
<refmeta>
<refentrytitle>htmlhelp.map.file</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.map.file</refname>
<refpurpose>Filename of map file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.map.file.frag">
<xsl:param name="htmlhelp.map.file">context.h</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set the name of map file. The default is
<filename>context.h</filename>. (used for context-sensitive
help).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.alias.file">
<refmeta>
<refentrytitle>htmlhelp.alias.file</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.alias.file</refname>
<refpurpose>Filename of alias file.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.alias.file.frag">
<xsl:param name="htmlhelp.alias.file">alias.h</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Specifies the filename of the alias file (used for context-sensitive help).</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc.section.depth">
<refmeta>
<refentrytitle>htmlhelp.hhc.section.depth</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc.section.depth</refname>
<refpurpose>Depth of TOC for sections in a left pane.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.section.depth.frag">
<xsl:param name="htmlhelp.hhc.section.depth">5</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set the section depth in the left pane of HTML Help viewer. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc.show.root">
<refmeta>
<refentrytitle>htmlhelp.hhc.show.root</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc.show.root</refname>
<refpurpose>Should there be an entry for the root element in the ToC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.show.root.frag">
<xsl:param name="htmlhelp.hhc.show.root" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If set to zero, there will be no entry for the root element in the
ToC. This is useful when you want to provide the user with an expanded
ToC as a default.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc.folders.instead.books">
<refmeta>
<refentrytitle>htmlhelp.hhc.folders.instead.books</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc.folders.instead.books</refname>
<refpurpose>Use folder icons in ToC (instead of book icons)?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.folders.instead.books.frag">
<xsl:param name="htmlhelp.hhc.folders.instead.books" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero for folder-like icons or zero for book-like icons in the ToC.
If you want to use folder-like icons, you must switch off the binary ToC using
<parameter>htmlhelp.hhc.binary</parameter>.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc.binary">
<refmeta>
<refentrytitle>htmlhelp.hhc.binary</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc.binary</refname>
<refpurpose>Generate binary ToC?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.binary.frag">
<xsl:param name="htmlhelp.hhc.binary" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to generate a binary TOC. You must create a binary TOC
if you want to add Prev/Next buttons to toolbar (which is default
behaviour). Files with binary TOC can't be merged.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.hhc.width">
<refmeta>
<refentrytitle>htmlhelp.hhc.width</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">integer</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.hhc.width</refname>
<refpurpose>Width of navigation pane</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.hhc.width.frag">
<xsl:param name="htmlhelp.hhc.width"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies the width of the navigation pane (containing TOC and
other navigation tabs) in pixels.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.title">
<refmeta>
<refentrytitle>htmlhelp.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.title</refname>
<refpurpose>Title of HTML Help</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.title.frag">
<xsl:param name="htmlhelp.title"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Content of this parameter will be used as a title for generated
HTML Help. If empty, title will be automatically taken from document.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.show.menu">
<refmeta>
<refentrytitle>htmlhelp.show.menu</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.show.menu</refname>
<refpurpose>Should the menu bar be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.show.menu.frag">
<xsl:param name="htmlhelp.show.menu" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to have an application menu bar in your HTML Help window.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.show.toolbar.text">
<refmeta>
<refentrytitle>htmlhelp.show.toolbar.text</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.show.toolbar.text</refname>
<refpurpose>Show text under toolbar buttons?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.show.toolbar.text.frag">
<xsl:param name="htmlhelp.show.toolbar.text" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to display texts under toolbar buttons, zero to switch
off displays.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.show.advanced.search">
<refmeta>
<refentrytitle>htmlhelp.show.advanced.search</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.show.advanced.search</refname>
<refpurpose>Should advanced search features be available?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.show.advanced.search.frag">
<xsl:param name="htmlhelp.show.advanced.search" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want advanced search features in your help, turn this
parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.show.favorities">
<refmeta>
<refentrytitle>htmlhelp.show.favorities</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.show.favorities</refname>
<refpurpose>Should the Favorites tab be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.show.favorities.frag">
<xsl:param name="htmlhelp.show.favorities" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include a Favorites tab in the navigation pane
of the help window.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.hideshow">
<refmeta>
<refentrytitle>htmlhelp.button.hideshow</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.hideshow</refname>
<refpurpose>Should the Hide/Show button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.hideshow.frag">
<xsl:param name="htmlhelp.button.hideshow" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Hide/Show button shown on toolbar</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.back">
<refmeta>
<refentrytitle>htmlhelp.button.back</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.back</refname>
<refpurpose>Should the Back button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.back.frag">
<xsl:param name="htmlhelp.button.back" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Hide/Show button shown on toolbar</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.forward">
<refmeta>
<refentrytitle>htmlhelp.button.forward</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.forward</refname>
<refpurpose>Should the Forward button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.forward.frag">
<xsl:param name="htmlhelp.button.forward" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Forward button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.stop">
<refmeta>
<refentrytitle>htmlhelp.button.stop</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.stop</refname>
<refpurpose>Should the Stop button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.stop.frag">
<xsl:param name="htmlhelp.button.stop" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want Stop button shown on toolbar, turn this
parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.refresh">
<refmeta>
<refentrytitle>htmlhelp.button.refresh</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.refresh</refname>
<refpurpose>Should the Refresh button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.refresh.frag">
<xsl:param name="htmlhelp.button.refresh" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Stop button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.home">
<refmeta>
<refentrytitle>htmlhelp.button.home</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.home</refname>
<refpurpose>Should the Home button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.home.frag">
<xsl:param name="htmlhelp.button.home" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Home button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.home.url">
<refmeta>
<refentrytitle>htmlhelp.button.home.url</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.home.url</refname>
<refpurpose>URL address of page accessible by Home button</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.home.url.frag">
<xsl:param name="htmlhelp.button.home.url"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>URL address of page accessible by Home button.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.options">
<refmeta>
<refentrytitle>htmlhelp.button.options</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.options</refname>
<refpurpose>Should the Options button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.options.frag">
<xsl:param name="htmlhelp.button.options" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want Options button shown on toolbar, turn this
parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.print">
<refmeta>
<refentrytitle>htmlhelp.button.print</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.print</refname>
<refpurpose>Should the Print button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.print.frag">
<xsl:param name="htmlhelp.button.print" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Print button on the toolbar.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.locate">
<refmeta>
<refentrytitle>htmlhelp.button.locate</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.locate</refname>
<refpurpose>Should the Locate button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.locate.frag">
<xsl:param name="htmlhelp.button.locate" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want Locate button shown on toolbar, turn this
parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump1">
<refmeta>
<refentrytitle>htmlhelp.button.jump1</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump1</refname>
<refpurpose>Should the Jump1 button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump1.frag">
<xsl:param name="htmlhelp.button.jump1" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the <literal>Jump1</literal> button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump1.url">
<refmeta>
<refentrytitle>htmlhelp.button.jump1.url</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump1.url</refname>
<refpurpose>URL address of page accessible by Jump1 button</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump1.url.frag">
<xsl:param name="htmlhelp.button.jump1.url"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>URL address of page accessible by Jump1 button.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump1.title">
<refmeta>
<refentrytitle>htmlhelp.button.jump1.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump1.title</refname>
<refpurpose>Title of Jump1 button</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump1.title.frag">
<xsl:param name="htmlhelp.button.jump1.title">User1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Title of Jump1 button.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump2">
<refmeta>
<refentrytitle>htmlhelp.button.jump2</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump2</refname>
<refpurpose>Should the Jump2 button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump2.frag">
<xsl:param name="htmlhelp.button.jump2" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Jump2 button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump2.url">
<refmeta>
<refentrytitle>htmlhelp.button.jump2.url</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump2.url</refname>
<refpurpose>URL address of page accessible by Jump2 button</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump2.url.frag">
<xsl:param name="htmlhelp.button.jump2.url"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>URL address of page accessible by Jump2 button.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.jump2.title">
<refmeta>
<refentrytitle>htmlhelp.button.jump2.title</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.jump2.title</refname>
<refpurpose>Title of Jump2 button</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.jump2.title.frag">
<xsl:param name="htmlhelp.button.jump2.title">User2</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Title of Jump2 button.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.next">
<refmeta>
<refentrytitle>htmlhelp.button.next</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.next</refname>
<refpurpose>Should the Next button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.next.frag">
<xsl:param name="htmlhelp.button.next" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Next button on the toolbar.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.prev">
<refmeta>
<refentrytitle>htmlhelp.button.prev</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.prev</refname>
<refpurpose>Should the Prev button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.prev.frag">
<xsl:param name="htmlhelp.button.prev" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Prev button on the toolbar.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.button.zoom">
<refmeta>
<refentrytitle>htmlhelp.button.zoom</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.button.zoom</refname>
<refpurpose>Should the Zoom button be shown?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.button.zoom.frag">
<xsl:param name="htmlhelp.button.zoom" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to include the Zoom button on the toolbar.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.remember.window.position">
<refmeta>
<refentrytitle>htmlhelp.remember.window.position</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.remember.window.position</refname>
<refpurpose>Remember help window position?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.remember.window.position.frag">
<xsl:param name="htmlhelp.remember.window.position" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero to remember help window position between starts.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.window.geometry">
<refmeta>
<refentrytitle>htmlhelp.window.geometry</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.window.geometry</refname>
<refpurpose>Set initial geometry of help window</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.window.geometry.frag">
<xsl:param name="htmlhelp.window.geometry"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>This parameter specifies initial position of help
window. E.g.</para>
<programlisting><xsl:param name="htmlhelp.window.geometry">[160,64,992,704]</xsl:param></programlisting>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.use.hhk">
<refmeta>
<refentrytitle>htmlhelp.use.hhk</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.use.hhk</refname>
<refpurpose>Should the index be built using the HHK file?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.use.hhk.frag">
<xsl:param name="htmlhelp.use.hhk" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the index is created using the HHK file (instead of using <tag role="html">object</tag>
elements in the HTML files). For more information, see <link xmlns:xlink="http://www.w3.org/1999/xlink" role="tcg" xlink:href="HtmlHelp.html#HHGenIndex">Generating an index</link>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="htmlhelp.only">
<refmeta>
<refentrytitle>htmlhelp.only</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>htmlhelp.only</refname>
<refpurpose>Should only project files be generated?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="htmlhelp.only.frag">
<xsl:param name="htmlhelp.only" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set to non-zero if you want to play with various HTML Help parameters
and you don't need to regenerate all HTML files. This setting will not
process whole document, only project files (hhp, hhc, hhk,...) will be
generated.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="eclipse_help"><title>Eclipse Help Platform</title>
<refentry version="5.0" xml:id="eclipse.autolabel">
<refmeta>
<refentrytitle>eclipse.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>eclipse.autolabel</refname>
<refpurpose>Should tree-like ToC use autonumbering feature?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="eclipse.autolabel.frag">
<xsl:param name="eclipse.autolabel" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If you want to include chapter and section numbers into ToC in
the left panel, set this parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="eclipse.plugin.name">
<refmeta>
<refentrytitle>eclipse.plugin.name</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>eclipse.plugin.name</refname>
<refpurpose>Eclipse Help plugin name</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="eclipse.plugin.name.frag">
<xsl:param name="eclipse.plugin.name">DocBook Online Help Sample</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Eclipse Help plugin name.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="eclipse.plugin.id">
<refmeta>
<refentrytitle>eclipse.plugin.id</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>eclipse.plugin.id</refname>
<refpurpose>Eclipse Help plugin id</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="eclipse.plugin.id.frag">
<xsl:param name="eclipse.plugin.id">com.example.help</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Eclipse Help plugin id. You should change this id to something
unique for each help.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="eclipse.plugin.provider">
<refmeta>
<refentrytitle>eclipse.plugin.provider</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>eclipse.plugin.provider</refname>
<refpurpose>Eclipse Help plugin provider name</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="eclipse.plugin.provider.frag">
<xsl:param name="eclipse.plugin.provider">Example provider</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Eclipse Help plugin provider name.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="webhelp"><title>WebHelp</title>
<refentry version="5.0" xml:id="webhelp.autolabel">
<refmeta>
<refentrytitle>webhelp.autolabel</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.autolabel</refname>
<refpurpose>Should tree-like ToC use autonumbering feature?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.autolabel.frag">
<xsl:param name="webhelp.autolabel">0</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>To include chapter and section numbers the table of contents pane, set this parameter to 1.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.base.dir">
<refmeta>
<refentrytitle>webhelp.base.dir</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.base.dir</refname>
<refpurpose>The base directory for webhelp output.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.base.dir.frag">
<xsl:param name="webhelp.base.dir">docs</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If specified, the <parameter>webhelp.base.dir</parameter>
parameter identifies the output directory for webhelp. (If not
specified, the output directory is system dependent.) By default, this
parameter is set to <filename>docs</filename>.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.common.dir">
<refmeta>
<refentrytitle>webhelp.common.dir</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.common.dir</refname>
<refpurpose>Path to the directory for the common webhelp resources (JavaScript, css, common images, etc).</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.common.dir.frag">
<xsl:param name="webhelp.common.dir">../common/</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>By default, webhelp creates a common directory containing resources such as JavaScript files, css, common images, etc. In some cases you may prefer to store these files in a standard location on your site and point all webhelp documents to that location. You can use this parameter to control the urls written to these common resources. For example, you might set this parameter to <code>/common</code> and create a single common directory at the root of your web server. </para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.default.topic">
<refmeta>
<refentrytitle>webhelp.default.topic</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.default.topic</refname>
<refpurpose>The name of the file to which the start file in the webhelp base directory redirects</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.default.topic.frag">
<xsl:param name="webhelp.default.topic">index.html</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Currently webhelp creates a base directory and puts the output
files in a <filename>content</filename> subdirectory. It creates a
file in the base directory that redirects to a configured file in the
<filename>content</filename> directory. The
<parameter>webhelp.default.topic</parameter> parameter lets you
configure the name of the file that is redirected to.
<note>
<para>This parameter will be removed from a future version of
webhelp along with the <filename>content</filename>
directory.</para>
</note>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.include.search.tab">
<refmeta>
<refentrytitle>webhelp.include.search.tab</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.include.search.tab</refname>
<refpurpose>Should the webhelp output include a Search tab?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.include.search.tab.frag">
<xsl:param name="webhelp.include.search.tab">1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Set this parameter to 0 to suppress the search tab from webhelp output.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.indexer.language">
<refmeta>
<refentrytitle>webhelp.indexer.language</refentrytitle>
<refmiscinfo class="other" otherclass="datatype"/>
</refmeta>
<refnamediv>
<refname>webhelp.indexer.language</refname>
<refpurpose>The language to use for creating the webhelp search index.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.indexer.language.frag">
<xsl:param name="webhelp.indexer.language">en</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>To support stemming in the client-side webhelp stemmer, you must provide the language code. By default, the following languages are supported:
<itemizedlist>
<listitem>
<para><code>en</code>: English</para>
</listitem>
<listitem>
<para><code>de</code>: German</para>
</listitem>
<listitem>
<para><code>fr</code>: French</para>
</listitem>
<listitem>
<para><code>zh</code>: Chinese</para>
</listitem>
<listitem>
<para><code>ja</code>: Japanese</para>
</listitem>
<listitem>
<para><code>ko</code>: Korean</para>
</listitem>
</itemizedlist>
See the webhelp documentation for information on adding support for additional languages.
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.start.filename">
<refmeta>
<refentrytitle>webhelp.start.filename</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.start.filename</refname>
<refpurpose>The name of the start file in the webhelp base directory.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.start.filename.frag">
<xsl:param name="webhelp.start.filename">index.html</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Currently webhelp creates a base directory and puts the output
files in a <filename>content</filename> subdirectory. It creates a
file in the base directory that redirects to a configured file in the
<filename>content</filename> directory. The <parameter>webhelp.start.filename</parameter> parameter lets you configure the name of the redirect file.
<note>
<para>This parameter will be removed from a future version of
webhelp along with the <filename>content</filename>
directory.</para>
</note>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="webhelp.tree.cookie.id">
<refmeta>
<refentrytitle>webhelp.tree.cookie.id</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>webhelp.tree.cookie.id</refname>
<refpurpose>Controls how the cookie that stores the webhelp toc state is named.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="webhelp.tree.cookie.id.frag">
<xsl:param name="webhelp.tree.cookie.id" select="concat( 'treeview-', count(//node()) )"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The webhelp output does not use a frameset. Instead, the table of contents is a div on each page. To preserve the state of the table of contents as the user navigates from page to page, webhelp stores the state in a cookie and reads that cookie when you get to the next page. If you've published several webhelp documents on the same domain, it is important that each cookie have a unique id. In lieu of calling on a GUID generator, by default this parameter is just set to the number of nodes in the document on the assumption that it is unlikely that you will have more than one document with the exact number of nodes. A more optimal solution would be for the user to pass in some unique, stable identifier from the build system to use as the webhelp cookie id. For example, if you have safeguards in place to ensure that the xml:id of the root element of each document will be unique on your site, then you could set webhelptree.cookie.id as follows:
<programlisting>
<xsl:param name="webhelp.tree.cookie.id">
<xsl:choose>
<xsl:when test="/*/@xml:id">
<xsl:value-of select="concat('treeview-',/*/@xml:id)"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat( 'treeview-', count(//node()) )"/>
</xsl:otherwise>
</xsl:choose>
</xsl:param>
</programlisting>
</para>
</refsection>
</refentry>
</reference>
<reference xml:id="javahelp"><title>JavaHelp</title>
<refentry version="5.0" xml:id="javahelp.encoding">
<refmeta>
<refentrytitle>javahelp.encoding</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>javahelp.encoding</refname>
<refpurpose>Character encoding to use in control files for JavaHelp.</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="javahelp.encoding.frag">
<xsl:param name="javahelp.encoding">iso-8859-1</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>JavaHelp crashes on some characters when written as character
references. In that case you can use this parameter to select an appropriate encoding.</para>
</refsection>
</refentry>
</reference>
<reference xml:id="l10n"><title>Localization</title>
<refentry version="5.0" xml:id="l10n.gentext.language">
<refmeta>
<refentrytitle>l10n.gentext.language</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>l10n.gentext.language</refname>
<refpurpose>Sets the gentext language</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="l10n.gentext.language.frag">
<xsl:param name="l10n.gentext.language"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If this parameter is set to any value other than the empty string, its
value will be used as the value for the language when generating text. Setting
<parameter>l10n.gentext.language</parameter> overrides any settings within the
document being formatted.</para>
<para>It's much more likely that you might want to set the
<parameter>l10n.gentext.default.language</parameter> parameter.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="l10n.gentext.default.language">
<refmeta>
<refentrytitle>l10n.gentext.default.language</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>l10n.gentext.default.language</refname>
<refpurpose>Sets the default language for generated text</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="l10n.gentext.default.language.frag">
<xsl:param name="l10n.gentext.default.language">en</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>The value of the <parameter>l10n.gentext.default.language</parameter>
parameter is used as the language for generated text if no setting is provided
in the source document.</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="l10n.gentext.use.xref.language">
<refmeta>
<refentrytitle>l10n.gentext.use.xref.language</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>l10n.gentext.use.xref.language</refname>
<refpurpose>Use the language of target when generating cross-reference text?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="l10n.gentext.use.xref.language.frag">
<xsl:param name="l10n.gentext.use.xref.language" select="0"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, the language of the target will be used when
generating cross reference text. Usually, the <quote>current</quote>
language is used when generating text (that is, the language of the
element that contains the cross-reference element). But setting this parameter
allows the language of the element <emphasis>pointed to</emphasis> to control
the generated text.</para>
<para>Consider the following example:</para>
<informalexample>
<programlisting><para lang="en">See also <xref linkend="chap3"/>.</para>
</programlisting>
</informalexample>
<para>Suppose that Chapter 3 happens to be written in German.
If <parameter>l10n.gentext.use.xref.language</parameter> is non-zero, the
resulting text will be something like this:</para>
<blockquote>
<para>See also Kapital 3.</para>
</blockquote>
<para>Where the more traditional rendering would be:</para>
<blockquote>
<para>See also Chapter 3.</para>
</blockquote>
</refsection>
</refentry>
<refentry version="5.0" xml:id="l10n.lang.value.rfc.compliant">
<refmeta>
<refentrytitle>l10n.lang.value.rfc.compliant</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>l10n.lang.value.rfc.compliant</refname>
<refpurpose>Make value of lang attribute RFC compliant?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="l10n.lang.value.rfc.compliant.frag">
<xsl:param name="l10n.lang.value.rfc.compliant" select="1"></xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>If non-zero, ensure that the values for all <tag class="attribute">lang</tag> attributes in HTML output are RFC
compliant<footnote><para>Section 8.1.1, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.w3.org/TR/REC-html40/struct/dirlang.html#h-8.1.1">Language Codes</link>, in the HTML 4.0 Recommendation states that:
<blockquote><para>[RFC1766] defines and explains the language codes
that must be used in HTML documents.</para>
<para>Briefly, language codes consist of a primary code and a possibly
empty series of subcodes:
<literallayout class="monospaced">language-code = primary-code ( "-" subcode )*</literallayout>
</para>
<para>And in RFC 1766, <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://www.ietf.org/rfc/rfc1766.txt">Tags for the Identification
of Languages</link>, the EBNF for "language tag" is given as:
<literallayout class="monospaced">Language-Tag = Primary-tag *( "-" Subtag )
Primary-tag = 1*8ALPHA
Subtag = 1*8ALPHA</literallayout>
</para>
</blockquote>
</para></footnote>.
by taking any underscore characters in any <tag class="attribute">lang</tag> values found in source documents, and
replacing them with hyphen characters in output HTML files. For
example, <literal>zh_CN</literal> in a source document becomes
<literal>zh-CN</literal> in the HTML output form that source.
<note>
<para>This parameter does not cause any case change in <tag class="attribute">lang</tag> values, because RFC 1766
explicitly states that all "language tags" (as it calls them) "are
to be treated as case insensitive".</para>
</note>
</para>
</refsection>
</refentry>
<refentry version="5.0" xml:id="writing.mode">
<refmeta>
<refentrytitle>writing.mode</refentrytitle>
<refmiscinfo class="other" otherclass="datatype">string</refmiscinfo>
</refmeta>
<refnamediv>
<refname>writing.mode</refname>
<refpurpose>Direction of text flow based on locale</refpurpose>
</refnamediv>
<refsynopsisdiv>
<programlisting xml:id="writing.mode.frag">
<xsl:param name="writing.mode">
<xsl:call-template name="gentext">
<xsl:with-param name="key">writing-mode</xsl:with-param>
<xsl:with-param name="lang">
<xsl:call-template name="l10n.language">
<xsl:with-param name="target" select="/*[1]"></xsl:with-param>
</xsl:call-template>
</xsl:with-param>
</xsl:call-template>
</xsl:param>
</programlisting>
</refsynopsisdiv>
<refsection><info><title>Description</title></info>
<para>Sets direction of text flow and text alignment based on locale.
The value is normally taken from the gentext file for the
lang attribute of the document's root element, using the
key name 'writing-mode' to look it up in the gentext file.
But this param can also be
set on the command line to override that gentext value.
</para>
<para>Accepted values are:
<variablelist>
<varlistentry>
<term>lr-tb</term>
<listitem>
<para>Left-to-right text flow in each line, lines stack top to bottom.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>rl-tb</term>
<listitem>
<para>Right-to-left text flow in each line, lines stack top to bottom.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>tb-rl</term>
<listitem>
<para>Top-to-bottom text flow in each vertical line, lines stack right to left.
Supported by only a few XSL-FO processors. Not supported in HTML output.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>lr</term>
<listitem>
<para>Shorthand for lr-tb.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>rl</term>
<listitem>
<para>Shorthand for rl-tb.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>tb</term>
<listitem>
<para>Shorthand for tb-rl.</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsection>
</refentry>
</reference>
<appendix xml:id="stylesheet"><title>The Stylesheet</title>
<para>The <filename>param.xsl</filename> stylesheet is just a wrapper
around all these parameters.</para>
<programlisting xml:id="top">
<!-- This file is generated from param.xweb -->
<xsl:stylesheet exclude-result-prefixes="src" version="1.0">
<!-- ********************************************************************
This file is part of the XSL DocBook Stylesheet distribution.
See ../README or http://cdn.docbook.org/release/xsl/current/ for
copyright and other information.
******************************************************************** -->
<src:fragref linkend="abstract.notitle.enabled.frag"></src:fragref>
<src:fragref linkend="activate.external.olinks.frag"></src:fragref>
<src:fragref linkend="admon.graphics.extension.frag"></src:fragref>
<src:fragref linkend="admon.graphics.frag"></src:fragref>
<src:fragref linkend="admon.graphics.path.frag"></src:fragref>
<src:fragref linkend="admon.style.frag"></src:fragref>
<src:fragref linkend="admon.textlabel.frag"></src:fragref>
<src:fragref linkend="annotate.toc.frag"></src:fragref>
<src:fragref linkend="annotation.css.frag"></src:fragref>
<src:fragref linkend="annotation.graphic.close.frag"></src:fragref>
<src:fragref linkend="annotation.graphic.open.frag"></src:fragref>
<src:fragref linkend="annotation.js.frag"></src:fragref>
<src:fragref linkend="annotation.support.frag"></src:fragref>
<src:fragref linkend="appendix.autolabel.frag"></src:fragref>
<src:fragref linkend="author.othername.in.middle.frag"></src:fragref>
<src:fragref linkend="autotoc.label.in.hyperlink.frag"></src:fragref>
<src:fragref linkend="autotoc.label.separator.frag"></src:fragref>
<src:fragref linkend="autolink.index.see.frag"></src:fragref>
<src:fragref linkend="base.dir.frag"></src:fragref>
<src:fragref linkend="biblioentry.item.separator.frag"></src:fragref>
<src:fragref linkend="bibliography.collection.frag"></src:fragref>
<src:fragref linkend="bibliography.numbered.frag"></src:fragref>
<src:fragref linkend="bibliography.style.frag"></src:fragref>
<src:fragref linkend="blurb.on.titlepage.enabled.frag"></src:fragref>
<src:fragref linkend="bridgehead.in.toc.frag"></src:fragref>
<src:fragref linkend="callout.defaultcolumn.frag"></src:fragref>
<src:fragref linkend="callout.graphics.extension.frag"></src:fragref>
<src:fragref linkend="callout.graphics.frag"></src:fragref>
<src:fragref linkend="callout.graphics.number.limit.frag"></src:fragref>
<src:fragref linkend="callout.graphics.path.frag"></src:fragref>
<src:fragref linkend="callout.list.table.frag"></src:fragref>
<src:fragref linkend="callout.unicode.frag"></src:fragref>
<src:fragref linkend="callout.unicode.number.limit.frag"></src:fragref>
<src:fragref linkend="callout.unicode.start.character.frag"></src:fragref>
<src:fragref linkend="callouts.extension.frag"></src:fragref>
<src:fragref linkend="chapter.autolabel.frag"></src:fragref>
<src:fragref linkend="chunk.append.frag"></src:fragref>
<src:fragref linkend="chunk.first.sections.frag"></src:fragref>
<src:fragref linkend="chunk.quietly.frag"></src:fragref>
<src:fragref linkend="chunk.section.depth.frag"></src:fragref>
<src:fragref linkend="chunk.separate.lots.frag"></src:fragref>
<src:fragref linkend="chunk.toc.frag"></src:fragref>
<src:fragref linkend="chunk.tocs.and.lots.frag"></src:fragref>
<src:fragref linkend="chunk.tocs.and.lots.has.title.frag"></src:fragref>
<src:fragref linkend="chunked.filename.prefix.frag"></src:fragref>
<src:fragref linkend="citerefentry.link.frag"></src:fragref>
<src:fragref linkend="collect.xref.targets.frag"></src:fragref>
<src:fragref linkend="component.label.includes.part.label.frag"></src:fragref>
<src:fragref linkend="contrib.inline.enabled.frag"></src:fragref>
<src:fragref linkend="css.decoration.frag"></src:fragref>
<src:fragref linkend="current.docid.frag"></src:fragref>
<src:fragref linkend="custom.css.source.frag"></src:fragref>
<src:fragref linkend="default.float.class.frag"></src:fragref>
<src:fragref linkend="default.image.width.frag"></src:fragref>
<src:fragref linkend="default.table.frame.frag"></src:fragref>
<src:fragref linkend="default.table.width.frag"></src:fragref>
<src:fragref linkend="docbook.css.link.frag"></src:fragref>
<src:fragref linkend="docbook.css.source.frag"></src:fragref>
<src:fragref linkend="draft.mode.frag"></src:fragref>
<src:fragref linkend="draft.watermark.image.frag"></src:fragref>
<src:fragref linkend="ebnf.assignment.frag"></src:fragref>
<src:fragref linkend="ebnf.statement.terminator.frag"></src:fragref>
<src:fragref linkend="ebnf.table.bgcolor.frag"></src:fragref>
<src:fragref linkend="ebnf.table.border.frag"></src:fragref>
<src:fragref linkend="eclipse.autolabel.frag"></src:fragref>
<src:fragref linkend="eclipse.plugin.id.frag"></src:fragref>
<src:fragref linkend="eclipse.plugin.name.frag"></src:fragref>
<src:fragref linkend="eclipse.plugin.provider.frag"></src:fragref>
<src:fragref linkend="editedby.enabled.frag"></src:fragref>
<src:fragref linkend="email.delimiters.enabled.frag"></src:fragref>
<src:fragref linkend="emphasis.propagates.style.frag"></src:fragref>
<src:fragref linkend="entry.propagates.style.frag"></src:fragref>
<src:fragref linkend="exsl.node.set.available.frag"></src:fragref>
<src:fragref linkend="firstterm.only.link.frag"></src:fragref>
<src:fragref linkend="footer.rule.frag"></src:fragref>
<src:fragref linkend="footnote.number.format.frag"></src:fragref>
<src:fragref linkend="footnote.number.symbols.frag"></src:fragref>
<src:fragref linkend="formal.procedures.frag"></src:fragref>
<src:fragref linkend="formal.title.placement.frag"></src:fragref>
<src:fragref linkend="funcsynopsis.decoration.frag"></src:fragref>
<src:fragref linkend="funcsynopsis.style.frag"></src:fragref>
<src:fragref linkend="function.parens.frag"></src:fragref>
<src:fragref linkend="generate.consistent.ids.frag"></src:fragref>
<src:fragref linkend="generate.css.header.frag"></src:fragref>
<src:fragref linkend="generate.id.attributes.frag"></src:fragref>
<src:fragref linkend="generate.index.frag"></src:fragref>
<src:fragref linkend="generate.legalnotice.link.frag"></src:fragref>
<src:fragref linkend="generate.manifest.frag"></src:fragref>
<src:fragref linkend="generate.meta.abstract.frag"></src:fragref>
<src:fragref linkend="generate.revhistory.link.frag"></src:fragref>
<src:fragref linkend="generate.section.toc.level.frag"></src:fragref>
<src:fragref linkend="generate.toc.frag"></src:fragref>
<src:fragref linkend="glossary.collection.frag"></src:fragref>
<src:fragref linkend="glossary.sort.frag"></src:fragref>
<src:fragref linkend="glossentry.show.acronym.frag"></src:fragref>
<src:fragref linkend="glossterm.auto.link.frag"></src:fragref>
<src:fragref linkend="graphic.default.extension.frag"></src:fragref>
<src:fragref linkend="graphicsize.extension.frag"></src:fragref>
<src:fragref linkend="graphicsize.use.img.src.path.frag"></src:fragref>
<src:fragref linkend="header.rule.frag"></src:fragref>
<src:fragref linkend="highlight.default.language.frag"></src:fragref>
<src:fragref linkend="highlight.source.frag"></src:fragref>
<src:fragref linkend="highlight.xslthl.config.frag"></src:fragref>
<src:fragref linkend="html.append.frag"></src:fragref>
<src:fragref linkend="html.base.frag"></src:fragref>
<src:fragref linkend="html.cellpadding.frag"></src:fragref>
<src:fragref linkend="html.cellspacing.frag"></src:fragref>
<src:fragref linkend="html.cleanup.frag"></src:fragref>
<src:fragref linkend="html.ext.frag"></src:fragref>
<src:fragref linkend="html.extra.head.links.frag"></src:fragref>
<src:fragref linkend="html.head.legalnotice.link.multiple.frag"></src:fragref>
<src:fragref linkend="html.head.legalnotice.link.types.frag"></src:fragref>
<src:fragref linkend="html.longdesc.frag"></src:fragref>
<src:fragref linkend="html.longdesc.link.frag"></src:fragref>
<src:fragref linkend="html.script.frag"></src:fragref>
<src:fragref linkend="html.script.type.frag"></src:fragref>
<src:fragref linkend="html.stylesheet.frag"></src:fragref>
<src:fragref linkend="html.stylesheet.type.frag"></src:fragref>
<src:fragref linkend="htmlhelp.alias.file.frag"></src:fragref>
<src:fragref linkend="htmlhelp.autolabel.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.back.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.forward.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.hideshow.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.home.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.home.url.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump1.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump1.title.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump1.url.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump2.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump2.title.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.jump2.url.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.locate.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.next.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.options.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.prev.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.print.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.refresh.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.stop.frag"></src:fragref>
<src:fragref linkend="htmlhelp.button.zoom.frag"></src:fragref>
<src:fragref linkend="htmlhelp.chm.frag"></src:fragref>
<src:fragref linkend="htmlhelp.default.topic.frag"></src:fragref>
<src:fragref linkend="htmlhelp.display.progress.frag"></src:fragref>
<src:fragref linkend="htmlhelp.encoding.frag"></src:fragref>
<src:fragref linkend="htmlhelp.enhanced.decompilation.frag"></src:fragref>
<src:fragref linkend="htmlhelp.enumerate.images.frag"></src:fragref>
<src:fragref linkend="htmlhelp.force.map.and.alias.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.binary.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.folders.instead.books.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.section.depth.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.show.root.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhc.width.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhk.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhp.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhp.tail.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhp.window.frag"></src:fragref>
<src:fragref linkend="htmlhelp.hhp.windows.frag"></src:fragref>
<src:fragref linkend="htmlhelp.map.file.frag"></src:fragref>
<src:fragref linkend="htmlhelp.only.frag"></src:fragref>
<src:fragref linkend="htmlhelp.remember.window.position.frag"></src:fragref>
<src:fragref linkend="htmlhelp.show.advanced.search.frag"></src:fragref>
<src:fragref linkend="htmlhelp.show.favorities.frag"></src:fragref>
<src:fragref linkend="htmlhelp.show.menu.frag"></src:fragref>
<src:fragref linkend="htmlhelp.show.toolbar.text.frag"></src:fragref>
<src:fragref linkend="htmlhelp.title.frag"></src:fragref>
<src:fragref linkend="htmlhelp.use.hhk.frag"></src:fragref>
<src:fragref linkend="htmlhelp.window.geometry.frag"></src:fragref>
<src:fragref linkend="id.warnings.frag"></src:fragref>
<src:fragref linkend="ignore.image.scaling.frag"></src:fragref>
<src:fragref linkend="img.src.path.frag"></src:fragref>
<src:fragref linkend="index.links.to.section.frag"></src:fragref>
<src:fragref linkend="index.method.frag"></src:fragref>
<src:fragref linkend="index.number.separator.frag"></src:fragref>
<src:fragref linkend="index.on.role.frag"></src:fragref>
<src:fragref linkend="index.on.type.frag"></src:fragref>
<src:fragref linkend="index.prefer.titleabbrev.frag"></src:fragref>
<src:fragref linkend="index.range.separator.frag"></src:fragref>
<src:fragref linkend="index.term.separator.frag"></src:fragref>
<src:fragref linkend="inherit.keywords.frag"></src:fragref>
<src:fragref linkend="insert.olink.page.number.frag"></src:fragref>
<src:fragref linkend="insert.olink.pdf.frag.frag"></src:fragref>
<src:fragref linkend="insert.xref.page.number.frag"></src:fragref>
<src:fragref linkend="insert.xref.page.number.para.frag"></src:fragref>
<src:fragref linkend="javahelp.encoding.frag"></src:fragref>
<src:fragref linkend="keep.relative.image.uris.frag"></src:fragref>
<src:fragref linkend="l10n.gentext.default.language.frag"></src:fragref>
<src:fragref linkend="l10n.gentext.language.frag"></src:fragref>
<src:fragref linkend="l10n.gentext.use.xref.language.frag"></src:fragref>
<src:fragref linkend="l10n.lang.value.rfc.compliant.frag"></src:fragref>
<src:fragref linkend="label.from.part.frag"></src:fragref>
<src:fragref linkend="linenumbering.everyNth.frag"></src:fragref>
<src:fragref linkend="linenumbering.extension.frag"></src:fragref>
<src:fragref linkend="linenumbering.separator.frag"></src:fragref>
<src:fragref linkend="linenumbering.width.frag"></src:fragref>
<src:fragref linkend="link.mailto.url.frag"></src:fragref>
<src:fragref linkend="make.clean.html.frag"></src:fragref>
<src:fragref linkend="make.graphic.viewport.frag"></src:fragref>
<src:fragref linkend="make.single.year.ranges.frag"></src:fragref>
<src:fragref linkend="make.valid.html.frag"></src:fragref>
<src:fragref linkend="make.year.ranges.frag"></src:fragref>
<src:fragref linkend="manifest.frag"></src:fragref>
<src:fragref linkend="manifest.in.base.dir.frag"></src:fragref>
<src:fragref linkend="manual.toc.frag"></src:fragref>
<src:fragref linkend="menuchoice.menu.separator.frag"></src:fragref>
<src:fragref linkend="menuchoice.separator.frag"></src:fragref>
<src:fragref linkend="navig.graphics.extension.frag"></src:fragref>
<src:fragref linkend="navig.graphics.frag"></src:fragref>
<src:fragref linkend="navig.graphics.path.frag"></src:fragref>
<src:fragref linkend="navig.showtitles.frag"></src:fragref>
<src:fragref linkend="nominal.image.depth.frag"></src:fragref>
<src:fragref linkend="nominal.image.width.frag"></src:fragref>
<src:fragref linkend="nominal.table.width.frag"></src:fragref>
<src:fragref linkend="olink.base.uri.frag"></src:fragref>
<src:fragref linkend="olink.debug.frag"></src:fragref>
<src:fragref linkend="olink.doctitle.frag"></src:fragref>
<src:fragref linkend="olink.lang.fallback.sequence.frag"></src:fragref>
<src:fragref linkend="olink.properties.frag"></src:fragref>
<src:fragref linkend="othercredit.like.author.enabled.frag"></src:fragref>
<src:fragref linkend="para.propagates.style.frag"></src:fragref>
<src:fragref linkend="part.autolabel.frag"></src:fragref>
<src:fragref linkend="phrase.propagates.style.frag"></src:fragref>
<src:fragref linkend="pixels.per.inch.frag"></src:fragref>
<src:fragref linkend="points.per.em.frag"></src:fragref>
<src:fragref linkend="preface.autolabel.frag"></src:fragref>
<src:fragref linkend="prefer.internal.olink.frag"></src:fragref>
<src:fragref linkend="preferred.mediaobject.role.frag"></src:fragref>
<src:fragref linkend="process.empty.source.toc.frag"></src:fragref>
<src:fragref linkend="process.source.toc.frag"></src:fragref>
<src:fragref linkend="profile.arch.frag"></src:fragref>
<src:fragref linkend="profile.attribute.frag"></src:fragref>
<src:fragref linkend="profile.audience.frag"></src:fragref>
<src:fragref linkend="profile.condition.frag"></src:fragref>
<src:fragref linkend="profile.conformance.frag"></src:fragref>
<src:fragref linkend="profile.lang.frag"></src:fragref>
<src:fragref linkend="profile.os.frag"></src:fragref>
<src:fragref linkend="profile.outputformat.frag"></src:fragref>
<src:fragref linkend="profile.revision.frag"></src:fragref>
<src:fragref linkend="profile.revisionflag.frag"></src:fragref>
<src:fragref linkend="profile.role.frag"></src:fragref>
<src:fragref linkend="profile.security.frag"></src:fragref>
<src:fragref linkend="profile.separator.frag"></src:fragref>
<src:fragref linkend="profile.status.frag"></src:fragref>
<src:fragref linkend="profile.userlevel.frag"></src:fragref>
<src:fragref linkend="profile.value.frag"></src:fragref>
<src:fragref linkend="profile.vendor.frag"></src:fragref>
<src:fragref linkend="profile.wordsize.frag"></src:fragref>
<src:fragref linkend="punct.honorific.frag"></src:fragref>
<src:fragref linkend="qanda.defaultlabel.frag"></src:fragref>
<src:fragref linkend="qanda.in.toc.frag"></src:fragref>
<src:fragref linkend="qanda.inherit.numeration.frag"></src:fragref>
<src:fragref linkend="qanda.nested.in.toc.frag"></src:fragref>
<src:fragref linkend="qandadiv.autolabel.frag"></src:fragref>
<src:fragref linkend="refclass.suppress.frag"></src:fragref>
<src:fragref linkend="refentry.generate.name.frag"></src:fragref>
<src:fragref linkend="refentry.generate.title.frag"></src:fragref>
<src:fragref linkend="refentry.separator.frag"></src:fragref>
<src:fragref linkend="refentry.xref.manvolnum.frag"></src:fragref>
<src:fragref linkend="reference.autolabel.frag"></src:fragref>
<src:fragref linkend="root.filename.frag"></src:fragref>
<src:fragref linkend="rootid.frag"></src:fragref>
<src:fragref linkend="runinhead.default.title.end.punct.frag"></src:fragref>
<src:fragref linkend="runinhead.title.end.punct.frag"></src:fragref>
<src:fragref linkend="section.autolabel.frag"></src:fragref>
<src:fragref linkend="section.autolabel.max.depth.frag"></src:fragref>
<src:fragref linkend="section.label.includes.component.label.frag"></src:fragref>
<src:fragref linkend="segmentedlist.as.table.frag"></src:fragref>
<src:fragref linkend="shade.verbatim.frag"></src:fragref>
<src:fragref linkend="shade.verbatim.style.frag"></src:fragref>
<src:fragref linkend="show.comments.frag"></src:fragref>
<src:fragref linkend="show.revisionflag.frag"></src:fragref>
<src:fragref linkend="simplesect.in.toc.frag"></src:fragref>
<src:fragref linkend="spacing.paras.frag"></src:fragref>
<src:fragref linkend="suppress.footer.navigation.frag"></src:fragref>
<src:fragref linkend="suppress.header.navigation.frag"></src:fragref>
<src:fragref linkend="suppress.navigation.frag"></src:fragref>
<src:fragref linkend="table.borders.with.css.frag"></src:fragref>
<src:fragref linkend="table.cell.border.color.frag"></src:fragref>
<src:fragref linkend="table.cell.border.style.frag"></src:fragref>
<src:fragref linkend="table.cell.border.thickness.frag"></src:fragref>
<src:fragref linkend="table.footnote.number.format.frag"></src:fragref>
<src:fragref linkend="table.footnote.number.symbols.frag"></src:fragref>
<src:fragref linkend="table.frame.border.color.frag"></src:fragref>
<src:fragref linkend="table.frame.border.style.frag"></src:fragref>
<src:fragref linkend="table.frame.border.thickness.frag"></src:fragref>
<src:fragref linkend="tablecolumns.extension.frag"></src:fragref>
<src:fragref linkend="target.database.document.frag"></src:fragref>
<src:fragref linkend="targets.filename.frag"></src:fragref>
<src:fragref linkend="tex.math.delims.frag"></src:fragref>
<src:fragref linkend="tex.math.file.frag"></src:fragref>
<src:fragref linkend="tex.math.in.alt.frag"></src:fragref>
<src:fragref linkend="textdata.default.encoding.frag"></src:fragref>
<src:fragref linkend="textinsert.extension.frag"></src:fragref>
<src:fragref linkend="toc.list.type.frag"></src:fragref>
<src:fragref linkend="toc.max.depth.frag"></src:fragref>
<src:fragref linkend="toc.section.depth.frag"></src:fragref>
<src:fragref linkend="ulink.target.frag"></src:fragref>
<src:fragref linkend="use.embed.for.svg.frag"></src:fragref>
<src:fragref linkend="use.extensions.frag"></src:fragref>
<src:fragref linkend="use.id.as.filename.frag"></src:fragref>
<src:fragref linkend="use.local.olink.style.frag"></src:fragref>
<src:fragref linkend="use.role.as.xrefstyle.frag"></src:fragref>
<src:fragref linkend="use.role.for.mediaobject.frag"></src:fragref>
<src:fragref linkend="use.svg.frag"></src:fragref>
<src:fragref linkend="variablelist.as.table.frag"></src:fragref>
<src:fragref linkend="variablelist.term.break.after.frag"></src:fragref>
<src:fragref linkend="variablelist.term.separator.frag"></src:fragref>
<src:fragref linkend="webhelp.autolabel.frag"></src:fragref>
<src:fragref linkend="webhelp.base.dir.frag"></src:fragref>
<src:fragref linkend="webhelp.common.dir.frag"></src:fragref>
<src:fragref linkend="webhelp.default.topic.frag"></src:fragref>
<src:fragref linkend="webhelp.include.search.tab.frag"></src:fragref>
<src:fragref linkend="webhelp.indexer.language.frag"></src:fragref>
<src:fragref linkend="webhelp.start.filename.frag"></src:fragref>
<src:fragref linkend="webhelp.tree.cookie.id.frag"></src:fragref>
<src:fragref linkend="writing.mode.frag"></src:fragref>
<src:fragref linkend="xref.label-page.separator.frag"></src:fragref>
<src:fragref linkend="xref.label-title.separator.frag"></src:fragref>
<src:fragref linkend="xref.title-page.separator.frag"></src:fragref>
<src:fragref linkend="xref.with.number.and.title.frag"></src:fragref>
<src:fragref linkend="link.to.self.for.mediaobject.frag"></src:fragref>
</xsl:stylesheet>
</programlisting>
</appendix>
</book>
|