-
Notifications
You must be signed in to change notification settings - Fork 2
/
manual.muse
2287 lines (1612 loc) · 70.5 KB
/
manual.muse
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
#pubdate 2022-11-12
#title The Text::Amuse markup manual
#lang en
#topics doc, howto
#authors Marco Pessotto, Michael Olson, John Wiegley
#subtitle The writer’s guide
#date 2022
#teaser Everything you have to know about the Text::Amuse markup. Last
updated for version 1.81 (1.81 March 29, 2022).
Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
Foundation, Inc.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software
Foundation; with no Invariant Sections, no Front-Cover Texts, and
no Back-Cover Texts. A copy of the license is included in the
section entitled “GNU Free Documentation License.”
* The Muse markup
A Muse document uses special, contextual markup rules to determine how
to format the output result. For example, if a paragraph is indented,
Muse assumes it should be quoted. Indentation is heavily used to
determine if the paragraph is something different from “normal” text.
There are not too many markup rules, and all of them strive to be as
simple as possible so that you can focus on document creation, rather
than formatting.
This document describes Muse, which was written by John
Wiegley, then maintained by Michael Olson and heavily edited and partially rewritten for this
implementation by Marco Pessotto.
** Paragraphs
Paragraphs in Muse must be separated by a blank line.
*** Centered and right aligned paragraphs and quotations
A line that begins with six or more columns of whitespace
(but less than 20) indicates a centered paragraph.
Alternatively, you can use the =<center>= tag to surround regions that
are to be published as centered paragraphs.
Like this
But if the line begins with more than 20 spaces, you’ll have a right
aligned paragraph. This is handy for signatures.
Like this right-aligned one.
The same result is done with the =right= tag.
Using the tags:
<center>
Like this centered one
</center>
<right>
And this is right
</right>
This is a quotation:
But if a line begins with whitespace (at least 2 spaces), though
less than six columns, it indicates a quoted paragraph.
Alternatively, you can use the =<quote>= tag to surround regions that
are to be published as quoted paragraphs.
**** Source
<example>
A line that begins with six or more columns of
whitespace (but less than 20) indicates a centered
paragraph.
Alternatively, you can use the =<center>= tag to
surround regions that are to be published as centered
paragraphs.
Like this
But if the line begins with more than 20 spaces, you’ll
have a right aligned paragraph. This is handy for
signatures.
Like this right-aligned one.
The same result is done with the =right= tag.
Using the tags:
<center>
Like this centered one
</center>
<right>
And this is right
</right>
This is a quotation:
But if a line begins with whitespace (at least 2
spaces), though less than six columns, it indicates a
quoted paragraph. Alternatively, you can use the
=<quote>= tag to surround regions that are to be
published as quoted paragraphs.
</example>
**Please keep in mind that indentation must be consistent if you prefer
to keep the lines short** and break them inserting a new line. Long
lines (using the rule 1 line, 1 paragraph) are perfectly fine. The
rule of paragraphs separated by blank lines still apply, though.
Also, =<tags>= which start and stop blocks, **must be placed on a line
by themselves and don’t mix with environments marked by leading
spaces, notably lists and tables.**
*** Literal paragraphs
The =<example>= tag is used for examples, where whitespace should be
preserved, the text rendered in monospace, and any characters special
to the output style escaped.
Example:
{{{
<example>
The =<example>= tag is used for examples, where
whitespace should be preserved, the text rendered in
monospace, and any characters special to the output
style escaped.
</example>
}}}
There is no =<literal>= tag as in the original Muse markup, because it’s
not a private tool and will be exposed to the internet.
**Please note** that the output will keep the lines
untouched. This means that it’s very likely that you
will get overflowing lines. To avoid this, a safe value
for a line length could be 60 characters. Use longer
lines at your perils.
An alternate syntax for the =<example>= tag is ={{{= =}}}=:
<example>
{{{
This is verbatim as well
}}}
</example>
*** Line breaks
If you need a line break, then use the =br= tag. Most of the time
this tag is unnecessary, because Muse will automatically detect
paragraphs by means of blank lines. If you want to preserve newlines in
several lines of text, then use =verse= markup instead.
<example>
This line will break <br> And continue
</example>
Yields:
This line will break <br> And continue.
<br>
If you want to add a blank, line, put the =br= tag on a line by itself:
<example>
Here we add a blank line
<br>
Here we go.
</example>
Here we add a blank line
<br>
Here we go.
*** Page breaks
If you put exactly five <verbatim>“*”</verbatim> separated by whitespace on a line by
itself, indented by 6 or more spaces (like a centered paragraph),
you’ll get a page break in the PDF.
This code will break the page.
<example>
* * * * *
</example>
* * * * *
Anyway, using three of them is just a decorator and it’s not treated specially.
* * *
It’s just a centered paragraph with 3 <verbatim>“*”</verbatim>.
** Levels of headings
A heading becomes a chapter or section in printed output — depending on
the style. To indicate a heading, start a new paragraph with one or
more asterisks, followed by a space and the heading title. Then begin
another paragraph to enter the text for that section.
All levels of headings will be published. There is support for 5 levels.
The first level is a “part”, and should be used only for larger texts. In this document is used for the License and for the main title.
The second level is a “chapter”. It starts a new page on the PDF output.
The third level is undoubtedly the most used. It usually separate a
section of an article. For example the “Literal paragraph” above.
The fourth level goes down further.
**** Fourth level, a “subsection”
The fifth level is very, very low and does not create a Table of Contents entry.
***** Fifth level 1
Some text.
***** Fifth level 2
Some other text.
**** The example of levels
<example>
* First level, aka part
** Second level, aka chapter
*** Third level, aka section
**** Fourth level, aka subsection
***** Fifth level, aka subsubsection
</example>
*** Alternate headings | How to indicate alternate headings
[*This syntax is available with Text::Amuse version 1.40, released on
2020-02-16.*]
Sometimes it's desirable to have an alternate, usually shorter, title
for the table of content. You can indicate that using this syntax:
{{{
** Alternate headings | How to indicate alternate headings
}}}
I.e. separate the short and the long title with a pipe character
<code>|</code> surrounded by spaces.
In this example, "The Alternate headings" will go into the table of
contents, while the second part will go in the document.
** Directives at the beginning of a document
Directives are lines beginning with the ‘#’ character that come before
any paragraphs or sections in the document.
Directives are of the form =#directive content of directive=.
You can use any combination of uppercase and lowercase letters for
directives, even if the directive is not in the list below. The
directives are completely arbitrary. You can put there whatever you
want. It’s the template job to pick them up. In the templates shipped
with this bundle there is support for the following directives:
The following is a list of directives that Muse uses.
- =#author=
The author of the text.
- =#title=
The title of the document
- =#lang=
The language code of the document (2 or 3 letters). Defaults to =en=.
- =#LISTtitle=
This directive is used (defaulting to =#title=) to alphabetically
sort the titles. It’s handy if you want, for example, sort “A
title” under “T” and not under “A”.
In this case you may write =#LISTtitle Title=
- =#subtitle=
The subtitle (if any)
- =#SORTauthors=
If not provided, this default to =#author=. It’s a list
separated by semicolons or commas with the various authors. While
=#author= affects the display only, this one is used to index the
document.
- =#SORTtopics=
As for authors, it’s a list (comma- or
semicolon-separated) list of topics for the current text. Used to
index the document.
- =#date=
The **year** of publishing of the document. More information
should be provided in the =#notes= directive.
- =#notes=
This directive is used for additional information here (original
title, translators, credits, etc.).
- =#source=
This directive is used for the source or the text (url, scanned from
original, original contribution, etc.). The preferred format is
“Retrieved on March 8, 2012 from [[http://url.org][the url]]”
- =#publisher=
Publisher data, if any.
- =#isbn=
ISBN, if any.
- =#rights=
Copyright info, if any.
- =#seriesname=
If the book belongs to a serie, put it here.
- =#seriesnumber=
If the book belongs to a serie, use this slot for the number.
- =#hyphenation=
See below.
A number of directives affects the output formats. The directives have
a mandatory argument, so "1" usually means a generic true value.
- =#slides 1=
Indicates that the document is meant to produce slides as well as
the regular formats.
- =#DELETED REASON=
Indicates that the text is not meant to be published.
- =#cover file.jpg=
Put the named image (jpg or png, in the same directory of the muse
file) on the cover page.
- =#coverwidth 0.5=
Specify the width of the cover image in a fraction of the text
block width. This is mostly to give you some control over its
dimensions if the default doesn't look good.
- =#nocoverpage 1=
Do not create a cover page but start the text right away.
- =#notoc 1=
Do not create a table of contents.
- =#nofinalpage 1=
Do not create a final page.
- =#impressum 1=
Create an impressum page after the cover page.
- =#continuefootnotes 1=
Continue the footnotes numbering across chapters.
- =#centerchapter 1=
Use centered chapter titles.
- =#centersection 1=
Use centered section titles (all levels).
- =#formats CODE=
Select the [[/library/templates-and-formats][custom formats]] for
this text.
*** Correcting the hyphenation in the PDF output
Sometimes you may notice some words with incorrect hyphenation in your
document. You can fix this adding the breakpoint in the
<code>#hyphenation</code> directive.
E.g.
<example>
#title Test
#lang it
#hyphenation al-be-rel-lo que-sto
Questo alberello...
</example>
You can as many words with breakpoints as you wish, separated by
spaces, but you can’t insert numbers or special characters (accents
and diacritics are fine, though). You specify a breakpoint with the
hyphen character “-”. Using a word without any hyphen will prevent the
hyphenation for that word.
** Bold, italicized and monospace text, non breaking space.
To emphasize text, surround it with certain specially recognized
characters.
The following example will produce:
*emphasis*
**strong emphasis**
***very strong emphasis***
=verbatim and monospace=
<example>
*emphasis*
**strong emphasis**
***very strong emphasis***
=verbatim and monospace=
</example>
Each of these forms may span
multiple lines, but not multiple paragraphs.
You can also use the =<code>= tag to indicate code and monospace
text. This is handy for regions that have a <verbatim>“=”</verbatim> in them.
If the <verbatim>“*”</verbatim> confuse you or the preview is screwed up, you can use
inline tag =<em>= and =<strong>=, which are guaranteed to work in any
case.
The above example rewritten with tags:
<example>
<em>emphasis</em>
<strong>strong emphasis</strong>
<strong><em>very strong emphasis</em></strong>
<code>verbatim and monospace</code>
</example>
And produces the same thing.
<em>emphasis</em>
<strong>strong emphasis</strong>
<strong><em>very strong emphasis</em></strong>
<code>verbatim and monospace</code>
Please note that there is no support for the underline. Underlining is
an handwritten substitute for the italics. You simply don’t need it.
Also, small caps are missing, mainly because on the HTML they look
awful and a very few fonts have decent small caps.
Since Text::Amuse version 0.96 (released 2018-01-27), which restored
Emacs Muse compatibility in this regard, material in =<code>= tags and
equivalent markup between equal signs is also verbatim, but with a
monospace font.
Other tags are =<sub>= and
=<sup>= for subscript and superscript. And
there is also a =<del>= tag for overstriking.
<example>
This is the <sup>superscript</sup> and this is a
<sub>subscript</sub>, and this is <del>something
deleted and overstriked</del>
</example>
This is the <sup>superscript</sup> and this is a
<sub>subscript</sub>, and this is <del>something deleted and
overstriked</del>
If you nest the same tag (e.g. =<em>this <em>and
this</em></em>=, you are going to get weird results
(and doesn’t make any sense), so don’t do it. <code>=</code> and
<code>*</code> when surrounding words have the same meaning of the
respective tags:
{{{
*this* is the same as <em>this</em>
=this= is the same as <code>this</code>
}}}
Starting with Text::Amuse version 1.72 (released on February 6, 2021),
there are two additional inline tags.
{{{
<sf>Sans Serif font</sf> and <sc>Small Caps</sc>
}}}
Resulting in <sf>Sans Serif font</sf> and <sc>Small Caps</sc>.
Caution is advised when using the sans tag. There is no semantic
attached to it and basically provides access to an alternate font.
There is little use for that in a web application (e.g., Amusewiki
pages), where if the main font is already a sans serif (like in the
default Amusewiki theme), it would be invisible. However, you can
customize the output adding a CSS rule for the class =muse-sf=.
However, there is a potential use for this font, as you can switch to
a secondary font (labeled as sans-serif, but not necessarily a sans
one) if the main one is missing some characters (e.g., you suddenly
need greek fonts, and your main one doesn't have them). In this case
you could read =sf= as "switch font".
*** Non-breaking space.
Non breaking space (=0xA0= Unicode, NO-BREAK SPACE) is just a regular
character, but it's somehow complicate to manage, because very often
appears like a normal space. You can use a double tilde
<verbatim>~~</verbatim> to insert a non~~breaking~~space which is
explicit in the muse document.
This feature was added in Text::Amuse 0.94 but it was present in Emacs
Muse.
** Footnotes
A footnote reference is simply a number in square brackets. To define
the footnote, place this definition starting the line with a digit in
square brackets.
<example>
This is the text, and we refer to a footnote [1]
Here the text continues.
[1] This footnote
spans more lines in the source
You can continue the footnote on another paragraph, as long as it
has the same amount of indentation of the previous item.
[2] But this is not, because of the initial
whitespace.
[3] Footnotes which don’t have a referrer will
disappear on the PDF output and preserved in the
HTML. But will lead to incorrect code, as it will
point to a non-existent anchor
</example>
This is the result:
----
This is the text, and we refer to a footnote [1]
Here the text continues.
[1] This footnote
spans more lines in the source
You can continue the footnote on another paragraph, as long as it
has the same amount of indentation of the previous item.
[2] But this is not, because of the initial whitespace.
[3] Footnotes which don’t have a referrer will disappear on the PDF
output and preserved in the HTML. But will lead to incorrect
code, as it will point to a non-existent anchor
----
You can break the footnotes lines (even if it’s not recommended), but
keep the indentation consistent, as shown above.
*** Secondary footnotes (support added in Text::Amuse 0.91, 2017-12-10)
Rarely needed, but supported, are the secondary footnotes, i.e. an
additional apparatus. They obey the same rules as the regular
footnotes, but they are marked with curly brackets instead of square
ones. You can also place secondary footnotes in regular footnotes.
This is meant for critical edition, but you may use them to
differentiate between author's notes and translator's notes.
{{{
This is a regular [4] footnote, and this a secondary {1}
[4] Regular footnote, and has a secondary one on it {2}
{1} Secondary footnote body (1)
{2} Secondary footnote body (2)
}}}
Which produces:
----
This is a regular [4] footnote, and this a secondary {1}
[4] Regular footnote, and has a secondary one on it {2}
{1} Secondary footnote body (1)
{2} Secondary footnote body (2)
----
** Poetic stanzas
Poetry requires that whitespace be preserved, but without resorting to
monospace. To indicate this, use the following markup, reminiscent of
email quotations, or use the =verse= tag.
<example>
> A line of Emacs verse;
> forgive its being so terse.
<verse>
A line of Emacs verse;
forgive its being so terse.
</verse>
</example>
This yields:
> A line of Emacs verse;
> forgive its being so terse.
<verse>
A line of Emacs verse;
forgive its being so terse.
</verse>
Multiple stanzas may be included in one set of <verse> tags, as
follows.
<example>
<verse>
A line of Emacs verse;
forgive its being so terse.
In terms of terse verse,
you could do worse.
</verse>
Or this
> A line of Emacs verse;
> forgive its being so terse.
>
> In terms of terse verse,
> you could do worse.
</example>
<verse>
A line of Emacs verse;
forgive its being so terse.
In terms of terse verse,
you could do worse.
</verse>
Or this
> A line of Emacs verse;
> forgive its being so terse.
>
> In terms of terse verse,
> you could do worse.
** Lists
Lists are given using special characters at the beginning of a line.
Whitespace must occur before bullets or numbered items, to distinguish
from the possibility of those characters occurring in a real sentence.
Description lists are marked by some initial whitespace, the term, a
double colon surrounded by whitespace, and the description body.
<example>
Normal text.
- bullet item one
- bullet item two
An enumerated list follows.
1. Enum item one
2. Enum item two
A list with roman numbering
i. First
ii. Second
iii. Third
A list with upper roman numbering
I. First
II. Second
III. Third
A list with upper letters
A. first
B. second
C. third
A list with lower letters
a. first
b. second
c. third
A description list
First term :: definition and description
Second term :: definition and description
</example>
Please note the consistent indentation, **especially** for roman numbering.
Normal text.
- bullet item one
- bullet item two
An enumerated list follows.
1. Enum item one
2. Enum item two
A list with roman numbering
i. First
ii. Second
iii. Third
A list with upper roman numbering
I. First
II. Second
III. Third
A list with upper letters
A. first
B. second
C. third
A list with lower letters
a. first
b. second
c. third
A description list
First term :: definition and description
Second term :: definition and description
*** Breaking lists
If for some reason you want to break the list without starting a
regular paragraph, you can do so by inserting a
=<br>= tag (which adds some white space between
them) or a comment (invisible). E.g.
{{{
List:
a. bullet item one
a. bullet item two, and will break
; a comment
a. bullet item one
a. bullet item two, and break
<br>
a. bullet item one
a. bullet item two, and end
}}}
Resulting in:
List:
a. bullet item one
a. bullet item two, and will break
; a comment
a. bullet item one
a. bullet item two, and break
<br>
a. bullet item one
a. bullet item two, and end
*** Nested lists
It is possible to nest lists of the same or different kinds. The
“level” of the list is determined by the amount of initial whitespace.
<example>
Normal text.
- Level 1, bullet item one
1. Level 2, enum item one
2. Level 2, enum item two
- Level 1, bullet item two
1. Level 2, enum item one
2. Level 2, enum item two
i. Level 3, enum item i
ii. Level 3, enum item ii
3. Level 2, enum item three
- Back to Level 1, third bullet
a. Level 2, enum item “a”
b. Level 2, enum item “b”
I. Level 3, enum item “I”
One term :: description
Another term :: description
- Back to the bullets
</example>
Normal text.
- Level 1, bullet item one
1. Level 2, enum item one
2. Level 2, enum item two
- Level 1, bullet item two
1. Level 2, enum item one
2. Level 2, enum item two
i. Level 3, enum item i
ii. Level 3, enum item ii
3. Level 2, enum item three
- Back to Level 1, third bullet
a. Level 2, enum item “a”
b. Level 2, enum item “b”
I. Level 3, enum item “I”
One term :: description
Another term :: description
- Back to the bullets
*** Breaking list items
If you want to break up a line within any list type, just put one blank
line between the end of the previous line and the beginning of the next
line, using the same amount of initial indentation.
Keep in mind that if you put random indentation you’ll get random and
probably unexpected results (but it should not crash — if it does,
please contact me).
Also, you can be lazy with numbered list. The parser actually doesn’t
care if you number them properly, or just do something like that.
<example>
1. first
1. second
1. third
or
a. first
a. second
a. third
</example>
There results will always be:
1. first
1. second
1. third
or
a. first
a. second
a. third
*** Complete example
<example>
Normal text.
- Level 1, bullet item one, this is the first
paragraph. I can break the line, keeping the same
amount of indentation
Here I have the same amount of indentation, and it
continues the item above.
1. Level 2, enum item one. I can break the line,
keeping the same amount of indentation
Here I have the same amount of indentation, and
it continues the item above.
2. Level 2, enum item two
which continues
Here I have the same amount of indentation, and
it continues the item above.
- Level 1, bullet item two
which continues
Here I have the same amount of indentation, and it
continues the item above.
1. Level 2, enum item one
which continues
Here I have the same amount of indentation, and
it continues the item above.
2. Level 2, enum item two
which continues
Here I have the same amount of indentation, and
it continues the item above.
i. Level 3, enum item i
Here I have the same amount of indentation,
and it continues the item above.
ii. Level 3, enum item ii
Here I have the same amount of indentation,
and it continues the item above.
3. Level 2, enum item three
which continues
Here I have the same amount of indentation, and
it continues the item above.
- Back to Level 1, third bullet
Here I have the same amount of indentation, and it