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
|
'\" t
.\" Automatically generated by Pandoc 2.14.0.1
.\"
.TH "Pandoc User\[cq]s Guide" "" "June 20, 2021" "pandoc 2.14.0.3" ""
.hy
.SH NAME
pandoc - general markup converter
.SH SYNOPSIS
.PP
\f[C]pandoc\f[R] [\f[I]options\f[R]] [\f[I]input-file\f[R]]\&...
.SH DESCRIPTION
.PP
Pandoc is a Haskell library for converting from one markup format to
another, and a command-line tool that uses this library.
.PP
Pandoc can convert between numerous markup and word processing formats,
including, but not limited to, various flavors of Markdown, HTML, LaTeX
and Word docx.
For the full lists of input and output formats, see the \f[C]--from\f[R]
and \f[C]--to\f[R] options below.
Pandoc can also produce PDF output: see creating a PDF, below.
.PP
Pandoc\[cq]s enhanced version of Markdown includes syntax for tables,
definition lists, metadata blocks, footnotes, citations, math, and much
more.
See below under Pandoc\[cq]s Markdown.
.PP
Pandoc has a modular design: it consists of a set of readers, which
parse text in a given format and produce a native representation of the
document (an \f[I]abstract syntax tree\f[R] or AST), and a set of
writers, which convert this native representation into a target format.
Thus, adding an input or output format requires only adding a reader or
writer.
Users can also run custom pandoc filters to modify the intermediate AST.
.PP
Because pandoc\[cq]s intermediate representation of a document is less
expressive than many of the formats it converts between, one should not
expect perfect conversions between every format and every other.
Pandoc attempts to preserve the structural elements of a document, but
not formatting details such as margin size.
And some document elements, such as complex tables, may not fit into
pandoc\[cq]s simple document model.
While conversions from pandoc\[cq]s Markdown to all formats aspire to be
perfect, conversions from formats more expressive than pandoc\[cq]s
Markdown can be expected to be lossy.
.SS Using pandoc
.PP
If no \f[I]input-files\f[R] are specified, input is read from
\f[I]stdin\f[R].
Output goes to \f[I]stdout\f[R] by default.
For output to a file, use the \f[C]-o\f[R] option:
.IP
.nf
\f[C]
pandoc -o output.html input.txt
\f[R]
.fi
.PP
By default, pandoc produces a document fragment.
To produce a standalone document (e.g.\ a valid HTML file including
\f[C]<head>\f[R] and \f[C]<body>\f[R]), use the \f[C]-s\f[R] or
\f[C]--standalone\f[R] flag:
.IP
.nf
\f[C]
pandoc -s -o output.html input.txt
\f[R]
.fi
.PP
For more information on how standalone documents are produced, see
Templates below.
.PP
If multiple input files are given, \f[C]pandoc\f[R] will concatenate
them all (with blank lines between them) before parsing.
(Use \f[C]--file-scope\f[R] to parse files individually.)
.SS Specifying formats
.PP
The format of the input and output can be specified explicitly using
command-line options.
The input format can be specified using the \f[C]-f/--from\f[R] option,
the output format using the \f[C]-t/--to\f[R] option.
Thus, to convert \f[C]hello.txt\f[R] from Markdown to LaTeX, you could
type:
.IP
.nf
\f[C]
pandoc -f markdown -t latex hello.txt
\f[R]
.fi
.PP
To convert \f[C]hello.html\f[R] from HTML to Markdown:
.IP
.nf
\f[C]
pandoc -f html -t markdown hello.html
\f[R]
.fi
.PP
Supported input and output formats are listed below under Options (see
\f[C]-f\f[R] for input formats and \f[C]-t\f[R] for output formats).
You can also use \f[C]pandoc --list-input-formats\f[R] and
\f[C]pandoc --list-output-formats\f[R] to print lists of supported
formats.
.PP
If the input or output format is not specified explicitly,
\f[C]pandoc\f[R] will attempt to guess it from the extensions of the
filenames.
Thus, for example,
.IP
.nf
\f[C]
pandoc -o hello.tex hello.txt
\f[R]
.fi
.PP
will convert \f[C]hello.txt\f[R] from Markdown to LaTeX.
If no output file is specified (so that output goes to
\f[I]stdout\f[R]), or if the output file\[cq]s extension is unknown, the
output format will default to HTML.
If no input file is specified (so that input comes from
\f[I]stdin\f[R]), or if the input files\[cq] extensions are unknown, the
input format will be assumed to be Markdown.
.SS Character encoding
.PP
Pandoc uses the UTF-8 character encoding for both input and output.
If your local character encoding is not UTF-8, you should pipe input and
output through \f[C]iconv\f[R]:
.IP
.nf
\f[C]
iconv -t utf-8 input.txt | pandoc | iconv -f utf-8
\f[R]
.fi
.PP
Note that in some output formats (such as HTML, LaTeX, ConTeXt, RTF,
OPML, DocBook, and Texinfo), information about the character encoding is
included in the document header, which will only be included if you use
the \f[C]-s/--standalone\f[R] option.
.SS Creating a PDF
.PP
To produce a PDF, specify an output file with a \f[C].pdf\f[R]
extension:
.IP
.nf
\f[C]
pandoc test.txt -o test.pdf
\f[R]
.fi
.PP
By default, pandoc will use LaTeX to create the PDF, which requires that
a LaTeX engine be installed (see \f[C]--pdf-engine\f[R] below).
Alternatively, pandoc can use ConTeXt, roff ms, or HTML as an
intermediate format.
To do this, specify an output file with a \f[C].pdf\f[R] extension, as
before, but add the \f[C]--pdf-engine\f[R] option or
\f[C]-t context\f[R], \f[C]-t html\f[R], or \f[C]-t ms\f[R] to the
command line.
The tool used to generate the PDF from the intermediate format may be
specified using \f[C]--pdf-engine\f[R].
.PP
You can control the PDF style using variables, depending on the
intermediate format used: see variables for LaTeX, variables for
ConTeXt, variables for \f[C]wkhtmltopdf\f[R], variables for ms.
When HTML is used as an intermediate format, the output can be styled
using \f[C]--css\f[R].
.PP
To debug the PDF creation, it can be useful to look at the intermediate
representation: instead of \f[C]-o test.pdf\f[R], use for example
\f[C]-s -o test.tex\f[R] to output the generated LaTeX.
You can then test it with \f[C]pdflatex test.tex\f[R].
.PP
When using LaTeX, the following packages need to be available (they are
included with all recent versions of TeX Live): \f[C]amsfonts\f[R],
\f[C]amsmath\f[R], \f[C]lm\f[R], \f[C]unicode-math\f[R],
\f[C]iftex\f[R], \f[C]listings\f[R] (if the \f[C]--listings\f[R] option
is used), \f[C]fancyvrb\f[R], \f[C]longtable\f[R], \f[C]booktabs\f[R],
\f[C]graphicx\f[R] (if the document contains images),
\f[C]hyperref\f[R], \f[C]xcolor\f[R], \f[C]ulem\f[R], \f[C]geometry\f[R]
(with the \f[C]geometry\f[R] variable set), \f[C]setspace\f[R] (with
\f[C]linestretch\f[R]), and \f[C]babel\f[R] (with \f[C]lang\f[R]).
The use of \f[C]xelatex\f[R] or \f[C]lualatex\f[R] as the PDF engine
requires \f[C]fontspec\f[R].
\f[C]lualatex\f[R] uses \f[C]selnolig\f[R].
\f[C]xelatex\f[R] uses \f[C]polyglossia\f[R] (with \f[C]lang\f[R]),
\f[C]xecjk\f[R], and \f[C]bidi\f[R] (with the \f[C]dir\f[R] variable
set).
If the \f[C]mathspec\f[R] variable is set, \f[C]xelatex\f[R] will use
\f[C]mathspec\f[R] instead of \f[C]unicode-math\f[R].
The \f[C]upquote\f[R] and \f[C]microtype\f[R] packages are used if
available, and \f[C]csquotes\f[R] will be used for typography if the
\f[C]csquotes\f[R] variable or metadata field is set to a true value.
The \f[C]natbib\f[R], \f[C]biblatex\f[R], \f[C]bibtex\f[R], and
\f[C]biber\f[R] packages can optionally be used for citation rendering.
The following packages will be used to improve output quality if
present, but pandoc does not require them to be present:
\f[C]upquote\f[R] (for straight quotes in verbatim environments),
\f[C]microtype\f[R] (for better spacing adjustments), \f[C]parskip\f[R]
(for better inter-paragraph spaces), \f[C]xurl\f[R] (for better line
breaks in URLs), \f[C]bookmark\f[R] (for better PDF bookmarks), and
\f[C]footnotehyper\f[R] or \f[C]footnote\f[R] (to allow footnotes in
tables).
.SS Reading from the Web
.PP
Instead of an input file, an absolute URI may be given.
In this case pandoc will fetch the content using HTTP:
.IP
.nf
\f[C]
pandoc -f html -t markdown https://www.fsf.org
\f[R]
.fi
.PP
It is possible to supply a custom User-Agent string or other header when
requesting a document from a URL:
.IP
.nf
\f[C]
pandoc -f html -t markdown --request-header User-Agent:\[dq]Mozilla/5.0\[dq] \[rs]
https://www.fsf.org
\f[R]
.fi
.SH OPTIONS
.SS General options
.TP
\f[B]\f[CB]-f\f[B]\f[R] \f[I]FORMAT\f[R], \f[B]\f[CB]-r\f[B]\f[R] \f[I]FORMAT\f[R], \f[B]\f[CB]--from=\f[B]\f[R]\f[I]FORMAT\f[R], \f[B]\f[CB]--read=\f[B]\f[R]\f[I]FORMAT\f[R]
Specify input format.
\f[I]FORMAT\f[R] can be:
.RS
.IP \[bu] 2
\f[C]bibtex\f[R] (BibTeX bibliography)
.IP \[bu] 2
\f[C]biblatex\f[R] (BibLaTeX bibliography)
.IP \[bu] 2
\f[C]commonmark\f[R] (CommonMark Markdown)
.IP \[bu] 2
\f[C]commonmark_x\f[R] (CommonMark Markdown with extensions)
.IP \[bu] 2
\f[C]creole\f[R] (Creole 1.0)
.IP \[bu] 2
\f[C]csljson\f[R] (CSL JSON bibliography)
.IP \[bu] 2
\f[C]csv\f[R] (CSV table)
.IP \[bu] 2
\f[C]docbook\f[R] (DocBook)
.IP \[bu] 2
\f[C]docx\f[R] (Word docx)
.IP \[bu] 2
\f[C]dokuwiki\f[R] (DokuWiki markup)
.IP \[bu] 2
\f[C]epub\f[R] (EPUB)
.IP \[bu] 2
\f[C]fb2\f[R] (FictionBook2 e-book)
.IP \[bu] 2
\f[C]gfm\f[R] (GitHub-Flavored Markdown), or the deprecated and less
accurate \f[C]markdown_github\f[R]; use \f[C]markdown_github\f[R] only
if you need extensions not supported in \f[C]gfm\f[R].
.IP \[bu] 2
\f[C]haddock\f[R] (Haddock markup)
.IP \[bu] 2
\f[C]html\f[R] (HTML)
.IP \[bu] 2
\f[C]ipynb\f[R] (Jupyter notebook)
.IP \[bu] 2
\f[C]jats\f[R] (JATS XML)
.IP \[bu] 2
\f[C]jira\f[R] (Jira/Confluence wiki markup)
.IP \[bu] 2
\f[C]json\f[R] (JSON version of native AST)
.IP \[bu] 2
\f[C]latex\f[R] (LaTeX)
.IP \[bu] 2
\f[C]markdown\f[R] (Pandoc\[cq]s Markdown)
.IP \[bu] 2
\f[C]markdown_mmd\f[R] (MultiMarkdown)
.IP \[bu] 2
\f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
.IP \[bu] 2
\f[C]markdown_strict\f[R] (original unextended Markdown)
.IP \[bu] 2
\f[C]mediawiki\f[R] (MediaWiki markup)
.IP \[bu] 2
\f[C]man\f[R] (roff man)
.IP \[bu] 2
\f[C]muse\f[R] (Muse)
.IP \[bu] 2
\f[C]native\f[R] (native Haskell)
.IP \[bu] 2
\f[C]odt\f[R] (ODT)
.IP \[bu] 2
\f[C]opml\f[R] (OPML)
.IP \[bu] 2
\f[C]org\f[R] (Emacs Org mode)
.IP \[bu] 2
\f[C]rst\f[R] (reStructuredText)
.IP \[bu] 2
\f[C]t2t\f[R] (txt2tags)
.IP \[bu] 2
\f[C]textile\f[R] (Textile)
.IP \[bu] 2
\f[C]tikiwiki\f[R] (TikiWiki markup)
.IP \[bu] 2
\f[C]twiki\f[R] (TWiki markup)
.IP \[bu] 2
\f[C]vimwiki\f[R] (Vimwiki)
.PP
Extensions can be individually enabled or disabled by appending
\f[C]+EXTENSION\f[R] or \f[C]-EXTENSION\f[R] to the format name.
See Extensions below, for a list of extensions and their names.
See \f[C]--list-input-formats\f[R] and \f[C]--list-extensions\f[R],
below.
.RE
.TP
\f[B]\f[CB]-t\f[B]\f[R] \f[I]FORMAT\f[R], \f[B]\f[CB]-w\f[B]\f[R] \f[I]FORMAT\f[R], \f[B]\f[CB]--to=\f[B]\f[R]\f[I]FORMAT\f[R], \f[B]\f[CB]--write=\f[B]\f[R]\f[I]FORMAT\f[R]
Specify output format.
\f[I]FORMAT\f[R] can be:
.RS
.IP \[bu] 2
\f[C]asciidoc\f[R] (AsciiDoc) or \f[C]asciidoctor\f[R] (AsciiDoctor)
.IP \[bu] 2
\f[C]beamer\f[R] (LaTeX beamer slide show)
.IP \[bu] 2
\f[C]bibtex\f[R] (BibTeX bibliography)
.IP \[bu] 2
\f[C]biblatex\f[R] (BibLaTeX bibliography)
.IP \[bu] 2
\f[C]commonmark\f[R] (CommonMark Markdown)
.IP \[bu] 2
\f[C]commonmark_x\f[R] (CommonMark Markdown with extensions)
.IP \[bu] 2
\f[C]context\f[R] (ConTeXt)
.IP \[bu] 2
\f[C]csljson\f[R] (CSL JSON bibliography)
.IP \[bu] 2
\f[C]docbook\f[R] or \f[C]docbook4\f[R] (DocBook 4)
.IP \[bu] 2
\f[C]docbook5\f[R] (DocBook 5)
.IP \[bu] 2
\f[C]docx\f[R] (Word docx)
.IP \[bu] 2
\f[C]dokuwiki\f[R] (DokuWiki markup)
.IP \[bu] 2
\f[C]epub\f[R] or \f[C]epub3\f[R] (EPUB v3 book)
.IP \[bu] 2
\f[C]epub2\f[R] (EPUB v2)
.IP \[bu] 2
\f[C]fb2\f[R] (FictionBook2 e-book)
.IP \[bu] 2
\f[C]gfm\f[R] (GitHub-Flavored Markdown), or the deprecated and less
accurate \f[C]markdown_github\f[R]; use \f[C]markdown_github\f[R] only
if you need extensions not supported in \f[C]gfm\f[R].
.IP \[bu] 2
\f[C]haddock\f[R] (Haddock markup)
.IP \[bu] 2
\f[C]html\f[R] or \f[C]html5\f[R] (HTML, i.e.\ HTML5/XHTML polyglot
markup)
.IP \[bu] 2
\f[C]html4\f[R] (XHTML 1.0 Transitional)
.IP \[bu] 2
\f[C]icml\f[R] (InDesign ICML)
.IP \[bu] 2
\f[C]ipynb\f[R] (Jupyter notebook)
.IP \[bu] 2
\f[C]jats_archiving\f[R] (JATS XML, Archiving and Interchange Tag Set)
.IP \[bu] 2
\f[C]jats_articleauthoring\f[R] (JATS XML, Article Authoring Tag Set)
.IP \[bu] 2
\f[C]jats_publishing\f[R] (JATS XML, Journal Publishing Tag Set)
.IP \[bu] 2
\f[C]jats\f[R] (alias for \f[C]jats_archiving\f[R])
.IP \[bu] 2
\f[C]jira\f[R] (Jira/Confluence wiki markup)
.IP \[bu] 2
\f[C]json\f[R] (JSON version of native AST)
.IP \[bu] 2
\f[C]latex\f[R] (LaTeX)
.IP \[bu] 2
\f[C]man\f[R] (roff man)
.IP \[bu] 2
\f[C]markdown\f[R] (Pandoc\[cq]s Markdown)
.IP \[bu] 2
\f[C]markdown_mmd\f[R] (MultiMarkdown)
.IP \[bu] 2
\f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
.IP \[bu] 2
\f[C]markdown_strict\f[R] (original unextended Markdown)
.IP \[bu] 2
\f[C]mediawiki\f[R] (MediaWiki markup)
.IP \[bu] 2
\f[C]ms\f[R] (roff ms)
.IP \[bu] 2
\f[C]muse\f[R] (Muse),
.IP \[bu] 2
\f[C]native\f[R] (native Haskell),
.IP \[bu] 2
\f[C]odt\f[R] (OpenOffice text document)
.IP \[bu] 2
\f[C]opml\f[R] (OPML)
.IP \[bu] 2
\f[C]opendocument\f[R] (OpenDocument)
.IP \[bu] 2
\f[C]org\f[R] (Emacs Org mode)
.IP \[bu] 2
\f[C]pdf\f[R] (PDF)
.IP \[bu] 2
\f[C]plain\f[R] (plain text),
.IP \[bu] 2
\f[C]pptx\f[R] (PowerPoint slide show)
.IP \[bu] 2
\f[C]rst\f[R] (reStructuredText)
.IP \[bu] 2
\f[C]rtf\f[R] (Rich Text Format)
.IP \[bu] 2
\f[C]texinfo\f[R] (GNU Texinfo)
.IP \[bu] 2
\f[C]textile\f[R] (Textile)
.IP \[bu] 2
\f[C]slideous\f[R] (Slideous HTML and JavaScript slide show)
.IP \[bu] 2
\f[C]slidy\f[R] (Slidy HTML and JavaScript slide show)
.IP \[bu] 2
\f[C]dzslides\f[R] (DZSlides HTML5 + JavaScript slide show),
.IP \[bu] 2
\f[C]revealjs\f[R] (reveal.js HTML5 + JavaScript slide show)
.IP \[bu] 2
\f[C]s5\f[R] (S5 HTML and JavaScript slide show)
.IP \[bu] 2
\f[C]tei\f[R] (TEI Simple)
.IP \[bu] 2
\f[C]xwiki\f[R] (XWiki markup)
.IP \[bu] 2
\f[C]zimwiki\f[R] (ZimWiki markup)
.IP \[bu] 2
the path of a custom Lua writer, see Custom writers below
.PP
Note that \f[C]odt\f[R], \f[C]docx\f[R], \f[C]epub\f[R], and
\f[C]pdf\f[R] output will not be directed to \f[I]stdout\f[R] unless
forced with \f[C]-o -\f[R].
.PP
Extensions can be individually enabled or disabled by appending
\f[C]+EXTENSION\f[R] or \f[C]-EXTENSION\f[R] to the format name.
See Extensions below, for a list of extensions and their names.
See \f[C]--list-output-formats\f[R] and \f[C]--list-extensions\f[R],
below.
.RE
.TP
\f[B]\f[CB]-o\f[B]\f[R] \f[I]FILE\f[R], \f[B]\f[CB]--output=\f[B]\f[R]\f[I]FILE\f[R]
Write output to \f[I]FILE\f[R] instead of \f[I]stdout\f[R].
If \f[I]FILE\f[R] is \f[C]-\f[R], output will go to \f[I]stdout\f[R],
even if a non-textual format (\f[C]docx\f[R], \f[C]odt\f[R],
\f[C]epub2\f[R], \f[C]epub3\f[R]) is specified.
.TP
\f[B]\f[CB]--data-dir=\f[B]\f[R]\f[I]DIRECTORY\f[R]
Specify the user data directory to search for pandoc data files.
If this option is not specified, the default user data directory will be
used.
On *nix and macOS systems this will be the \f[C]pandoc\f[R] subdirectory
of the XDG data directory (by default, \f[C]$HOME/.local/share\f[R],
overridable by setting the \f[C]XDG_DATA_HOME\f[R] environment
variable).
If that directory does not exist and \f[C]$HOME/.pandoc\f[R] exists, it
will be used (for backwards compatibility).
On Windows the default user data directory is
\f[C]C:\[rs]Users\[rs]USERNAME\[rs]AppData\[rs]Roaming\[rs]pandoc\f[R].
You can find the default user data directory on your system by looking
at the output of \f[C]pandoc --version\f[R].
Data files placed in this directory (for example,
\f[C]reference.odt\f[R], \f[C]reference.docx\f[R], \f[C]epub.css\f[R],
\f[C]templates\f[R]) will override pandoc\[cq]s normal defaults.
.TP
\f[B]\f[CB]-d\f[B]\f[R] \f[I]FILE\f[R], \f[B]\f[CB]--defaults=\f[B]\f[R]\f[I]FILE\f[R]
Specify a set of default option settings.
\f[I]FILE\f[R] is a YAML file whose fields correspond to command-line
option settings.
All options for document conversion, including input and output files,
can be set using a defaults file.
The file will be searched for first in the working directory, and then
in the \f[C]defaults\f[R] subdirectory of the user data directory (see
\f[C]--data-dir\f[R]).
The \f[C].yaml\f[R] extension may be omitted.
See the section Default files for more information on the file format.
Settings from the defaults file may be overridden or extended by
subsequent options on the command line.
.TP
\f[B]\f[CB]--bash-completion\f[B]\f[R]
Generate a bash completion script.
To enable bash completion with pandoc, add this to your
\f[C].bashrc\f[R]:
.RS
.IP
.nf
\f[C]
eval \[dq]$(pandoc --bash-completion)\[dq]
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]--verbose\f[B]\f[R]
Give verbose debugging output.
.TP
\f[B]\f[CB]--quiet\f[B]\f[R]
Suppress warning messages.
.TP
\f[B]\f[CB]--fail-if-warnings\f[B]\f[R]
Exit with error status if there are any warnings.
.TP
\f[B]\f[CB]--log=\f[B]\f[R]\f[I]FILE\f[R]
Write log messages in machine-readable JSON format to \f[I]FILE\f[R].
All messages above DEBUG level will be written, regardless of verbosity
settings (\f[C]--verbose\f[R], \f[C]--quiet\f[R]).
.TP
\f[B]\f[CB]--list-input-formats\f[B]\f[R]
List supported input formats, one per line.
.TP
\f[B]\f[CB]--list-output-formats\f[B]\f[R]
List supported output formats, one per line.
.TP
\f[B]\f[CB]--list-extensions\f[B]\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]FORMAT\f[R]]
List supported extensions for \f[I]FORMAT\f[R], one per line, preceded
by a \f[C]+\f[R] or \f[C]-\f[R] indicating whether it is enabled by
default in \f[I]FORMAT\f[R].
If \f[I]FORMAT\f[R] is not specified, defaults for pandoc\[cq]s Markdown
are given.
.TP
\f[B]\f[CB]--list-highlight-languages\f[B]\f[R]
List supported languages for syntax highlighting, one per line.
.TP
\f[B]\f[CB]--list-highlight-styles\f[B]\f[R]
List supported styles for syntax highlighting, one per line.
See \f[C]--highlight-style\f[R].
.TP
\f[B]\f[CB]-v\f[B]\f[R], \f[B]\f[CB]--version\f[B]\f[R]
Print version.
.TP
\f[B]\f[CB]-h\f[B]\f[R], \f[B]\f[CB]--help\f[B]\f[R]
Show usage message.
.SS Reader options
.TP
\f[B]\f[CB]--shift-heading-level-by=\f[B]\f[R]\f[I]NUMBER\f[R]
Shift heading levels by a positive or negative integer.
For example, with \f[C]--shift-heading-level-by=-1\f[R], level 2
headings become level 1 headings, and level 3 headings become level 2
headings.
Headings cannot have a level less than 1, so a heading that would be
shifted below level 1 becomes a regular paragraph.
Exception: with a shift of -N, a level-N heading at the beginning of the
document replaces the metadata title.
\f[C]--shift-heading-level-by=-1\f[R] is a good choice when converting
HTML or Markdown documents that use an initial level-1 heading for the
document title and level-2+ headings for sections.
\f[C]--shift-heading-level-by=1\f[R] may be a good choice for converting
Markdown documents that use level-1 headings for sections to HTML, since
pandoc uses a level-1 heading to render the document title.
.TP
\f[B]\f[CB]--base-header-level=\f[B]\f[R]\f[I]NUMBER\f[R]
\f[I]Deprecated. Use \f[CI]--shift-heading-level-by\f[I]=X instead,
where X = NUMBER - 1.\f[R] Specify the base level for headings (defaults
to 1).
.TP
\f[B]\f[CB]--strip-empty-paragraphs\f[B]\f[R]
\f[I]Deprecated. Use the \f[CI]+empty_paragraphs\f[I] extension
instead.\f[R] Ignore paragraphs with no content.
This option is useful for converting word processing documents where
users have used empty paragraphs to create inter-paragraph space.
.TP
\f[B]\f[CB]--indented-code-classes=\f[B]\f[R]\f[I]CLASSES\f[R]
Specify classes to use for indented code blocks\[en]for example,
\f[C]perl,numberLines\f[R] or \f[C]haskell\f[R].
Multiple classes may be separated by spaces or commas.
.TP
\f[B]\f[CB]--default-image-extension=\f[B]\f[R]\f[I]EXTENSION\f[R]
Specify a default extension to use when image paths/URLs have no
extension.
This allows you to use the same source for formats that require
different kinds of images.
Currently this option only affects the Markdown and LaTeX readers.
.TP
\f[B]\f[CB]--file-scope\f[B]\f[R]
Parse each file individually before combining for multifile documents.
This will allow footnotes in different files with the same identifiers
to work as expected.
If this option is set, footnotes and links will not work across files.
Reading binary files (docx, odt, epub) implies \f[C]--file-scope\f[R].
.TP
\f[B]\f[CB]-F\f[B]\f[R] \f[I]PROGRAM\f[R], \f[B]\f[CB]--filter=\f[B]\f[R]\f[I]PROGRAM\f[R]
Specify an executable to be used as a filter transforming the pandoc AST
after the input is parsed and before the output is written.
The executable should read JSON from stdin and write JSON to stdout.
The JSON must be formatted like pandoc\[cq]s own JSON input and output.
The name of the output format will be passed to the filter as the first
argument.
Hence,
.RS
.IP
.nf
\f[C]
pandoc --filter ./caps.py -t latex
\f[R]
.fi
.PP
is equivalent to
.IP
.nf
\f[C]
pandoc -t json | ./caps.py latex | pandoc -f json -t latex
\f[R]
.fi
.PP
The latter form may be useful for debugging filters.
.PP
Filters may be written in any language.
\f[C]Text.Pandoc.JSON\f[R] exports \f[C]toJSONFilter\f[R] to facilitate
writing filters in Haskell.
Those who would prefer to write filters in python can use the module
\f[C]pandocfilters\f[R], installable from PyPI.
There are also pandoc filter libraries in PHP, perl, and
JavaScript/node.js.
.PP
In order of preference, pandoc will look for filters in
.IP "1." 3
a specified full or relative path (executable or non-executable)
.IP "2." 3
\f[C]$DATADIR/filters\f[R] (executable or non-executable) where
\f[C]$DATADIR\f[R] is the user data directory (see \f[C]--data-dir\f[R],
above).
.IP "3." 3
\f[C]$PATH\f[R] (executable only)
.PP
Filters, Lua-filters, and citeproc processing are applied in the order
specified on the command line.
.RE
.TP
\f[B]\f[CB]-L\f[B]\f[R] \f[I]SCRIPT\f[R], \f[B]\f[CB]--lua-filter=\f[B]\f[R]\f[I]SCRIPT\f[R]
Transform the document in a similar fashion as JSON filters (see
\f[C]--filter\f[R]), but use pandoc\[cq]s built-in Lua filtering system.
The given Lua script is expected to return a list of Lua filters which
will be applied in order.
Each Lua filter must contain element-transforming functions indexed by
the name of the AST element on which the filter function should be
applied.
.RS
.PP
The \f[C]pandoc\f[R] Lua module provides helper functions for element
creation.
It is always loaded into the script\[cq]s Lua environment.
.PP
See the Lua filters documentation for further details.
.PP
In order of preference, pandoc will look for Lua filters in
.IP "1." 3
a specified full or relative path
.IP "2." 3
\f[C]$DATADIR/filters\f[R] where \f[C]$DATADIR\f[R] is the user data
directory (see \f[C]--data-dir\f[R], above).
.PP
Filters, Lua filters, and citeproc processing are applied in the order
specified on the command line.
.RE
.TP
\f[B]\f[CB]-M\f[B]\f[R] \f[I]KEY\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]VAL\f[R]], \f[B]\f[CB]--metadata=\f[B]\f[R]\f[I]KEY\f[R][\f[B]\f[CB]:\f[B]\f[R]\f[I]VAL\f[R]]
Set the metadata field \f[I]KEY\f[R] to the value \f[I]VAL\f[R].
A value specified on the command line overrides a value specified in the
document using YAML metadata blocks.
Values will be parsed as YAML boolean or string values.
If no value is specified, the value will be treated as Boolean true.
Like \f[C]--variable\f[R], \f[C]--metadata\f[R] causes template
variables to be set.
But unlike \f[C]--variable\f[R], \f[C]--metadata\f[R] affects the
metadata of the underlying document (which is accessible from filters
and may be printed in some output formats) and metadata values will be
escaped when inserted into the template.
.TP
\f[B]\f[CB]--metadata-file=\f[B]\f[R]\f[I]FILE\f[R]
Read metadata from the supplied YAML (or JSON) file.
This option can be used with every input format, but string scalars in
the YAML file will always be parsed as Markdown.
Generally, the input will be handled the same as in YAML metadata
blocks.
This option can be used repeatedly to include multiple metadata files;
values in files specified later on the command line will be preferred
over those specified in earlier files.
Metadata values specified inside the document, or by using \f[C]-M\f[R],
overwrite values specified with this option.
.TP
\f[B]\f[CB]-p\f[B]\f[R], \f[B]\f[CB]--preserve-tabs\f[B]\f[R]
Preserve tabs instead of converting them to spaces.
(By default, pandoc converts tabs to spaces before parsing its input.)
Note that this will only affect tabs in literal code spans and code
blocks.
Tabs in regular text are always treated as spaces.
.TP
\f[B]\f[CB]--tab-stop=\f[B]\f[R]\f[I]NUMBER\f[R]
Specify the number of spaces per tab (default is 4).
.TP
\f[B]\f[CB]--track-changes=accept\f[B]\f[R]|\f[B]\f[CB]reject\f[B]\f[R]|\f[B]\f[CB]all\f[B]\f[R]
Specifies what to do with insertions, deletions, and comments produced
by the MS Word \[lq]Track Changes\[rq] feature.
\f[C]accept\f[R] (the default) processes all the insertions and
deletions.
\f[C]reject\f[R] ignores them.
Both \f[C]accept\f[R] and \f[C]reject\f[R] ignore comments.
\f[C]all\f[R] includes all insertions, deletions, and comments, wrapped
in spans with \f[C]insertion\f[R], \f[C]deletion\f[R],
\f[C]comment-start\f[R], and \f[C]comment-end\f[R] classes,
respectively.
The author and time of change is included.
\f[C]all\f[R] is useful for scripting: only accepting changes from a
certain reviewer, say, or before a certain date.
If a paragraph is inserted or deleted, \f[C]track-changes=all\f[R]
produces a span with the class
\f[C]paragraph-insertion\f[R]/\f[C]paragraph-deletion\f[R] before the
affected paragraph break.
This option only affects the docx reader.
.TP
\f[B]\f[CB]--extract-media=\f[B]\f[R]\f[I]DIR\f[R]
Extract images and other media contained in or linked from the source
document to the path \f[I]DIR\f[R], creating it if necessary, and adjust
the images references in the document so they point to the extracted
files.
Media are downloaded, read from the file system, or extracted from a
binary container (e.g.\ docx), as needed.
The original file paths are used if they are relative paths not
containing \f[C]..\f[R].
Otherwise filenames are constructed from the SHA1 hash of the contents.
.TP
\f[B]\f[CB]--abbreviations=\f[B]\f[R]\f[I]FILE\f[R]
Specifies a custom abbreviations file, with abbreviations one to a line.
If this option is not specified, pandoc will read the data file
\f[C]abbreviations\f[R] from the user data directory or fall back on a
system default.
To see the system default, use
\f[C]pandoc --print-default-data-file=abbreviations\f[R].
The only use pandoc makes of this list is in the Markdown reader.
Strings found in this list will be followed by a nonbreaking space, and
the period will not produce sentence-ending space in formats like LaTeX.
The strings may not contain spaces.
.SS General writer options
.TP
\f[B]\f[CB]-s\f[B]\f[R], \f[B]\f[CB]--standalone\f[B]\f[R]
Produce output with an appropriate header and footer (e.g.\ a standalone
HTML, LaTeX, TEI, or RTF file, not a fragment).
This option is set automatically for \f[C]pdf\f[R], \f[C]epub\f[R],
\f[C]epub3\f[R], \f[C]fb2\f[R], \f[C]docx\f[R], and \f[C]odt\f[R]
output.
For \f[C]native\f[R] output, this option causes metadata to be included;
otherwise, metadata is suppressed.
.TP
\f[B]\f[CB]--template=\f[B]\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Use the specified file as a custom template for the generated document.
Implies \f[C]--standalone\f[R].
See Templates, below, for a description of template syntax.
If no extension is specified, an extension corresponding to the writer
will be added, so that \f[C]--template=special\f[R] looks for
\f[C]special.html\f[R] for HTML output.
If the template is not found, pandoc will search for it in the
\f[C]templates\f[R] subdirectory of the user data directory (see
\f[C]--data-dir\f[R]).
If this option is not used, a default template appropriate for the
output format will be used (see \f[C]-D/--print-default-template\f[R]).
.TP
\f[B]\f[CB]-V\f[B]\f[R] \f[I]KEY\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]VAL\f[R]], \f[B]\f[CB]--variable=\f[B]\f[R]\f[I]KEY\f[R][\f[B]\f[CB]:\f[B]\f[R]\f[I]VAL\f[R]]
Set the template variable \f[I]KEY\f[R] to the value \f[I]VAL\f[R] when
rendering the document in standalone mode.
If no \f[I]VAL\f[R] is specified, the key will be given the value
\f[C]true\f[R].
.TP
\f[B]\f[CB]-D\f[B]\f[R] \f[I]FORMAT\f[R], \f[B]\f[CB]--print-default-template=\f[B]\f[R]\f[I]FORMAT\f[R]
Print the system default template for an output \f[I]FORMAT\f[R].
(See \f[C]-t\f[R] for a list of possible \f[I]FORMAT\f[R]s.) Templates
in the user data directory are ignored.
This option may be used with \f[C]-o\f[R]/\f[C]--output\f[R] to redirect
output to a file, but \f[C]-o\f[R]/\f[C]--output\f[R] must come before
\f[C]--print-default-template\f[R] on the command line.
.RS
.PP
Note that some of the default templates use partials, for example
\f[C]styles.html\f[R].
To print the partials, use \f[C]--print-default-data-file\f[R]: for
example, \f[C]--print-default-data-file=templates/styles.html\f[R].
.RE
.TP
\f[B]\f[CB]--print-default-data-file=\f[B]\f[R]\f[I]FILE\f[R]
Print a system default data file.
Files in the user data directory are ignored.
This option may be used with \f[C]-o\f[R]/\f[C]--output\f[R] to redirect
output to a file, but \f[C]-o\f[R]/\f[C]--output\f[R] must come before
\f[C]--print-default-data-file\f[R] on the command line.
.TP
\f[B]\f[CB]--eol=crlf\f[B]\f[R]|\f[B]\f[CB]lf\f[B]\f[R]|\f[B]\f[CB]native\f[B]\f[R]
Manually specify line endings: \f[C]crlf\f[R] (Windows), \f[C]lf\f[R]
(macOS/Linux/UNIX), or \f[C]native\f[R] (line endings appropriate to the
OS on which pandoc is being run).
The default is \f[C]native\f[R].
.TP
\f[B]\f[CB]--dpi\f[B]\f[R]=\f[I]NUMBER\f[R]
Specify the default dpi (dots per inch) value for conversion from pixels
to inch/centimeters and vice versa.
(Technically, the correct term would be ppi: pixels per inch.) The
default is 96dpi.
When images contain information about dpi internally, the encoded value
is used instead of the default specified by this option.
.TP
\f[B]\f[CB]--wrap=auto\f[B]\f[R]|\f[B]\f[CB]none\f[B]\f[R]|\f[B]\f[CB]preserve\f[B]\f[R]
Determine how text is wrapped in the output (the source code, not the
rendered version).
With \f[C]auto\f[R] (the default), pandoc will attempt to wrap lines to
the column width specified by \f[C]--columns\f[R] (default 72).
With \f[C]none\f[R], pandoc will not wrap lines at all.
With \f[C]preserve\f[R], pandoc will attempt to preserve the wrapping
from the source document (that is, where there are nonsemantic newlines
in the source, there will be nonsemantic newlines in the output as
well).
Automatic wrapping does not currently work in HTML output.
In \f[C]ipynb\f[R] output, this option affects wrapping of the contents
of markdown cells.
.TP
\f[B]\f[CB]--columns=\f[B]\f[R]\f[I]NUMBER\f[R]
Specify length of lines in characters.
This affects text wrapping in the generated source code (see
\f[C]--wrap\f[R]).
It also affects calculation of column widths for plain text tables (see
Tables below).
.TP
\f[B]\f[CB]--toc\f[B]\f[R], \f[B]\f[CB]--table-of-contents\f[B]\f[R]
Include an automatically generated table of contents (or, in the case of
\f[C]latex\f[R], \f[C]context\f[R], \f[C]docx\f[R], \f[C]odt\f[R],
\f[C]opendocument\f[R], \f[C]rst\f[R], or \f[C]ms\f[R], an instruction
to create one) in the output document.
This option has no effect unless \f[C]-s/--standalone\f[R] is used, and
it has no effect on \f[C]man\f[R], \f[C]docbook4\f[R],
\f[C]docbook5\f[R], or \f[C]jats\f[R] output.
.RS
.PP
Note that if you are producing a PDF via \f[C]ms\f[R], the table of
contents will appear at the beginning of the document, before the title.
If you would prefer it to be at the end of the document, use the option
\f[C]--pdf-engine-opt=--no-toc-relocation\f[R].
.RE
.TP
\f[B]\f[CB]--toc-depth=\f[B]\f[R]\f[I]NUMBER\f[R]
Specify the number of section levels to include in the table of
contents.
The default is 3 (which means that level-1, 2, and 3 headings will be
listed in the contents).
.TP
\f[B]\f[CB]--strip-comments\f[B]\f[R]
Strip out HTML comments in the Markdown or Textile source, rather than
passing them on to Markdown, Textile or HTML output as raw HTML.
This does not apply to HTML comments inside raw HTML blocks when the
\f[C]markdown_in_html_blocks\f[R] extension is not set.
.TP
\f[B]\f[CB]--no-highlight\f[B]\f[R]
Disables syntax highlighting for code blocks and inlines, even when a
language attribute is given.
.TP
\f[B]\f[CB]--highlight-style=\f[B]\f[R]\f[I]STYLE\f[R]|\f[I]FILE\f[R]
Specifies the coloring style to be used in highlighted source code.
Options are \f[C]pygments\f[R] (the default), \f[C]kate\f[R],
\f[C]monochrome\f[R], \f[C]breezeDark\f[R], \f[C]espresso\f[R],
\f[C]zenburn\f[R], \f[C]haddock\f[R], and \f[C]tango\f[R].
For more information on syntax highlighting in pandoc, see Syntax
highlighting, below.
See also \f[C]--list-highlight-styles\f[R].
.RS
.PP
Instead of a \f[I]STYLE\f[R] name, a JSON file with extension
\f[C].theme\f[R] may be supplied.
This will be parsed as a KDE syntax highlighting theme and (if valid)
used as the highlighting style.
.PP
To generate the JSON version of an existing style, use
\f[C]--print-highlight-style\f[R].
.RE
.TP
\f[B]\f[CB]--print-highlight-style=\f[B]\f[R]\f[I]STYLE\f[R]|\f[I]FILE\f[R]
Prints a JSON version of a highlighting style, which can be modified,
saved with a \f[C].theme\f[R] extension, and used with
\f[C]--highlight-style\f[R].
This option may be used with \f[C]-o\f[R]/\f[C]--output\f[R] to redirect
output to a file, but \f[C]-o\f[R]/\f[C]--output\f[R] must come before
\f[C]--print-highlight-style\f[R] on the command line.
.TP
\f[B]\f[CB]--syntax-definition=\f[B]\f[R]\f[I]FILE\f[R]
Instructs pandoc to load a KDE XML syntax definition file, which will be
used for syntax highlighting of appropriately marked code blocks.
This can be used to add support for new languages or to use altered
syntax definitions for existing languages.
This option may be repeated to add multiple syntax definitions.
.TP
\f[B]\f[CB]-H\f[B]\f[R] \f[I]FILE\f[R], \f[B]\f[CB]--include-in-header=\f[B]\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Include contents of \f[I]FILE\f[R], verbatim, at the end of the header.
This can be used, for example, to include special CSS or JavaScript in
HTML documents.
This option can be used repeatedly to include multiple files in the
header.
They will be included in the order specified.
Implies \f[C]--standalone\f[R].
.TP
\f[B]\f[CB]-B\f[B]\f[R] \f[I]FILE\f[R], \f[B]\f[CB]--include-before-body=\f[B]\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Include contents of \f[I]FILE\f[R], verbatim, at the beginning of the
document body (e.g.\ after the \f[C]<body>\f[R] tag in HTML, or the
\f[C]\[rs]begin{document}\f[R] command in LaTeX).
This can be used to include navigation bars or banners in HTML
documents.
This option can be used repeatedly to include multiple files.
They will be included in the order specified.
Implies \f[C]--standalone\f[R].
.TP
\f[B]\f[CB]-A\f[B]\f[R] \f[I]FILE\f[R], \f[B]\f[CB]--include-after-body=\f[B]\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Include contents of \f[I]FILE\f[R], verbatim, at the end of the document
body (before the \f[C]</body>\f[R] tag in HTML, or the
\f[C]\[rs]end{document}\f[R] command in LaTeX).
This option can be used repeatedly to include multiple files.
They will be included in the order specified.
Implies \f[C]--standalone\f[R].
.TP
\f[B]\f[CB]--resource-path=\f[B]\f[R]\f[I]SEARCHPATH\f[R]
List of paths to search for images and other resources.
The paths should be separated by \f[C]:\f[R] on Linux, UNIX, and macOS
systems, and by \f[C];\f[R] on Windows.
If \f[C]--resource-path\f[R] is not specified, the default resource path
is the working directory.
Note that, if \f[C]--resource-path\f[R] is specified, the working
directory must be explicitly listed or it will not be searched.
For example: \f[C]--resource-path=.:test\f[R] will search the working
directory and the \f[C]test\f[R] subdirectory, in that order.
This option can be used repeatedly.
Search path components that come later on the command line will be
searched before those that come earlier, so
\f[C]--resource-path foo:bar --resource-path baz:bim\f[R] is equivalent
to \f[C]--resource-path baz:bim:foo:bar\f[R].
.TP
\f[B]\f[CB]--request-header=\f[B]\f[R]\f[I]NAME\f[R]\f[B]\f[CB]:\f[B]\f[R]\f[I]VAL\f[R]
Set the request header \f[I]NAME\f[R] to the value \f[I]VAL\f[R] when
making HTTP requests (for example, when a URL is given on the command
line, or when resources used in a document must be downloaded).
If you\[cq]re behind a proxy, you also need to set the environment
variable \f[C]http_proxy\f[R] to \f[C]http://...\f[R].
.TP
\f[B]\f[CB]--no-check-certificate\f[B]\f[R]
Disable the certificate verification to allow access to unsecure HTTP
resources (for example when the certificate is no longer valid or self
signed).
.SS Options affecting specific writers
.TP
\f[B]\f[CB]--self-contained\f[B]\f[R]
Produce a standalone HTML file with no external dependencies, using
\f[C]data:\f[R] URIs to incorporate the contents of linked scripts,
stylesheets, images, and videos.
Implies \f[C]--standalone\f[R].
The resulting file should be \[lq]self-contained,\[rq] in the sense that
it needs no external files and no net access to be displayed properly by
a browser.
This option works only with HTML output formats, including
\f[C]html4\f[R], \f[C]html5\f[R], \f[C]html+lhs\f[R],
\f[C]html5+lhs\f[R], \f[C]s5\f[R], \f[C]slidy\f[R], \f[C]slideous\f[R],
\f[C]dzslides\f[R], and \f[C]revealjs\f[R].
Scripts, images, and stylesheets at absolute URLs will be downloaded;
those at relative URLs will be sought relative to the working directory
(if the first source file is local) or relative to the base URL (if the
first source file is remote).
Elements with the attribute \f[C]data-external=\[dq]1\[dq]\f[R] will be
left alone; the documents they link to will not be incorporated in the
document.
Limitation: resources that are loaded dynamically through JavaScript
cannot be incorporated; as a result, \f[C]--self-contained\f[R] does not
work with \f[C]--mathjax\f[R], and some advanced features (e.g.\ zoom or
speaker notes) may not work in an offline \[lq]self-contained\[rq]
\f[C]reveal.js\f[R] slide show.
.TP
\f[B]\f[CB]--html-q-tags\f[B]\f[R]
Use \f[C]<q>\f[R] tags for quotes in HTML.
(This option only has an effect if the \f[C]smart\f[R] extension is
enabled for the input format used.)
.TP
\f[B]\f[CB]--ascii\f[B]\f[R]
Use only ASCII characters in output.
Currently supported for XML and HTML formats (which use entities instead
of UTF-8 when this option is selected), CommonMark, gfm, and Markdown
(which use entities), roff ms (which use hexadecimal escapes), and to a
limited degree LaTeX (which uses standard commands for accented
characters when possible).
roff man output uses ASCII by default.
.TP
\f[B]\f[CB]--reference-links\f[B]\f[R]
Use reference-style links, rather than inline links, in writing Markdown
or reStructuredText.
By default inline links are used.
The placement of link references is affected by the
\f[C]--reference-location\f[R] option.
.TP
\f[B]\f[CB]--reference-location=block\f[B]\f[R]|\f[B]\f[CB]section\f[B]\f[R]|\f[B]\f[CB]document\f[B]\f[R]
Specify whether footnotes (and references, if \f[C]reference-links\f[R]
is set) are placed at the end of the current (top-level) block, the
current section, or the document.
The default is \f[C]document\f[R].
Currently only affects the markdown writer.
.TP
\f[B]\f[CB]--markdown-headings=setext\f[B]\f[R]|\f[B]\f[CB]atx\f[B]\f[R]
Specify whether to use ATX-style (\f[C]#\f[R]-prefixed) or Setext-style
(underlined) headings for level 1 and 2 headings in Markdown output.
(The default is \f[C]atx\f[R].) ATX-style headings are always used for
levels 3+.
This option also affects Markdown cells in \f[C]ipynb\f[R] output.
.TP
\f[B]\f[CB]--atx-headers\f[B]\f[R]
\f[I]Deprecated synonym for \f[CI]--markdown-headings=atx\f[I].\f[R]
.TP
\f[B]\f[CB]--top-level-division=default\f[B]\f[R]|\f[B]\f[CB]section\f[B]\f[R]|\f[B]\f[CB]chapter\f[B]\f[R]|\f[B]\f[CB]part\f[B]\f[R]
Treat top-level headings as the given division type in LaTeX, ConTeXt,
DocBook, and TEI output.
The hierarchy order is part, chapter, then section; all headings are
shifted such that the top-level heading becomes the specified type.
The default behavior is to determine the best division type via
heuristics: unless other conditions apply, \f[C]section\f[R] is chosen.
When the \f[C]documentclass\f[R] variable is set to \f[C]report\f[R],
\f[C]book\f[R], or \f[C]memoir\f[R] (unless the \f[C]article\f[R] option
is specified), \f[C]chapter\f[R] is implied as the setting for this
option.
If \f[C]beamer\f[R] is the output format, specifying either
\f[C]chapter\f[R] or \f[C]part\f[R] will cause top-level headings to
become \f[C]\[rs]part{..}\f[R], while second-level headings remain as
their default type.
.TP
\f[B]\f[CB]-N\f[B]\f[R], \f[B]\f[CB]--number-sections\f[B]\f[R]
Number section headings in LaTeX, ConTeXt, HTML, Docx, ms, or EPUB
output.
By default, sections are not numbered.
Sections with class \f[C]unnumbered\f[R] will never be numbered, even if
\f[C]--number-sections\f[R] is specified.
.TP
\f[B]\f[CB]--number-offset=\f[B]\f[R]\f[I]NUMBER\f[R][\f[B]\f[CB],\f[B]\f[R]\f[I]NUMBER\f[R]\f[B]\f[CB],\f[B]\f[R]\f[I]\&...\f[R]]
Offset for section headings in HTML output (ignored in other output
formats).
The first number is added to the section number for top-level headings,
the second for second-level headings, and so on.
So, for example, if you want the first top-level heading in your
document to be numbered \[lq]6\[rq], specify
\f[C]--number-offset=5\f[R].
If your document starts with a level-2 heading which you want to be
numbered \[lq]1.5\[rq], specify \f[C]--number-offset=1,4\f[R].
Offsets are 0 by default.
Implies \f[C]--number-sections\f[R].
.TP
\f[B]\f[CB]--listings\f[B]\f[R]
Use the \f[C]listings\f[R] package for LaTeX code blocks.
The package does not support multi-byte encoding for source code.
To handle UTF-8 you would need to use a custom template.
This issue is fully documented here: Encoding issue with the listings
package.
.TP
\f[B]\f[CB]-i\f[B]\f[R], \f[B]\f[CB]--incremental\f[B]\f[R]
Make list items in slide shows display incrementally (one by one).
The default is for lists to be displayed all at once.
.TP
\f[B]\f[CB]--slide-level=\f[B]\f[R]\f[I]NUMBER\f[R]
Specifies that headings with the specified level create slides (for
\f[C]beamer\f[R], \f[C]s5\f[R], \f[C]slidy\f[R], \f[C]slideous\f[R],
\f[C]dzslides\f[R]).
Headings above this level in the hierarchy are used to divide the slide
show into sections; headings below this level create subheads within a
slide.
Note that content that is not contained under slide-level headings will
not appear in the slide show.
The default is to set the slide level based on the contents of the
document; see Structuring the slide show.
.TP
\f[B]\f[CB]--section-divs\f[B]\f[R]
Wrap sections in \f[C]<section>\f[R] tags (or \f[C]<div>\f[R] tags for
\f[C]html4\f[R]), and attach identifiers to the enclosing
\f[C]<section>\f[R] (or \f[C]<div>\f[R]) rather than the heading itself.
See Heading identifiers, below.
.TP
\f[B]\f[CB]--email-obfuscation=none\f[B]\f[R]|\f[B]\f[CB]javascript\f[B]\f[R]|\f[B]\f[CB]references\f[B]\f[R]
Specify a method for obfuscating \f[C]mailto:\f[R] links in HTML
documents.
\f[C]none\f[R] leaves \f[C]mailto:\f[R] links as they are.
\f[C]javascript\f[R] obfuscates them using JavaScript.
\f[C]references\f[R] obfuscates them by printing their letters as
decimal or hexadecimal character references.
The default is \f[C]none\f[R].
.TP
\f[B]\f[CB]--id-prefix=\f[B]\f[R]\f[I]STRING\f[R]
Specify a prefix to be added to all identifiers and internal links in
HTML and DocBook output, and to footnote numbers in Markdown and Haddock
output.
This is useful for preventing duplicate identifiers when generating
fragments to be included in other pages.
.TP
\f[B]\f[CB]-T\f[B]\f[R] \f[I]STRING\f[R], \f[B]\f[CB]--title-prefix=\f[B]\f[R]\f[I]STRING\f[R]
Specify \f[I]STRING\f[R] as a prefix at the beginning of the title that
appears in the HTML header (but not in the title as it appears at the
beginning of the HTML body).
Implies \f[C]--standalone\f[R].
.TP
\f[B]\f[CB]-c\f[B]\f[R] \f[I]URL\f[R], \f[B]\f[CB]--css=\f[B]\f[R]\f[I]URL\f[R]
Link to a CSS style sheet.
This option can be used repeatedly to include multiple files.
They will be included in the order specified.
.RS
.PP
A stylesheet is required for generating EPUB.
If none is provided using this option (or the \f[C]css\f[R] or
\f[C]stylesheet\f[R] metadata fields), pandoc will look for a file
\f[C]epub.css\f[R] in the user data directory (see
\f[C]--data-dir\f[R]).
If it is not found there, sensible defaults will be used.
.RE
.TP
\f[B]\f[CB]--reference-doc=\f[B]\f[R]\f[I]FILE\f[R]
Use the specified file as a style reference in producing a docx or ODT
file.
.RS
.TP
Docx
For best results, the reference docx should be a modified version of a
docx file produced using pandoc.
The contents of the reference docx are ignored, but its stylesheets and
document properties (including margins, page size, header, and footer)
are used in the new docx.
If no reference docx is specified on the command line, pandoc will look
for a file \f[C]reference.docx\f[R] in the user data directory (see
\f[C]--data-dir\f[R]).
If this is not found either, sensible defaults will be used.
.RS
.PP
To produce a custom \f[C]reference.docx\f[R], first get a copy of the
default \f[C]reference.docx\f[R]:
\f[C]pandoc -o custom-reference.docx --print-default-data-file reference.docx\f[R].
Then open \f[C]custom-reference.docx\f[R] in Word, modify the styles as
you wish, and save the file.
For best results, do not make changes to this file other than modifying
the styles used by pandoc:
.PP
Paragraph styles:
.IP \[bu] 2
Normal
.IP \[bu] 2
Body Text
.IP \[bu] 2
First Paragraph
.IP \[bu] 2
Compact
.IP \[bu] 2
Title
.IP \[bu] 2
Subtitle
.IP \[bu] 2
Author
.IP \[bu] 2
Date
.IP \[bu] 2
Abstract
.IP \[bu] 2
Bibliography
.IP \[bu] 2
Heading 1
.IP \[bu] 2
Heading 2
.IP \[bu] 2
Heading 3
.IP \[bu] 2
Heading 4
.IP \[bu] 2
Heading 5
.IP \[bu] 2
Heading 6
.IP \[bu] 2
Heading 7
.IP \[bu] 2
Heading 8
.IP \[bu] 2
Heading 9
.IP \[bu] 2
Block Text
.IP \[bu] 2
Footnote Text
.IP \[bu] 2
Definition Term
.IP \[bu] 2
Definition
.IP \[bu] 2
Caption
.IP \[bu] 2
Table Caption
.IP \[bu] 2
Image Caption
.IP \[bu] 2
Figure
.IP \[bu] 2
Captioned Figure
.IP \[bu] 2
TOC Heading
.PP
Character styles:
.IP \[bu] 2
Default Paragraph Font
.IP \[bu] 2
Body Text Char
.IP \[bu] 2
Verbatim Char
.IP \[bu] 2
Footnote Reference
.IP \[bu] 2
Hyperlink
.IP \[bu] 2
Section Number
.PP
Table style:
.IP \[bu] 2
Table
.RE
.TP
ODT
For best results, the reference ODT should be a modified version of an
ODT produced using pandoc.
The contents of the reference ODT are ignored, but its stylesheets are
used in the new ODT.
If no reference ODT is specified on the command line, pandoc will look
for a file \f[C]reference.odt\f[R] in the user data directory (see
\f[C]--data-dir\f[R]).
If this is not found either, sensible defaults will be used.
.RS
.PP
To produce a custom \f[C]reference.odt\f[R], first get a copy of the
default \f[C]reference.odt\f[R]:
\f[C]pandoc -o custom-reference.odt --print-default-data-file reference.odt\f[R].
Then open \f[C]custom-reference.odt\f[R] in LibreOffice, modify the
styles as you wish, and save the file.
.RE
.TP
PowerPoint
Templates included with Microsoft PowerPoint 2013 (either with
\f[C].pptx\f[R] or \f[C].potx\f[R] extension) are known to work, as are
most templates derived from these.
.RS
.PP
The specific requirement is that the template should begin with the
following first four layouts:
.IP "1." 3
Title Slide
.IP "2." 3
Title and Content
.IP "3." 3
Section Header
.IP "4." 3
Two Content
.PP
All templates included with a recent version of MS PowerPoint will fit
these criteria.
(You can click on \f[C]Layout\f[R] under the \f[C]Home\f[R] menu to
check.)
.PP
You can also modify the default \f[C]reference.pptx\f[R]: first run
\f[C]pandoc -o custom-reference.pptx --print-default-data-file reference.pptx\f[R],
and then modify \f[C]custom-reference.pptx\f[R] in MS PowerPoint (pandoc
will use the first four layout slides, as mentioned above).
.RE
.RE
.TP
\f[B]\f[CB]--epub-cover-image=\f[B]\f[R]\f[I]FILE\f[R]
Use the specified image as the EPUB cover.
It is recommended that the image be less than 1000px in width and
height.
Note that in a Markdown source document you can also specify
\f[C]cover-image\f[R] in a YAML metadata block (see EPUB Metadata,
below).
.TP
\f[B]\f[CB]--epub-metadata=\f[B]\f[R]\f[I]FILE\f[R]
Look in the specified XML file for metadata for the EPUB.
The file should contain a series of Dublin Core elements.
For example:
.RS
.IP
.nf
\f[C]
<dc:rights>Creative Commons</dc:rights>
<dc:language>es-AR</dc:language>
\f[R]
.fi
.PP
By default, pandoc will include the following metadata elements:
\f[C]<dc:title>\f[R] (from the document title), \f[C]<dc:creator>\f[R]
(from the document authors), \f[C]<dc:date>\f[R] (from the document
date, which should be in ISO 8601 format), \f[C]<dc:language>\f[R] (from
the \f[C]lang\f[R] variable, or, if is not set, the locale), and
\f[C]<dc:identifier id=\[dq]BookId\[dq]>\f[R] (a randomly generated
UUID).
Any of these may be overridden by elements in the metadata file.
.PP
Note: if the source document is Markdown, a YAML metadata block in the
document can be used instead.
See below under EPUB Metadata.
.RE
.TP
\f[B]\f[CB]--epub-embed-font=\f[B]\f[R]\f[I]FILE\f[R]
Embed the specified font in the EPUB.
This option can be repeated to embed multiple fonts.
Wildcards can also be used: for example, \f[C]DejaVuSans-*.ttf\f[R].
However, if you use wildcards on the command line, be sure to escape
them or put the whole filename in single quotes, to prevent them from
being interpreted by the shell.
To use the embedded fonts, you will need to add declarations like the
following to your CSS (see \f[C]--css\f[R]):
.RS
.IP
.nf
\f[C]
\[at]font-face {
font-family: DejaVuSans;
font-style: normal;
font-weight: normal;
src:url(\[dq]DejaVuSans-Regular.ttf\[dq]);
}
\[at]font-face {
font-family: DejaVuSans;
font-style: normal;
font-weight: bold;
src:url(\[dq]DejaVuSans-Bold.ttf\[dq]);
}
\[at]font-face {
font-family: DejaVuSans;
font-style: italic;
font-weight: normal;
src:url(\[dq]DejaVuSans-Oblique.ttf\[dq]);
}
\[at]font-face {
font-family: DejaVuSans;
font-style: italic;
font-weight: bold;
src:url(\[dq]DejaVuSans-BoldOblique.ttf\[dq]);
}
body { font-family: \[dq]DejaVuSans\[dq]; }
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]--epub-chapter-level=\f[B]\f[R]\f[I]NUMBER\f[R]
Specify the heading level at which to split the EPUB into separate
\[lq]chapter\[rq] files.
The default is to split into chapters at level-1 headings.
This option only affects the internal composition of the EPUB, not the
way chapters and sections are displayed to users.
Some readers may be slow if the chapter files are too large, so for
large documents with few level-1 headings, one might want to use a
chapter level of 2 or 3.
.TP
\f[B]\f[CB]--epub-subdirectory=\f[B]\f[R]\f[I]DIRNAME\f[R]
Specify the subdirectory in the OCF container that is to hold the
EPUB-specific contents.
The default is \f[C]EPUB\f[R].
To put the EPUB contents in the top level, use an empty string.
.TP
\f[B]\f[CB]--ipynb-output=all|none|best\f[B]\f[R]
Determines how ipynb output cells are treated.
\f[C]all\f[R] means that all of the data formats included in the
original are preserved.
\f[C]none\f[R] means that the contents of data cells are omitted.
\f[C]best\f[R] causes pandoc to try to pick the richest data block in
each output cell that is compatible with the output format.
The default is \f[C]best\f[R].
.TP
\f[B]\f[CB]--pdf-engine=\f[B]\f[R]\f[I]PROGRAM\f[R]
Use the specified engine when producing PDF output.
Valid values are \f[C]pdflatex\f[R], \f[C]lualatex\f[R],
\f[C]xelatex\f[R], \f[C]latexmk\f[R], \f[C]tectonic\f[R],
\f[C]wkhtmltopdf\f[R], \f[C]weasyprint\f[R], \f[C]prince\f[R],
\f[C]context\f[R], and \f[C]pdfroff\f[R].
If the engine is not in your PATH, the full path of the engine may be
specified here.
If this option is not specified, pandoc uses the following defaults
depending on the output format specified using \f[C]-t/--to\f[R]:
.RS
.IP \[bu] 2
\f[C]-t latex\f[R] or none: \f[C]pdflatex\f[R] (other options:
\f[C]xelatex\f[R], \f[C]lualatex\f[R], \f[C]tectonic\f[R],
\f[C]latexmk\f[R])
.IP \[bu] 2
\f[C]-t context\f[R]: \f[C]context\f[R]
.IP \[bu] 2
\f[C]-t html\f[R]: \f[C]wkhtmltopdf\f[R] (other options:
\f[C]prince\f[R], \f[C]weasyprint\f[R]; see print-css.rocks for a good
introduction to PDF generation from HTML/CSS.)
.IP \[bu] 2
\f[C]-t ms\f[R]: \f[C]pdfroff\f[R]
.RE
.TP
\f[B]\f[CB]--pdf-engine-opt=\f[B]\f[R]\f[I]STRING\f[R]
Use the given string as a command-line argument to the
\f[C]pdf-engine\f[R].
For example, to use a persistent directory \f[C]foo\f[R] for
\f[C]latexmk\f[R]\[cq]s auxiliary files, use
\f[C]--pdf-engine-opt=-outdir=foo\f[R].
Note that no check for duplicate options is done.
.SS Citation rendering
.TP
\f[B]\f[CB]-C\f[B]\f[R], \f[B]\f[CB]--citeproc\f[B]\f[R]
Process the citations in the file, replacing them with rendered
citations and adding a bibliography.
Citation processing will not take place unless bibliographic data is
supplied, either through an external file specified using the
\f[C]--bibliography\f[R] option or the \f[C]bibliography\f[R] field in
metadata, or via a \f[C]references\f[R] section in metadata containing a
list of citations in CSL YAML format with Markdown formatting.
The style is controlled by a CSL stylesheet specified using the
\f[C]--csl\f[R] option or the \f[C]csl\f[R] field in metadata.
(If no stylesheet is specified, the \f[C]chicago-author-date\f[R] style
will be used by default.) The citation processing transformation may be
applied before or after filters or Lua filters (see \f[C]--filter\f[R],
\f[C]--lua-filter\f[R]): these transformations are applied in the order
they appear on the command line.
For more information, see the section on Citations.
.TP
\f[B]\f[CB]--bibliography=\f[B]\f[R]\f[I]FILE\f[R]
Set the \f[C]bibliography\f[R] field in the document\[cq]s metadata to
\f[I]FILE\f[R], overriding any value set in the metadata.
If you supply this argument multiple times, each \f[I]FILE\f[R] will be
added to bibliography.
If \f[I]FILE\f[R] is a URL, it will be fetched via HTTP.
If \f[I]FILE\f[R] is not found relative to the working directory, it
will be sought in the resource path (see \f[C]--resource-path\f[R]).
.TP
\f[B]\f[CB]--csl=\f[B]\f[R]\f[I]FILE\f[R]
Set the \f[C]csl\f[R] field in the document\[cq]s metadata to
\f[I]FILE\f[R], overriding any value set in the metadata.
(This is equivalent to \f[C]--metadata csl=FILE\f[R].) If \f[I]FILE\f[R]
is a URL, it will be fetched via HTTP.
If \f[I]FILE\f[R] is not found relative to the working directory, it
will be sought in the resource path (see \f[C]--resource-path\f[R]) and
finally in the \f[C]csl\f[R] subdirectory of the pandoc user data
directory.
.TP
\f[B]\f[CB]--citation-abbreviations=\f[B]\f[R]\f[I]FILE\f[R]
Set the \f[C]citation-abbreviations\f[R] field in the document\[cq]s
metadata to \f[I]FILE\f[R], overriding any value set in the metadata.
(This is equivalent to
\f[C]--metadata citation-abbreviations=FILE\f[R].) If \f[I]FILE\f[R] is
a URL, it will be fetched via HTTP.
If \f[I]FILE\f[R] is not found relative to the working directory, it
will be sought in the resource path (see \f[C]--resource-path\f[R]) and
finally in the \f[C]csl\f[R] subdirectory of the pandoc user data
directory.
.TP
\f[B]\f[CB]--natbib\f[B]\f[R]
Use \f[C]natbib\f[R] for citations in LaTeX output.
This option is not for use with the \f[C]--citeproc\f[R] option or with
PDF output.
It is intended for use in producing a LaTeX file that can be processed
with \f[C]bibtex\f[R].
.TP
\f[B]\f[CB]--biblatex\f[B]\f[R]
Use \f[C]biblatex\f[R] for citations in LaTeX output.
This option is not for use with the \f[C]--citeproc\f[R] option or with
PDF output.
It is intended for use in producing a LaTeX file that can be processed
with \f[C]bibtex\f[R] or \f[C]biber\f[R].
.SS Math rendering in HTML
.PP
The default is to render TeX math as far as possible using Unicode
characters.
Formulas are put inside a \f[C]span\f[R] with
\f[C]class=\[dq]math\[dq]\f[R], so that they may be styled differently
from the surrounding text if needed.
However, this gives acceptable results only for basic math, usually you
will want to use \f[C]--mathjax\f[R] or another of the following
options.
.TP
\f[B]\f[CB]--mathjax\f[B]\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]URL\f[R]]
Use MathJax to display embedded TeX math in HTML output.
TeX math will be put between \f[C]\[rs](...\[rs])\f[R] (for inline math)
or \f[C]\[rs][...\[rs]]\f[R] (for display math) and wrapped in
\f[C]<span>\f[R] tags with class \f[C]math\f[R].
Then the MathJax JavaScript will render it.
The \f[I]URL\f[R] should point to the \f[C]MathJax.js\f[R] load script.
If a \f[I]URL\f[R] is not provided, a link to the Cloudflare CDN will be
inserted.
.TP
\f[B]\f[CB]--mathml\f[B]\f[R]
Convert TeX math to MathML (in \f[C]epub3\f[R], \f[C]docbook4\f[R],
\f[C]docbook5\f[R], \f[C]jats\f[R], \f[C]html4\f[R] and
\f[C]html5\f[R]).
This is the default in \f[C]odt\f[R] output.
Note that currently only Firefox and Safari (and select e-book readers)
natively support MathML.
.TP
\f[B]\f[CB]--webtex\f[B]\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]URL\f[R]]
Convert TeX formulas to \f[C]<img>\f[R] tags that link to an external
script that converts formulas to images.
The formula will be URL-encoded and concatenated with the URL provided.
For SVG images you can for example use
\f[C]--webtex https://latex.codecogs.com/svg.latex?\f[R].
If no URL is specified, the CodeCogs URL generating PNGs will be used
(\f[C]https://latex.codecogs.com/png.latex?\f[R]).
Note: the \f[C]--webtex\f[R] option will affect Markdown output as well
as HTML, which is useful if you\[cq]re targeting a version of Markdown
without native math support.
.TP
\f[B]\f[CB]--katex\f[B]\f[R][\f[B]\f[CB]=\f[B]\f[R]\f[I]URL\f[R]]
Use KaTeX to display embedded TeX math in HTML output.
The \f[I]URL\f[R] is the base URL for the KaTeX library.
That directory should contain a \f[C]katex.min.js\f[R] and a
\f[C]katex.min.css\f[R] file.
If a \f[I]URL\f[R] is not provided, a link to the KaTeX CDN will be
inserted.
.TP
\f[B]\f[CB]--gladtex\f[B]\f[R]
Enclose TeX math in \f[C]<eq>\f[R] tags in HTML output.
The resulting HTML can then be processed by GladTeX to produce SVG
images of the typeset formulas and an HTML file with these images
embedded.
.RS
.IP
.nf
\f[C]
pandoc -s --gladtex input.md -o myfile.htex
gladtex -d image_dir myfile.htex
# produces myfile.html and images in image_dir
\f[R]
.fi
.RE
.SS Options for wrapper scripts
.TP
\f[B]\f[CB]--dump-args\f[B]\f[R]
Print information about command-line arguments to \f[I]stdout\f[R], then
exit.
This option is intended primarily for use in wrapper scripts.
The first line of output contains the name of the output file specified
with the \f[C]-o\f[R] option, or \f[C]-\f[R] (for \f[I]stdout\f[R]) if
no output file was specified.
The remaining lines contain the command-line arguments, one per line, in
the order they appear.
These do not include regular pandoc options and their arguments, but do
include any options appearing after a \f[C]--\f[R] separator at the end
of the line.
.TP
\f[B]\f[CB]--ignore-args\f[B]\f[R]
Ignore command-line arguments (for use in wrapper scripts).
Regular pandoc options are not ignored.
Thus, for example,
.RS
.IP
.nf
\f[C]
pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
\f[R]
.fi
.PP
is equivalent to
.IP
.nf
\f[C]
pandoc -o foo.html -s
\f[R]
.fi
.RE
.SH EXIT CODES
.PP
If pandoc completes successfully, it will return exit code 0.
Nonzero exit codes have the following meanings:
.PP
.TS
tab(@);
r l.
T{
Code
T}@T{
Error
T}
_
T{
3
T}@T{
PandocFailOnWarningError
T}
T{
4
T}@T{
PandocAppError
T}
T{
5
T}@T{
PandocTemplateError
T}
T{
6
T}@T{
PandocOptionError
T}
T{
21
T}@T{
PandocUnknownReaderError
T}
T{
22
T}@T{
PandocUnknownWriterError
T}
T{
23
T}@T{
PandocUnsupportedExtensionError
T}
T{
24
T}@T{
PandocCiteprocError
T}
T{
31
T}@T{
PandocEpubSubdirectoryError
T}
T{
43
T}@T{
PandocPDFError
T}
T{
44
T}@T{
PandocXMLError
T}
T{
47
T}@T{
PandocPDFProgramNotFoundError
T}
T{
61
T}@T{
PandocHttpError
T}
T{
62
T}@T{
PandocShouldNeverHappenError
T}
T{
63
T}@T{
PandocSomeError
T}
T{
64
T}@T{
PandocParseError
T}
T{
65
T}@T{
PandocParsecError
T}
T{
66
T}@T{
PandocMakePDFError
T}
T{
67
T}@T{
PandocSyntaxMapError
T}
T{
83
T}@T{
PandocFilterError
T}
T{
91
T}@T{
PandocMacroLoop
T}
T{
92
T}@T{
PandocUTF8DecodingError
T}
T{
93
T}@T{
PandocIpynbDecodingError
T}
T{
94
T}@T{
PandocUnsupportedCharsetError
T}
T{
97
T}@T{
PandocCouldNotFindDataFileError
T}
T{
99
T}@T{
PandocResourceNotFound
T}
.TE
.SH DEFAULT FILES
.PP
The \f[C]--defaults\f[R] option may be used to specify a package of
options.
Here is a sample defaults file demonstrating all of the fields that may
be used:
.IP
.nf
\f[C]
from: markdown+emoji
# reader: may be used instead of from:
to: html5
# writer: may be used instead of to:
# leave blank for output to stdout:
output-file:
# leave blank for input from stdin, use [] for no input:
input-files:
- preface.md
- content.md
# or you may use input-file: with a single value
# Include options from the specified defaults files.
# The files will be searched for first in the working directory
# and then in the defaults subdirectory of the user data directory.
# The files are included in the same order in which they appear in
# the list. Options specified in this defaults file always have
# priority over the included ones.
defaults:
- defsA
- defsB
template: letter
standalone: true
self-contained: false
# note that structured variables may be specified:
variables:
documentclass: book
classoption:
- twosides
- draft
# metadata values specified here are parsed as literal
# string text, not markdown:
metadata:
author:
- Sam Smith
- Julie Liu
metadata-files:
- boilerplate.yaml
# or you may use metadata-file: with a single value
# Note that these take files, not their contents:
include-before-body: []
include-after-body: []
include-in-header: []
resource-path: [\[dq].\[dq]]
# turn on built-in citation processing. Note that if you need
# control over when the citeproc processing is done relative
# to other filters, you should instead use \[ga]citeproc\[ga] in the
# list of \[ga]filters\[ga] (see below).
citeproc: true
csl: ieee
bibliography:
- foobar.bib
- barbaz.json
citation-abbreviations: abbrevs.json
# Filters will be assumed to be Lua filters if they have
# the .lua extension, and json filters otherwise. But
# the filter type can also be specified explicitly, as shown.
# Filters are run in the order specified.
# To include the built-in citeproc filter, use either \[ga]citeproc\[ga]
# or \[ga]{type: citeproc}\[ga].
filters:
- wordcount.lua
- type: json
path: foo.lua
file-scope: false
data-dir:
# ERROR, WARNING, or INFO
verbosity: INFO
log-file: log.json
# citeproc, natbib, or biblatex. This only affects LaTeX
# output. If you want to use citeproc to format citations,
# you should also set \[aq]citeproc: true\[aq] (see above).
cite-method: citeproc
# part, chapter, section, or default:
top-level-division: chapter
abbreviations:
pdf-engine: pdflatex
pdf-engine-opts:
- \[dq]-shell-escape\[dq]
# you may also use pdf-engine-opt: with a single option
# pdf-engine-opt: \[dq]-shell-escape\[dq]
# auto, preserve, or none
wrap: auto
columns: 78
dpi: 72
extract-media: mediadir
table-of-contents: true
toc-depth: 2
number-sections: false
# a list of offsets at each heading level
number-offset: [0,0,0,0,0,0]
# toc: may also be used instead of table-of-contents:
shift-heading-level-by: 1
section-divs: true
identifier-prefix: foo
title-prefix: \[dq]\[dq]
strip-empty-paragraphs: true
# lf, crlf, or native
eol: lf
strip-comments: false
indented-code-classes: []
ascii: true
default-image-extension: \[dq].jpg\[dq]
# either a style name of a style definition file:
highlight-style: pygments
syntax-definitions:
- c.xml
# or you may use syntax-definition: with a single value
listings: false
reference-doc: myref.docx
# method is plain, webtex, gladtex, mathml, mathjax, katex
# you may specify a url with webtex, mathjax, katex
html-math-method:
method: mathjax
url: \[dq]https://cdn.jsdelivr.net/npm/mathjax\[at]3/es5/tex-mml-chtml.js\[dq]
# none, references, or javascript
email-obfuscation: javascript
tab-stop: 8
preserve-tabs: true
incremental: false
slide-level: 2
epub-subdirectory: EPUB
epub-metadata: meta.xml
epub-fonts:
- foobar.otf
epub-chapter-level: 1
epub-cover-image: cover.jpg
reference-links: true
# block, section, or document
reference-location: block
markdown-headings: setext
# accept, reject, or all
track-changes: accept
html-q-tags: false
css:
- site.css
# none, all, or best
ipynb-output: best
# A list of two-element lists
request-headers:
- [\[dq]User-Agent\[dq], \[dq]Mozilla/5.0\[dq]]
fail-if-warnings: false
dump-args: false
ignore-args: false
trace: false
\f[R]
.fi
.PP
Fields that are omitted will just have their regular default values.
So a defaults file can be as simple as one line:
.IP
.nf
\f[C]
verbosity: INFO
\f[R]
.fi
.PP
In fields that expect a file path (or list of file paths), the following
syntax may be used to interpolate environment variables:
.IP
.nf
\f[C]
csl: ${HOME}/mycsldir/special.csl
\f[R]
.fi
.PP
\f[C]${USERDATA}\f[R] may also be used; this will always resolve to the
user data directory that is current when the defaults file is parsed,
regardless of the setting of the environment variable
\f[C]USERDATA\f[R].
.PP
\f[C]${.}\f[R] will resolve to the directory containing the default file
itself.
This allows you to refer to resources contained in that directory:
.IP
.nf
\f[C]
epub-cover-image: ${.}/cover.jpg
epub-metadata: ${.}/meta.xml
resource-path:
- . # the working directory from which pandoc is run
- ${.}/images # the images subdirectory of the directory
# containing this defaults file
\f[R]
.fi
.PP
This environment variable interpolation syntax \f[I]only\f[R] works in
fields that expect file paths.
.PP
Default files can be placed in the \f[C]defaults\f[R] subdirectory of
the user data directory and used from any directory.
For example, one could create a file specifying defaults for writing
letters, save it as \f[C]letter.yaml\f[R] in the \f[C]defaults\f[R]
subdirectory of the user data directory, and then invoke these defaults
from any directory using \f[C]pandoc --defaults letter\f[R] or
\f[C]pandoc -dletter\f[R].
.PP
When multiple defaults are used, their contents will be combined.
.PP
Note that, where command-line arguments may be repeated
(\f[C]--metadata-file\f[R], \f[C]--css\f[R],
\f[C]--include-in-header\f[R], \f[C]--include-before-body\f[R],
\f[C]--include-after-body\f[R], \f[C]--variable\f[R],
\f[C]--metadata\f[R], \f[C]--syntax-definition\f[R]), the values
specified on the command line will combine with values specified in the
defaults file, rather than replacing them.
.SH TEMPLATES
.PP
When the \f[C]-s/--standalone\f[R] option is used, pandoc uses a
template to add header and footer material that is needed for a
self-standing document.
To see the default template that is used, just type
.IP
.nf
\f[C]
pandoc -D *FORMAT*
\f[R]
.fi
.PP
where \f[I]FORMAT\f[R] is the name of the output format.
A custom template can be specified using the \f[C]--template\f[R]
option.
You can also override the system default templates for a given output
format \f[I]FORMAT\f[R] by putting a file
\f[C]templates/default.*FORMAT*\f[R] in the user data directory (see
\f[C]--data-dir\f[R], above).
\f[I]Exceptions:\f[R]
.IP \[bu] 2
For \f[C]odt\f[R] output, customize the \f[C]default.opendocument\f[R]
template.
.IP \[bu] 2
For \f[C]pdf\f[R] output, customize the \f[C]default.latex\f[R] template
(or the \f[C]default.context\f[R] template, if you use
\f[C]-t context\f[R], or the \f[C]default.ms\f[R] template, if you use
\f[C]-t ms\f[R], or the \f[C]default.html\f[R] template, if you use
\f[C]-t html\f[R]).
.IP \[bu] 2
\f[C]docx\f[R] and \f[C]pptx\f[R] have no template (however, you can use
\f[C]--reference-doc\f[R] to customize the output).
.PP
Templates contain \f[I]variables\f[R], which allow for the inclusion of
arbitrary information at any point in the file.
They may be set at the command line using the \f[C]-V/--variable\f[R]
option.
If a variable is not set, pandoc will look for the key in the
document\[cq]s metadata, which can be set using either YAML metadata
blocks or with the \f[C]-M/--metadata\f[R] option.
In addition, some variables are given default values by pandoc.
See Variables below for a list of variables used in pandoc\[cq]s default
templates.
.PP
If you use custom templates, you may need to revise them as pandoc
changes.
We recommend tracking the changes in the default templates, and
modifying your custom templates accordingly.
An easy way to do this is to fork the pandoc-templates repository and
merge in changes after each pandoc release.
.SS Template syntax
.SS Comments
.PP
Anything between the sequence \f[C]$--\f[R] and the end of the line will
be treated as a comment and omitted from the output.
.SS Delimiters
.PP
To mark variables and control structures in the template, either
\f[C]$\f[R]\&...\f[C]$\f[R] or \f[C]${\f[R]\&...\f[C]}\f[R] may be used
as delimiters.
The styles may also be mixed in the same template, but the opening and
closing delimiter must match in each case.
The opening delimiter may be followed by one or more spaces or tabs,
which will be ignored.
The closing delimiter may be followed by one or more spaces or tabs,
which will be ignored.
.PP
To include a literal \f[C]$\f[R] in the document, use \f[C]$$\f[R].
.SS Interpolated variables
.PP
A slot for an interpolated variable is a variable name surrounded by
matched delimiters.
Variable names must begin with a letter and can contain letters,
numbers, \f[C]_\f[R], \f[C]-\f[R], and \f[C].\f[R].
The keywords \f[C]it\f[R], \f[C]if\f[R], \f[C]else\f[R],
\f[C]endif\f[R], \f[C]for\f[R], \f[C]sep\f[R], and \f[C]endfor\f[R] may
not be used as variable names.
Examples:
.IP
.nf
\f[C]
$foo$
$foo.bar.baz$
$foo_bar.baz-bim$
$ foo $
${foo}
${foo.bar.baz}
${foo_bar.baz-bim}
${ foo }
\f[R]
.fi
.PP
Variable names with periods are used to get at structured variable
values.
So, for example, \f[C]employee.salary\f[R] will return the value of the
\f[C]salary\f[R] field of the object that is the value of the
\f[C]employee\f[R] field.
.IP \[bu] 2
If the value of the variable is simple value, it will be rendered
verbatim.
(Note that no escaping is done; the assumption is that the calling
program will escape the strings appropriately for the output format.)
.IP \[bu] 2
If the value is a list, the values will be concatenated.
.IP \[bu] 2
If the value is a map, the string \f[C]true\f[R] will be rendered.
.IP \[bu] 2
Every other value will be rendered as the empty string.
.SS Conditionals
.PP
A conditional begins with \f[C]if(variable)\f[R] (enclosed in matched
delimiters) and ends with \f[C]endif\f[R] (enclosed in matched
delimiters).
It may optionally contain an \f[C]else\f[R] (enclosed in matched
delimiters).
The \f[C]if\f[R] section is used if \f[C]variable\f[R] has a non-empty
value, otherwise the \f[C]else\f[R] section is used (if present).
Examples:
.IP
.nf
\f[C]
$if(foo)$bar$endif$
$if(foo)$
$foo$
$endif$
$if(foo)$
part one
$else$
part two
$endif$
${if(foo)}bar${endif}
${if(foo)}
${foo}
${endif}
${if(foo)}
${ foo.bar }
${else}
no foo!
${endif}
\f[R]
.fi
.PP
The keyword \f[C]elseif\f[R] may be used to simplify complex nested
conditionals:
.IP
.nf
\f[C]
$if(foo)$
XXX
$elseif(bar)$
YYY
$else$
ZZZ
$endif$
\f[R]
.fi
.SS For loops
.PP
A for loop begins with \f[C]for(variable)\f[R] (enclosed in matched
delimiters) and ends with \f[C]endfor\f[R] (enclosed in matched
delimiters.
.IP \[bu] 2
If \f[C]variable\f[R] is an array, the material inside the loop will be
evaluated repeatedly, with \f[C]variable\f[R] being set to each value of
the array in turn, and concatenated.
.IP \[bu] 2
If \f[C]variable\f[R] is a map, the material inside will be set to the
map.
.IP \[bu] 2
If the value of the associated variable is not an array or a map, a
single iteration will be performed on its value.
.PP
Examples:
.IP
.nf
\f[C]
$for(foo)$$foo$$sep$, $endfor$
$for(foo)$
- $foo.last$, $foo.first$
$endfor$
${ for(foo.bar) }
- ${ foo.bar.last }, ${ foo.bar.first }
${ endfor }
$for(mymap)$
$it.name$: $it.office$
$endfor$
\f[R]
.fi
.PP
You may optionally specify a separator between consecutive values using
\f[C]sep\f[R] (enclosed in matched delimiters).
The material between \f[C]sep\f[R] and the \f[C]endfor\f[R] is the
separator.
.IP
.nf
\f[C]
${ for(foo) }${ foo }${ sep }, ${ endfor }
\f[R]
.fi
.PP
Instead of using \f[C]variable\f[R] inside the loop, the special
anaphoric keyword \f[C]it\f[R] may be used.
.IP
.nf
\f[C]
${ for(foo.bar) }
- ${ it.last }, ${ it.first }
${ endfor }
\f[R]
.fi
.SS Partials
.PP
Partials (subtemplates stored in different files) may be included by
using the name of the partial, followed by \f[C]()\f[R], for example:
.IP
.nf
\f[C]
${ styles() }
\f[R]
.fi
.PP
Partials will be sought in the directory containing the main template.
The file name will be assumed to have the same extension as the main
template if it lacks an extension.
When calling the partial, the full name including file extension can
also be used:
.IP
.nf
\f[C]
${ styles.html() }
\f[R]
.fi
.PP
(If a partial is not found in the directory of the template and the
template path is given as a relative path, it will also be sought in the
\f[C]templates\f[R] subdirectory of the user data directory.)
.PP
Partials may optionally be applied to variables using a colon:
.IP
.nf
\f[C]
${ date:fancy() }
${ articles:bibentry() }
\f[R]
.fi
.PP
If \f[C]articles\f[R] is an array, this will iterate over its values,
applying the partial \f[C]bibentry()\f[R] to each one.
So the second example above is equivalent to
.IP
.nf
\f[C]
${ for(articles) }
${ it:bibentry() }
${ endfor }
\f[R]
.fi
.PP
Note that the anaphoric keyword \f[C]it\f[R] must be used when iterating
over partials.
In the above examples, the \f[C]bibentry\f[R] partial should contain
\f[C]it.title\f[R] (and so on) instead of \f[C]articles.title\f[R].
.PP
Final newlines are omitted from included partials.
.PP
Partials may include other partials.
.PP
A separator between values of an array may be specified in square
brackets, immediately after the variable name or partial:
.IP
.nf
\f[C]
${months[, ]}$
${articles:bibentry()[; ]$
\f[R]
.fi
.PP
The separator in this case is literal and (unlike with \f[C]sep\f[R] in
an explicit \f[C]for\f[R] loop) cannot contain interpolated variables or
other template directives.
.SS Nesting
.PP
To ensure that content is \[lq]nested,\[rq] that is, subsequent lines
indented, use the \f[C]\[ha]\f[R] directive:
.IP
.nf
\f[C]
$item.number$ $\[ha]$$item.description$ ($item.price$)
\f[R]
.fi
.PP
In this example, if \f[C]item.description\f[R] has multiple lines, they
will all be indented to line up with the first line:
.IP
.nf
\f[C]
00123 A fine bottle of 18-year old
Oban whiskey. ($148)
\f[R]
.fi
.PP
To nest multiple lines to the same level, align them with the
\f[C]\[ha]\f[R] directive in the template.
For example:
.IP
.nf
\f[C]
$item.number$ $\[ha]$$item.description$ ($item.price$)
(Available til $item.sellby$.)
\f[R]
.fi
.PP
will produce
.IP
.nf
\f[C]
00123 A fine bottle of 18-year old
Oban whiskey. ($148)
(Available til March 30, 2020.)
\f[R]
.fi
.PP
If a variable occurs by itself on a line, preceded by whitespace and not
followed by further text or directives on the same line, and the
variable\[cq]s value contains multiple lines, it will be nested
automatically.
.SS Breakable spaces
.PP
Normally, spaces in the template itself (as opposed to values of the
interpolated variables) are not breakable, but they can be made
breakable in part of the template by using the \f[C]\[ti]\f[R] keyword
(ended with another \f[C]\[ti]\f[R]).
.IP
.nf
\f[C]
$\[ti]$This long line may break if the document is rendered
with a short line length.$\[ti]$
\f[R]
.fi
.SS Pipes
.PP
A pipe transforms the value of a variable or partial.
Pipes are specified using a slash (\f[C]/\f[R]) between the variable
name (or partial) and the pipe name.
Example:
.IP
.nf
\f[C]
$for(name)$
$name/uppercase$
$endfor$
$for(metadata/pairs)$
- $it.key$: $it.value$
$endfor$
$employee:name()/uppercase$
\f[R]
.fi
.PP
Pipes may be chained:
.IP
.nf
\f[C]
$for(employees/pairs)$
$it.key/alpha/uppercase$. $it.name$
$endfor$
\f[R]
.fi
.PP
Some pipes take parameters:
.IP
.nf
\f[C]
|----------------------|------------|
$for(employee)$
$it.name.first/uppercase/left 20 \[dq]| \[dq]$$it.name.salary/right 10 \[dq] | \[dq] \[dq] |\[dq]$
$endfor$
|----------------------|------------|
\f[R]
.fi
.PP
Currently the following pipes are predefined:
.IP \[bu] 2
\f[C]pairs\f[R]: Converts a map or array to an array of maps, each with
\f[C]key\f[R] and \f[C]value\f[R] fields.
If the original value was an array, the \f[C]key\f[R] will be the array
index, starting with 1.
.IP \[bu] 2
\f[C]uppercase\f[R]: Converts text to uppercase.
.IP \[bu] 2
\f[C]lowercase\f[R]: Converts text to lowercase.
.IP \[bu] 2
\f[C]length\f[R]: Returns the length of the value: number of characters
for a textual value, number of elements for a map or array.
.IP \[bu] 2
\f[C]reverse\f[R]: Reverses a textual value or array, and has no effect
on other values.
.IP \[bu] 2
\f[C]first\f[R]: Returns the first value of an array, if applied to a
non-empty array; otherwise returns the original value.
.IP \[bu] 2
\f[C]last\f[R]: Returns the last value of an array, if applied to a
non-empty array; otherwise returns the original value.
.IP \[bu] 2
\f[C]rest\f[R]: Returns all but the first value of an array, if applied
to a non-empty array; otherwise returns the original value.
.IP \[bu] 2
\f[C]allbutlast\f[R]: Returns all but the last value of an array, if
applied to a non-empty array; otherwise returns the original value.
.IP \[bu] 2
\f[C]chomp\f[R]: Removes trailing newlines (and breakable space).
.IP \[bu] 2
\f[C]nowrap\f[R]: Disables line wrapping on breakable spaces.
.IP \[bu] 2
\f[C]alpha\f[R]: Converts textual values that can be read as an integer
into lowercase alphabetic characters \f[C]a..z\f[R] (mod 26).
This can be used to get lettered enumeration from array indices.
To get uppercase letters, chain with \f[C]uppercase\f[R].
.IP \[bu] 2
\f[C]roman\f[R]: Converts textual values that can be read as an integer
into lowercase roman numerials.
This can be used to get lettered enumeration from array indices.
To get uppercase roman, chain with \f[C]uppercase\f[R].
.IP \[bu] 2
\f[C]left n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders a
textual value in a block of width \f[C]n\f[R], aligned to the left, with
an optional left and right border.
Has no effect on other values.
This can be used to align material in tables.
Widths are positive integers indicating the number of characters.
Borders are strings inside double quotes; literal \f[C]\[dq]\f[R] and
\f[C]\[rs]\f[R] characters must be backslash-escaped.
.IP \[bu] 2
\f[C]right n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders a
textual value in a block of width \f[C]n\f[R], aligned to the right, and
has no effect on other values.
.IP \[bu] 2
\f[C]center n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders a
textual value in a block of width \f[C]n\f[R], aligned to the center,
and has no effect on other values.
.SS Variables
.SS Metadata variables
.TP
\f[B]\f[CB]title\f[B]\f[R], \f[B]\f[CB]author\f[B]\f[R], \f[B]\f[CB]date\f[B]\f[R]
allow identification of basic aspects of the document.
Included in PDF metadata through LaTeX and ConTeXt.
These can be set through a pandoc title block, which allows for multiple
authors, or through a YAML metadata block:
.RS
.IP
.nf
\f[C]
---
author:
- Aristotle
- Peter Abelard
\&...
\f[R]
.fi
.PP
Note that if you just want to set PDF or HTML metadata, without
including a title block in the document itself, you can set the
\f[C]title-meta\f[R], \f[C]author-meta\f[R], and \f[C]date-meta\f[R]
variables.
(By default these are set automatically, based on \f[C]title\f[R],
\f[C]author\f[R], and \f[C]date\f[R].) The page title in HTML is set by
\f[C]pagetitle\f[R], which is equal to \f[C]title\f[R] by default.
.RE
.TP
\f[B]\f[CB]subtitle\f[B]\f[R]
document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and docx
documents
.TP
\f[B]\f[CB]abstract\f[B]\f[R]
document summary, included in LaTeX, ConTeXt, AsciiDoc, and docx
documents
.TP
\f[B]\f[CB]keywords\f[B]\f[R]
list of keywords to be included in HTML, PDF, ODT, pptx, docx and
AsciiDoc metadata; repeat as for \f[C]author\f[R], above
.TP
\f[B]\f[CB]subject\f[B]\f[R]
document subject, included in ODT, PDF, docx and pptx metadata
.TP
\f[B]\f[CB]description\f[B]\f[R]
document description, included in ODT, docx and pptx metadata.
Some applications show this as \f[C]Comments\f[R] metadata.
.TP
\f[B]\f[CB]category\f[B]\f[R]
document category, included in docx and pptx metadata
.PP
Additionally, any root-level string metadata, not included in ODT, docx
or pptx metadata is added as a \f[I]custom property\f[R].
The following YAML metadata block for instance:
.IP
.nf
\f[C]
---
title: \[aq]This is the title\[aq]
subtitle: \[dq]This is the subtitle\[dq]
author:
- Author One
- Author Two
description: |
This is a long
description.
It consists of two paragraphs
\&...
\f[R]
.fi
.PP
will include \f[C]title\f[R], \f[C]author\f[R] and \f[C]description\f[R]
as standard document properties and \f[C]subtitle\f[R] as a custom
property when converting to docx, ODT or pptx.
.SS Language variables
.TP
\f[B]\f[CB]lang\f[B]\f[R]
identifies the main language of the document using IETF language tags
(following the BCP 47 standard), such as \f[C]en\f[R] or
\f[C]en-GB\f[R].
The Language subtag lookup tool can look up or verify these tags.
This affects most formats, and controls hyphenation in PDF output when
using LaTeX (through \f[C]babel\f[R] and \f[C]polyglossia\f[R]) or
ConTeXt.
.RS
.PP
Use native pandoc Divs and Spans with the \f[C]lang\f[R] attribute to
switch the language:
.IP
.nf
\f[C]
---
lang: en-GB
\&...
Text in the main document language (British English).
::: {lang=fr-CA}
> Cette citation est \['e]crite en fran\[,c]ais canadien.
:::
More text in English. [\[aq]Zitat auf Deutsch.\[aq]]{lang=de}
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]dir\f[B]\f[R]
the base script direction, either \f[C]rtl\f[R] (right-to-left) or
\f[C]ltr\f[R] (left-to-right).
.RS
.PP
For bidirectional documents, native pandoc \f[C]span\f[R]s and
\f[C]div\f[R]s with the \f[C]dir\f[R] attribute (value \f[C]rtl\f[R] or
\f[C]ltr\f[R]) can be used to override the base direction in some output
formats.
This may not always be necessary if the final renderer (e.g.\ the
browser, when generating HTML) supports the Unicode Bidirectional
Algorithm.
.PP
When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[R]
engine is fully supported (use \f[C]--pdf-engine=xelatex\f[R]).
.RE
.SS Variables for HTML
.TP
\f[B]\f[CB]document-css\f[B]\f[R]
Enables inclusion of most of the CSS in the \f[C]styles.html\f[R]
partial (have a look with
\f[C]pandoc --print-default-data-file=templates/styles.html\f[R]).
Unless you use \f[C]--css\f[R], this variable is set to \f[C]true\f[R]
by default.
You can disable it with e.g.\ \f[C]pandoc -M document-css=false\f[R].
.TP
\f[B]\f[CB]mainfont\f[B]\f[R]
sets the CSS \f[C]font-family\f[R] property on the \f[C]html\f[R]
element.
.TP
\f[B]\f[CB]fontsize\f[B]\f[R]
sets the base CSS \f[C]font-size\f[R], which you\[cq]d usually set to
e.g.\ \f[C]20px\f[R], but it also accepts \f[C]pt\f[R] (12pt = 16px in
most browsers).
.TP
\f[B]\f[CB]fontcolor\f[B]\f[R]
sets the CSS \f[C]color\f[R] property on the \f[C]html\f[R] element.
.TP
\f[B]\f[CB]linkcolor\f[B]\f[R]
sets the CSS \f[C]color\f[R] property on all links.
.TP
\f[B]\f[CB]monofont\f[B]\f[R]
sets the CSS \f[C]font-family\f[R] property on \f[C]code\f[R] elements.
.TP
\f[B]\f[CB]monobackgroundcolor\f[B]\f[R]
sets the CSS \f[C]background-color\f[R] property on \f[C]code\f[R]
elements and adds extra padding.
.TP
\f[B]\f[CB]linestretch\f[B]\f[R]
sets the CSS \f[C]line-height\f[R] property on the \f[C]html\f[R]
element, which is preferred to be unitless.
.TP
\f[B]\f[CB]backgroundcolor\f[B]\f[R]
sets the CSS \f[C]background-color\f[R] property on the \f[C]html\f[R]
element.
.TP
\f[B]\f[CB]margin-left\f[B]\f[R], \f[B]\f[CB]margin-right\f[B]\f[R], \f[B]\f[CB]margin-top\f[B]\f[R], \f[B]\f[CB]margin-bottom\f[B]\f[R]
sets the corresponding CSS \f[C]padding\f[R] properties on the
\f[C]body\f[R] element.
.PP
To override or extend some CSS for just one document, include for
example:
.IP
.nf
\f[C]
---
header-includes: |
<style>
blockquote {
font-style: italic;
}
tr.even {
background-color: #f0f0f0;
}
td, th {
padding: 0.5em 2em 0.5em 0.5em;
}
tbody {
border-bottom: none;
}
</style>
---
\f[R]
.fi
.SS Variables for HTML math
.TP
\f[B]\f[CB]classoption\f[B]\f[R]
when using KaTeX, you can render display math equations flush left using
YAML metadata or with \f[C]-M classoption=fleqn\f[R].
.SS Variables for HTML slides
.PP
These affect HTML output when [producing slide shows with pandoc].
.TP
\f[B]\f[CB]institute\f[B]\f[R]
author affiliations: can be a list when there are multiple authors
.TP
\f[B]\f[CB]revealjs-url\f[B]\f[R]
base URL for reveal.js documents (defaults to
\f[C]https://unpkg.com/reveal.js\[at]\[ha]4/\f[R])
.TP
\f[B]\f[CB]s5-url\f[B]\f[R]
base URL for S5 documents (defaults to \f[C]s5/default\f[R])
.TP
\f[B]\f[CB]slidy-url\f[B]\f[R]
base URL for Slidy documents (defaults to
\f[C]https://www.w3.org/Talks/Tools/Slidy2\f[R])
.TP
\f[B]\f[CB]slideous-url\f[B]\f[R]
base URL for Slideous documents (defaults to \f[C]slideous\f[R])
.TP
\f[B]\f[CB]title-slide-attributes\f[B]\f[R]
additional attributes for the title slide of reveal.js slide shows.
See background in reveal.js and beamer for an example.
.PP
All reveal.js configuration options are available as variables.
To turn off boolean flags that default to true in reveal.js, use
\f[C]0\f[R].
.SS Variables for Beamer slides
.PP
These variables change the appearance of PDF slides using
\f[C]beamer\f[R].
.TP
\f[B]\f[CB]aspectratio\f[B]\f[R]
slide aspect ratio (\f[C]43\f[R] for 4:3 [default], \f[C]169\f[R] for
16:9, \f[C]1610\f[R] for 16:10, \f[C]149\f[R] for 14:9, \f[C]141\f[R]
for 1.41:1, \f[C]54\f[R] for 5:4, \f[C]32\f[R] for 3:2)
.TP
\f[B]\f[CB]beamerarticle\f[B]\f[R]
produce an article from Beamer slides
.TP
\f[B]\f[CB]beameroption\f[B]\f[R]
add extra beamer option with \f[C]\[rs]setbeameroption{}\f[R]
.TP
\f[B]\f[CB]institute\f[B]\f[R]
author affiliations: can be a list when there are multiple authors
.TP
\f[B]\f[CB]logo\f[B]\f[R]
logo image for slides
.TP
\f[B]\f[CB]navigation\f[B]\f[R]
controls navigation symbols (default is \f[C]empty\f[R] for no
navigation symbols; other valid values are \f[C]frame\f[R],
\f[C]vertical\f[R], and \f[C]horizontal\f[R])
.TP
\f[B]\f[CB]section-titles\f[B]\f[R]
enables \[lq]title pages\[rq] for new sections (default is true)
.TP
\f[B]\f[CB]theme\f[B]\f[R], \f[B]\f[CB]colortheme\f[B]\f[R], \f[B]\f[CB]fonttheme\f[B]\f[R], \f[B]\f[CB]innertheme\f[B]\f[R], \f[B]\f[CB]outertheme\f[B]\f[R]
beamer themes
.TP
\f[B]\f[CB]themeoptions\f[B]\f[R]
options for LaTeX beamer themes (a list).
.TP
\f[B]\f[CB]titlegraphic\f[B]\f[R]
image for title slide
.SS Variables for PowerPoint
.PP
These variables control the visual aspects of a slide show that are not
easily controlled via templates.
.TP
\f[B]\f[CB]monofont\f[B]\f[R]
font to use for code.
.SS Variables for LaTeX
.PP
Pandoc uses these variables when creating a PDF with a LaTeX engine.
.SS Layout
.TP
\f[B]\f[CB]block-headings\f[B]\f[R]
make \f[C]\[rs]paragraph\f[R] and \f[C]\[rs]subparagraph\f[R] (fourth-
and fifth-level headings, or fifth- and sixth-level with book classes)
free-standing rather than run-in; requires further formatting to
distinguish from \f[C]\[rs]subsubsection\f[R] (third- or fourth-level
headings).
Instead of using this option, KOMA-Script can adjust headings more
extensively:
.RS
.IP
.nf
\f[C]
---
documentclass: scrartcl
header-includes: |
\[rs]RedeclareSectionCommand[
beforeskip=-10pt plus -2pt minus -1pt,
afterskip=1sp plus -1sp minus 1sp,
font=\[rs]normalfont\[rs]itshape]{paragraph}
\[rs]RedeclareSectionCommand[
beforeskip=-10pt plus -2pt minus -1pt,
afterskip=1sp plus -1sp minus 1sp,
font=\[rs]normalfont\[rs]scshape,
indent=0pt]{subparagraph}
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]classoption\f[B]\f[R]
option for document class, e.g.\ \f[C]oneside\f[R]; repeat for multiple
options:
.RS
.IP
.nf
\f[C]
---
classoption:
- twocolumn
- landscape
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]documentclass\f[B]\f[R]
document class: usually one of the standard classes, \f[C]article\f[R],
\f[C]book\f[R], and \f[C]report\f[R]; the KOMA-Script equivalents,
\f[C]scrartcl\f[R], \f[C]scrbook\f[R], and \f[C]scrreprt\f[R], which
default to smaller margins; or \f[C]memoir\f[R]
.TP
\f[B]\f[CB]geometry\f[B]\f[R]
option for \f[C]geometry\f[R] package, e.g.\ \f[C]margin=1in\f[R];
repeat for multiple options:
.RS
.IP
.nf
\f[C]
---
geometry:
- top=30mm
- left=20mm
- heightrounded
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]hyperrefoptions\f[B]\f[R]
option for \f[C]hyperref\f[R] package, e.g.\ \f[C]linktoc=all\f[R];
repeat for multiple options:
.RS
.IP
.nf
\f[C]
---
hyperrefoptions:
- linktoc=all
- pdfwindowui
- pdfpagemode=FullScreen
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]indent\f[B]\f[R]
if true, pandoc will use document class settings for indentation (the
default LaTeX template otherwise removes indentation and adds space
between paragraphs)
.TP
\f[B]\f[CB]linestretch\f[B]\f[R]
adjusts line spacing using the \f[C]setspace\f[R] package,
e.g.\ \f[C]1.25\f[R], \f[C]1.5\f[R]
.TP
\f[B]\f[CB]margin-left\f[B]\f[R], \f[B]\f[CB]margin-right\f[B]\f[R], \f[B]\f[CB]margin-top\f[B]\f[R], \f[B]\f[CB]margin-bottom\f[B]\f[R]
sets margins if \f[C]geometry\f[R] is not used (otherwise
\f[C]geometry\f[R] overrides these)
.TP
\f[B]\f[CB]pagestyle\f[B]\f[R]
control \f[C]\[rs]pagestyle{}\f[R]: the default article class supports
\f[C]plain\f[R] (default), \f[C]empty\f[R] (no running heads or page
numbers), and \f[C]headings\f[R] (section titles in running heads)
.TP
\f[B]\f[CB]papersize\f[B]\f[R]
paper size, e.g.\ \f[C]letter\f[R], \f[C]a4\f[R]
.TP
\f[B]\f[CB]secnumdepth\f[B]\f[R]
numbering depth for sections (with \f[C]--number-sections\f[R] option or
\f[C]numbersections\f[R] variable)
.SS Fonts
.TP
\f[B]\f[CB]fontenc\f[B]\f[R]
allows font encoding to be specified through \f[C]fontenc\f[R] package
(with \f[C]pdflatex\f[R]); default is \f[C]T1\f[R] (see LaTeX font
encodings guide)
.TP
\f[B]\f[CB]fontfamily\f[B]\f[R]
font package for use with \f[C]pdflatex\f[R]: TeX Live includes many
options, documented in the LaTeX Font Catalogue.
The default is Latin Modern.
.TP
\f[B]\f[CB]fontfamilyoptions\f[B]\f[R]
options for package used as \f[C]fontfamily\f[R]; repeat for multiple
options.
For example, to use the Libertine font with proportional lowercase
(old-style) figures through the \f[C]libertinus\f[R] package:
.RS
.IP
.nf
\f[C]
---
fontfamily: libertinus
fontfamilyoptions:
- osf
- p
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]fontsize\f[B]\f[R]
font size for body text.
The standard classes allow 10pt, 11pt, and 12pt.
To use another size, set \f[C]documentclass\f[R] to one of the
KOMA-Script classes, such as \f[C]scrartcl\f[R] or \f[C]scrbook\f[R].
.TP
\f[B]\f[CB]mainfont\f[B]\f[R], \f[B]\f[CB]sansfont\f[B]\f[R], \f[B]\f[CB]monofont\f[B]\f[R], \f[B]\f[CB]mathfont\f[B]\f[R], \f[B]\f[CB]CJKmainfont\f[B]\f[R]
font families for use with \f[C]xelatex\f[R] or \f[C]lualatex\f[R]: take
the name of any system font, using the \f[C]fontspec\f[R] package.
\f[C]CJKmainfont\f[R] uses the \f[C]xecjk\f[R] package.
.TP
\f[B]\f[CB]mainfontoptions\f[B]\f[R], \f[B]\f[CB]sansfontoptions\f[B]\f[R], \f[B]\f[CB]monofontoptions\f[B]\f[R], \f[B]\f[CB]mathfontoptions\f[B]\f[R], \f[B]\f[CB]CJKoptions\f[B]\f[R]
options to use with \f[C]mainfont\f[R], \f[C]sansfont\f[R],
\f[C]monofont\f[R], \f[C]mathfont\f[R], \f[C]CJKmainfont\f[R] in
\f[C]xelatex\f[R] and \f[C]lualatex\f[R].
Allow for any choices available through \f[C]fontspec\f[R]; repeat for
multiple options.
For example, to use the TeX Gyre version of Palatino with lowercase
figures:
.RS
.IP
.nf
\f[C]
---
mainfont: TeX Gyre Pagella
mainfontoptions:
- Numbers=Lowercase
- Numbers=Proportional
\&...
\f[R]
.fi
.RE
.TP
\f[B]\f[CB]microtypeoptions\f[B]\f[R]
options to pass to the microtype package
.SS Links
.TP
\f[B]\f[CB]colorlinks\f[B]\f[R]
add color to link text; automatically enabled if any of
\f[C]linkcolor\f[R], \f[C]filecolor\f[R], \f[C]citecolor\f[R],
\f[C]urlcolor\f[R], or \f[C]toccolor\f[R] are set
.TP
\f[B]\f[CB]linkcolor\f[B]\f[R], \f[B]\f[CB]filecolor\f[B]\f[R], \f[B]\f[CB]citecolor\f[B]\f[R], \f[B]\f[CB]urlcolor\f[B]\f[R], \f[B]\f[CB]toccolor\f[B]\f[R]
color for internal links, external links, citation links, linked URLs,
and links in table of contents, respectively: uses options allowed by
\f[C]xcolor\f[R], including the \f[C]dvipsnames\f[R],
\f[C]svgnames\f[R], and \f[C]x11names\f[R] lists
.TP
\f[B]\f[CB]links-as-notes\f[B]\f[R]
causes links to be printed as footnotes
.SS Front matter
.TP
\f[B]\f[CB]lof\f[B]\f[R], \f[B]\f[CB]lot\f[B]\f[R]
include list of figures, list of tables
.TP
\f[B]\f[CB]thanks\f[B]\f[R]
contents of acknowledgments footnote after document title
.TP
\f[B]\f[CB]toc\f[B]\f[R]
include table of contents (can also be set using
\f[C]--toc/--table-of-contents\f[R])
.TP
\f[B]\f[CB]toc-depth\f[B]\f[R]
level of section to include in table of contents
.SS BibLaTeX Bibliographies
.PP
These variables function when using BibLaTeX for citation rendering.
.TP
\f[B]\f[CB]biblatexoptions\f[B]\f[R]
list of options for biblatex
.TP
\f[B]\f[CB]biblio-style\f[B]\f[R]
bibliography style, when used with \f[C]--natbib\f[R] and
\f[C]--biblatex\f[R].
.TP
\f[B]\f[CB]biblio-title\f[B]\f[R]
bibliography title, when used with \f[C]--natbib\f[R] and
\f[C]--biblatex\f[R].
.TP
\f[B]\f[CB]bibliography\f[B]\f[R]
bibliography to use for resolving references
.TP
\f[B]\f[CB]natbiboptions\f[B]\f[R]
list of options for natbib
.SS Variables for ConTeXt
.PP
Pandoc uses these variables when creating a PDF with ConTeXt.
.TP
\f[B]\f[CB]fontsize\f[B]\f[R]
font size for body text (e.g.\ \f[C]10pt\f[R], \f[C]12pt\f[R])
.TP
\f[B]\f[CB]headertext\f[B]\f[R], \f[B]\f[CB]footertext\f[B]\f[R]
text to be placed in running header or footer (see ConTeXt Headers and
Footers); repeat up to four times for different placement
.TP
\f[B]\f[CB]indenting\f[B]\f[R]
controls indentation of paragraphs, e.g.\ \f[C]yes,small,next\f[R] (see
ConTeXt Indentation); repeat for multiple options
.TP
\f[B]\f[CB]interlinespace\f[B]\f[R]
adjusts line spacing, e.g.\ \f[C]4ex\f[R] (using
\f[C]setupinterlinespace\f[R]); repeat for multiple options
.TP
\f[B]\f[CB]layout\f[B]\f[R]
options for page margins and text arrangement (see ConTeXt Layout);
repeat for multiple options
.TP
\f[B]\f[CB]linkcolor\f[B]\f[R], \f[B]\f[CB]contrastcolor\f[B]\f[R]
color for links outside and inside a page, e.g.\ \f[C]red\f[R],
\f[C]blue\f[R] (see ConTeXt Color)
.TP
\f[B]\f[CB]linkstyle\f[B]\f[R]
typeface style for links, e.g.\ \f[C]normal\f[R], \f[C]bold\f[R],
\f[C]slanted\f[R], \f[C]boldslanted\f[R], \f[C]type\f[R], \f[C]cap\f[R],
\f[C]small\f[R]
.TP
\f[B]\f[CB]lof\f[B]\f[R], \f[B]\f[CB]lot\f[B]\f[R]
include list of figures, list of tables
.TP
\f[B]\f[CB]mainfont\f[B]\f[R], \f[B]\f[CB]sansfont\f[B]\f[R], \f[B]\f[CB]monofont\f[B]\f[R], \f[B]\f[CB]mathfont\f[B]\f[R]
font families: take the name of any system font (see ConTeXt Font
Switching)
.TP
\f[B]\f[CB]margin-left\f[B]\f[R], \f[B]\f[CB]margin-right\f[B]\f[R], \f[B]\f[CB]margin-top\f[B]\f[R], \f[B]\f[CB]margin-bottom\f[B]\f[R]
sets margins, if \f[C]layout\f[R] is not used (otherwise
\f[C]layout\f[R] overrides these)
.TP
\f[B]\f[CB]pagenumbering\f[B]\f[R]
page number style and location (using \f[C]setuppagenumbering\f[R]);
repeat for multiple options
.TP
\f[B]\f[CB]papersize\f[B]\f[R]
paper size, e.g.\ \f[C]letter\f[R], \f[C]A4\f[R], \f[C]landscape\f[R]
(see ConTeXt Paper Setup); repeat for multiple options
.TP
\f[B]\f[CB]pdfa\f[B]\f[R]
adds to the preamble the setup necessary to generate PDF/A of the type
specified, e.g.\ \f[C]1a:2005\f[R], \f[C]2a\f[R].
If no type is specified (i.e.\ the value is set to True, by e.g.
\f[C]--metadata=pdfa\f[R] or \f[C]pdfa: true\f[R] in a YAML metadata
block), \f[C]1b:2005\f[R] will be used as default, for reasons of
backwards compatibility.
Using \f[C]--variable=pdfa\f[R] without specified value is not
supported.
To successfully generate PDF/A the required ICC color profiles have to
be available and the content and all included files (such as images)
have to be standard conforming.
The ICC profiles and output intent may be specified using the variables
\f[C]pdfaiccprofile\f[R] and \f[C]pdfaintent\f[R].
See also ConTeXt PDFA for more details.
.TP
\f[B]\f[CB]pdfaiccprofile\f[B]\f[R]
when used in conjunction with \f[C]pdfa\f[R], specifies the ICC profile
to use in the PDF, e.g.\ \f[C]default.cmyk\f[R].
If left unspecified, \f[C]sRGB.icc\f[R] is used as default.
May be repeated to include multiple profiles.
Note that the profiles have to be available on the system.
They can be obtained from ConTeXt ICC Profiles.
.TP
\f[B]\f[CB]pdfaintent\f[B]\f[R]
when used in conjunction with \f[C]pdfa\f[R], specifies the output
intent for the colors,
e.g.\ \f[C]ISO coated v2 300\[rs]letterpercent\[rs]space (ECI)\f[R] If
left unspecified, \f[C]sRGB IEC61966-2.1\f[R] is used as default.
.TP
\f[B]\f[CB]toc\f[B]\f[R]
include table of contents (can also be set using
\f[C]--toc/--table-of-contents\f[R])
.TP
\f[B]\f[CB]whitespace\f[B]\f[R]
spacing between paragraphs, e.g.\ \f[C]none\f[R], \f[C]small\f[R] (using
\f[C]setupwhitespace\f[R])
.TP
\f[B]\f[CB]includesource\f[B]\f[R]
include all source documents as file attachments in the PDF file
.SS Variables for \f[C]wkhtmltopdf\f[R]
.PP
Pandoc uses these variables when creating a PDF with
\f[C]wkhtmltopdf\f[R].
The \f[C]--css\f[R] option also affects the output.
.TP
\f[B]\f[CB]footer-html\f[B]\f[R], \f[B]\f[CB]header-html\f[B]\f[R]
add information to the header and footer
.TP
\f[B]\f[CB]margin-left\f[B]\f[R], \f[B]\f[CB]margin-right\f[B]\f[R], \f[B]\f[CB]margin-top\f[B]\f[R], \f[B]\f[CB]margin-bottom\f[B]\f[R]
set the page margins
.TP
\f[B]\f[CB]papersize\f[B]\f[R]
sets the PDF paper size
.SS Variables for man pages
.TP
\f[B]\f[CB]adjusting\f[B]\f[R]
adjusts text to left (\f[C]l\f[R]), right (\f[C]r\f[R]), center
(\f[C]c\f[R]), or both (\f[C]b\f[R]) margins
.TP
\f[B]\f[CB]footer\f[B]\f[R]
footer in man pages
.TP
\f[B]\f[CB]header\f[B]\f[R]
header in man pages
.TP
\f[B]\f[CB]hyphenate\f[B]\f[R]
if \f[C]true\f[R] (the default), hyphenation will be used
.TP
\f[B]\f[CB]section\f[B]\f[R]
section number in man pages
.SS Variables for ms
.TP
\f[B]\f[CB]fontfamily\f[B]\f[R]
font family (e.g.\ \f[C]T\f[R] or \f[C]P\f[R])
.TP
\f[B]\f[CB]indent\f[B]\f[R]
paragraph indent (e.g.\ \f[C]2m\f[R])
.TP
\f[B]\f[CB]lineheight\f[B]\f[R]
line height (e.g.\ \f[C]12p\f[R])
.TP
\f[B]\f[CB]pointsize\f[B]\f[R]
point size (e.g.\ \f[C]10p\f[R])
.SS Variables set automatically
.PP
Pandoc sets these variables automatically in response to options or
document contents; users can also modify them.
These vary depending on the output format, and include the following:
.TP
\f[B]\f[CB]body\f[B]\f[R]
body of document
.TP
\f[B]\f[CB]date-meta\f[B]\f[R]
the \f[C]date\f[R] variable converted to ISO 8601 YYYY-MM-DD, included
in all HTML based formats (dzslides, epub, html, html4, html5, revealjs,
s5, slideous, slidy).
The recognized formats for \f[C]date\f[R] are: \f[C]mm/dd/yyyy\f[R],
\f[C]mm/dd/yy\f[R], \f[C]yyyy-mm-dd\f[R] (ISO 8601),
\f[C]dd MM yyyy\f[R] (e.g.\ either \f[C]02 Apr 2018\f[R] or
\f[C]02 April 2018\f[R]), \f[C]MM dd, yyyy\f[R]
(e.g.\ \f[C]Apr. 02, 2018\f[R] or
\f[C]April 02, 2018),\f[R]yyyy[mm[dd]]]\f[C](e.g.\f[R]20180402,
\f[C]201804\f[R] or \f[C]2018\f[R]).
.TP
\f[B]\f[CB]header-includes\f[B]\f[R]
contents specified by \f[C]-H/--include-in-header\f[R] (may have
multiple values)
.TP
\f[B]\f[CB]include-before\f[B]\f[R]
contents specified by \f[C]-B/--include-before-body\f[R] (may have
multiple values)
.TP
\f[B]\f[CB]include-after\f[B]\f[R]
contents specified by \f[C]-A/--include-after-body\f[R] (may have
multiple values)
.TP
\f[B]\f[CB]meta-json\f[B]\f[R]
JSON representation of all of the document\[cq]s metadata.
Field values are transformed to the selected output format.
.TP
\f[B]\f[CB]numbersections\f[B]\f[R]
non-null value if \f[C]-N/--number-sections\f[R] was specified
.TP
\f[B]\f[CB]sourcefile\f[B]\f[R], \f[B]\f[CB]outputfile\f[B]\f[R]
source and destination filenames, as given on the command line.
\f[C]sourcefile\f[R] can also be a list if input comes from multiple
files, or empty if input is from stdin.
You can use the following snippet in your template to distinguish them:
.RS
.IP
.nf
\f[C]
$if(sourcefile)$
$for(sourcefile)$
$sourcefile$
$endfor$
$else$
(stdin)
$endif$
\f[R]
.fi
.PP
Similarly, \f[C]outputfile\f[R] can be \f[C]-\f[R] if output goes to the
terminal.
.PP
If you need absolute paths, use e.g.\ \f[C]$curdir$/$sourcefile$\f[R].
.RE
.TP
\f[B]\f[CB]curdir\f[B]\f[R]
working directory from which pandoc is run.
.TP
\f[B]\f[CB]toc\f[B]\f[R]
non-null value if \f[C]--toc/--table-of-contents\f[R] was specified
.TP
\f[B]\f[CB]toc-title\f[B]\f[R]
title of table of contents (works only with EPUB, HTML, opendocument,
odt, docx, pptx, beamer, LaTeX)
.SH EXTENSIONS
.PP
The behavior of some of the readers and writers can be adjusted by
enabling or disabling various extensions.
.PP
An extension can be enabled by adding \f[C]+EXTENSION\f[R] to the format
name and disabled by adding \f[C]-EXTENSION\f[R].
For example, \f[C]--from markdown_strict+footnotes\f[R] is strict
Markdown with footnotes enabled, while
\f[C]--from markdown-footnotes-pipe_tables\f[R] is pandoc\[cq]s Markdown
without footnotes or pipe tables.
.PP
The markdown reader and writer make by far the most use of extensions.
Extensions only used by them are therefore covered in the section
Pandoc\[cq]s Markdown below (See Markdown variants for
\f[C]commonmark\f[R] and \f[C]gfm\f[R].) In the following, extensions
that also work for other formats are covered.
.PP
Note that markdown extensions added to the \f[C]ipynb\f[R] format affect
Markdown cells in Jupyter notebooks (as do command-line options like
\f[C]--atx-headers\f[R]).
.SS Typography
.SS Extension: \f[C]smart\f[R]
.PP
Interpret straight quotes as curly quotes, \f[C]---\f[R] as em-dashes,
\f[C]--\f[R] as en-dashes, and \f[C]...\f[R] as ellipses.
Nonbreaking spaces are inserted after certain abbreviations, such as
\[lq]Mr.\[rq]
.PP
This extension can be enabled/disabled for the following formats:
.TP
input formats
\f[C]markdown\f[R], \f[C]commonmark\f[R], \f[C]latex\f[R],
\f[C]mediawiki\f[R], \f[C]org\f[R], \f[C]rst\f[R], \f[C]twiki\f[R]
.TP
output formats
\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]context\f[R], \f[C]rst\f[R]
.TP
enabled by default in
\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]context\f[R] (both input and
output)
.PP
Note: If you are \f[I]writing\f[R] Markdown, then the \f[C]smart\f[R]
extension has the reverse effect: what would have been curly quotes
comes out straight.
.PP
In LaTeX, \f[C]smart\f[R] means to use the standard TeX ligatures for
quotation marks (\f[C]\[ga]\[ga]\f[R] and \f[C]\[aq]\[aq]\f[R] for
double quotes, \f[C]\[ga]\f[R] and \f[C]\[aq]\f[R] for single quotes)
and dashes (\f[C]--\f[R] for en-dash and \f[C]---\f[R] for em-dash).
If \f[C]smart\f[R] is disabled, then in reading LaTeX pandoc will parse
these characters literally.
In writing LaTeX, enabling \f[C]smart\f[R] tells pandoc to use the
ligatures when possible; if \f[C]smart\f[R] is disabled pandoc will use
unicode quotation mark and dash characters.
.SS Headings and sections
.SS Extension: \f[C]auto_identifiers\f[R]
.PP
A heading without an explicitly specified identifier will be
automatically assigned a unique identifier based on the heading text.
.PP
This extension can be enabled/disabled for the following formats:
.TP
input formats
\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]rst\f[R], \f[C]mediawiki\f[R],
\f[C]textile\f[R]
.TP
output formats
\f[C]markdown\f[R], \f[C]muse\f[R]
.TP
enabled by default in
\f[C]markdown\f[R], \f[C]muse\f[R]
.PP
The default algorithm used to derive the identifier from the heading
text is:
.IP \[bu] 2
Remove all formatting, links, etc.
.IP \[bu] 2
Remove all footnotes.
.IP \[bu] 2
Remove all non-alphanumeric characters, except underscores, hyphens, and
periods.
.IP \[bu] 2
Replace all spaces and newlines with hyphens.
.IP \[bu] 2
Convert all alphabetic characters to lowercase.
.IP \[bu] 2
Remove everything up to the first letter (identifiers may not begin with
a number or punctuation mark).
.IP \[bu] 2
If nothing is left after this, use the identifier \f[C]section\f[R].
.PP
Thus, for example,
.PP
.TS
tab(@);
l l.
T{
Heading
T}@T{
Identifier
T}
_
T{
\f[C]Heading identifiers in HTML\f[R]
T}@T{
\f[C]heading-identifiers-in-html\f[R]
T}
T{
\f[C]Ma\[^i]tre d\[aq]h\[^o]tel\f[R]
T}@T{
\f[C]ma\[^i]tre-dh\[^o]tel\f[R]
T}
T{
\f[C]*Dogs*?--in *my* house?\f[R]
T}@T{
\f[C]dogs--in-my-house\f[R]
T}
T{
\f[C][HTML], [S5], or [RTF]?\f[R]
T}@T{
\f[C]html-s5-or-rtf\f[R]
T}
T{
\f[C]3. Applications\f[R]
T}@T{
\f[C]applications\f[R]
T}
T{
\f[C]33\f[R]
T}@T{
\f[C]section\f[R]
T}
.TE
.PP
These rules should, in most cases, allow one to determine the identifier
from the heading text.
The exception is when several headings have the same text; in this case,
the first will get an identifier as described above; the second will get
the same identifier with \f[C]-1\f[R] appended; the third with
\f[C]-2\f[R]; and so on.
.PP
(However, a different algorithm is used if
\f[C]gfm_auto_identifiers\f[R] is enabled; see below.)
.PP
These identifiers are used to provide link targets in the table of
contents generated by the \f[C]--toc|--table-of-contents\f[R] option.
They also make it easy to provide links from one section of a document
to another.
A link to this section, for example, might look like this:
.IP
.nf
\f[C]
See the section on
[heading identifiers](#heading-identifiers-in-html-latex-and-context).
\f[R]
.fi
.PP
Note, however, that this method of providing links to sections works
only in HTML, LaTeX, and ConTeXt formats.
.PP
If the \f[C]--section-divs\f[R] option is specified, then each section
will be wrapped in a \f[C]section\f[R] (or a \f[C]div\f[R], if
\f[C]html4\f[R] was specified), and the identifier will be attached to
the enclosing \f[C]<section>\f[R] (or \f[C]<div>\f[R]) tag rather than
the heading itself.
This allows entire sections to be manipulated using JavaScript or
treated differently in CSS.
.SS Extension: \f[C]ascii_identifiers\f[R]
.PP
Causes the identifiers produced by \f[C]auto_identifiers\f[R] to be pure
ASCII.
Accents are stripped off of accented Latin letters, and non-Latin
letters are omitted.
.SS Extension: \f[C]gfm_auto_identifiers\f[R]
.PP
Changes the algorithm used by \f[C]auto_identifiers\f[R] to conform to
GitHub\[cq]s method.
Spaces are converted to dashes (\f[C]-\f[R]), uppercase characters to
lowercase characters, and punctuation characters other than \f[C]-\f[R]
and \f[C]_\f[R] are removed.
Emojis are replaced by their names.
.SS Math Input
.PP
The extensions \f[C]tex_math_dollars\f[R],
\f[C]tex_math_single_backslash\f[R], and
\f[C]tex_math_double_backslash\f[R] are described in the section about
Pandoc\[cq]s Markdown.
.PP
However, they can also be used with HTML input.
This is handy for reading web pages formatted using MathJax, for
example.
.SS Raw HTML/TeX
.PP
The following extensions are described in more detail in their
respective sections of Pandoc\[cq]s Markdown:
.IP \[bu] 2
\f[C]raw_html\f[R] allows HTML elements which are not representable in
pandoc\[cq]s AST to be parsed as raw HTML.
By default, this is disabled for HTML input.
.IP \[bu] 2
\f[C]raw_tex\f[R] allows raw LaTeX, TeX, and ConTeXt to be included in a
document.
This extension can be enabled/disabled for the following formats (in
addition to \f[C]markdown\f[R]):
.RS 2
.TP
input formats
\f[C]latex\f[R], \f[C]textile\f[R], \f[C]html\f[R] (environments,
\f[C]\[rs]ref\f[R], and \f[C]\[rs]eqref\f[R] only), \f[C]ipynb\f[R]
.TP
output formats
\f[C]textile\f[R], \f[C]commonmark\f[R]
.PP
Note: as applied to \f[C]ipynb\f[R], \f[C]raw_html\f[R] and
\f[C]raw_tex\f[R] affect not only raw TeX in markdown cells, but data
with mime type \f[C]text/html\f[R] in output cells.
Since the \f[C]ipynb\f[R] reader attempts to preserve the richest
possible outputs when several options are given, you will get best
results if you disable \f[C]raw_html\f[R] and \f[C]raw_tex\f[R] when
converting to formats like \f[C]docx\f[R] which don\[cq]t allow raw
\f[C]html\f[R] or \f[C]tex\f[R].
.RE
.IP \[bu] 2
\f[C]native_divs\f[R] causes HTML \f[C]div\f[R] elements to be parsed as
native pandoc Div blocks.
If you want them to be parsed as raw HTML, use
\f[C]-f html-native_divs+raw_html\f[R].
.IP \[bu] 2
\f[C]native_spans\f[R] causes HTML \f[C]span\f[R] elements to be parsed
as native pandoc Span inlines.
If you want them to be parsed as raw HTML, use
\f[C]-f html-native_spans+raw_html\f[R].
If you want to drop all \f[C]div\f[R]s and \f[C]span\f[R]s when
converting HTML to Markdown, you can use
\f[C]pandoc -f html-native_divs-native_spans -t markdown\f[R].
.SS Literate Haskell support
.SS Extension: \f[C]literate_haskell\f[R]
.PP
Treat the document as literate Haskell source.
.PP
This extension can be enabled/disabled for the following formats:
.TP
input formats
\f[C]markdown\f[R], \f[C]rst\f[R], \f[C]latex\f[R]
.TP
output formats
\f[C]markdown\f[R], \f[C]rst\f[R], \f[C]latex\f[R], \f[C]html\f[R]
.PP
If you append \f[C]+lhs\f[R] (or \f[C]+literate_haskell\f[R]) to one of
the formats above, pandoc will treat the document as literate Haskell
source.
This means that
.IP \[bu] 2
In Markdown input, \[lq]bird track\[rq] sections will be parsed as
Haskell code rather than block quotations.
Text between \f[C]\[rs]begin{code}\f[R] and \f[C]\[rs]end{code}\f[R]
will also be treated as Haskell code.
For ATX-style headings the character `=' will be used instead of `#'.
.IP \[bu] 2
In Markdown output, code blocks with classes \f[C]haskell\f[R] and
\f[C]literate\f[R] will be rendered using bird tracks, and block
quotations will be indented one space, so they will not be treated as
Haskell code.
In addition, headings will be rendered setext-style (with underlines)
rather than ATX-style (with `#' characters).
(This is because ghc treats `#' characters in column 1 as introducing
line numbers.)
.IP \[bu] 2
In restructured text input, \[lq]bird track\[rq] sections will be parsed
as Haskell code.
.IP \[bu] 2
In restructured text output, code blocks with class \f[C]haskell\f[R]
will be rendered using bird tracks.
.IP \[bu] 2
In LaTeX input, text in \f[C]code\f[R] environments will be parsed as
Haskell code.
.IP \[bu] 2
In LaTeX output, code blocks with class \f[C]haskell\f[R] will be
rendered inside \f[C]code\f[R] environments.
.IP \[bu] 2
In HTML output, code blocks with class \f[C]haskell\f[R] will be
rendered with class \f[C]literatehaskell\f[R] and bird tracks.
.PP
Examples:
.IP
.nf
\f[C]
pandoc -f markdown+lhs -t html
\f[R]
.fi
.PP
reads literate Haskell source formatted with Markdown conventions and
writes ordinary HTML (without bird tracks).
.IP
.nf
\f[C]
pandoc -f markdown+lhs -t html+lhs
\f[R]
.fi
.PP
writes HTML with the Haskell code in bird tracks, so it can be copied
and pasted as literate Haskell source.
.PP
Note that GHC expects the bird tracks in the first column, so indented
literate code blocks (e.g.\ inside an itemized environment) will not be
picked up by the Haskell compiler.
.SS Other extensions
.SS Extension: \f[C]empty_paragraphs\f[R]
.PP
Allows empty paragraphs.
By default empty paragraphs are omitted.
.PP
This extension can be enabled/disabled for the following formats:
.TP
input formats
\f[C]docx\f[R], \f[C]html\f[R]
.TP
output formats
\f[C]docx\f[R], \f[C]odt\f[R], \f[C]opendocument\f[R], \f[C]html\f[R]
.SS Extension: \f[C]native_numbering\f[R]
.PP
Enables native numbering of figures and tables.
Enumeration starts at 1.
.PP
This extension can be enabled/disabled for the following formats:
.TP
output formats
\f[C]odt\f[R], \f[C]opendocument\f[R]
.SS Extension: \f[C]xrefs_name\f[R]
.PP
Links to headings, figures and tables inside the document are
substituted with cross-references that will use the name or caption of
the referenced item.
The original link text is replaced once the generated document is
refreshed.
This extension can be combined with \f[C]xrefs_number\f[R] in which case
numbers will appear before the name.
.PP
Text in cross-references is only made consistent with the referenced
item once the document has been refreshed.
.PP
This extension can be enabled/disabled for the following formats:
.TP
output formats
\f[C]odt\f[R], \f[C]opendocument\f[R]
.SS Extension: \f[C]xrefs_number\f[R]
.PP
Links to headings, figures and tables inside the document are
substituted with cross-references that will use the number of the
referenced item.
The original link text is discarded.
This extension can be combined with \f[C]xrefs_name\f[R] in which case
the name or caption numbers will appear after the number.
.PP
For the \f[C]xrefs_number\f[R] to be useful heading numbers must be
enabled in the generated document, also table and figure captions must
be enabled using for example the \f[C]native_numbering\f[R] extension.
.PP
Numbers in cross-references are only visible in the final document once
it has been refreshed.
.PP
This extension can be enabled/disabled for the following formats:
.TP
output formats
\f[C]odt\f[R], \f[C]opendocument\f[R]
.SS Extension: \f[C]styles\f[R]
.PP
When converting from docx, read all docx styles as divs (for paragraph
styles) and spans (for character styles) regardless of whether pandoc
understands the meaning of these styles.
This can be used with docx custom styles.
Disabled by default.
.TP
input formats
\f[C]docx\f[R]
.SS Extension: \f[C]amuse\f[R]
.PP
In the \f[C]muse\f[R] input format, this enables Text::Amuse extensions
to Emacs Muse markup.
.SS Extension: \f[C]raw_markdown\f[R]
.PP
In the \f[C]ipynb\f[R] input format, this causes Markdown cells to be
included as raw Markdown blocks (allowing lossless round-tripping)
rather than being parsed.
Use this only when you are targeting \f[C]ipynb\f[R] or a markdown-based
output format.
.SS Extension: \f[C]citations\f[R]
.PP
Some aspects of Pandoc\[cq]s Markdown citation syntax are also accepted
in \f[C]org\f[R] input.
.SS Extension: \f[C]element_citations\f[R]
.PP
In the \f[C]jats\f[R] output formats, this causes reference items to be
replaced with \f[C]<element-citation>\f[R] elements.
These elements are not influenced by CSL styles, but all information on
the item is included in tags.
.SS Extension: \f[C]ntb\f[R]
.PP
In the \f[C]context\f[R] output format this enables the use of Natural
Tables (TABLE) instead of the default Extreme Tables (xtables).
Natural tables allow more fine-grained global customization but come at
a performance penalty compared to extreme tables.
.SH PANDOC\[cq]S MARKDOWN
.PP
Pandoc understands an extended and slightly revised version of John
Gruber\[cq]s Markdown syntax.
This document explains the syntax, noting differences from standard
Markdown.
Except where noted, these differences can be suppressed by using the
\f[C]markdown_strict\f[R] format instead of \f[C]markdown\f[R].
Extensions can be enabled or disabled to specify the behavior more
granularly.
They are described in the following.
See also Extensions above, for extensions that work also on other
formats.
.SS Philosophy
.PP
Markdown is designed to be easy to write, and, even more importantly,
easy to read:
.RS
.PP
A Markdown-formatted document should be publishable as-is, as plain
text, without looking like it\[cq]s been marked up with tags or
formatting instructions.
\[en] John Gruber
.RE
.PP
This principle has guided pandoc\[cq]s decisions in finding syntax for
tables, footnotes, and other extensions.
.PP
There is, however, one respect in which pandoc\[cq]s aims are different
from the original aims of Markdown.
Whereas Markdown was originally designed with HTML generation in mind,
pandoc is designed for multiple output formats.
Thus, while pandoc allows the embedding of raw HTML, it discourages it,
and provides other, non-HTMLish ways of representing important document
elements like definition lists, tables, mathematics, and footnotes.
.SS Paragraphs
.PP
A paragraph is one or more lines of text followed by one or more blank
lines.
Newlines are treated as spaces, so you can reflow your paragraphs as you
like.
If you need a hard line break, put two or more spaces at the end of a
line.
.SS Extension: \f[C]escaped_line_breaks\f[R]
.PP
A backslash followed by a newline is also a hard line break.
Note: in multiline and grid table cells, this is the only way to create
a hard line break, since trailing spaces in the cells are ignored.
.SS Headings
.PP
There are two kinds of headings: Setext and ATX.
.SS Setext-style headings
.PP
A setext-style heading is a line of text \[lq]underlined\[rq] with a row
of \f[C]=\f[R] signs (for a level-one heading) or \f[C]-\f[R] signs (for
a level-two heading):
.IP
.nf
\f[C]
A level-one heading
===================
A level-two heading
-------------------
\f[R]
.fi
.PP
The heading text can contain inline formatting, such as emphasis (see
Inline formatting, below).
.SS ATX-style headings
.PP
An ATX-style heading consists of one to six \f[C]#\f[R] signs and a line
of text, optionally followed by any number of \f[C]#\f[R] signs.
The number of \f[C]#\f[R] signs at the beginning of the line is the
heading level:
.IP
.nf
\f[C]
## A level-two heading
### A level-three heading ###
\f[R]
.fi
.PP
As with setext-style headings, the heading text can contain formatting:
.IP
.nf
\f[C]
# A level-one heading with a [link](/url) and *emphasis*
\f[R]
.fi
.SS Extension: \f[C]blank_before_header\f[R]
.PP
Standard Markdown syntax does not require a blank line before a heading.
Pandoc does require this (except, of course, at the beginning of the
document).
The reason for the requirement is that it is all too easy for a
\f[C]#\f[R] to end up at the beginning of a line by accident (perhaps
through line wrapping).
Consider, for example:
.IP
.nf
\f[C]
I like several of their flavors of ice cream:
#22, for example, and #5.
\f[R]
.fi
.SS Extension: \f[C]space_in_atx_header\f[R]
.PP
Many Markdown implementations do not require a space between the opening
\f[C]#\f[R]s of an ATX heading and the heading text, so that
\f[C]#5 bolt\f[R] and \f[C]#hashtag\f[R] count as headings.
With this extension, pandoc does require the space.
.SS Heading identifiers
.PP
See also the \f[C]auto_identifiers\f[R] extension above.
.SS Extension: \f[C]header_attributes\f[R]
.PP
Headings can be assigned attributes using this syntax at the end of the
line containing the heading text:
.IP
.nf
\f[C]
{#identifier .class .class key=value key=value}
\f[R]
.fi
.PP
Thus, for example, the following headings will all be assigned the
identifier \f[C]foo\f[R]:
.IP
.nf
\f[C]
# My heading {#foo}
## My heading ## {#foo}
My other heading {#foo}
---------------
\f[R]
.fi
.PP
(This syntax is compatible with PHP Markdown Extra.)
.PP
Note that although this syntax allows assignment of classes and
key/value attributes, writers generally don\[cq]t use all of this
information.
Identifiers, classes, and key/value attributes are used in HTML and
HTML-based formats such as EPUB and slidy.
Identifiers are used for labels and link anchors in the LaTeX, ConTeXt,
Textile, Jira markup, and AsciiDoc writers.
.PP
Headings with the class \f[C]unnumbered\f[R] will not be numbered, even
if \f[C]--number-sections\f[R] is specified.
A single hyphen (\f[C]-\f[R]) in an attribute context is equivalent to
\f[C].unnumbered\f[R], and preferable in non-English documents.
So,
.IP
.nf
\f[C]
# My heading {-}
\f[R]
.fi
.PP
is just the same as
.IP
.nf
\f[C]
# My heading {.unnumbered}
\f[R]
.fi
.PP
If the \f[C]unlisted\f[R] class is present in addition to
\f[C]unnumbered\f[R], the heading will not be included in a table of
contents.
(Currently this feature is only implemented for certain formats: those
based on LaTeX and HTML, PowerPoint, and RTF.)
.SS Extension: \f[C]implicit_header_references\f[R]
.PP
Pandoc behaves as if reference links have been defined for each heading.
So, to link to a heading
.IP
.nf
\f[C]
# Heading identifiers in HTML
\f[R]
.fi
.PP
you can simply write
.IP
.nf
\f[C]
[Heading identifiers in HTML]
\f[R]
.fi
.PP
or
.IP
.nf
\f[C]
[Heading identifiers in HTML][]
\f[R]
.fi
.PP
or
.IP
.nf
\f[C]
[the section on heading identifiers][heading identifiers in
HTML]
\f[R]
.fi
.PP
instead of giving the identifier explicitly:
.IP
.nf
\f[C]
[Heading identifiers in HTML](#heading-identifiers-in-html)
\f[R]
.fi
.PP
If there are multiple headings with identical text, the corresponding
reference will link to the first one only, and you will need to use
explicit links to link to the others, as described above.
.PP
Like regular reference links, these references are case-insensitive.
.PP
Explicit link reference definitions always take priority over implicit
heading references.
So, in the following example, the link will point to \f[C]bar\f[R], not
to \f[C]#foo\f[R]:
.IP
.nf
\f[C]
# Foo
[foo]: bar
See [foo]
\f[R]
.fi
.SS Block quotations
.PP
Markdown uses email conventions for quoting blocks of text.
A block quotation is one or more paragraphs or other block elements
(such as lists or headings), with each line preceded by a \f[C]>\f[R]
character and an optional space.
(The \f[C]>\f[R] need not start at the left margin, but it should not be
indented more than three spaces.)
.IP
.nf
\f[C]
> This is a block quote. This
> paragraph has two lines.
>
> 1. This is a list inside a block quote.
> 2. Second item.
\f[R]
.fi
.PP
A \[lq]lazy\[rq] form, which requires the \f[C]>\f[R] character only on
the first line of each block, is also allowed:
.IP
.nf
\f[C]
> This is a block quote. This
paragraph has two lines.
> 1. This is a list inside a block quote.
2. Second item.
\f[R]
.fi
.PP
Among the block elements that can be contained in a block quote are
other block quotes.
That is, block quotes can be nested:
.IP
.nf
\f[C]
> This is a block quote.
>
> > A block quote within a block quote.
\f[R]
.fi
.PP
If the \f[C]>\f[R] character is followed by an optional space, that
space will be considered part of the block quote marker and not part of
the indentation of the contents.
Thus, to put an indented code block in a block quote, you need five
spaces after the \f[C]>\f[R]:
.IP
.nf
\f[C]
> code
\f[R]
.fi
.SS Extension: \f[C]blank_before_blockquote\f[R]
.PP
Standard Markdown syntax does not require a blank line before a block
quote.
Pandoc does require this (except, of course, at the beginning of the
document).
The reason for the requirement is that it is all too easy for a
\f[C]>\f[R] to end up at the beginning of a line by accident (perhaps
through line wrapping).
So, unless the \f[C]markdown_strict\f[R] format is used, the following
does not produce a nested block quote in pandoc:
.IP
.nf
\f[C]
> This is a block quote.
>> Nested.
\f[R]
.fi
.SS Verbatim (code) blocks
.SS Indented code blocks
.PP
A block of text indented four spaces (or one tab) is treated as verbatim
text: that is, special characters do not trigger special formatting, and
all spaces and line breaks are preserved.
For example,
.IP
.nf
\f[C]
if (a > 3) {
moveShip(5 * gravity, DOWN);
}
\f[R]
.fi
.PP
The initial (four space or one tab) indentation is not considered part
of the verbatim text, and is removed in the output.
.PP
Note: blank lines in the verbatim text need not begin with four spaces.
.SS Fenced code blocks
.SS Extension: \f[C]fenced_code_blocks\f[R]
.PP
In addition to standard indented code blocks, pandoc supports
\f[I]fenced\f[R] code blocks.
These begin with a row of three or more tildes (\f[C]\[ti]\f[R]) and end
with a row of tildes that must be at least as long as the starting row.
Everything between these lines is treated as code.
No indentation is necessary:
.IP
.nf
\f[C]
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
if (a > 3) {
moveShip(5 * gravity, DOWN);
}
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
\f[R]
.fi
.PP
Like regular code blocks, fenced code blocks must be separated from
surrounding text by blank lines.
.PP
If the code itself contains a row of tildes or backticks, just use a
longer row of tildes or backticks at the start and end:
.IP
.nf
\f[C]
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
code including tildes
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
\f[R]
.fi
.SS Extension: \f[C]backtick_code_blocks\f[R]
.PP
Same as \f[C]fenced_code_blocks\f[R], but uses backticks
(\f[C]\[ga]\f[R]) instead of tildes (\f[C]\[ti]\f[R]).
.SS Extension: \f[C]fenced_code_attributes\f[R]
.PP
Optionally, you may attach attributes to fenced or backtick code block
using this syntax:
.IP
.nf
\f[C]
\[ti]\[ti]\[ti]\[ti] {#mycode .haskell .numberLines startFrom=\[dq]100\[dq]}
qsort [] = []
qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
qsort (filter (>= x) xs)
\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
\f[R]
.fi
.PP
Here \f[C]mycode\f[R] is an identifier, \f[C]haskell\f[R] and
\f[C]numberLines\f[R] are classes, and \f[C]startFrom\f[R] is an
attribute with value \f[C]100\f[R].
Some output formats can use this information to do syntax highlighting.
Currently, the only output formats that uses this information are HTML,
LaTeX, Docx, Ms, and PowerPoint.
If highlighting is supported for your output format and language, then
the code block above will appear highlighted, with numbered lines.
(To see which languages are supported, type
\f[C]pandoc --list-highlight-languages\f[R].) Otherwise, the code block
above will appear as follows:
.IP
.nf
\f[C]
<pre id=\[dq]mycode\[dq] class=\[dq]haskell numberLines\[dq] startFrom=\[dq]100\[dq]>
<code>
...
</code>
</pre>
\f[R]
.fi
.PP
The \f[C]numberLines\f[R] (or \f[C]number-lines\f[R]) class will cause
the lines of the code block to be numbered, starting with \f[C]1\f[R] or
the value of the \f[C]startFrom\f[R] attribute.
The \f[C]lineAnchors\f[R] (or \f[C]line-anchors\f[R]) class will cause
the lines to be clickable anchors in HTML output.
.PP
A shortcut form can also be used for specifying the language of the code
block:
.IP
.nf
\f[C]
\[ga]\[ga]\[ga]haskell
qsort [] = []
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
This is equivalent to:
.IP
.nf
\f[C]
\[ga]\[ga]\[ga] {.haskell}
qsort [] = []
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
If the \f[C]fenced_code_attributes\f[R] extension is disabled, but input
contains class attribute(s) for the code block, the first class
attribute will be printed after the opening fence as a bare word.
.PP
To prevent all highlighting, use the \f[C]--no-highlight\f[R] flag.
To set the highlighting style, use \f[C]--highlight-style\f[R].
For more information on highlighting, see Syntax highlighting, below.
.SS Line blocks
.SS Extension: \f[C]line_blocks\f[R]
.PP
A line block is a sequence of lines beginning with a vertical bar
(\f[C]|\f[R]) followed by a space.
The division into lines will be preserved in the output, as will any
leading spaces; otherwise, the lines will be formatted as Markdown.
This is useful for verse and addresses:
.IP
.nf
\f[C]
| The limerick packs laughs anatomical
| In space that is quite economical.
| But the good ones I\[aq]ve seen
| So seldom are clean
| And the clean ones so seldom are comical
| 200 Main St.
| Berkeley, CA 94718
\f[R]
.fi
.PP
The lines can be hard-wrapped if needed, but the continuation line must
begin with a space.
.IP
.nf
\f[C]
| The Right Honorable Most Venerable and Righteous Samuel L.
Constable, Jr.
| 200 Main St.
| Berkeley, CA 94718
\f[R]
.fi
.PP
Inline formatting (such as emphasis) is allowed in the content, but not
block-level formatting (such as block quotes or lists).
.PP
This syntax is borrowed from reStructuredText.
.SS Lists
.SS Bullet lists
.PP
A bullet list is a list of bulleted list items.
A bulleted list item begins with a bullet (\f[C]*\f[R], \f[C]+\f[R], or
\f[C]-\f[R]).
Here is a simple example:
.IP
.nf
\f[C]
* one
* two
* three
\f[R]
.fi
.PP
This will produce a \[lq]compact\[rq] list.
If you want a \[lq]loose\[rq] list, in which each item is formatted as a
paragraph, put spaces between the items:
.IP
.nf
\f[C]
* one
* two
* three
\f[R]
.fi
.PP
The bullets need not be flush with the left margin; they may be indented
one, two, or three spaces.
The bullet must be followed by whitespace.
.PP
List items look best if subsequent lines are flush with the first line
(after the bullet):
.IP
.nf
\f[C]
* here is my first
list item.
* and my second.
\f[R]
.fi
.PP
But Markdown also allows a \[lq]lazy\[rq] format:
.IP
.nf
\f[C]
* here is my first
list item.
* and my second.
\f[R]
.fi
.SS Block content in list items
.PP
A list item may contain multiple paragraphs and other block-level
content.
However, subsequent paragraphs must be preceded by a blank line and
indented to line up with the first non-space content after the list
marker.
.IP
.nf
\f[C]
* First paragraph.
Continued.
* Second paragraph. With a code block, which must be indented
eight spaces:
{ code }
\f[R]
.fi
.PP
Exception: if the list marker is followed by an indented code block,
which must begin 5 spaces after the list marker, then subsequent
paragraphs must begin two columns after the last character of the list
marker:
.IP
.nf
\f[C]
* code
continuation paragraph
\f[R]
.fi
.PP
List items may include other lists.
In this case the preceding blank line is optional.
The nested list must be indented to line up with the first non-space
character after the list marker of the containing list item.
.IP
.nf
\f[C]
* fruits
+ apples
- macintosh
- red delicious
+ pears
+ peaches
* vegetables
+ broccoli
+ chard
\f[R]
.fi
.PP
As noted above, Markdown allows you to write list items
\[lq]lazily,\[rq] instead of indenting continuation lines.
However, if there are multiple paragraphs or other blocks in a list
item, the first line of each must be indented.
.IP
.nf
\f[C]
+ A lazy, lazy, list
item.
+ Another one; this looks
bad but is legal.
Second paragraph of second
list item.
\f[R]
.fi
.SS Ordered lists
.PP
Ordered lists work just like bulleted lists, except that the items begin
with enumerators rather than bullets.
.PP
In standard Markdown, enumerators are decimal numbers followed by a
period and a space.
The numbers themselves are ignored, so there is no difference between
this list:
.IP
.nf
\f[C]
1. one
2. two
3. three
\f[R]
.fi
.PP
and this one:
.IP
.nf
\f[C]
5. one
7. two
1. three
\f[R]
.fi
.SS Extension: \f[C]fancy_lists\f[R]
.PP
Unlike standard Markdown, pandoc allows ordered list items to be marked
with uppercase and lowercase letters and roman numerals, in addition to
Arabic numerals.
List markers may be enclosed in parentheses or followed by a single
right-parentheses or period.
They must be separated from the text that follows by at least one space,
and, if the list marker is a capital letter with a period, by at least
two spaces.
.PP
The \f[C]fancy_lists\f[R] extension also allows `\f[C]#\f[R]' to be used
as an ordered list marker in place of a numeral:
.IP
.nf
\f[C]
#. one
#. two
\f[R]
.fi
.SS Extension: \f[C]startnum\f[R]
.PP
Pandoc also pays attention to the type of list marker used, and to the
starting number, and both of these are preserved where possible in the
output format.
Thus, the following yields a list with numbers followed by a single
parenthesis, starting with 9, and a sublist with lowercase roman
numerals:
.IP
.nf
\f[C]
9) Ninth
10) Tenth
11) Eleventh
i. subone
ii. subtwo
iii. subthree
\f[R]
.fi
.PP
Pandoc will start a new list each time a different type of list marker
is used.
So, the following will create three lists:
.IP
.nf
\f[C]
(2) Two
(5) Three
1. Four
* Five
\f[R]
.fi
.PP
If default list markers are desired, use \f[C]#.\f[R]:
.IP
.nf
\f[C]
#. one
#. two
#. three
\f[R]
.fi
.SS Extension: \f[C]task_lists\f[R]
.PP
Pandoc supports task lists, using the syntax of GitHub-Flavored
Markdown.
.IP
.nf
\f[C]
- [ ] an unchecked task list item
- [x] checked item
\f[R]
.fi
.SS Definition lists
.SS Extension: \f[C]definition_lists\f[R]
.PP
Pandoc supports definition lists, using the syntax of PHP Markdown Extra
with some extensions.
.IP
.nf
\f[C]
Term 1
: Definition 1
Term 2 with *inline markup*
: Definition 2
{ some code, part of Definition 2 }
Third paragraph of definition 2.
\f[R]
.fi
.PP
Each term must fit on one line, which may optionally be followed by a
blank line, and must be followed by one or more definitions.
A definition begins with a colon or tilde, which may be indented one or
two spaces.
.PP
A term may have multiple definitions, and each definition may consist of
one or more block elements (paragraph, code block, list, etc.), each
indented four spaces or one tab stop.
The body of the definition (including the first line, aside from the
colon or tilde) should be indented four spaces.
However, as with other Markdown lists, you can \[lq]lazily\[rq] omit
indentation except at the beginning of a paragraph or other block
element:
.IP
.nf
\f[C]
Term 1
: Definition
with lazy continuation.
Second paragraph of the definition.
\f[R]
.fi
.PP
If you leave space before the definition (as in the example above), the
text of the definition will be treated as a paragraph.
In some output formats, this will mean greater spacing between
term/definition pairs.
For a more compact definition list, omit the space before the
definition:
.IP
.nf
\f[C]
Term 1
\[ti] Definition 1
Term 2
\[ti] Definition 2a
\[ti] Definition 2b
\f[R]
.fi
.PP
Note that space between items in a definition list is required.
(A variant that loosens this requirement, but disallows \[lq]lazy\[rq]
hard wrapping, can be activated with \f[C]compact_definition_lists\f[R]:
see Non-default extensions, below.)
.SS Numbered example lists
.SS Extension: \f[C]example_lists\f[R]
.PP
The special list marker \f[C]\[at]\f[R] can be used for sequentially
numbered examples.
The first list item with a \f[C]\[at]\f[R] marker will be numbered `1',
the next `2', and so on, throughout the document.
The numbered examples need not occur in a single list; each new list
using \f[C]\[at]\f[R] will take up where the last stopped.
So, for example:
.IP
.nf
\f[C]
(\[at]) My first example will be numbered (1).
(\[at]) My second example will be numbered (2).
Explanation of examples.
(\[at]) My third example will be numbered (3).
\f[R]
.fi
.PP
Numbered examples can be labeled and referred to elsewhere in the
document:
.IP
.nf
\f[C]
(\[at]good) This is a good example.
As (\[at]good) illustrates, ...
\f[R]
.fi
.PP
The label can be any string of alphanumeric characters, underscores, or
hyphens.
.PP
Note: continuation paragraphs in example lists must always be indented
four spaces, regardless of the length of the list marker.
That is, example lists always behave as if the \f[C]four_space_rule\f[R]
extension is set.
This is because example labels tend to be long, and indenting content to
the first non-space character after the label would be awkward.
.SS Ending a list
.PP
What if you want to put an indented code block after a list?
.IP
.nf
\f[C]
- item one
- item two
{ my code block }
\f[R]
.fi
.PP
Trouble! Here pandoc (like other Markdown implementations) will treat
\f[C]{ my code block }\f[R] as the second paragraph of item two, and not
as a code block.
.PP
To \[lq]cut off\[rq] the list after item two, you can insert some
non-indented content, like an HTML comment, which won\[cq]t produce
visible output in any format:
.IP
.nf
\f[C]
- item one
- item two
<!-- end of list -->
{ my code block }
\f[R]
.fi
.PP
You can use the same trick if you want two consecutive lists instead of
one big list:
.IP
.nf
\f[C]
1. one
2. two
3. three
<!-- -->
1. uno
2. dos
3. tres
\f[R]
.fi
.SS Horizontal rules
.PP
A line containing a row of three or more \f[C]*\f[R], \f[C]-\f[R], or
\f[C]_\f[R] characters (optionally separated by spaces) produces a
horizontal rule:
.IP
.nf
\f[C]
* * * *
---------------
\f[R]
.fi
.SS Tables
.PP
Four kinds of tables may be used.
The first three kinds presuppose the use of a fixed-width font, such as
Courier.
The fourth kind can be used with proportionally spaced fonts, as it does
not require lining up columns.
.SS Extension: \f[C]table_captions\f[R]
.PP
A caption may optionally be provided with all 4 kinds of tables (as
illustrated in the examples below).
A caption is a paragraph beginning with the string \f[C]Table:\f[R] (or
just \f[C]:\f[R]), which will be stripped off.
It may appear either before or after the table.
.SS Extension: \f[C]simple_tables\f[R]
.PP
Simple tables look like this:
.IP
.nf
\f[C]
Right Left Center Default
------- ------ ---------- -------
12 12 12 12
123 123 123 123
1 1 1 1
Table: Demonstration of simple table syntax.
\f[R]
.fi
.PP
The header and table rows must each fit on one line.
Column alignments are determined by the position of the header text
relative to the dashed line below it:
.IP \[bu] 2
If the dashed line is flush with the header text on the right side but
extends beyond it on the left, the column is right-aligned.
.IP \[bu] 2
If the dashed line is flush with the header text on the left side but
extends beyond it on the right, the column is left-aligned.
.IP \[bu] 2
If the dashed line extends beyond the header text on both sides, the
column is centered.
.IP \[bu] 2
If the dashed line is flush with the header text on both sides, the
default alignment is used (in most cases, this will be left).
.PP
The table must end with a blank line, or a line of dashes followed by a
blank line.
.PP
The column header row may be omitted, provided a dashed line is used to
end the table.
For example:
.IP
.nf
\f[C]
------- ------ ---------- -------
12 12 12 12
123 123 123 123
1 1 1 1
------- ------ ---------- -------
\f[R]
.fi
.PP
When the header row is omitted, column alignments are determined on the
basis of the first line of the table body.
So, in the tables above, the columns would be right, left, center, and
right aligned, respectively.
.SS Extension: \f[C]multiline_tables\f[R]
.PP
Multiline tables allow header and table rows to span multiple lines of
text (but cells that span multiple columns or rows of the table are not
supported).
Here is an example:
.IP
.nf
\f[C]
-------------------------------------------------------------
Centered Default Right Left
Header Aligned Aligned Aligned
----------- ------- --------------- -------------------------
First row 12.0 Example of a row that
spans multiple lines.
Second row 5.0 Here\[aq]s another one. Note
the blank line between
rows.
-------------------------------------------------------------
Table: Here\[aq]s the caption. It, too, may span
multiple lines.
\f[R]
.fi
.PP
These work like simple tables, but with the following differences:
.IP \[bu] 2
They must begin with a row of dashes, before the header text (unless the
header row is omitted).
.IP \[bu] 2
They must end with a row of dashes, then a blank line.
.IP \[bu] 2
The rows must be separated by blank lines.
.PP
In multiline tables, the table parser pays attention to the widths of
the columns, and the writers try to reproduce these relative widths in
the output.
So, if you find that one of the columns is too narrow in the output, try
widening it in the Markdown source.
.PP
The header may be omitted in multiline tables as well as simple tables:
.IP
.nf
\f[C]
----------- ------- --------------- -------------------------
First row 12.0 Example of a row that
spans multiple lines.
Second row 5.0 Here\[aq]s another one. Note
the blank line between
rows.
----------- ------- --------------- -------------------------
: Here\[aq]s a multiline table without a header.
\f[R]
.fi
.PP
It is possible for a multiline table to have just one row, but the row
should be followed by a blank line (and then the row of dashes that ends
the table), or the table may be interpreted as a simple table.
.SS Extension: \f[C]grid_tables\f[R]
.PP
Grid tables look like this:
.IP
.nf
\f[C]
: Sample grid table.
+---------------+---------------+--------------------+
| Fruit | Price | Advantages |
+===============+===============+====================+
| Bananas | $1.34 | - built-in wrapper |
| | | - bright color |
+---------------+---------------+--------------------+
| Oranges | $2.10 | - cures scurvy |
| | | - tasty |
+---------------+---------------+--------------------+
\f[R]
.fi
.PP
The row of \f[C]=\f[R]s separates the header from the table body, and
can be omitted for a headerless table.
The cells of grid tables may contain arbitrary block elements (multiple
paragraphs, code blocks, lists, etc.).
Cells that span multiple columns or rows are not supported.
Grid tables can be created easily using Emacs\[cq] table-mode
(\f[C]M-x table-insert\f[R]).
.PP
Alignments can be specified as with pipe tables, by putting colons at
the boundaries of the separator line after the header:
.IP
.nf
\f[C]
+---------------+---------------+--------------------+
| Right | Left | Centered |
+==============:+:==============+:==================:+
| Bananas | $1.34 | built-in wrapper |
+---------------+---------------+--------------------+
\f[R]
.fi
.PP
For headerless tables, the colons go on the top line instead:
.IP
.nf
\f[C]
+--------------:+:--------------+:------------------:+
| Right | Left | Centered |
+---------------+---------------+--------------------+
\f[R]
.fi
.SS Grid Table Limitations
.PP
Pandoc does not support grid tables with row spans or column spans.
This means that neither variable numbers of columns across rows nor
variable numbers of rows across columns are supported by Pandoc.
All grid tables must have the same number of columns in each row, and
the same number of rows in each column.
For example, the Docutils sample grid tables will not render as expected
with Pandoc.
.SS Extension: \f[C]pipe_tables\f[R]
.PP
Pipe tables look like this:
.IP
.nf
\f[C]
| Right | Left | Default | Center |
|------:|:-----|---------|:------:|
| 12 | 12 | 12 | 12 |
| 123 | 123 | 123 | 123 |
| 1 | 1 | 1 | 1 |
: Demonstration of pipe table syntax.
\f[R]
.fi
.PP
The syntax is identical to PHP Markdown Extra tables.
The beginning and ending pipe characters are optional, but pipes are
required between all columns.
The colons indicate column alignment as shown.
The header cannot be omitted.
To simulate a headerless table, include a header with blank cells.
.PP
Since the pipes indicate column boundaries, columns need not be
vertically aligned, as they are in the above example.
So, this is a perfectly legal (though ugly) pipe table:
.IP
.nf
\f[C]
fruit| price
-----|-----:
apple|2.05
pear|1.37
orange|3.09
\f[R]
.fi
.PP
The cells of pipe tables cannot contain block elements like paragraphs
and lists, and cannot span multiple lines.
If a pipe table contains a row whose Markdown content is wider than the
column width (see \f[C]--columns\f[R]), then the table will take up the
full text width and the cell contents will wrap, with the relative cell
widths determined by the number of dashes in the line separating the
table header from the table body.
(For example \f[C]---|-\f[R] would make the first column 3/4 and the
second column 1/4 of the full text width.) On the other hand, if no
lines are wider than column width, then cell contents will not be
wrapped, and the cells will be sized to their contents.
.PP
Note: pandoc also recognizes pipe tables of the following form, as can
be produced by Emacs\[cq] orgtbl-mode:
.IP
.nf
\f[C]
| One | Two |
|-----+-------|
| my | table |
| is | nice |
\f[R]
.fi
.PP
The difference is that \f[C]+\f[R] is used instead of \f[C]|\f[R].
Other orgtbl features are not supported.
In particular, to get non-default column alignment, you\[cq]ll need to
add colons as above.
.SS Metadata blocks
.SS Extension: \f[C]pandoc_title_block\f[R]
.PP
If the file begins with a title block
.IP
.nf
\f[C]
% title
% author(s) (separated by semicolons)
% date
\f[R]
.fi
.PP
it will be parsed as bibliographic information, not regular text.
(It will be used, for example, in the title of standalone LaTeX or HTML
output.) The block may contain just a title, a title and an author, or
all three elements.
If you want to include an author but no title, or a title and a date but
no author, you need a blank line:
.IP
.nf
\f[C]
%
% Author
\f[R]
.fi
.IP
.nf
\f[C]
% My title
%
% June 15, 2006
\f[R]
.fi
.PP
The title may occupy multiple lines, but continuation lines must begin
with leading space, thus:
.IP
.nf
\f[C]
% My title
on multiple lines
\f[R]
.fi
.PP
If a document has multiple authors, the authors may be put on separate
lines with leading space, or separated by semicolons, or both.
So, all of the following are equivalent:
.IP
.nf
\f[C]
% Author One
Author Two
\f[R]
.fi
.IP
.nf
\f[C]
% Author One; Author Two
\f[R]
.fi
.IP
.nf
\f[C]
% Author One;
Author Two
\f[R]
.fi
.PP
The date must fit on one line.
.PP
All three metadata fields may contain standard inline formatting
(italics, links, footnotes, etc.).
.PP
Title blocks will always be parsed, but they will affect the output only
when the \f[C]--standalone\f[R] (\f[C]-s\f[R]) option is chosen.
In HTML output, titles will appear twice: once in the document head
\[en] this is the title that will appear at the top of the window in a
browser \[en] and once at the beginning of the document body.
The title in the document head can have an optional prefix attached
(\f[C]--title-prefix\f[R] or \f[C]-T\f[R] option).
The title in the body appears as an H1 element with class
\[lq]title\[rq], so it can be suppressed or reformatted with CSS.
If a title prefix is specified with \f[C]-T\f[R] and no title block
appears in the document, the title prefix will be used by itself as the
HTML title.
.PP
The man page writer extracts a title, man page section number, and other
header and footer information from the title line.
The title is assumed to be the first word on the title line, which may
optionally end with a (single-digit) section number in parentheses.
(There should be no space between the title and the parentheses.)
Anything after this is assumed to be additional footer and header text.
A single pipe character (\f[C]|\f[R]) should be used to separate the
footer text from the header text.
Thus,
.IP
.nf
\f[C]
% PANDOC(1)
\f[R]
.fi
.PP
will yield a man page with the title \f[C]PANDOC\f[R] and section 1.
.IP
.nf
\f[C]
% PANDOC(1) Pandoc User Manuals
\f[R]
.fi
.PP
will also have \[lq]Pandoc User Manuals\[rq] in the footer.
.IP
.nf
\f[C]
% PANDOC(1) Pandoc User Manuals | Version 4.0
\f[R]
.fi
.PP
will also have \[lq]Version 4.0\[rq] in the header.
.SS Extension: \f[C]yaml_metadata_block\f[R]
.PP
A YAML metadata block is a valid YAML object, delimited by a line of
three hyphens (\f[C]---\f[R]) at the top and a line of three hyphens
(\f[C]---\f[R]) or three dots (\f[C]...\f[R]) at the bottom.
A YAML metadata block may occur anywhere in the document, but if it is
not at the beginning, it must be preceded by a blank line.
(Note that, because of the way pandoc concatenates input files when
several are provided, you may also keep the metadata in a separate YAML
file and pass it to pandoc as an argument, along with your Markdown
files:
.IP
.nf
\f[C]
pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html
\f[R]
.fi
.PP
Just be sure that the YAML file begins with \f[C]---\f[R] and ends with
\f[C]---\f[R] or \f[C]...\f[R].) Alternatively, you can use the
\f[C]--metadata-file\f[R] option.
Using that approach however, you cannot reference content (like
footnotes) from the main markdown input document.
.PP
Metadata will be taken from the fields of the YAML object and added to
any existing document metadata.
Metadata can contain lists and objects (nested arbitrarily), but all
string scalars will be interpreted as Markdown.
Fields with names ending in an underscore will be ignored by pandoc.
(They may be given a role by external processors.) Field names must not
be interpretable as YAML numbers or boolean values (so, for example,
\f[C]yes\f[R], \f[C]True\f[R], and \f[C]15\f[R] cannot be used as field
names).
.PP
A document may contain multiple metadata blocks.
If two metadata blocks attempt to set the same field, the value from the
second block will be taken.
.PP
When pandoc is used with \f[C]-t markdown\f[R] to create a Markdown
document, a YAML metadata block will be produced only if the
\f[C]-s/--standalone\f[R] option is used.
All of the metadata will appear in a single block at the beginning of
the document.
.PP
Note that YAML escaping rules must be followed.
Thus, for example, if a title contains a colon, it must be quoted, and
if it contains a backslash escape, then it must be ensured that it is
not treated as a YAML escape sequence.
The pipe character (\f[C]|\f[R]) can be used to begin an indented block
that will be interpreted literally, without need for escaping.
This form is necessary when the field contains blank lines or
block-level formatting:
.IP
.nf
\f[C]
---
title: \[aq]This is the title: it contains a colon\[aq]
author:
- Author One
- Author Two
keywords: [nothing, nothingness]
abstract: |
This is the abstract.
It consists of two paragraphs.
\&...
\f[R]
.fi
.PP
The literal block after the \f[C]|\f[R] must be indented relative to the
line containing the \f[C]|\f[R].
If it is not, the YAML will be invalid and pandoc will not interpret it
as metadata.
For an overview of the complex rules governing YAML, see the Wikipedia
entry on YAML syntax.
.PP
Template variables will be set automatically from the metadata.
Thus, for example, in writing HTML, the variable \f[C]abstract\f[R] will
be set to the HTML equivalent of the Markdown in the \f[C]abstract\f[R]
field:
.IP
.nf
\f[C]
<p>This is the abstract.</p>
<p>It consists of two paragraphs.</p>
\f[R]
.fi
.PP
Variables can contain arbitrary YAML structures, but the template must
match this structure.
The \f[C]author\f[R] variable in the default templates expects a simple
list or string, but can be changed to support more complicated
structures.
The following combination, for example, would add an affiliation to the
author if one is given:
.IP
.nf
\f[C]
---
title: The document title
author:
- name: Author One
affiliation: University of Somewhere
- name: Author Two
affiliation: University of Nowhere
\&...
\f[R]
.fi
.PP
To use the structured authors in the example above, you would need a
custom template:
.IP
.nf
\f[C]
$for(author)$
$if(author.name)$
$author.name$$if(author.affiliation)$ ($author.affiliation$)$endif$
$else$
$author$
$endif$
$endfor$
\f[R]
.fi
.PP
Raw content to include in the document\[cq]s header may be specified
using \f[C]header-includes\f[R]; however, it is important to mark up
this content as raw code for a particular output format, using the
\f[C]raw_attribute\f[R] extension), or it will be interpreted as
markdown.
For example:
.IP
.nf
\f[C]
header-includes:
- |
\[ga]\[ga]\[ga]{=latex}
\[rs]let\[rs]oldsection\[rs]section
\[rs]renewcommand{\[rs]section}[1]{\[rs]clearpage\[rs]oldsection{#1}}
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
Note: the \f[C]yaml_metadata_block\f[R] extension works with
\f[C]commonmark\f[R] as well as \f[C]markdown\f[R] (and it is enabled by
default in \f[C]gfm\f[R] and \f[C]commonmark_x\f[R]).
However, in these formats the following restrictions apply:
.IP \[bu] 2
The YAML metadata block must occur at the beginning of the document (and
there can be only one).
If multiple files are given as arguments to pandoc, only the first can
be a YAML metadata block.
.IP \[bu] 2
The leaf nodes of the YAML structure are parsed in isolation from each
other and from the rest of the document.
So, for example, you can\[cq]t use a reference link in these contexts if
the link definition is somewhere else in the document.
.SS Backslash escapes
.SS Extension: \f[C]all_symbols_escapable\f[R]
.PP
Except inside a code block or inline code, any punctuation or space
character preceded by a backslash will be treated literally, even if it
would normally indicate formatting.
Thus, for example, if one writes
.IP
.nf
\f[C]
*\[rs]*hello\[rs]**
\f[R]
.fi
.PP
one will get
.IP
.nf
\f[C]
<em>*hello*</em>
\f[R]
.fi
.PP
instead of
.IP
.nf
\f[C]
<strong>hello</strong>
\f[R]
.fi
.PP
This rule is easier to remember than standard Markdown\[cq]s rule, which
allows only the following characters to be backslash-escaped:
.IP
.nf
\f[C]
\[rs]\[ga]*_{}[]()>#+-.!
\f[R]
.fi
.PP
(However, if the \f[C]markdown_strict\f[R] format is used, the standard
Markdown rule will be used.)
.PP
A backslash-escaped space is parsed as a nonbreaking space.
In TeX output, it will appear as \f[C]\[ti]\f[R].
In HTML and XML output, it will appear as a literal unicode nonbreaking
space character (note that it will thus actually look
\[lq]invisible\[rq] in the generated HTML source; you can still use the
\f[C]--ascii\f[R] command-line option to make it appear as an explicit
entity).
.PP
A backslash-escaped newline (i.e.\ a backslash occurring at the end of a
line) is parsed as a hard line break.
It will appear in TeX output as \f[C]\[rs]\[rs]\f[R] and in HTML as
\f[C]<br />\f[R].
This is a nice alternative to Markdown\[cq]s \[lq]invisible\[rq] way of
indicating hard line breaks using two trailing spaces on a line.
.PP
Backslash escapes do not work in verbatim contexts.
.SS Inline formatting
.SS Emphasis
.PP
To \f[I]emphasize\f[R] some text, surround it with \f[C]*\f[R]s or
\f[C]_\f[R], like this:
.IP
.nf
\f[C]
This text is _emphasized with underscores_, and this
is *emphasized with asterisks*.
\f[R]
.fi
.PP
Double \f[C]*\f[R] or \f[C]_\f[R] produces \f[B]strong emphasis\f[R]:
.IP
.nf
\f[C]
This is **strong emphasis** and __with underscores__.
\f[R]
.fi
.PP
A \f[C]*\f[R] or \f[C]_\f[R] character surrounded by spaces, or
backslash-escaped, will not trigger emphasis:
.IP
.nf
\f[C]
This is * not emphasized *, and \[rs]*neither is this\[rs]*.
\f[R]
.fi
.SS Extension: \f[C]intraword_underscores\f[R]
.PP
Because \f[C]_\f[R] is sometimes used inside words and identifiers,
pandoc does not interpret a \f[C]_\f[R] surrounded by alphanumeric
characters as an emphasis marker.
If you want to emphasize just part of a word, use \f[C]*\f[R]:
.IP
.nf
\f[C]
feas*ible*, not feas*able*.
\f[R]
.fi
.SS Strikeout
.SS Extension: \f[C]strikeout\f[R]
.PP
To strikeout a section of text with a horizontal line, begin and end it
with \f[C]\[ti]\[ti]\f[R].
Thus, for example,
.IP
.nf
\f[C]
This \[ti]\[ti]is deleted text.\[ti]\[ti]
\f[R]
.fi
.SS Superscripts and subscripts
.SS Extension: \f[C]superscript\f[R], \f[C]subscript\f[R]
.PP
Superscripts may be written by surrounding the superscripted text by
\f[C]\[ha]\f[R] characters; subscripts may be written by surrounding the
subscripted text by \f[C]\[ti]\f[R] characters.
Thus, for example,
.IP
.nf
\f[C]
H\[ti]2\[ti]O is a liquid. 2\[ha]10\[ha] is 1024.
\f[R]
.fi
.PP
The text between \f[C]\[ha]...\[ha]\f[R] or \f[C]\[ti]...\[ti]\f[R] may
not contain spaces or newlines.
If the superscripted or subscripted text contains spaces, these spaces
must be escaped with backslashes.
(This is to prevent accidental superscripting and subscripting through
the ordinary use of \f[C]\[ti]\f[R] and \f[C]\[ha]\f[R], and also bad
interactions with footnotes.) Thus, if you want the letter P with `a
cat' in subscripts, use \f[C]P\[ti]a\[rs] cat\[ti]\f[R], not
\f[C]P\[ti]a cat\[ti]\f[R].
.SS Verbatim
.PP
To make a short span of text verbatim, put it inside backticks:
.IP
.nf
\f[C]
What is the difference between \[ga]>>=\[ga] and \[ga]>>\[ga]?
\f[R]
.fi
.PP
If the verbatim text includes a backtick, use double backticks:
.IP
.nf
\f[C]
Here is a literal backtick \[ga]\[ga] \[ga] \[ga]\[ga].
\f[R]
.fi
.PP
(The spaces after the opening backticks and before the closing backticks
will be ignored.)
.PP
The general rule is that a verbatim span starts with a string of
consecutive backticks (optionally followed by a space) and ends with a
string of the same number of backticks (optionally preceded by a space).
.PP
Note that backslash-escapes (and other Markdown constructs) do not work
in verbatim contexts:
.IP
.nf
\f[C]
This is a backslash followed by an asterisk: \[ga]\[rs]*\[ga].
\f[R]
.fi
.SS Extension: \f[C]inline_code_attributes\f[R]
.PP
Attributes can be attached to verbatim text, just as with fenced code
blocks:
.IP
.nf
\f[C]
\[ga]<$>\[ga]{.haskell}
\f[R]
.fi
.SS Small caps
.PP
To write small caps, use the \f[C]smallcaps\f[R] class:
.IP
.nf
\f[C]
[Small caps]{.smallcaps}
\f[R]
.fi
.PP
Or, without the \f[C]bracketed_spans\f[R] extension:
.IP
.nf
\f[C]
<span class=\[dq]smallcaps\[dq]>Small caps</span>
\f[R]
.fi
.PP
For compatibility with other Markdown flavors, CSS is also supported:
.IP
.nf
\f[C]
<span style=\[dq]font-variant:small-caps;\[dq]>Small caps</span>
\f[R]
.fi
.PP
This will work in all output formats that support small caps.
.SS Math
.SS Extension: \f[C]tex_math_dollars\f[R]
.PP
Anything between two \f[C]$\f[R] characters will be treated as TeX math.
The opening \f[C]$\f[R] must have a non-space character immediately to
its right, while the closing \f[C]$\f[R] must have a non-space character
immediately to its left, and must not be followed immediately by a
digit.
Thus, \f[C]$20,000 and $30,000\f[R] won\[cq]t parse as math.
If for some reason you need to enclose text in literal \f[C]$\f[R]
characters, backslash-escape them and they won\[cq]t be treated as math
delimiters.
.PP
For display math, use \f[C]$$\f[R] delimiters.
(In this case, the delimiters may be separated from the formula by
whitespace.
However, there can be no blank lines betwen the opening and closing
\f[C]$$\f[R] delimiters.)
.PP
TeX math will be printed in all output formats.
How it is rendered depends on the output format:
.TP
LaTeX
It will appear verbatim surrounded by \f[C]\[rs](...\[rs])\f[R] (for
inline math) or \f[C]\[rs][...\[rs]]\f[R] (for display math).
.TP
Markdown, Emacs Org mode, ConTeXt, ZimWiki
It will appear verbatim surrounded by \f[C]$...$\f[R] (for inline math)
or \f[C]$$...$$\f[R] (for display math).
.TP
XWiki
It will appear verbatim surrounded by
\f[C]{{formula}}..{{/formula}}\f[R].
.TP
reStructuredText
It will be rendered using an interpreted text role \f[C]:math:\f[R].
.TP
AsciiDoc
For AsciiDoc output format (\f[C]-t asciidoc\f[R]) it will appear
verbatim surrounded by \f[C]latexmath:[$...$]\f[R] (for inline math) or
\f[C][latexmath]++++\[rs][...\[rs]]+++\f[R] (for display math).
For AsciiDoctor output format (\f[C]-t asciidoctor\f[R]) the LaTex
delimiters (\f[C]$..$\f[R] and \f[C]\[rs][..\[rs]]\f[R]) are omitted.
.TP
Texinfo
It will be rendered inside a \f[C]\[at]math\f[R] command.
.TP
roff man, Jira markup
It will be rendered verbatim without \f[C]$\f[R]\[cq]s.
.TP
MediaWiki, DokuWiki
It will be rendered inside \f[C]<math>\f[R] tags.
.TP
Textile
It will be rendered inside \f[C]<span class=\[dq]math\[dq]>\f[R] tags.
.TP
RTF, OpenDocument
It will be rendered, if possible, using Unicode characters, and will
otherwise appear verbatim.
.TP
ODT
It will be rendered, if possible, using MathML.
.TP
DocBook
If the \f[C]--mathml\f[R] flag is used, it will be rendered using MathML
in an \f[C]inlineequation\f[R] or \f[C]informalequation\f[R] tag.
Otherwise it will be rendered, if possible, using Unicode characters.
.TP
Docx
It will be rendered using OMML math markup.
.TP
FictionBook2
If the \f[C]--webtex\f[R] option is used, formulas are rendered as
images using CodeCogs or other compatible web service, downloaded and
embedded in the e-book.
Otherwise, they will appear verbatim.
.TP
HTML, Slidy, DZSlides, S5, EPUB
The way math is rendered in HTML will depend on the command-line options
selected.
Therefore see Math rendering in HTML above.
.SS Raw HTML
.SS Extension: \f[C]raw_html\f[R]
.PP
Markdown allows you to insert raw HTML (or DocBook) anywhere in a
document (except verbatim contexts, where \f[C]<\f[R], \f[C]>\f[R], and
\f[C]&\f[R] are interpreted literally).
(Technically this is not an extension, since standard Markdown allows
it, but it has been made an extension so that it can be disabled if
desired.)
.PP
The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,
DZSlides, EPUB, Markdown, CommonMark, Emacs Org mode, and Textile
output, and suppressed in other formats.
.PP
For a more explicit way of including raw HTML in a Markdown document,
see the \f[C]raw_attribute\f[R] extension.
.PP
In the CommonMark format, if \f[C]raw_html\f[R] is enabled,
superscripts, subscripts, strikeouts and small capitals will be
represented as HTML.
Otherwise, plain-text fallbacks will be used.
Note that even if \f[C]raw_html\f[R] is disabled, tables will be
rendered with HTML syntax if they cannot use pipe syntax.
.SS Extension: \f[C]markdown_in_html_blocks\f[R]
.PP
Standard Markdown allows you to include HTML \[lq]blocks\[rq]: blocks of
HTML between balanced tags that are separated from the surrounding text
with blank lines, and start and end at the left margin.
Within these blocks, everything is interpreted as HTML, not Markdown; so
(for example), \f[C]*\f[R] does not signify emphasis.
.PP
Pandoc behaves this way when the \f[C]markdown_strict\f[R] format is
used; but by default, pandoc interprets material between HTML block tags
as Markdown.
Thus, for example, pandoc will turn
.IP
.nf
\f[C]
<table>
<tr>
<td>*one*</td>
<td>[a link](https://google.com)</td>
</tr>
</table>
\f[R]
.fi
.PP
into
.IP
.nf
\f[C]
<table>
<tr>
<td><em>one</em></td>
<td><a href=\[dq]https://google.com\[dq]>a link</a></td>
</tr>
</table>
\f[R]
.fi
.PP
whereas \f[C]Markdown.pl\f[R] will preserve it as is.
.PP
There is one exception to this rule: text between \f[C]<script>\f[R],
\f[C]<style>\f[R], and \f[C]<textarea>\f[R] tags is not interpreted as
Markdown.
.PP
This departure from standard Markdown should make it easier to mix
Markdown with HTML block elements.
For example, one can surround a block of Markdown text with
\f[C]<div>\f[R] tags without preventing it from being interpreted as
Markdown.
.SS Extension: \f[C]native_divs\f[R]
.PP
Use native pandoc \f[C]Div\f[R] blocks for content inside
\f[C]<div>\f[R] tags.
For the most part this should give the same output as
\f[C]markdown_in_html_blocks\f[R], but it makes it easier to write
pandoc filters to manipulate groups of blocks.
.SS Extension: \f[C]native_spans\f[R]
.PP
Use native pandoc \f[C]Span\f[R] blocks for content inside
\f[C]<span>\f[R] tags.
For the most part this should give the same output as
\f[C]raw_html\f[R], but it makes it easier to write pandoc filters to
manipulate groups of inlines.
.SS Extension: \f[C]raw_tex\f[R]
.PP
In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be
included in a document.
Inline TeX commands will be preserved and passed unchanged to the LaTeX
and ConTeXt writers.
Thus, for example, you can use LaTeX to include BibTeX citations:
.IP
.nf
\f[C]
This result was proved in \[rs]cite{jones.1967}.
\f[R]
.fi
.PP
Note that in LaTeX environments, like
.IP
.nf
\f[C]
\[rs]begin{tabular}{|l|l|}\[rs]hline
Age & Frequency \[rs]\[rs] \[rs]hline
18--25 & 15 \[rs]\[rs]
26--35 & 33 \[rs]\[rs]
36--45 & 22 \[rs]\[rs] \[rs]hline
\[rs]end{tabular}
\f[R]
.fi
.PP
the material between the begin and end tags will be interpreted as raw
LaTeX, not as Markdown.
.PP
For a more explicit and flexible way of including raw TeX in a Markdown
document, see the \f[C]raw_attribute\f[R] extension.
.PP
Inline LaTeX is ignored in output formats other than Markdown, LaTeX,
Emacs Org mode, and ConTeXt.
.SS Generic raw attribute
.SS Extension: \f[C]raw_attribute\f[R]
.PP
Inline spans and fenced code blocks with a special kind of attribute
will be parsed as raw content with the designated format.
For example, the following produces a raw roff \f[C]ms\f[R] block:
.IP
.nf
\f[C]
\[ga]\[ga]\[ga]{=ms}
\&.MYMACRO
blah blah
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
And the following produces a raw \f[C]html\f[R] inline element:
.IP
.nf
\f[C]
This is \[ga]<a>html</a>\[ga]{=html}
\f[R]
.fi
.PP
This can be useful to insert raw xml into \f[C]docx\f[R] documents, e.g.
a pagebreak:
.IP
.nf
\f[C]
\[ga]\[ga]\[ga]{=openxml}
<w:p>
<w:r>
<w:br w:type=\[dq]page\[dq]/>
</w:r>
</w:p>
\[ga]\[ga]\[ga]
\f[R]
.fi
.PP
The format name should match the target format name (see
\f[C]-t/--to\f[R], above, for a list, or use
\f[C]pandoc --list-output-formats\f[R]).
Use \f[C]openxml\f[R] for \f[C]docx\f[R] output, \f[C]opendocument\f[R]
for \f[C]odt\f[R] output, \f[C]html5\f[R] for \f[C]epub3\f[R] output,
\f[C]html4\f[R] for \f[C]epub2\f[R] output, and \f[C]latex\f[R],
\f[C]beamer\f[R], \f[C]ms\f[R], or \f[C]html5\f[R] for \f[C]pdf\f[R]
output (depending on what you use for \f[C]--pdf-engine\f[R]).
.PP
This extension presupposes that the relevant kind of inline code or
fenced code block is enabled.
Thus, for example, to use a raw attribute with a backtick code block,
\f[C]backtick_code_blocks\f[R] must be enabled.
.PP
The raw attribute cannot be combined with regular attributes.
.SS LaTeX macros
.SS Extension: \f[C]latex_macros\f[R]
.PP
When this extension is enabled, pandoc will parse LaTeX macro
definitions and apply the resulting macros to all LaTeX math and raw
LaTeX.
So, for example, the following will work in all output formats, not just
LaTeX:
.IP
.nf
\f[C]
\[rs]newcommand{\[rs]tuple}[1]{\[rs]langle #1 \[rs]rangle}
$\[rs]tuple{a, b, c}$
\f[R]
.fi
.PP
Note that LaTeX macros will not be applied if they occur inside a raw
span or block marked with the \f[C]raw_attribute\f[R] extension.
.PP
When \f[C]latex_macros\f[R] is disabled, the raw LaTeX and math will not
have macros applied.
This is usually a better approach when you are targeting LaTeX or PDF.
.PP
Macro definitions in LaTeX will be passed through as raw LaTeX only if
\f[C]latex_macros\f[R] is not enabled.
Macro definitions in Markdown source (or other formats allowing
\f[C]raw_tex\f[R]) will be passed through regardless of whether
\f[C]latex_macros\f[R] is enabled.
.SS Links
.PP
Markdown allows links to be specified in several ways.
.SS Automatic links
.PP
If you enclose a URL or email address in pointy brackets, it will become
a link:
.IP
.nf
\f[C]
<https://google.com>
<sam\[at]green.eggs.ham>
\f[R]
.fi
.SS Inline links
.PP
An inline link consists of the link text in square brackets, followed by
the URL in parentheses.
(Optionally, the URL can be followed by a link title, in quotes.)
.IP
.nf
\f[C]
This is an [inline link](/url), and here\[aq]s [one with
a title](https://fsf.org \[dq]click here for a good time!\[dq]).
\f[R]
.fi
.PP
There can be no space between the bracketed part and the parenthesized
part.
The link text can contain formatting (such as emphasis), but the title
cannot.
.PP
Email addresses in inline links are not autodetected, so they have to be
prefixed with \f[C]mailto\f[R]:
.IP
.nf
\f[C]
[Write me!](mailto:sam\[at]green.eggs.ham)
\f[R]
.fi
.SS Reference links
.PP
An \f[I]explicit\f[R] reference link has two parts, the link itself and
the link definition, which may occur elsewhere in the document (either
before or after the link).
.PP
The link consists of link text in square brackets, followed by a label
in square brackets.
(There cannot be space between the two unless the
\f[C]spaced_reference_links\f[R] extension is enabled.) The link
definition consists of the bracketed label, followed by a colon and a
space, followed by the URL, and optionally (after a space) a link title
either in quotes or in parentheses.
The label must not be parseable as a citation (assuming the
\f[C]citations\f[R] extension is enabled): citations take precedence
over link labels.
.PP
Here are some examples:
.IP
.nf
\f[C]
[my label 1]: /foo/bar.html \[dq]My title, optional\[dq]
[my label 2]: /foo
[my label 3]: https://fsf.org (The free software foundation)
[my label 4]: /bar#special \[aq]A title in single quotes\[aq]
\f[R]
.fi
.PP
The URL may optionally be surrounded by angle brackets:
.IP
.nf
\f[C]
[my label 5]: <http://foo.bar.baz>
\f[R]
.fi
.PP
The title may go on the next line:
.IP
.nf
\f[C]
[my label 3]: https://fsf.org
\[dq]The free software foundation\[dq]
\f[R]
.fi
.PP
Note that link labels are not case sensitive.
So, this will work:
.IP
.nf
\f[C]
Here is [my link][FOO]
[Foo]: /bar/baz
\f[R]
.fi
.PP
In an \f[I]implicit\f[R] reference link, the second pair of brackets is
empty:
.IP
.nf
\f[C]
See [my website][].
[my website]: http://foo.bar.baz
\f[R]
.fi
.PP
Note: In \f[C]Markdown.pl\f[R] and most other Markdown implementations,
reference link definitions cannot occur in nested constructions such as
list items or block quotes.
Pandoc lifts this arbitrary seeming restriction.
So the following is fine in pandoc, though not in most other
implementations:
.IP
.nf
\f[C]
> My block [quote].
>
> [quote]: /foo
\f[R]
.fi
.SS Extension: \f[C]shortcut_reference_links\f[R]
.PP
In a \f[I]shortcut\f[R] reference link, the second pair of brackets may
be omitted entirely:
.IP
.nf
\f[C]
See [my website].
[my website]: http://foo.bar.baz
\f[R]
.fi
.SS Internal links
.PP
To link to another section of the same document, use the automatically
generated identifier (see Heading identifiers).
For example:
.IP
.nf
\f[C]
See the [Introduction](#introduction).
\f[R]
.fi
.PP
or
.IP
.nf
\f[C]
See the [Introduction].
[Introduction]: #introduction
\f[R]
.fi
.PP
Internal links are currently supported for HTML formats (including HTML
slide shows and EPUB), LaTeX, and ConTeXt.
.SS Images
.PP
A link immediately preceded by a \f[C]!\f[R] will be treated as an
image.
The link text will be used as the image\[cq]s alt text:
.IP
.nf
\f[C]
![movie reel]
[movie reel]: movie.gif
\f[R]
.fi
.SS Extension: \f[C]implicit_figures\f[R]
.PP
An image with nonempty alt text, occurring by itself in a paragraph,
will be rendered as a figure with a caption.
The image\[cq]s alt text will be used as the caption.
.IP
.nf
\f[C]
\f[R]
.fi
.PP
How this is rendered depends on the output format.
Some output formats (e.g.\ RTF) do not yet support figures.
In those formats, you\[cq]ll just get an image in a paragraph by itself,
with no caption.
.PP
If you just want a regular inline image, just make sure it is not the
only thing in the paragraph.
One way to do this is to insert a nonbreaking space after the image:
.IP
.nf
\f[C]
![This image won\[aq]t be a figure](/url/of/image.png)\[rs]
\f[R]
.fi
.PP
Note that in reveal.js slide shows, an image in a paragraph by itself
that has the \f[C]stretch\f[R] class will fill the screen, and the
caption and figure tags will be omitted.
.SS Extension: \f[C]link_attributes\f[R]
.PP
Attributes can be set on links and images:
.IP
.nf
\f[C]
An inline {#id .class width=30 height=20px}
and a reference ![image][ref] with attributes.
[ref]: foo.jpg \[dq]optional title\[dq] {#id .class key=val key2=\[dq]val 2\[dq]}
\f[R]
.fi
.PP
(This syntax is compatible with PHP Markdown Extra when only
\f[C]#id\f[R] and \f[C].class\f[R] are used.)
.PP
For HTML and EPUB, all known HTML5 attributes except \f[C]width\f[R] and
\f[C]height\f[R] (but including \f[C]srcset\f[R] and \f[C]sizes\f[R])
are passed through as is.
Unknown attributes are passed through as custom attributes, with
\f[C]data-\f[R] prepended.
The other writers ignore attributes that are not specifically supported
by their output format.
.PP
The \f[C]width\f[R] and \f[C]height\f[R] attributes on images are
treated specially.
When used without a unit, the unit is assumed to be pixels.
However, any of the following unit identifiers can be used:
\f[C]px\f[R], \f[C]cm\f[R], \f[C]mm\f[R], \f[C]in\f[R], \f[C]inch\f[R]
and \f[C]%\f[R].
There must not be any spaces between the number and the unit.
For example:
.IP
.nf
\f[C]
{ width=50% }
\f[R]
.fi
.IP \[bu] 2
Dimensions may be converted to a form that is compatible with the output
format (for example, dimensions given in pixels will be converted to
inches when converting HTML to LaTeX).
Conversion between pixels and physical measurements is affected by the
\f[C]--dpi\f[R] option (by default, 96 dpi is assumed, unless the image
itself contains dpi information).
.IP \[bu] 2
The \f[C]%\f[R] unit is generally relative to some available space.
For example the above example will render to the following.
.RS 2
.IP \[bu] 2
HTML:
\f[C]<img href=\[dq]file.jpg\[dq] style=\[dq]width: 50%;\[dq] />\f[R]
.IP \[bu] 2
LaTeX:
\f[C]\[rs]includegraphics[width=0.5\[rs]textwidth,height=\[rs]textheight]{file.jpg}\f[R]
(If you\[cq]re using a custom template, you need to configure
\f[C]graphicx\f[R] as in the default template.)
.IP \[bu] 2
ConTeXt:
\f[C]\[rs]externalfigure[file.jpg][width=0.5\[rs]textwidth]\f[R]
.RE
.IP \[bu] 2
Some output formats have a notion of a class (ConTeXt) or a unique
identifier (LaTeX \f[C]\[rs]caption\f[R]), or both (HTML).
.IP \[bu] 2
When no \f[C]width\f[R] or \f[C]height\f[R] attributes are specified,
the fallback is to look at the image resolution and the dpi metadata
embedded in the image file.
.SS Divs and Spans
.PP
Using the \f[C]native_divs\f[R] and \f[C]native_spans\f[R] extensions
(see above), HTML syntax can be used as part of markdown to create
native \f[C]Div\f[R] and \f[C]Span\f[R] elements in the pandoc AST (as
opposed to raw HTML).
However, there is also nicer syntax available:
.SS Extension: \f[C]fenced_divs\f[R]
.PP
Allow special fenced syntax for native \f[C]Div\f[R] blocks.
A Div starts with a fence containing at least three consecutive colons
plus some attributes.
The attributes may optionally be followed by another string of
consecutive colons.
The attribute syntax is exactly as in fenced code blocks (see Extension:
\f[C]fenced_code_attributes\f[R]).
As with fenced code blocks, one can use either attributes in curly
braces or a single unbraced word, which will be treated as a class name.
The Div ends with another line containing a string of at least three
consecutive colons.
The fenced Div should be separated by blank lines from preceding and
following blocks.
.PP
Example:
.IP
.nf
\f[C]
::::: {#special .sidebar}
Here is a paragraph.
And another.
:::::
\f[R]
.fi
.PP
Fenced divs can be nested.
Opening fences are distinguished because they \f[I]must\f[R] have
attributes:
.IP
.nf
\f[C]
::: Warning ::::::
This is a warning.
::: Danger
This is a warning within a warning.
:::
::::::::::::::::::
\f[R]
.fi
.PP
Fences without attributes are always closing fences.
Unlike with fenced code blocks, the number of colons in the closing
fence need not match the number in the opening fence.
However, it can be helpful for visual clarity to use fences of different
lengths to distinguish nested divs from their parents.
.SS Extension: \f[C]bracketed_spans\f[R]
.PP
A bracketed sequence of inlines, as one would use to begin a link, will
be treated as a \f[C]Span\f[R] with attributes if it is followed
immediately by attributes:
.IP
.nf
\f[C]
[This is *some text*]{.class key=\[dq]val\[dq]}
\f[R]
.fi
.SS Footnotes
.SS Extension: \f[C]footnotes\f[R]
.PP
Pandoc\[cq]s Markdown allows footnotes, using the following syntax:
.IP
.nf
\f[C]
Here is a footnote reference,[\[ha]1] and another.[\[ha]longnote]
[\[ha]1]: Here is the footnote.
[\[ha]longnote]: Here\[aq]s one with multiple blocks.
Subsequent paragraphs are indented to show that they
belong to the previous footnote.
{ some.code }
The whole paragraph can be indented, or just the first
line. In this way, multi-paragraph footnotes work like
multi-paragraph list items.
This paragraph won\[aq]t be part of the note, because it
isn\[aq]t indented.
\f[R]
.fi
.PP
The identifiers in footnote references may not contain spaces, tabs, or
newlines.
These identifiers are used only to correlate the footnote reference with
the note itself; in the output, footnotes will be numbered sequentially.
.PP
The footnotes themselves need not be placed at the end of the document.
They may appear anywhere except inside other block elements (lists,
block quotes, tables, etc.).
Each footnote should be separated from surrounding content (including
other footnotes) by blank lines.
.SS Extension: \f[C]inline_notes\f[R]
.PP
Inline footnotes are also allowed (though, unlike regular notes, they
cannot contain multiple paragraphs).
The syntax is as follows:
.IP
.nf
\f[C]
Here is an inline note.\[ha][Inlines notes are easier to write, since
you don\[aq]t have to pick an identifier and move down to type the
note.]
\f[R]
.fi
.PP
Inline and regular footnotes may be mixed freely.
.SS Citation syntax
.SS Extension: \f[C]citations\f[R]
.PP
To cite a bibliographic item with an identifier foo, use the syntax
\f[C]\[at]foo\f[R].
Normal citations should be included in square brackets, with semicolons
separating distinct items:
.IP
.nf
\f[C]
Blah blah [\[at]doe99; \[at]smith2000; \[at]smith2004].
\f[R]
.fi
.PP
How this is rendered depends on the citation style.
In an author-date style, it might render as
.IP
.nf
\f[C]
Blah blah (Doe 1999, Smith 2000, 2004).
\f[R]
.fi
.PP
In a footnote style, it might render as
.IP
.nf
\f[C]
Blah blah.[\[ha]1]
[\[ha]1]: John Doe, \[dq]Frogs,\[dq] *Journal of Amphibians* 44 (1999);
Susan Smith, \[dq]Flies,\[dq] *Journal of Insects* (2000);
Susan Smith, \[dq]Bees,\[dq] *Journal of Insects* (2004).
\f[R]
.fi
.PP
See the CSL user documentation for more information about CSL styles and
how they affect rendering.
.PP
Unless a citation key start with a letter, digit, or \f[C]_\f[R], and
contains only alphanumerics and internal punctuation characters
(\f[C]:.#$%&-+?<>\[ti]/\f[R]), it must be surrounded by curly braces,
which are not considered part of the key.
In \f[C]\[at]Foo_bar.baz.\f[R], the key is \f[C]Foo_bar.baz\f[R].
The final period is not \f[I]internal\f[R] punctuation, so it is not
included in the key.
In \f[C]\[at]{Foo_bar.baz.}\f[R], the key is \f[C]Foo_bar.baz.\f[R],
including the final period.
The curly braces are recommended if you use URLs as keys:
\f[C][\[at]{https://example.com/bib?name=foobar&date=2000}, p. 33]\f[R].
.PP
Citation items may optionally include a prefix, a locator, and a suffix.
In
.IP
.nf
\f[C]
Blah blah [see \[at]doe99, pp. 33-35 and *passim*; \[at]smith04, chap. 1].
\f[R]
.fi
.PP
The first item (\f[C]doe99\f[R]) has prefix \f[C]see\f[R], locator
\f[C]pp. 33-35\f[R], and suffix \f[C]and *passim*\f[R].
The second item (\f[C]smith04\f[R]) has locator \f[C]chap. 1\f[R] and no
prefix or suffix.
.PP
Pandoc uses some heuristics to separate the locator from the rest of the
subject.
It is sensitive to the locator terms defined in the CSL locale files.
Either abbreviated or unabbreviated forms are accepted.
In the \f[C]en-US\f[R] locale, locator terms can be written in either
singular or plural forms, as \f[C]book\f[R],
\f[C]bk.\f[R]/\f[C]bks.\f[R]; \f[C]chapter\f[R],
\f[C]chap.\f[R]/\f[C]chaps.\f[R]; \f[C]column\f[R],
\f[C]col.\f[R]/\f[C]cols.\f[R]; \f[C]figure\f[R],
\f[C]fig.\f[R]/\f[C]figs.\f[R]; \f[C]folio\f[R],
\f[C]fol.\f[R]/\f[C]fols.\f[R]; \f[C]number\f[R],
\f[C]no.\f[R]/\f[C]nos.\f[R]; \f[C]line\f[R],
\f[C]l.\f[R]/\f[C]ll.\f[R]; \f[C]note\f[R], \f[C]n.\f[R]/\f[C]nn.\f[R];
\f[C]opus\f[R], \f[C]op.\f[R]/\f[C]opp.\f[R]; \f[C]page\f[R],
\f[C]p.\f[R]/\f[C]pp.\f[R]; \f[C]paragraph\f[R],
\f[C]para.\f[R]/\f[C]paras.\f[R]; \f[C]part\f[R],
\f[C]pt.\f[R]/\f[C]pts.\f[R]; \f[C]section\f[R],
\f[C]sec.\f[R]/\f[C]secs.\f[R]; \f[C]sub verbo\f[R],
\f[C]s.v.\f[R]/\f[C]s.vv.\f[R]; \f[C]verse\f[R],
\f[C]v.\f[R]/\f[C]vv.\f[R]; \f[C]volume\f[R],
\f[C]vol.\f[R]/\f[C]vols.\f[R]; \f[C]\[ps]\f[R]/\f[C]\[ps]\[ps]\f[R];
\f[C]\[sc]\f[R]/\f[C]\[sc]\[sc]\f[R].
If no locator term is used, \[lq]page\[rq] is assumed.
.PP
In complex cases, you can force something to be treated as a locator by
enclosing it in curly braces or prevent parsing the suffix as locator by
prepending curly braces:
.IP
.nf
\f[C]
[\[at]smith{ii, A, D-Z}, with a suffix]
[\[at]smith, {pp. iv, vi-xi, (xv)-(xvii)} with suffix here]
[\[at]smith{}, 99 years later]
\f[R]
.fi
.PP
A minus sign (\f[C]-\f[R]) before the \f[C]\[at]\f[R] will suppress
mention of the author in the citation.
This can be useful when the author is already mentioned in the text:
.IP
.nf
\f[C]
Smith says blah [-\[at]smith04].
\f[R]
.fi
.PP
You can also write an author-in-text citation, by omitting the square
brackets:
.IP
.nf
\f[C]
\[at]smith04 says blah.
\[at]smith04 [p. 33] says blah.
\f[R]
.fi
.PP
This will cause the author\[cq]s name to be rendered, followed by the
bibliographical details.
Use this form when you want to make the citation the subject of a
sentence.
.PP
When you are using a note style, it is usually better to let citeproc
create the footnotes from citations rather than writing an explicit
note.
If you do write an explicit note that contains a citation, note that
normal citations will be put in parentheses, while author-in-text
citations will not.
For this reason, it is sometimes preferable to use the author-in-text
style inside notes when using a note style.
.SS Non-default extensions
.PP
The following Markdown syntax extensions are not enabled by default in
pandoc, but may be enabled by adding \f[C]+EXTENSION\f[R] to the format
name, where \f[C]EXTENSION\f[R] is the name of the extension.
Thus, for example, \f[C]markdown+hard_line_breaks\f[R] is Markdown with
hard line breaks.
.SS Extension: \f[C]rebase_relative_paths\f[R]
.PP
Rewrite relative paths for Markdown links and images, depending on the
path of the file containing the link or image link.
For each link or image, pandoc will compute the directory of the
containing file, relative to the working directory, and prepend the
resulting path to the link or image path.
.PP
The use of this extension is best understood by example.
Suppose you have a a subdirectory for each chapter of a book,
\f[C]chap1\f[R], \f[C]chap2\f[R], \f[C]chap3\f[R].
Each contains a file \f[C]text.md\f[R] and a number of images used in
the chapter.
You would like to have \f[C]\f[R] in
\f[C]chap1/text.md\f[R] refer to \f[C]chap1/spider.jpg\f[R] and
\f[C]\f[R] in \f[C]chap2/text.md\f[R] refer to
\f[C]chap2/spider.jpg\f[R].
To do this, use
.IP
.nf
\f[C]
pandoc chap*/*.md -f markdown+rebase_relative_paths
\f[R]
.fi
.PP
Without this extension, you would have to use
\f[C]\f[R] in \f[C]chap1/text.md\f[R] and
\f[C]\f[R] in \f[C]chap2/text.md\f[R].
Links with relative paths will be rewritten in the same way as images.
.PP
Absolute paths and URLs are not changed.
Neither are empty paths or paths consisting entirely of a fragment,
e.g., \f[C]#foo\f[R].
.PP
Note that relative paths in reference links and images will be rewritten
relative to the file containing the link reference definition, not the
file containing the reference link or image itself, if these differ.
.SS Extension: \f[C]attributes\f[R]
.PP
Allows attributes to be attached to any inline or block-level element.
The syntax for the attributes is the same as that used in
\f[C]header_attributes\f[R].
.IP \[bu] 2
Attributes that occur immediately after an inline element affect that
element.
If they follow a space, then they belong to the space.
(Hence, this option subsumes \f[C]inline_code_attributes\f[R] and
\f[C]link_attributes\f[R].)
.IP \[bu] 2
Attributes that occur immediately before a block element, on a line by
themselves, affect that element.
.IP \[bu] 2
Consecutive attribute specifiers may be used, either for blocks or for
inlines.
Their attributes will be combined.
.IP \[bu] 2
Attributes that occur at the end of the text of a Setext or ATX heading
(separated by whitespace from the text) affect the heading element.
(Hence, this option subsumes \f[C]header_attributes\f[R].)
.IP \[bu] 2
Attributes that occur after the opening fence in a fenced code block
affect the code block element.
(Hence, this option subsumes \f[C]fenced_code_attributes\f[R].)
.IP \[bu] 2
Attributes that occur at the end of a reference link definition affect
links that refer to that definition.
.PP
Note that pandoc\[cq]s AST does not currently allow attributes to be
attached to arbitrary elements.
Hence a Span or Div container will be added if needed.
.SS Extension: \f[C]old_dashes\f[R]
.PP
Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes:
\f[C]-\f[R] before a numeral is an en-dash, and \f[C]--\f[R] is an
em-dash.
This option only has an effect if \f[C]smart\f[R] is enabled.
It is selected automatically for \f[C]textile\f[R] input.
.SS Extension: \f[C]angle_brackets_escapable\f[R]
.PP
Allow \f[C]<\f[R] and \f[C]>\f[R] to be backslash-escaped, as they can
be in GitHub flavored Markdown but not original Markdown.
This is implied by pandoc\[cq]s default \f[C]all_symbols_escapable\f[R].
.SS Extension: \f[C]lists_without_preceding_blankline\f[R]
.PP
Allow a list to occur right after a paragraph, with no intervening blank
space.
.SS Extension: \f[C]four_space_rule\f[R]
.PP
Selects the pandoc <= 2.0 behavior for parsing lists, so that four
spaces indent are needed for list item continuation paragraphs.
.SS Extension: \f[C]spaced_reference_links\f[R]
.PP
Allow whitespace between the two components of a reference link, for
example,
.IP
.nf
\f[C]
[foo] [bar].
\f[R]
.fi
.SS Extension: \f[C]hard_line_breaks\f[R]
.PP
Causes all newlines within a paragraph to be interpreted as hard line
breaks instead of spaces.
.SS Extension: \f[C]ignore_line_breaks\f[R]
.PP
Causes newlines within a paragraph to be ignored, rather than being
treated as spaces or as hard line breaks.
This option is intended for use with East Asian languages where spaces
are not used between words, but text is divided into lines for
readability.
.SS Extension: \f[C]east_asian_line_breaks\f[R]
.PP
Causes newlines within a paragraph to be ignored, rather than being
treated as spaces or as hard line breaks, when they occur between two
East Asian wide characters.
This is a better choice than \f[C]ignore_line_breaks\f[R] for texts that
include a mix of East Asian wide characters and other characters.
.SS Extension: \f[C]emoji\f[R]
.PP
Parses textual emojis like \f[C]:smile:\f[R] as Unicode emoticons.
.SS Extension: \f[C]tex_math_single_backslash\f[R]
.PP
Causes anything between \f[C]\[rs](\f[R] and \f[C]\[rs])\f[R] to be
interpreted as inline TeX math, and anything between \f[C]\[rs][\f[R]
and \f[C]\[rs]]\f[R] to be interpreted as display TeX math.
Note: a drawback of this extension is that it precludes escaping
\f[C](\f[R] and \f[C][\f[R].
.SS Extension: \f[C]tex_math_double_backslash\f[R]
.PP
Causes anything between \f[C]\[rs]\[rs](\f[R] and \f[C]\[rs]\[rs])\f[R]
to be interpreted as inline TeX math, and anything between
\f[C]\[rs]\[rs][\f[R] and \f[C]\[rs]\[rs]]\f[R] to be interpreted as
display TeX math.
.SS Extension: \f[C]markdown_attribute\f[R]
.PP
By default, pandoc interprets material inside block-level tags as
Markdown.
This extension changes the behavior so that Markdown is only parsed
inside block-level tags if the tags have the attribute
\f[C]markdown=1\f[R].
.SS Extension: \f[C]mmd_title_block\f[R]
.PP
Enables a MultiMarkdown style title block at the top of the document,
for example:
.IP
.nf
\f[C]
Title: My title
Author: John Doe
Date: September 1, 2008
Comment: This is a sample mmd title block, with
a field spanning multiple lines.
\f[R]
.fi
.PP
See the MultiMarkdown documentation for details.
If \f[C]pandoc_title_block\f[R] or \f[C]yaml_metadata_block\f[R] is
enabled, it will take precedence over \f[C]mmd_title_block\f[R].
.SS Extension: \f[C]abbreviations\f[R]
.PP
Parses PHP Markdown Extra abbreviation keys, like
.IP
.nf
\f[C]
*[HTML]: Hypertext Markup Language
\f[R]
.fi
.PP
Note that the pandoc document model does not support abbreviations, so
if this extension is enabled, abbreviation keys are simply skipped (as
opposed to being parsed as paragraphs).
.SS Extension: \f[C]autolink_bare_uris\f[R]
.PP
Makes all absolute URIs into links, even when not surrounded by pointy
braces \f[C]<...>\f[R].
.SS Extension: \f[C]mmd_link_attributes\f[R]
.PP
Parses multimarkdown style key-value attributes on link and image
references.
This extension should not be confused with the \f[C]link_attributes\f[R]
extension.
.IP
.nf
\f[C]
This is a reference ![image][ref] with multimarkdown attributes.
[ref]: https://path.to/image \[dq]Image title\[dq] width=20px height=30px
id=myId class=\[dq]myClass1 myClass2\[dq]
\f[R]
.fi
.SS Extension: \f[C]mmd_header_identifiers\f[R]
.PP
Parses multimarkdown style heading identifiers (in square brackets,
after the heading but before any trailing \f[C]#\f[R]s in an ATX
heading).
.SS Extension: \f[C]compact_definition_lists\f[R]
.PP
Activates the definition list syntax of pandoc 1.12.x and earlier.
This syntax differs from the one described above under Definition lists
in several respects:
.IP \[bu] 2
No blank line is required between consecutive items of the definition
list.
.IP \[bu] 2
To get a \[lq]tight\[rq] or \[lq]compact\[rq] list, omit space between
consecutive items; the space between a term and its definition does not
affect anything.
.IP \[bu] 2
Lazy wrapping of paragraphs is not allowed: the entire definition must
be indented four spaces.
.SS Extension: \f[C]gutenberg\f[R]
.PP
Use Project Gutenberg conventions for \f[C]plain\f[R] output: all-caps
for strong emphasis, surround by underscores for regular emphasis, add
extra blank space around headings.
.SS Extension: \f[C]sourcepos\f[R]
.PP
Include source position attributes when parsing \f[C]commonmark\f[R].
For elements that accept attributes, a \f[C]data-pos\f[R] attribute is
added; other elements are placed in a surrounding Div or Span elemnet
with a \f[C]data-pos\f[R] attribute.
.SS Markdown variants
.PP
In addition to pandoc\[cq]s extended Markdown, the following Markdown
variants are supported:
.IP \[bu] 2
\f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
.IP \[bu] 2
\f[C]markdown_github\f[R] (deprecated GitHub-Flavored Markdown)
.IP \[bu] 2
\f[C]markdown_mmd\f[R] (MultiMarkdown)
.IP \[bu] 2
\f[C]markdown_strict\f[R] (Markdown.pl)
.IP \[bu] 2
\f[C]commonmark\f[R] (CommonMark)
.IP \[bu] 2
\f[C]gfm\f[R] (Github-Flavored Markdown)
.IP \[bu] 2
\f[C]commonmark_x\f[R] (CommonMark with many pandoc extensions)
.PP
To see which extensions are supported for a given format, and which are
enabled by default, you can use the command
.IP
.nf
\f[C]
pandoc --list-extensions=FORMAT
\f[R]
.fi
.PP
where \f[C]FORMAT\f[R] is replaced with the name of the format.
.PP
Note that the list of extensions for \f[C]commonmark\f[R],
\f[C]gfm\f[R], and \f[C]commonmark_x\f[R] are defined relative to
default commonmark.
So, for example, \f[C]backtick_code_blocks\f[R] does not appear as an
extension, since it is enabled by default and cannot be disabled.
.SH CITATIONS
.PP
When the \f[C]--citeproc\f[R] option is used, pandoc can automatically
generate citations and a bibliography in a number of styles.
Basic usage is
.IP
.nf
\f[C]
pandoc --citeproc myinput.txt
\f[R]
.fi
.PP
To use this feature, you will need to have
.IP \[bu] 2
a document containing citations (see Extension: \f[C]citations\f[R]);
.IP \[bu] 2
a source of bibliographic data: either an external bibliography file or
a list of \f[C]references\f[R] in the document\[cq]s YAML metadata
.IP \[bu] 2
optionally, a CSL citation style.
.SS Specifying bibliographic data
.PP
You can specify an external bibliography using the
\f[C]bibliography\f[R] metadata field in a YAML metadata section or the
\f[C]--bibliography\f[R] command line argument.
If you want to use multiple bibliography files, you can supply multiple
\f[C]--bibliography\f[R] arguments or set \f[C]bibliography\f[R]
metadata field to YAML array.
A bibliography may have any of these formats:
.PP
.TS
tab(@);
l l.
T{
Format
T}@T{
File extension
T}
_
T{
BibLaTeX
T}@T{
\&.bib
T}
T{
BibTeX
T}@T{
\&.bibtex
T}
T{
CSL JSON
T}@T{
\&.json
T}
T{
CSL YAML
T}@T{
\&.yaml
T}
.TE
.PP
Note that \f[C].bib\f[R] can be used with both BibTeX and BibLaTeX
files; use the extension \f[C].bibtex\f[R] to force interpretation as
BibTeX.
.PP
In BibTeX and BibLaTeX databases, pandoc parses LaTeX markup inside
fields such as \f[C]title\f[R]; in CSL YAML databases, pandoc Markdown;
and in CSL JSON databases, an HTML-like markup:
.TP
\f[B]\f[CB]<i>...</i>\f[B]\f[R]
italics
.TP
\f[B]\f[CB]<b>...</b>\f[B]\f[R]
bold
.TP
\f[B]\f[CB]<span style=\[dq]font-variant:small-caps;\[dq]>...</span>\f[B]\f[R] or \f[B]\f[CB]<sc>...</sc>\f[B]\f[R]
small capitals
.TP
\f[B]\f[CB]<sub>...</sub>\f[B]\f[R]
subscript
.TP
\f[B]\f[CB]<sup>...</sup>\f[B]\f[R]
superscript
.TP
\f[B]\f[CB]<span class=\[dq]nocase\[dq]>...</span>\f[B]\f[R]
prevent a phrase from being capitalized as title case
.PP
As an alternative to specifying a bibliography file using
\f[C]--bibliography\f[R] or the YAML metadata field
\f[C]bibliography\f[R], you can include the citation data directly in
the \f[C]references\f[R] field of the document\[cq]s YAML metadata.
The field should contain an array of YAML-encoded references, for
example:
.IP
.nf
\f[C]
---
references:
- type: article-journal
id: WatsonCrick1953
author:
- family: Watson
given: J. D.
- family: Crick
given: F. H. C.
issued:
date-parts:
- - 1953
- 4
- 25
title: \[aq]Molecular structure of nucleic acids: a structure for
deoxyribose nucleic acid\[aq]
title-short: Molecular structure of nucleic acids
container-title: Nature
volume: 171
issue: 4356
page: 737-738
DOI: 10.1038/171737a0
URL: https://www.nature.com/articles/171737a0
language: en-GB
\&...
\f[R]
.fi
.PP
If both an external bibliography and inline (YAML metadata) references
are provided, both will be used.
In case of conflicting \f[C]id\f[R]s, the inline references will take
precedence.
.PP
Note that \f[C]pandoc\f[R] can be used to produce such a YAML metadata
section from a BibTeX, BibLaTeX, or CSL JSON bibliography:
.IP
.nf
\f[C]
pandoc chem.bib -s -f biblatex -t markdown
pandoc chem.json -s -f csljson -t markdown
\f[R]
.fi
.PP
Indeed, \f[C]pandoc\f[R] can convert between any of these citation
formats:
.IP
.nf
\f[C]
pandoc chem.bib -s -f biblatex -t csljson
pandoc chem.yaml -s -f markdown -t biblatex
\f[R]
.fi
.PP
Running pandoc on a bibliography file with the \f[C]--citeproc\f[R]
option will create a formatted bibliography in the format of your
choice:
.IP
.nf
\f[C]
pandoc chem.bib -s --citeproc -o chem.html
pandoc chem.bib -s --citeproc -o chem.pdf
\f[R]
.fi
.SS Capitalization in titles
.PP
If you are using a bibtex or biblatex bibliography, then observe the
following rules:
.IP \[bu] 2
English titles should be in title case.
Non-English titles should be in sentence case, and the \f[C]langid\f[R]
field in biblatex should be set to the relevant language.
(The following values are treated as English: \f[C]american\f[R],
\f[C]british\f[R], \f[C]canadian\f[R], \f[C]english\f[R],
\f[C]australian\f[R], \f[C]newzealand\f[R], \f[C]USenglish\f[R], or
\f[C]UKenglish\f[R].)
.IP \[bu] 2
As is standard with bibtex/biblatex, proper names should be protected
with curly braces so that they won\[cq]t be lowercased in styles that
call for sentence case.
For example:
.RS 2
.IP
.nf
\f[C]
title = {My Dinner with {Andre}}
\f[R]
.fi
.RE
.IP \[bu] 2
In addition, words that should remain lowercase (or camelCase) should be
protected:
.RS 2
.IP
.nf
\f[C]
title = {Spin Wave Dispersion on the {nm} Scale}
\f[R]
.fi
.PP
Though this is not necessary in bibtex/biblatex, it is necessary with
citeproc, which stores titles internally in sentence case, and converts
to title case in styles that require it.
Here we protect \[lq]nm\[rq] so that it doesn\[cq]t get converted to
\[lq]Nm\[rq] at this stage.
.RE
.PP
If you are using a CSL bibliography (either JSON or YAML), then observe
the following rules:
.IP \[bu] 2
All titles should be in sentence case.
.IP \[bu] 2
Use the \f[C]language\f[R] field for non-English titles to prevent their
conversion to title case in styles that call for this.
(Conversion happens only if \f[C]language\f[R] begins with \f[C]en\f[R]
or is left empty.)
.IP \[bu] 2
Protect words that should not be converted to title case using this
syntax:
.RS 2
.IP
.nf
\f[C]
Spin wave dispersion on the <span class=\[dq]nocase\[dq]>nm</span> scale
\f[R]
.fi
.RE
.SS Conference Papers, Published vs.\ Unpublished
.PP
For a formally published conference paper, use the biblatex entry type
\f[C]inproceedings\f[R] (which will be mapped to CSL
\f[C]paper-conference\f[R]).
.PP
For an unpublished manuscript, use the biblatex entry type
\f[C]unpublished\f[R] without an \f[C]eventtitle\f[R] field (this entry
type will be mapped to CSL \f[C]manuscript\f[R]).
.PP
For a talk, an unpublished conference paper, or a poster presentation,
use the biblatex entry type \f[C]unpublished\f[R] with an
\f[C]eventtitle\f[R] field (this entry type will be mapped to CSL
\f[C]speech\f[R]).
Use the biblatex \f[C]type\f[R] field to indicate the type,
e.g.\ \[lq]Paper\[rq], or \[lq]Poster\[rq].
\f[C]venue\f[R] and \f[C]eventdate\f[R] may be useful too, though
\f[C]eventdate\f[R] will not be rendered by most CSL styles.
Note that \f[C]venue\f[R] is for the event\[cq]s venue, unlike
\f[C]location\f[R] which describes the publisher\[cq]s location; do not
use the latter for an unpublished conference paper.
.SS Specifying a citation style
.PP
Citations and references can be formatted using any style supported by
the Citation Style Language, listed in the Zotero Style Repository.
These files are specified using the \f[C]--csl\f[R] option or the
\f[C]csl\f[R] (or \f[C]citation-style\f[R]) metadata field.
By default, pandoc will use the Chicago Manual of Style author-date
format.
(You can override this default by copying a CSL style of your choice to
\f[C]default.csl\f[R] in your user data directory.) The CSL project
provides further information on finding and editing styles.
.PP
The \f[C]--citation-abbreviations\f[R] option (or the
\f[C]citation-abbreviations\f[R] metadata field) may be used to specify
a JSON file containing abbreviations of journals that should be used in
formatted bibliographies when \f[C]form=\[dq]short\[dq]\f[R] is
specified.
The format of the file can be illustrated with an example:
.IP
.nf
\f[C]
{ \[dq]default\[dq]: {
\[dq]container-title\[dq]: {
\[dq]Lloyd\[aq]s Law Reports\[dq]: \[dq]Lloyd\[aq]s Rep\[dq],
\[dq]Estates Gazette\[dq]: \[dq]EG\[dq],
\[dq]Scots Law Times\[dq]: \[dq]SLT\[dq]
}
}
}
\f[R]
.fi
.SS Citations in note styles
.PP
Pandoc\[cq]s citation processing is designed to allow you to move
between author-date, numerical, and note styles without modifying the
markdown source.
When you\[cq]re using a note style, avoid inserting footnotes manually.
Instead, insert citations just as you would in an author-date
style\[em]for example,
.IP
.nf
\f[C]
Blah blah [\[at]foo, p. 33].
\f[R]
.fi
.PP
The footnote will be created automatically.
Pandoc will take care of removing the space and moving the note before
or after the period, depending on the setting of
\f[C]notes-after-punctuation\f[R], as described below in Other relevant
metadata fields.
.PP
In some cases you may need to put a citation inside a regular footnote.
Normal citations in footnotes (such as \f[C][\[at]foo, p. 33]\f[R]) will
be rendered in parentheses.
In-text citations (such as \f[C]\[at]foo [p. 33]\f[R]) will be rendered
without parentheses.
(A comma will be added if appropriate.) Thus:
.IP
.nf
\f[C]
[\[ha]1]: Some studies [\[at]foo; \[at]bar, p. 33] show that
frubulicious zoosnaps are quantical. For a survey
of the literature, see \[at]baz [chap. 1].
\f[R]
.fi
.SS Raw content in a style
.PP
To include raw content in a prefix, suffix, delimiter, or term, surround
it with these tags indicating the format:
.IP
.nf
\f[C]
{{jats}}<ref>{{/jats}}
\f[R]
.fi
.PP
Without the tags, the string will be interpreted as a string and escaped
in the output, rather than being passed through raw.
.PP
This feature allows stylesheets to be customized to give different
output for different output formats.
However, stylesheets customized in this way will not be usable by other
CSL implementations.
.SS Placement of the bibliography
.PP
If the style calls for a list of works cited, it will be placed in a div
with id \f[C]refs\f[R], if one exists:
.IP
.nf
\f[C]
::: {#refs}
:::
\f[R]
.fi
.PP
Otherwise, it will be placed at the end of the document.
Generation of the bibliography can be suppressed by setting
\f[C]suppress-bibliography: true\f[R] in the YAML metadata.
.PP
If you wish the bibliography to have a section heading, you can set
\f[C]reference-section-title\f[R] in the metadata, or put the heading at
the beginning of the div with id \f[C]refs\f[R] (if you are using it) or
at the end of your document:
.IP
.nf
\f[C]
last paragraph...
# References
\f[R]
.fi
.PP
The bibliography will be inserted after this heading.
Note that the \f[C]unnumbered\f[R] class will be added to this heading,
so that the section will not be numbered.
.SS Including uncited items in the bibliography
.PP
If you want to include items in the bibliography without actually citing
them in the body text, you can define a dummy \f[C]nocite\f[R] metadata
field and put the citations there:
.IP
.nf
\f[C]
---
nocite: |
\[at]item1, \[at]item2
\&...
\[at]item3
\f[R]
.fi
.PP
In this example, the document will contain a citation for
\f[C]item3\f[R] only, but the bibliography will contain entries for
\f[C]item1\f[R], \f[C]item2\f[R], and \f[C]item3\f[R].
.PP
It is possible to create a bibliography with all the citations, whether
or not they appear in the document, by using a wildcard:
.IP
.nf
\f[C]
---
nocite: |
\[at]*
\&...
\f[R]
.fi
.PP
For LaTeX output, you can also use \f[C]natbib\f[R] or
\f[C]biblatex\f[R] to render the bibliography.
In order to do so, specify bibliography files as outlined above, and add
\f[C]--natbib\f[R] or \f[C]--biblatex\f[R] argument to \f[C]pandoc\f[R]
invocation.
Bear in mind that bibliography files have to be in either BibTeX (for
\f[C]--natbib\f[R]) or BibLaTeX (for \f[C]--biblatex\f[R]) format.
.SS Other relevant metadata fields
.PP
A few other metadata fields affect bibliography formatting:
.TP
\f[B]\f[CB]link-citations\f[B]\f[R]
If true, citations will be hyperlinked to the corresponding bibliography
entries (for author-date and numerical styles only).
.TP
\f[B]\f[CB]lang\f[B]\f[R]
The \f[C]lang\f[R] field will affect how the style is localized, for
example in the translation of labels, the use of quotation marks, and
the way items are sorted.
(For backwards compatibility, \f[C]locale\f[R] may be used instead of
\f[C]lang\f[R], but this use is deprecated.)
.RS
.PP
A BCP 47 language tag is expected: for example, \f[C]en\f[R],
\f[C]de\f[R], \f[C]en-US\f[R], \f[C]fr-CA\f[R], \f[C]ug-Cyrl\f[R].
The unicode extension syntax (after \f[C]-u-\f[R]) may be used to
specify options for collation (sorting) more precisely.
Here are some examples:
.IP \[bu] 2
\f[C]zh-u-co-pinyin\f[R] \[en] Chinese with the Pinyin collation.
.IP \[bu] 2
\f[C]es-u-co-trad\f[R] \[en] Spanish with the traditional collation
(with \f[C]Ch\f[R] sorting after \f[C]C\f[R]).
.IP \[bu] 2
\f[C]fr-u-kb\f[R] \[en] French with \[lq]backwards\[rq] accent sorting
(with \f[C]cot\['e]\f[R] sorting after \f[C]c\[^o]te\f[R]).
.IP \[bu] 2
\f[C]en-US-u-kf-upper\f[R] \[en] English with uppercase letters sorting
before lower (default is lower before upper).
.RE
.TP
\f[B]\f[CB]notes-after-punctuation\f[B]\f[R]
If true (the default), pandoc will put footnote citations after
following punctuation.
For example, if the source contains \f[C]blah blah [\[at]jones99].\f[R],
the result will look like \f[C]blah blah.[\[ha]1]\f[R], with the note
moved after the period and the space collapsed.
If false, the space will still be collapsed, but the footnote will not
be moved after the punctuation.
.SH SLIDE SHOWS
.PP
You can use pandoc to produce an HTML + JavaScript slide presentation
that can be viewed via a web browser.
There are five ways to do this, using S5, DZSlides, Slidy, Slideous, or
reveal.js.
You can also produce a PDF slide show using LaTeX \f[C]beamer\f[R], or
slides shows in Microsoft PowerPoint format.
.PP
Here\[cq]s the Markdown source for a simple slide show,
\f[C]habits.txt\f[R]:
.IP
.nf
\f[C]
% Habits
% John Doe
% March 22, 2005
# In the morning
## Getting up
- Turn off alarm
- Get out of bed
## Breakfast
- Eat eggs
- Drink coffee
# In the evening
## Dinner
- Eat spaghetti
- Drink wine
------------------
## Going to sleep
- Get in bed
- Count sheep
\f[R]
.fi
.PP
To produce an HTML/JavaScript slide show, simply type
.IP
.nf
\f[C]
pandoc -t FORMAT -s habits.txt -o habits.html
\f[R]
.fi
.PP
where \f[C]FORMAT\f[R] is either \f[C]s5\f[R], \f[C]slidy\f[R],
\f[C]slideous\f[R], \f[C]dzslides\f[R], or \f[C]revealjs\f[R].
.PP
For Slidy, Slideous, reveal.js, and S5, the file produced by pandoc with
the \f[C]-s/--standalone\f[R] option embeds a link to JavaScript and CSS
files, which are assumed to be available at the relative path
\f[C]s5/default\f[R] (for S5), \f[C]slideous\f[R] (for Slideous),
\f[C]reveal.js\f[R] (for reveal.js), or at the Slidy website at
\f[C]w3.org\f[R] (for Slidy).
(These paths can be changed by setting the \f[C]slidy-url\f[R],
\f[C]slideous-url\f[R], \f[C]revealjs-url\f[R], or \f[C]s5-url\f[R]
variables; see Variables for HTML slides, above.) For DZSlides, the
(relatively short) JavaScript and CSS are included in the file by
default.
.PP
With all HTML slide formats, the \f[C]--self-contained\f[R] option can
be used to produce a single file that contains all of the data necessary
to display the slide show, including linked scripts, stylesheets,
images, and videos.
.PP
To produce a PDF slide show using beamer, type
.IP
.nf
\f[C]
pandoc -t beamer habits.txt -o habits.pdf
\f[R]
.fi
.PP
Note that a reveal.js slide show can also be converted to a PDF by
printing it to a file from the browser.
.PP
To produce a Powerpoint slide show, type
.IP
.nf
\f[C]
pandoc habits.txt -o habits.pptx
\f[R]
.fi
.SS Structuring the slide show
.PP
By default, the \f[I]slide level\f[R] is the highest heading level in
the hierarchy that is followed immediately by content, and not another
heading, somewhere in the document.
In the example above, level-1 headings are always followed by level-2
headings, which are followed by content, so the slide level is 2.
This default can be overridden using the \f[C]--slide-level\f[R] option.
.PP
The document is carved up into slides according to the following rules:
.IP \[bu] 2
A horizontal rule always starts a new slide.
.IP \[bu] 2
A heading at the slide level always starts a new slide.
.IP \[bu] 2
Headings \f[I]below\f[R] the slide level in the hierarchy create
headings \f[I]within\f[R] a slide.
(In beamer, a \[lq]block\[rq] will be created.
If the heading has the class \f[C]example\f[R], an
\f[C]exampleblock\f[R] environment will be used; if it has the class
\f[C]alert\f[R], an \f[C]alertblock\f[R] will be used; otherwise a
regular \f[C]block\f[R] will be used.)
.IP \[bu] 2
Headings \f[I]above\f[R] the slide level in the hierarchy create
\[lq]title slides,\[rq] which just contain the section title and help to
break the slide show into sections.
Non-slide content under these headings will be included on the title
slide (for HTML slide shows) or in a subsequent slide with the same
title (for beamer).
.IP \[bu] 2
A title page is constructed automatically from the document\[cq]s title
block, if present.
(In the case of beamer, this can be disabled by commenting out some
lines in the default template.)
.PP
These rules are designed to support many different styles of slide show.
If you don\[cq]t care about structuring your slides into sections and
subsections, you can just use level-1 headings for all each slide.
(In that case, level-1 will be the slide level.) But you can also
structure the slide show into sections, as in the example above.
.PP
Note: in reveal.js slide shows, if slide level is 2, a two-dimensional
layout will be produced, with level-1 headings building horizontally and
level-2 headings building vertically.
It is not recommended that you use deeper nesting of section levels with
reveal.js.
.SS Incremental lists
.PP
By default, these writers produce lists that display \[lq]all at
once.\[rq] If you want your lists to display incrementally (one item at
a time), use the \f[C]-i\f[R] option.
If you want a particular list to depart from the default, put it in a
\f[C]div\f[R] block with class \f[C]incremental\f[R] or
\f[C]nonincremental\f[R].
So, for example, using the \f[C]fenced div\f[R] syntax, the following
would be incremental regardless of the document default:
.IP
.nf
\f[C]
::: incremental
- Eat spaghetti
- Drink wine
:::
\f[R]
.fi
.PP
or
.IP
.nf
\f[C]
::: nonincremental
- Eat spaghetti
- Drink wine
:::
\f[R]
.fi
.PP
While using \f[C]incremental\f[R] and \f[C]nonincremental\f[R] divs are
the recommended method of setting incremental lists on a per-case basis,
an older method is also supported: putting lists inside a blockquote
will depart from the document default (that is, it will display
incrementally without the \f[C]-i\f[R] option and all at once with the
\f[C]-i\f[R] option):
.IP
.nf
\f[C]
> - Eat spaghetti
> - Drink wine
\f[R]
.fi
.PP
Both methods allow incremental and nonincremental lists to be mixed in a
single document.
.PP
Note: Neither the \f[C]-i/--incremental\f[R] option nor any of the
methods described here currently works for PowerPoint output.
.SS Inserting pauses
.PP
You can add \[lq]pauses\[rq] within a slide by including a paragraph
containing three dots, separated by spaces:
.IP
.nf
\f[C]
# Slide with a pause
content before the pause
\&. . .
content after the pause
\f[R]
.fi
.PP
Note: this feature is not yet implemented for PowerPoint output.
.SS Styling the slides
.PP
You can change the style of HTML slides by putting customized CSS files
in \f[C]$DATADIR/s5/default\f[R] (for S5), \f[C]$DATADIR/slidy\f[R] (for
Slidy), or \f[C]$DATADIR/slideous\f[R] (for Slideous), where
\f[C]$DATADIR\f[R] is the user data directory (see \f[C]--data-dir\f[R],
above).
The originals may be found in pandoc\[cq]s system data directory
(generally \f[C]$CABALDIR/pandoc-VERSION/s5/default\f[R]).
Pandoc will look there for any files it does not find in the user data
directory.
.PP
For dzslides, the CSS is included in the HTML file itself, and may be
modified there.
.PP
All reveal.js configuration options can be set through variables.
For example, themes can be used by setting the \f[C]theme\f[R] variable:
.IP
.nf
\f[C]
-V theme=moon
\f[R]
.fi
.PP
Or you can specify a custom stylesheet using the \f[C]--css\f[R] option.
.PP
To style beamer slides, you can specify a \f[C]theme\f[R],
\f[C]colortheme\f[R], \f[C]fonttheme\f[R], \f[C]innertheme\f[R], and
\f[C]outertheme\f[R], using the \f[C]-V\f[R] option:
.IP
.nf
\f[C]
pandoc -t beamer habits.txt -V theme:Warsaw -o habits.pdf
\f[R]
.fi
.PP
Note that heading attributes will turn into slide attributes (on a
\f[C]<div>\f[R] or \f[C]<section>\f[R]) in HTML slide formats, allowing
you to style individual slides.
In beamer, the only heading attribute that affects slides is the
\f[C]allowframebreaks\f[R] class, which sets the
\f[C]allowframebreaks\f[R] option, causing multiple slides to be created
if the content overfills the frame.
This is recommended especially for bibliographies:
.IP
.nf
\f[C]
# References {.allowframebreaks}
\f[R]
.fi
.SS Speaker notes
.PP
Speaker notes are supported in reveal.js and PowerPoint (pptx) output.
You can add notes to your Markdown document thus:
.IP
.nf
\f[C]
::: notes
This is my note.
- It can contain Markdown
- like this list
:::
\f[R]
.fi
.PP
To show the notes window in reveal.js, press \f[C]s\f[R] while viewing
the presentation.
Speaker notes in PowerPoint will be available, as usual, in handouts and
presenter view.
.PP
Notes are not yet supported for other slide formats, but the notes will
not appear on the slides themselves.
.SS Columns
.PP
To put material in side by side columns, you can use a native div
container with class \f[C]columns\f[R], containing two or more div
containers with class \f[C]column\f[R] and a \f[C]width\f[R] attribute:
.IP
.nf
\f[C]
:::::::::::::: {.columns}
::: {.column width=\[dq]40%\[dq]}
contents...
:::
::: {.column width=\[dq]60%\[dq]}
contents...
:::
::::::::::::::
\f[R]
.fi
.SS Additional columns attributes in beamer
.PP
The div containers with classes \f[C]columns\f[R] and \f[C]column\f[R]
can optionally have an \f[C]align\f[R] attribute.
The class \f[C]columns\f[R] can optionally have a \f[C]totalwidth\f[R]
attribute or an \f[C]onlytextwidth\f[R] class.
.IP
.nf
\f[C]
:::::::::::::: {.columns align=center totalwidth=8em}
::: {.column width=\[dq]40%\[dq]}
contents...
:::
::: {.column width=\[dq]60%\[dq] align=bottom}
contents...
:::
::::::::::::::
\f[R]
.fi
.PP
The \f[C]align\f[R] attributes on \f[C]columns\f[R] and \f[C]column\f[R]
can be used with the values \f[C]top\f[R], \f[C]top-baseline\f[R],
\f[C]center\f[R] and \f[C]bottom\f[R] to vertically align the columns.
It defaults to \f[C]top\f[R] in \f[C]columns\f[R].
.PP
The \f[C]totalwidth\f[R] attribute limits the width of the columns to
the given value.
.IP
.nf
\f[C]
:::::::::::::: {.columns align=top .onlytextwidth}
::: {.column width=\[dq]40%\[dq] align=center}
contents...
:::
::: {.column width=\[dq]60%\[dq]}
contents...
:::
::::::::::::::
\f[R]
.fi
.PP
The class \f[C]onlytextwidth\f[R] sets the \f[C]totalwidth\f[R] to
\f[C]\[rs]textwidth\f[R].
.PP
See Section 12.7 of the Beamer User\[cq]s Guide for more details.
.SS Frame attributes in beamer
.PP
Sometimes it is necessary to add the LaTeX \f[C][fragile]\f[R] option to
a frame in beamer (for example, when using the \f[C]minted\f[R]
environment).
This can be forced by adding the \f[C]fragile\f[R] class to the heading
introducing the slide:
.IP
.nf
\f[C]
# Fragile slide {.fragile}
\f[R]
.fi
.PP
All of the other frame attributes described in Section 8.1 of the Beamer
User\[cq]s Guide may also be used: \f[C]allowdisplaybreaks\f[R],
\f[C]allowframebreaks\f[R], \f[C]b\f[R], \f[C]c\f[R], \f[C]t\f[R],
\f[C]environment\f[R], \f[C]label\f[R], \f[C]plain\f[R],
\f[C]shrink\f[R], \f[C]standout\f[R], \f[C]noframenumbering\f[R].
.SS Background in reveal.js and beamer
.PP
Background images can be added to self-contained reveal.js slideshows
and to beamer slideshows.
.PP
For the same image on every slide, use the configuration option
\f[C]background-image\f[R] either in the YAML metadata block or as a
command-line variable.
(There are no other options in beamer and the rest of this section
concerns reveal.js slideshows.)
.PP
For reveal.js, you can instead use the reveal.js-native option
\f[C]parallaxBackgroundImage\f[R].
You can also set \f[C]parallaxBackgroundHorizontal\f[R] and
\f[C]parallaxBackgroundVertical\f[R] the same way and must also set
\f[C]parallaxBackgroundSize\f[R] to have your values take effect.
.PP
To set an image for a particular reveal.js slide, add
\f[C]{data-background-image=\[dq]/path/to/image\[dq]}\f[R] to the first
slide-level heading on the slide (which may even be empty).
.PP
In reveal.js\[cq]s overview mode, the parallaxBackgroundImage will show
up only on the first slide.
.PP
Other reveal.js background settings also work on individual slides,
including \f[C]data-background-size\f[R],
\f[C]data-background-repeat\f[R], \f[C]data-background-color\f[R],
\f[C]data-transition\f[R], and \f[C]data-transition-speed\f[R].
.PP
To add a background image to the automatically generated title slide,
use the \f[C]title-slide-attributes\f[R] variable in the YAML metadata
block.
It must contain a map of attribute names and values.
.PP
See the reveal.js documentation for more details.
.PP
For example in reveal.js:
.IP
.nf
\f[C]
---
title: My Slideshow
parallaxBackgroundImage: /path/to/my/background_image.png
title-slide-attributes:
data-background-image: /path/to/title_image.png
data-background-size: contain
---
## Slide One
Slide 1 has background_image.png as its background.
## {data-background-image=\[dq]/path/to/special_image.jpg\[dq]}
Slide 2 has a special image for its background, even though the heading has no content.
\f[R]
.fi
.SH EPUBS
.SS EPUB Metadata
.PP
EPUB metadata may be specified using the \f[C]--epub-metadata\f[R]
option, but if the source document is Markdown, it is better to use a
YAML metadata block.
Here is an example:
.IP
.nf
\f[C]
---
title:
- type: main
text: My Book
- type: subtitle
text: An investigation of metadata
creator:
- role: author
text: John Smith
- role: editor
text: Sarah Jones
identifier:
- scheme: DOI
text: doi:10.234234.234/33
publisher: My Press
rights: \[co] 2007 John Smith, CC BY-NC
ibooks:
version: 1.3.4
\&...
\f[R]
.fi
.PP
The following fields are recognized:
.TP
\f[B]\f[CB]identifier\f[B]\f[R]
Either a string value or an object with fields \f[C]text\f[R] and
\f[C]scheme\f[R].
Valid values for \f[C]scheme\f[R] are \f[C]ISBN-10\f[R],
\f[C]GTIN-13\f[R], \f[C]UPC\f[R], \f[C]ISMN-10\f[R], \f[C]DOI\f[R],
\f[C]LCCN\f[R], \f[C]GTIN-14\f[R], \f[C]ISBN-13\f[R],
\f[C]Legal deposit number\f[R], \f[C]URN\f[R], \f[C]OCLC\f[R],
\f[C]ISMN-13\f[R], \f[C]ISBN-A\f[R], \f[C]JP\f[R], \f[C]OLCC\f[R].
.TP
\f[B]\f[CB]title\f[B]\f[R]
Either a string value, or an object with fields \f[C]file-as\f[R] and
\f[C]type\f[R], or a list of such objects.
Valid values for \f[C]type\f[R] are \f[C]main\f[R], \f[C]subtitle\f[R],
\f[C]short\f[R], \f[C]collection\f[R], \f[C]edition\f[R],
\f[C]extended\f[R].
.TP
\f[B]\f[CB]creator\f[B]\f[R]
Either a string value, or an object with fields \f[C]role\f[R],
\f[C]file-as\f[R], and \f[C]text\f[R], or a list of such objects.
Valid values for \f[C]role\f[R] are MARC relators, but pandoc will
attempt to translate the human-readable versions (like \[lq]author\[rq]
and \[lq]editor\[rq]) to the appropriate marc relators.
.TP
\f[B]\f[CB]contributor\f[B]\f[R]
Same format as \f[C]creator\f[R].
.TP
\f[B]\f[CB]date\f[B]\f[R]
A string value in \f[C]YYYY-MM-DD\f[R] format.
(Only the year is necessary.) Pandoc will attempt to convert other
common date formats.
.TP
\f[B]\f[CB]lang\f[B]\f[R] (or legacy: \f[B]\f[CB]language\f[B]\f[R])
A string value in BCP 47 format.
Pandoc will default to the local language if nothing is specified.
.TP
\f[B]\f[CB]subject\f[B]\f[R]
A string value or a list of such values.
.TP
\f[B]\f[CB]description\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]type\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]format\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]relation\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]coverage\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]rights\f[B]\f[R]
A string value.
.TP
\f[B]\f[CB]belongs-to-collection\f[B]\f[R]
A string value.
identifies the name of a collection to which the EPUB Publication
belongs.
.TP
\f[B]\f[CB]group-position\f[B]\f[R]
The \f[C]group-position\f[R] field indicates the numeric position in
which the EPUB Publication belongs relative to other works belonging to
the same \f[C]belongs-to-collection\f[R] field.
.TP
\f[B]\f[CB]cover-image\f[B]\f[R]
A string value (path to cover image).
.TP
\f[B]\f[CB]css\f[B]\f[R] (or legacy: \f[B]\f[CB]stylesheet\f[B]\f[R])
A string value (path to CSS stylesheet).
.TP
\f[B]\f[CB]page-progression-direction\f[B]\f[R]
Either \f[C]ltr\f[R] or \f[C]rtl\f[R].
Specifies the \f[C]page-progression-direction\f[R] attribute for the
\f[C]spine\f[R] element.
.TP
\f[B]\f[CB]ibooks\f[B]\f[R]
iBooks-specific metadata, with the following fields:
.RS
.IP \[bu] 2
\f[C]version\f[R]: (string)
.IP \[bu] 2
\f[C]specified-fonts\f[R]: \f[C]true\f[R]|\f[C]false\f[R] (default
\f[C]false\f[R])
.IP \[bu] 2
\f[C]ipad-orientation-lock\f[R]:
\f[C]portrait-only\f[R]|\f[C]landscape-only\f[R]
.IP \[bu] 2
\f[C]iphone-orientation-lock\f[R]:
\f[C]portrait-only\f[R]|\f[C]landscape-only\f[R]
.IP \[bu] 2
\f[C]binding\f[R]: \f[C]true\f[R]|\f[C]false\f[R] (default
\f[C]true\f[R])
.IP \[bu] 2
\f[C]scroll-axis\f[R]:
\f[C]vertical\f[R]|\f[C]horizontal\f[R]|\f[C]default\f[R]
.RE
.SS The \f[C]epub:type\f[R] attribute
.PP
For \f[C]epub3\f[R] output, you can mark up the heading that corresponds
to an EPUB chapter using the \f[C]epub:type\f[R] attribute.
For example, to set the attribute to the value \f[C]prologue\f[R], use
this markdown:
.IP
.nf
\f[C]
# My chapter {epub:type=prologue}
\f[R]
.fi
.PP
Which will result in:
.IP
.nf
\f[C]
<body epub:type=\[dq]frontmatter\[dq]>
<section epub:type=\[dq]prologue\[dq]>
<h1>My chapter</h1>
\f[R]
.fi
.PP
Pandoc will output \f[C]<body epub:type=\[dq]bodymatter\[dq]>\f[R],
unless you use one of the following values, in which case either
\f[C]frontmatter\f[R] or \f[C]backmatter\f[R] will be output.
.PP
.TS
tab(@);
l l.
T{
\f[C]epub:type\f[R] of first section
T}@T{
\f[C]epub:type\f[R] of body
T}
_
T{
prologue
T}@T{
frontmatter
T}
T{
abstract
T}@T{
frontmatter
T}
T{
acknowledgments
T}@T{
frontmatter
T}
T{
copyright-page
T}@T{
frontmatter
T}
T{
dedication
T}@T{
frontmatter
T}
T{
credits
T}@T{
frontmatter
T}
T{
keywords
T}@T{
frontmatter
T}
T{
imprint
T}@T{
frontmatter
T}
T{
contributors
T}@T{
frontmatter
T}
T{
other-credits
T}@T{
frontmatter
T}
T{
errata
T}@T{
frontmatter
T}
T{
revision-history
T}@T{
frontmatter
T}
T{
titlepage
T}@T{
frontmatter
T}
T{
halftitlepage
T}@T{
frontmatter
T}
T{
seriespage
T}@T{
frontmatter
T}
T{
foreword
T}@T{
frontmatter
T}
T{
preface
T}@T{
frontmatter
T}
T{
appendix
T}@T{
backmatter
T}
T{
colophon
T}@T{
backmatter
T}
T{
bibliography
T}@T{
backmatter
T}
T{
index
T}@T{
backmatter
T}
.TE
.SS Linked media
.PP
By default, pandoc will download media referenced from any
\f[C]<img>\f[R], \f[C]<audio>\f[R], \f[C]<video>\f[R] or
\f[C]<source>\f[R] element present in the generated EPUB, and include it
in the EPUB container, yielding a completely self-contained EPUB.
If you want to link to external media resources instead, use raw HTML in
your source and add \f[C]data-external=\[dq]1\[dq]\f[R] to the tag with
the \f[C]src\f[R] attribute.
For example:
.IP
.nf
\f[C]
<audio controls=\[dq]1\[dq]>
<source src=\[dq]https://example.com/music/toccata.mp3\[dq]
data-external=\[dq]1\[dq] type=\[dq]audio/mpeg\[dq]>
</source>
</audio>
\f[R]
.fi
.SH JUPYTER NOTEBOOKS
.PP
When creating a Jupyter notebook, pandoc will try to infer the notebook
structure.
Code blocks with the class \f[C]code\f[R] will be taken as code cells,
and intervening content will be taken as Markdown cells.
Attachments will automatically be created for images in Markdown cells.
Metadata will be taken from the \f[C]jupyter\f[R] metadata field.
For example:
.IP
.nf
\f[C]
---
title: My notebook
jupyter:
nbformat: 4
nbformat_minor: 5
kernelspec:
display_name: Python 2
language: python
name: python2
language_info:
codemirror_mode:
name: ipython
version: 2
file_extension: \[dq].py\[dq]
mimetype: \[dq]text/x-python\[dq]
name: \[dq]python\[dq]
nbconvert_exporter: \[dq]python\[dq]
pygments_lexer: \[dq]ipython2\[dq]
version: \[dq]2.7.15\[dq]
---
# Lorem ipsum
**Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus
bibendum felis dictum sodales.
\[ga]\[ga]\[ga] code
print(\[dq]hello\[dq])
\[ga]\[ga]\[ga]
## Pyout
\[ga]\[ga]\[ga] code
from IPython.display import HTML
HTML(\[dq]\[dq]\[dq]
<script>
console.log(\[dq]hello\[dq]);
</script>
<b>HTML</b>
\[dq]\[dq]\[dq])
\[ga]\[ga]\[ga]
## Image
This image  will be
included as a cell attachment.
\f[R]
.fi
.PP
If you want to add cell attributes, group cells differently, or add
output to code cells, then you need to include divs to indicate the
structure.
You can use either fenced divs or native divs for this.
Here is an example:
.IP
.nf
\f[C]
:::::: {.cell .markdown}
# Lorem
**Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus
bibendum felis dictum sodales.
::::::
:::::: {.cell .code execution_count=1}
\[ga]\[ga]\[ga] {.python}
print(\[dq]hello\[dq])
\[ga]\[ga]\[ga]
::: {.output .stream .stdout}
\[ga]\[ga]\[ga]
hello
\[ga]\[ga]\[ga]
:::
::::::
:::::: {.cell .code execution_count=2}
\[ga]\[ga]\[ga] {.python}
from IPython.display import HTML
HTML(\[dq]\[dq]\[dq]
<script>
console.log(\[dq]hello\[dq]);
</script>
<b>HTML</b>
\[dq]\[dq]\[dq])
\[ga]\[ga]\[ga]
::: {.output .execute_result execution_count=2}
\[ga]\[ga]\[ga]{=html}
<script>
console.log(\[dq]hello\[dq]);
</script>
<b>HTML</b>
hello
\[ga]\[ga]\[ga]
:::
::::::
\f[R]
.fi
.PP
If you include raw HTML or TeX in an output cell, use the [raw
attribute][Extension: \f[C]fenced_attribute\f[R]], as shown in the last
cell of the example above.
Although pandoc can process \[lq]bare\[rq] raw HTML and TeX, the result
is often interspersed raw elements and normal textual elements, and in
an output cell pandoc expects a single, connected raw block.
To avoid using raw HTML or TeX except when marked explicitly using raw
attributes, we recommend specifying the extensions
\f[C]-raw_html-raw_tex+raw_attribute\f[R] when translating between
Markdown and ipynb notebooks.
.PP
Note that options and extensions that affect reading and writing of
Markdown will also affect Markdown cells in ipynb notebooks.
For example, \f[C]--wrap=preserve\f[R] will preserve soft line breaks in
Markdown cells; \f[C]--atx-headers\f[R] will cause ATX-style headings to
be used; and \f[C]--preserve-tabs\f[R] will prevent tabs from being
turned to spaces.
.SH SYNTAX HIGHLIGHTING
.PP
Pandoc will automatically highlight syntax in fenced code blocks that
are marked with a language name.
The Haskell library skylighting is used for highlighting.
Currently highlighting is supported only for HTML, EPUB, Docx, Ms, and
LaTeX/PDF output.
To see a list of language names that pandoc will recognize, type
\f[C]pandoc --list-highlight-languages\f[R].
.PP
The color scheme can be selected using the \f[C]--highlight-style\f[R]
option.
The default color scheme is \f[C]pygments\f[R], which imitates the
default color scheme used by the Python library pygments (though
pygments is not actually used to do the highlighting).
To see a list of highlight styles, type
\f[C]pandoc --list-highlight-styles\f[R].
.PP
If you are not satisfied with the predefined styles, you can use
\f[C]--print-highlight-style\f[R] to generate a JSON \f[C].theme\f[R]
file which can be modified and used as the argument to
\f[C]--highlight-style\f[R].
To get a JSON version of the \f[C]pygments\f[R] style, for example:
.IP
.nf
\f[C]
pandoc --print-highlight-style pygments > my.theme
\f[R]
.fi
.PP
Then edit \f[C]my.theme\f[R] and use it like this:
.IP
.nf
\f[C]
pandoc --highlight-style my.theme
\f[R]
.fi
.PP
If you are not satisfied with the built-in highlighting, or you want
highlight a language that isn\[cq]t supported, you can use the
\f[C]--syntax-definition\f[R] option to load a KDE-style XML syntax
definition file.
Before writing your own, have a look at KDE\[cq]s repository of syntax
definitions.
.PP
To disable highlighting, use the \f[C]--no-highlight\f[R] option.
.SH CUSTOM STYLES
.PP
Custom styles can be used in the docx and ICML formats.
.SS Output
.PP
By default, pandoc\[cq]s docx and ICML output applies a predefined set
of styles for blocks such as paragraphs and block quotes, and uses
largely default formatting (italics, bold) for inlines.
This will work for most purposes, especially alongside a
\f[C]reference.docx\f[R] file.
However, if you need to apply your own styles to blocks, or match a
preexisting set of styles, pandoc allows you to define custom styles for
blocks and text using \f[C]div\f[R]s and \f[C]span\f[R]s, respectively.
.PP
If you define a \f[C]div\f[R] or \f[C]span\f[R] with the attribute
\f[C]custom-style\f[R], pandoc will apply your specified style to the
contained elements (with the exception of elements whose function
depends on a style, like headings, code blocks, block quotes, or links).
So, for example, using the \f[C]bracketed_spans\f[R] syntax,
.IP
.nf
\f[C]
[Get out]{custom-style=\[dq]Emphatically\[dq]}, he said.
\f[R]
.fi
.PP
would produce a docx file with \[lq]Get out\[rq] styled with character
style \f[C]Emphatically\f[R].
Similarly, using the \f[C]fenced_divs\f[R] syntax,
.IP
.nf
\f[C]
Dickinson starts the poem simply:
::: {custom-style=\[dq]Poetry\[dq]}
| A Bird came down the Walk---
| He did not know I saw---
:::
\f[R]
.fi
.PP
would style the two contained lines with the \f[C]Poetry\f[R] paragraph
style.
.PP
For docx output, styles will be defined in the output file as inheriting
from normal text, if the styles are not yet in your reference.docx.
If they are already defined, pandoc will not alter the definition.
.PP
This feature allows for greatest customization in conjunction with
pandoc filters.
If you want all paragraphs after block quotes to be indented, you can
write a filter to apply the styles necessary.
If you want all italics to be transformed to the \f[C]Emphasis\f[R]
character style (perhaps to change their color), you can write a filter
which will transform all italicized inlines to inlines within an
\f[C]Emphasis\f[R] custom-style \f[C]span\f[R].
.PP
For docx output, you don\[cq]t need to enable any extensions for custom
styles to work.
.SS Input
.PP
The docx reader, by default, only reads those styles that it can convert
into pandoc elements, either by direct conversion or interpreting the
derivation of the input document\[cq]s styles.
.PP
By enabling the \f[C]styles\f[R] extension in the docx reader
(\f[C]-f docx+styles\f[R]), you can produce output that maintains the
styles of the input document, using the \f[C]custom-style\f[R] class.
Paragraph styles are interpreted as divs, while character styles are
interpreted as spans.
.PP
For example, using the \f[C]custom-style-reference.docx\f[R] file in the
test directory, we have the following different outputs:
.PP
Without the \f[C]+styles\f[R] extension:
.IP
.nf
\f[C]
$ pandoc test/docx/custom-style-reference.docx -f docx -t markdown
This is some text.
This is text with an *emphasized* text style. And this is text with a
**strengthened** text style.
> Here is a styled paragraph that inherits from Block Text.
\f[R]
.fi
.PP
And with the extension:
.IP
.nf
\f[C]
$ pandoc test/docx/custom-style-reference.docx -f docx+styles -t markdown
::: {custom-style=\[dq]First Paragraph\[dq]}
This is some text.
:::
::: {custom-style=\[dq]Body Text\[dq]}
This is text with an [emphasized]{custom-style=\[dq]Emphatic\[dq]} text style.
And this is text with a [strengthened]{custom-style=\[dq]Strengthened\[dq]}
text style.
:::
::: {custom-style=\[dq]My Block Style\[dq]}
> Here is a styled paragraph that inherits from Block Text.
:::
\f[R]
.fi
.PP
With these custom styles, you can use your input document as a
reference-doc while creating docx output (see below), and maintain the
same styles in your input and output files.
.SH CUSTOM WRITERS
.PP
Pandoc can be extended with custom writers written in Lua.
(Pandoc includes a Lua interpreter, so Lua need not be installed
separately.)
.PP
To use a custom writer, simply specify the path to the Lua script in
place of the output format.
For example:
.IP
.nf
\f[C]
pandoc -t data/sample.lua
\f[R]
.fi
.PP
Creating a custom writer requires writing a Lua function for each
possible element in a pandoc document.
To get a documented example which you can modify according to your
needs, do
.IP
.nf
\f[C]
pandoc --print-default-data-file sample.lua
\f[R]
.fi
.PP
Note that custom writers have no default template.
If you want to use \f[C]--standalone\f[R] with a custom writer, you will
need to specify a template manually using \f[C]--template\f[R] or add a
new default template with the name
\f[C]default.NAME_OF_CUSTOM_WRITER.lua\f[R] to the \f[C]templates\f[R]
subdirectory of your user data directory (see Templates).
.SH REPRODUCIBLE BUILDS
.PP
Some of the document formats pandoc targets (such as EPUB, docx, and
ODT) include build timestamps in the generated document.
That means that the files generated on successive builds will differ,
even if the source does not.
To avoid this, set the \f[C]SOURCE_DATE_EPOCH\f[R] environment variable,
and the timestamp will be taken from it instead of the current time.
\f[C]SOURCE_DATE_EPOCH\f[R] should contain an integer unix timestamp
(specifying the number of second since midnight UTC January 1, 1970).
.PP
Some document formats also include a unique identifier.
For EPUB, this can be set explicitly by setting the \f[C]identifier\f[R]
metadata field (see EPUB Metadata, above).
.SH A NOTE ON SECURITY
.PP
If you use pandoc to convert user-contributed content in a web
application, here are some things to keep in mind:
.IP "1." 3
Although pandoc itself will not create or modify any files other than
those you explicitly ask it create (with the exception of temporary
files used in producing PDFs), a filter or custom writer could in
principle do anything on your file system.
Please audit filters and custom writers very carefully before using
them.
.IP "2." 3
If your application uses pandoc as a Haskell library (rather than
shelling out to the executable), it is possible to use it in a mode that
fully isolates pandoc from your file system, by running the pandoc
operations in the \f[C]PandocPure\f[R] monad.
See the document Using the pandoc API for more details.
.IP "3." 3
Pandoc\[cq]s parsers can exhibit pathological performance on some corner
cases.
It is wise to put any pandoc operations under a timeout, to avoid DOS
attacks that exploit these issues.
If you are using the pandoc executable, you can add the command line
options \f[C]+RTS -M512M -RTS\f[R] (for example) to limit the heap size
to 512MB.
.IP "4." 3
The HTML generated by pandoc is not guaranteed to be safe.
If \f[C]raw_html\f[R] is enabled for the Markdown input, users can
inject arbitrary HTML.
Even if \f[C]raw_html\f[R] is disabled, users can include dangerous
content in URLs and attributes.
To be safe, you should run all the generated HTML through an HTML
sanitizer.
.SH AUTHORS
.PP
Copyright 2006\[en]2021 John MacFarlane (jgm\[at]berkeley.edu).
Released under the GPL, version 2 or greater.
This software carries no warranty of any kind.
(See COPYRIGHT for full copyright and warranty notices.) For a full list
of contributors, see the file AUTHORS.md in the pandoc source code.
.PP
The Pandoc source code and all documentation may be downloaded
from <https://pandoc.org>.
|
