apex-ruby 1.0.17 → 1.0.20

data/ext/apex_ext/apex_src/documentation/app-transformed/Syntax.md

@@ -0,0 +1,1367 @@
+# Syntax Reference
+
+This page documents all syntax features available in **unified mode**. For mode-specific syntax, see [Modes](Modes).
+
+## Basic Markdown
+
+### Headers
+
+**ATX-style headers:**
+```markdown
+# H1
+## H2
+### H3
+#### H4
+##### H5
+###### H6
+```
+
+**Setext-style headers:**
+```markdown
+H1 Alternative
+==============
+
+H2 Alternative
+--------------
+```
+
+**Multi-line setext headers (MMD 6):**
+Setext headers can span multiple lines before the underline. This is supported in **unified** and **MultiMarkdown** modes:
+
+```markdown
+This is
+a multi-line
+setext header
+========
+
+Another
+header
+with
+multiple
+lines
+--------
+```
+
+### Emphasis
+
+```markdown
+*italic*
+_italic_
+**bold**
+__bold__
+***bold italic***
+___bold italic___
+```
+
+### Superscript and Subscript
+
+MultiMarkdown-style superscript and subscript syntax:
+
+```markdown
+H~2~O          # H₂O (subscript - tildes within word)
+m^2             # m² (superscript)
+x^2 + y^2       # x² + y²
+H~2~SO~4~       # H₂SO₄ (multiple subscripts within word)
+~h2o~           # <u>h2o</u> (underline - tildes at word boundaries)
+```
+
+**Syntax rules:**
+- The `^` character creates superscript for the text immediately following it. The superscript stops at the first space, punctuation, or newline.
+- The `~` character creates subscript when used **within a word/identifier** with paired tildes (e.g., `H~2~O`). The subscript ends at the second tilde.
+- When tildes are at word boundaries (e.g., `~text~`), they create underline instead of subscript. This prevents interference with underline/strikethrough syntax.
+
+**Examples:**
+```markdown
+Water: H~2~O           # H₂O (subscript - tildes within word)
+Area: m^2              # m² (superscript)
+Formula: E = mc^2      # E = mc² (superscript)
+Chemical: H~2~SO~4~    # H₂SO₄ (multiple subscripts within word)
+~h2o~                  # <u>h2o</u> (underline - tildes at word boundaries)
+```
+
+This feature is enabled by default in **MultiMarkdown** and **unified** modes. In other modes, enable it in **Settings->Processor->Superscript/Subscript**.
+
+### Lists
+
+**Unordered:**
+```markdown
+- Item 1
+- Item 2
+  - Nested item
+  - Another nested
+- Item 3
+```
+
+**Ordered:**
+```markdown
+1. First item
+2. Second item
+   1. Nested item
+   2. Another nested
+3. Third item
+```
+
+**Mixed Markers (Unified & MultiMarkdown modes):**
+In unified and MultiMarkdown modes, you can mix different list marker types at the same indentation level. The list will inherit the type from the first item:
+
+```markdown
+1. First numbered item
+* Second item (becomes numbered)
+* Third item (becomes numbered)
+
+* First bullet item
+1. Second item (becomes bullet)
+2. Third item (becomes bullet)
+```
+
+By default, CommonMark and GFM modes create separate lists when marker types change. Enable **Settings->Processor->Mixed Lists** to enable this behavior in other modes, or disable it in unified/MultiMarkdown modes.
+
+**Alpha Lists (Unified mode):**
+In unified mode, you can use alphabetic markers for ordered lists:
+
+```markdown
+a. First item
+b. Second item
+c. Third item
+
+A. First item (uppercase)
+B. Second item (uppercase)
+C. Third item (uppercase)
+```
+
+Alpha lists are automatically converted to HTML with `style="list-style-type: lower-alpha"` or `style="list-style-type: upper-alpha"`. This feature is enabled by default in unified mode. Enable **Settings->Processor->Alpha Lists** in other modes, or disable it in unified mode.
+
+**Task Lists:**
+```markdown
+- [ ] Todo item
+- [x] Completed item
+- [ ] Another todo
+```
+
+### Links and Images
+
+**Standard Markdown links:**
+```markdown
+[Link text](https://example.com)
+[Link with title](https://example.com "Title")
+```
+
+**Link titles with different quote styles (MMD 6):**
+Link and image titles can use single quotes, double quotes, or parentheses. This is supported in **unified** and **MultiMarkdown** modes:
+
+```markdown
+[Link with double quotes](https://example.com "Title")
+[Link with single quotes](https://example.com 'Title')
+[Link with parentheses](https://example.com (Title))
+```
+
+**Images:**
+```markdown
+![Alt text](image.png)
+![Alt with title](image.png "Image title")
+```
+
+**Image titles with different quote styles (MMD 6):**
+```markdown
+![Image](image.png "Double quote title")
+![Image](image.png 'Single quote title')
+![Image](image.png (Parentheses title))
+```
+
+**Reference-style links and images:**
+Reference-style links and images also support all three quote styles for titles:
+
+```markdown
+[Link text][ref1]
+![Image][img1]
+
+[ref1]: https://example.com "Reference title"
+[ref2]: https://example.com 'Reference title'
+[ref3]: https://example.com (Reference title)
+
+[img1]: image.png "Image title"
+[img2]: image.png 'Image title'
+[img3]: image.png (Image title)
+```
+
+**Autolinks:**
+
+Apex can automatically convert URLs and email addresses into clickable links. Autolinking is enabled by default in **GFM**, **MultiMarkdown**, **Kramdown**, and **unified** modes. It is disabled by default in **CommonMark** mode.
+
+**Angle-bracket autolinks:**
+```markdown
+<https://example.com>
+<http://example.com>
+<mailto:user@example.com>
+```
+
+**Bare URL autolinks:**
+```markdown
+Visit https://example.com for more info.
+Check out http://example.com too.
+```
+
+**Email autolinks:**
+```markdown
+Contact me@example.com for details.
+Send to user@example.com.
+```
+
+**Important notes:**
+- Autolinks are **not** processed inside code spans (`` `code` ``) or code blocks (``` ``` ```)
+- Enable **Settings->Processor->Autolinks** to enable autolinking in modes where it's disabled by default
+- Disable **Settings->Processor->Autolinks** to disable autolinking in modes where it's enabled by default
+- Angle-bracket autolinks (`<url>`) are converted to standard Markdown links during preprocessing
+- Bare URLs and email addresses are also converted to Markdown links during preprocessing
+
+### Code
+
+**Inline code:**
+```markdown
+Use `code` in text.
+```
+
+**Fenced code blocks:**
+````markdown
+```python
+def hello():
+    print("Hello, World!")
+```
+````
+
+**Indented code blocks:**
+```markdown
+    def hello():
+        print("Hello, World!")
+```
+
+### Blockquotes
+
+```markdown
+> This is a quote.
+> It can span multiple lines.
+>
+> > Nested quotes are supported.
+```
+
+**Lists and definition lists in blockquotes:**
+
+Blockquotes can contain lists and definition lists:
+
+```markdown
+> 1. First item
+> 2. Second item
+>
+> - Unordered item
+> - Another item
+>
+> Term
+> : Definition
+```
+
+Nested blockquotes also support these features:
+
+```markdown
+> > Nested quote
+> > 1. List item
+> > Term
+> > : Definition
+```
+
+### Horizontal Rules
+
+```markdown
+---
+***
+___
+```
+
+## Tables
+
+### Standard Tables
+
+```markdown
+| Header 1 | Header 2 | Header 3 |
+| -------- | :------: | -------: |
+| Left     |  Center  |    Right |
+| Data     |   Data   |     Data |
+```
+
+Column alignment:
+- `:---` or `---` - Left (default)
+- `:---:` - Center
+- `---:` - Right
+
+### Relaxed Tables
+
+In unified and kramdown modes, tables don't require separator rows:
+
+```markdown
+one | two | three
+1 | 2 | 3
+4 | 5 | 6
+```
+
+This automatically becomes a table. See [Modes](Modes) for details.
+
+### Headerless Tables
+
+Apex supports tables that start with alignment rows (separator rows) without header rows. The alignment specified in the separator row is automatically applied to all columns:
+
+```markdown
+| --- | --- | --- |
+| a   | b   | c   |
+| 1   | 2   | 3   |
+```
+
+Alignment specifiers work as usual:
+
+```markdown
+|:---|:---:|---:|
+| left | center | right |
+```
+
+In this case, the first row (the alignment row) specifies the column alignment, and all subsequent data rows inherit that alignment. The empty header row that would normally be required is automatically handled.
+
+#### Row header columns
+
+You can also mark the **first column** as a row-header column by starting the header row with an **empty first cell**:
+
+```markdown
+|   | Header 1 | Header 2 |
+| Row 1 | data 1.1 | data 1.2 |
+| Row 2 | data 2.1 | data 2.2 |
+```
+
+When the first header cell is empty (for example, `| |` or `|   |`), Apex will:
+
+- Treat the rest of the header row as usual column headers.
+- Render the first cell of each body row as a **row header** using `<th scope="row">Row 1</th>`, `<th scope="row">Row 2</th>`, etc.
+
+Notes:
+
+- The row-header behavior only applies to the **first column** and only when the **first header cell is empty**.
+- Tables that start with `|data|data|` or `data|data` do **not** enable row headers.
+- This works together with all other table features (relaxed tables, headerless tables, colspans/rowspans, captions, etc.).
+
+### Inline Tables from CSV/TSV
+
+In addition to regular pipe tables, Apex can convert inline CSV/TSV text into tables.
+
+#### Fenced CSV/TSV tables
+
+Use a fenced code block with the info string `table`. The delimiter is detected automatically:
+
+- If any non-blank line contains a **tab**, the block is treated as TSV.
+- Otherwise, if any non-blank line contains a **comma**, the block is treated as CSV.
+- If no tabs or commas are found, the block is left unchanged as a normal `table`-info code block (useful for showing literal CSV/TSV).
+
+```table
+header 1,header 2,header 3
+data 1,data 2,data 3
+,,data 2c
+```
+
+You can also use TSV with real tab characters:
+
+```table
+col1\tcol2\tcol3
+val1\tval2\tval3
+```
+
+#### Alignment rows in CSV/TSV tables
+
+CSV/TSV inline tables can specify column alignment using a row of **alignment keywords**:
+
+```table
+H1,H2,H3
+left,center,right
+a,b,c
+```
+
+The alignment row is not rendered as data; it is converted to the equivalent Markdown alignment row:
+
+- `left` → `:---`
+- `center` → `:---:`
+- `right` → `---:`
+- `auto` → `---`
+
+If the first row contains only alignment keywords, it becomes a **headless table**: the alignment row is emitted first and all following rows become body rows. If there is **no alignment row at all**, Apex emits a default `---` separator row so that relaxed/headless table handling still works as expected.
+
+#### `<!--TABLE-->` markers
+
+You can also start an inline CSV/TSV table with an HTML comment:
+
+```markdown
+<!--TABLE-->
+header 1,header 2,header 3
+data 1,data 2,data 3
+,,data 2c
+```
+
+`<!--TABLE-->` consumes the following **contiguous non-blank lines** as table data (stopping at the first blank line), applies the same delimiter detection and optional alignment-row handling, and converts the block into a table. If no tabs or commas are found, the comment and lines are left unchanged.
+
+### Advanced Table Features
+
+**Column spans (empty cells):**
+```markdown
+| A   | B   | C   |
+| --- | --- | --- |
+| D   |     |     |
+```
+
+Empty cells merge with the previous cell.
+
+**Row spans:**
+```markdown
+| A   | B   |
+| --- | --- |
+| C   | D   |
+| ^^  | E   |
+```
+
+The `^^` marker creates a row span on the cell above. Consecutive `^^` markers stack to create larger row spans.
+
+**Table footers (tfoot):**
+```markdown
+| h1  |  h2   | h3  |
+| --- | :---: | --- |
+| d1  |  d2   | d3  |
+| d1  |  d2   | d3  |
+| === |  ===  | === |
+| d-4 |  d-5  | d-6 |
+```
+
+A row where every cell contains only `===` (three or more equals, with optional extra `=` and whitespace) is treated as a **footer divider**. That row is removed from the output and all following rows are rendered inside `<tfoot>`.
+
+**Individual cell alignment:**
+
+Table cells can be aligned individually using colons, similar to Jekyll Spaceship:
+
+```markdown
+| Header | Header | Header |
+| --- | --- | --- |
+| :Left | Center: | :Center: |
+| Right: | Normal | :Left |
+```
+
+- `:Text` or `: Text` - Left align (leading colon)
+- `Text:` or `Text :` - Right align (trailing colon)
+- `:Text:` or `: Text :` - Center align (both colons)
+
+The colons are removed from the output, and the alignment is applied via CSS `text-align` styles. Escaped colons (`\:`) are not treated as alignment markers.
+
+**Combined row and column spans:**
+
+You can mix rowspans and colspans in the same table to create more complex layouts:
+
+```markdown
+[Employee Performance Q4]
+| Department  | Employee | Q1-Q2 Average | Q3     | Q4  | Overall |
+| ----------- | -------- | ------------- | ------ | --- | ------- |
+| Engineering | Alice    | 93.5          | 94     | 96  | 94.25   |
+| ^^          | Bob      | 89.0          | 87     | 91  | 89.00   |
+| Marketing   | Charlie  | 92.0          | Absent |     | 92.00   |
+| Sales       | Diana    | 87.5          | 88     | 90  | 88.50   |
+| ^^          | Eve      | 93.0          | 95     | 93  | 93.50   |
+{: .performance-table #q4-results}
+```
+
+Here `^^` creates rowspans for the `Department` column, while empty cells in the "Absent" row allow the "Q4" value to span visually.
+
+**Table captions:**
+```markdown
+[Table Caption]
+
+| A   | B   |
+| --- | --- |
+| C   | D   |
+```
+
+Captions can appear **before or after** a table. They must be contiguous with the table (no other content between them), but a blank line is allowed:
+
+```markdown
+| A   | B   |
+| --- | --- |
+| C   | D   |
+
+[Caption after table]
+```
+
+In addition, Apex supports **Pandoc-style captions**:
+
+```markdown
+| A   | B   |
+| --- | --- |
+| C   | D   |
+
+Table: Caption after table
+```
+
+Pandoc-style `Table: Caption` lines are normalized to `[Caption]` before parsing, so they work with the same caption rendering as MultiMarkdown captions.
+
+Apex also supports **Pandoc table_attributes extension** using the `: Caption` syntax:
+
+```markdown
+| Key | Value |
+| --- | :---: |
+| one |   1   |
+| two |   2   |
+
+: Key value table {#table-id .testing key="value"}
+```
+
+The `: Caption` format (with optional IAL attributes) is recognized when it appears immediately before or after a table. IAL attributes in the caption are extracted and applied to the table element itself. This supports both Kramdown-style IALs (`{: #id .class}`) and Pandoc-style IALs without the colon (`{#id .class}`).
+
+**Note:** The `: Caption` syntax only works when adjacent to a table to avoid conflicts with definition list syntax. If a line starting with `:` is not next to a table, it will be processed as a definition list item.
+
+**Caption position:** By default, captions appear **below** the table. Configure caption position in **Settings->Processor->Table Captions**.
+
+## Footnotes
+
+### Reference Style
+
+```markdown
+Here's a footnote[^1] and another[^note].
+
+[^1]: First footnote content.
+[^note]: Second footnote with custom ID.
+```
+
+### Inline Style (Kramdown)
+
+```markdown
+This is a footnote^[inline content here].
+```
+
+### Inline Style (MultiMarkdown)
+
+```markdown
+This is a footnote[^inline content with spaces].
+```
+
+## Definition Lists
+
+```markdown
+Term
+: Definition text with **Markdown** support
+
+Apple
+: A fruit
+: A company
+
+Term with multiple definitions
+: First definition
+: Second definition
+```
+
+**Definition lists in blockquotes:**
+
+Definition lists work inside blockquotes, including nested blockquotes:
+
+```markdown
+> Term 1
+> : Definition 1
+> Term 2
+> : Definition 2
+
+> > Nested blockquote
+> > Term
+> > : Definition
+```
+
+This allows you to create quoted definitions and maintain proper nesting structure.
+
+## Citations
+
+**Note:** Citations are supported in **MultiMarkdown** and **unified** modes. A bibliography file must be provided via **Settings->Processor->Citations** or document metadata.
+
+### Pandoc Citation Syntax
+
+**Basic citation:**
+```markdown
+See [@doe99] for details.
+```
+
+**Multiple citations:**
+```markdown
+See [@doe99; @smith2000; @smith2004] for more information.
+```
+
+**Author in text:**
+```markdown
+@smith04 says blah.
+```
+
+**Author suppressed:**
+```markdown
+Smith says blah [-@smith04].
+```
+
+**With locator:**
+```markdown
+@smith04 [p. 33] says blah.
+```
+
+### MultiMarkdown Citation Syntax
+
+**Basic citation:**
+```markdown
+This is a statement[#Doe:2006].
+```
+
+**With locator:**
+```markdown
+This is a statement[p. 23][#Doe:2006].
+```
+
+**Inline citation:**
+```markdown
+As per Doe.[#John Doe. *A Totally Fake Book 1*. Vanity Press, 2006.]
+```
+
+### mmark Citation Syntax
+
+**Basic citation:**
+```markdown
+This references [@RFC2535].
+```
+
+**Normative citation:**
+```markdown
+This references [@!RFC1034] (normative).
+```
+
+**Multiple citations:**
+```markdown
+Multiple citations: [@RFC1034;@RFC1035].
+```
+
+**Combined reference:**
+```markdown
+Combined reference: [@RFC1034@STD3].
+```
+
+### Bibliography
+
+Bibliography is automatically generated from cited entries and inserted at the `<!-- REFERENCES -->` marker or appended to the end of the document.
+
+**Bibliography marker:**
+```markdown
+## References
+
+<!-- REFERENCES -->
+```
+
+**Bibliography in metadata:**
+```markdown
+---
+bibliography: references.bib
+---
+
+See [@doe99] for details.
+```
+
+**Multiple bibliography files:**
+```markdown
+---
+bibliography:
+  - refs1.bib
+  - refs2.bib
+---
+```
+
+For complete documentation of citations and bibliography, see [Citations](Citations).
+
+## Indices
+
+**Note:** Indices are supported in **MultiMarkdown** and **unified** modes. Enabled by default in these modes.
+
+### mmark Index Syntax
+
+**Basic index entry:**
+```markdown
+This is about protocols (!Protocol).
+```
+
+**Sub-item entry:**
+```markdown
+HTTP/1.1 (!HTTP, HTTP/1.1) is a protocol version.
+```
+
+**Primary entry (bold in index):**
+```markdown
+This is a primary topic (!!Primary Topic, Sub Topic).
+```
+
+**Multiple entries:**
+```markdown
+Protocols (!Protocol) and implementations (!Implementation) are important.
+```
+
+### TextIndex Syntax
+
+**Basic syntax (indexes preceding word):**
+```markdown
+Most mechanical keyboard firmware{^} supports key combinations.
+```
+
+**Explicit term:**
+```markdown
+This uses [key combinations]{^} for indexing.
+```
+
+**With parameters:**
+```markdown
+Term{^param1 param2}
+```
+
+### Index Generation
+
+The index is automatically generated at the end of the document or at the `<!--INDEX-->` marker if present:
+
+```markdown
+# Document
+
+This is about protocols (!Protocol).
+
+<!--INDEX-->
+
+More content after the index.
+```
+
+**Index features:**
+- Entries are sorted alphabetically
+- Can be grouped by first letter (default)
+- Sub-items are nested under main terms
+- Primary entries are marked (typically bold)
+- Each entry links back to its location in the document
+
+**Suppress index:**
+Disable **Settings->Processor->Generate Index** to suppress index generation while still creating index markers.
+
+## Math
+
+**Inline math:**
+```markdown
+The equation $E = mc^2$ is famous.
+```
+
+**Display math:**
+```markdown
+$$
+\int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi}
+$$
+```
+
+Math is wrapped in spans with appropriate classes for MathJax or KaTeX.
+
+## Wiki Links
+
+**Note:** Wiki links are **disabled by default** in all modes. Enable them in **Settings->Processor->Wiki Links**.
+
+```markdown
+[[Page Name]]                   # Link to page
+[[Page Name|Display Text]]      # Custom display text
+[[Page Name#Section]]           # Link to section
+[[Page Name#Section|Display]]   # Custom display with section
+```
+
+## Critic Markup
+
+Track changes and annotations:
+
+```markdown
+{++addition++}              # Added text
+{--deletion--}              # Deleted text
+{~~old text~>new text~~}    # Substitution
+{==highlighted==}           # Highlighted text
+{>>comment text<<}         # Comment/annotation
+```
+
+Critic Markup changes can be accepted or rejected using options in **Settings->Processor->Critic Markup**.
+
+## Callouts
+
+Bear/Obsidian/Xcode Playground syntax:
+
+```markdown
+> [!NOTE] Title
+> This is a note callout
+
+> [!WARNING] Be Careful
+> Warning content
+
+> [!TIP] Pro Tip
+> Helpful advice
+
+> [!DANGER] Critical
+> Dangerous operation
+
+> [!INFO] Information
+> Informational content
+```
+
+**Collapsible callouts:**
+```markdown
+> [!NOTE]+ Expandable
+> Defaults to open
+
+> [!NOTE]- Collapsed
+> Defaults to closed
+```
+
+## File Includes
+
+**Marked syntax:**
+```markdown
+<<[file.md]      # Include and process Markdown
+<<(code.py)      # Include as code block
+<<{raw.html}     # Include raw HTML
+```
+
+**MultiMarkdown transclusion:**
+```markdown
+{{file.md}}      # Include file
+{{file.*}}       # Prefer file.html, file.md, file.txt, file.tex (in that order)
+{{*.md}}         # Glob include (first matching .md file)
+{{c?de.py}}      # ? wildcard (e.g. resolves to code.py)
+```
+
+`{{file.*}}` implements MultiMarkdown-style wildcard resolution, trying common extensions in a preferred order.
+Patterns containing `*`, `?`, `[]`, or `{}` are treated as glob patterns and resolved relative to the current transclude base (see metadata `transclude base`).
+
+**iA Writer syntax:**
+```markdown
+/image.png       # Intelligent include (detects type)
+/code.py         # Auto-detects as code block
+/document.md     # Auto-detects as Markdown
+```
+
+CSV and TSV files automatically convert to tables.
+
+### Address Syntax for File Includes
+
+File includes support mmark-style address syntax to include specific line ranges or sections. This works with `{{file}}` and `<<[file]`, `<<(file)`, `<<{file}` syntaxes, but **not** with iA Writer `/file` syntax.
+
+**Line number ranges:**
+```markdown
+{{file.md}}[3,5]        # Include lines 3 to 5 (exclusive of 5)
+{{file.md}}[3,]         # Include from line 3 to end of file
+<<[file.md][1,10]       # Include lines 1 to 10 in Marked syntax
+<<(code.py)[5,15]       # Include lines 5 to 15 in code block
+```
+
+**Regular expression ranges:**
+```markdown
+{{file.md}}[/START/,/END/]     # Include lines between regex matches
+{{file.md}}[/^## /,/^## /]     # Include between heading markers
+<<[file.md][/function/,/^}/]   # Include from function to closing brace
+```
+
+**Prefix option:**
+```markdown
+{{file.md}}[3,5;prefix="C: "]   # Prefix each line with "C: "
+{{code.py}}[1,10;prefix="  "]  # Indent included lines
+```
+
+**Combined examples:**
+```markdown
+# Include lines 10-20 with prefix
+{{example.py}}[10,20;prefix="    "]
+
+# Include from regex match to end
+{{config.md}}[/^## Config/,]
+
+# Include between patterns with prefix
+{{script.sh}}[/# START/,/# END/;prefix="# "]
+```
+
+**Notes:**
+- Line numbers are 1-based
+- End line is exclusive (e.g., `[3,5]` includes lines 3 and 4, not 5)
+- Regex patterns use POSIX extended regular expressions
+- If start pattern is not found, empty content is returned
+- If end pattern is not found, content from start to end of file is included
+- Prefix is applied to each included line
+
+### Address Syntax for File Includes
+
+Apex supports mmark-style address syntax for specifying line ranges and applying prefixes to included files. This works with `{{file}}` and `<<[file]` syntaxes (but not iA Writer `/file` syntax).
+
+**Line number ranges:**
+```markdown
+{{file.md}}[3,5]      # Include lines 3 to 5 (exclusive of 5)
+{{file.md}}[3,]       # Include from line 3 to end of file
+<<[file.md][1,10]     # Include lines 1 to 10
+<<(code.py)[5,15]     # Include lines 5 to 15 from code file
+```
+
+**Regular expression ranges:**
+```markdown
+{{file.md}}[/START/,/END/]           # Include lines between regex matches
+{{file.md}}[/^## Section/,/^## /]     # Include from section to next section
+<<[file.md][/BEGIN/,/END/]            # Include between BEGIN and END markers
+```
+
+**Prefix option:**
+```markdown
+{{file.md}}[3,5;prefix="C: "]         # Prefix each line with "C: "
+{{file.md}}[prefix="> "]              # Prefix all lines with "> "
+<<(code.py)[1,10;prefix="    "]      # Prefix with 4 spaces (indentation)
+```
+
+**Combined examples:**
+```markdown
+{{config.py}}[/def setup/,/^def /;prefix="# "]
+# Includes lines from "def setup" to next "def", with "# " prefix
+
+<<[readme.md][10,20;prefix="> "]
+# Includes lines 10-20 with blockquote prefix
+```
+
+**Notes:**
+- Line numbers are 1-based
+- End line is exclusive (e.g., `[3,5]` includes lines 3 and 4, not 5)
+- Regex patterns use POSIX extended regular expressions
+- Prefix is applied to each included line
+- Address syntax does not apply to iA Writer syntax (`/file`)
+
+## Metadata
+
+### YAML Front Matter
+
+```yaml
+---
+title: My Document
+author: John Doe
+date: 2025-12-06
+---
+```
+
+### MultiMarkdown Metadata
+
+```markdown
+Title: My Document
+Author: John Doe
+Date: 2025-12-06
+
+```
+
+### Pandoc Title Block
+
+```markdown
+% My Document
+% John Doe
+% 2025-12-06
+```
+
+### Metadata Variables
+
+Use `[%key]` to insert metadata values anywhere:
+
+```markdown
+---
+title: Apex Guide
+version: 0.1.0
+---
+
+# [%title]
+
+Version: [%version]
+```
+
+You can also transform metadata values using the `[%key:transform]` syntax. See [Metadata Transforms](Metadata-Transforms) for a complete guide to available transforms.
+
+**External Metadata Sources:**
+
+Metadata can also be loaded from external files:
+
+- **Metadata File**: Select a metadata file in **Settings->Processor->Metadata File**, or specify a file in document metadata (YAML, MMD, or Pandoc format, auto-detected)
+
+Metadata precedence (highest to lowest):
+1. Document metadata (in the document)
+2. File metadata (from **Settings->Processor->Metadata File** or document metadata)
+
+**Reusable Metadata Files:**
+
+You can create reusable metadata files for common settings like language and quotes language. This is especially useful for maintaining consistent settings across multiple documents.
+
+**Example metadata file (`lang-fr.yml`):**
+```yaml
+---
+language: fr
+quoteslanguage: french
+---
+```
+
+**Note:** In YAML, keys with spaces must be quoted (e.g., `"Quotes Language": french`). Since Apex normalizes metadata keys (removes spaces, case-insensitive), you can use keys without spaces for cleaner YAML syntax. Both `quoteslanguage` and `"Quotes Language"` will work.
+
+**Example metadata file (`lang-de.mmd`):**
+```
+Language: de
+Quotes Language: german
+```
+
+**Note:** MultiMarkdown format allows spaces in keys, so `Quotes Language` works without quotes.
+
+**Usage:**
+
+Select the metadata file in **Settings->Processor->Metadata File** to apply it to all documents, or specify it in document metadata.
+
+**Benefits:**
+- **Consistency**: Ensure all documents use the same language settings
+- **Reusability**: Define language and quotes language once, use across many documents
+- **Maintainability**: Update language settings in one place
+- **Automatic fallback**: If `Quotes Language` is not specified, it automatically uses the `language` value
+
+**Controlling Settings via Metadata:**
+
+Most settings can be controlled via metadata, allowing per-document configuration. Boolean options accept `true`/`false`, `yes`/`no`, or `1`/`0` (case-insensitive). String options use the value directly.
+
+**Example:**
+```yaml
+---
+indices: false
+wikilinks: true
+bibliography: references.bib
+title: My Research Paper
+pretty: true
+standalone: true
+---
+```
+
+This enables per-document configuration where each file can have its own settings.
+
+## Abbreviations
+
+**Classic MMD syntax:**
+```markdown
+*[HTML]: Hypertext Markup Language
+*[CSS]: Cascading Style Sheets
+
+HTML and CSS are essential.
+```
+
+**MMD 6 reference syntax:**
+```markdown
+[>MMD]: MultiMarkdown
+
+Using [>MMD] here and [>MMD] again.
+```
+
+**MMD 6 inline syntax:**
+```markdown
+This is [>(MD) Markdown] and [>(CSS) Cascading Style Sheets].
+```
+
+## Inline Attribute Lists (IAL)
+
+Kramdown and Pandoc syntax for adding HTML attributes (IDs, classes, and custom key-value pairs) to Markdown elements.
+
+Apex supports both **Kramdown-style IALs** (`{: ...}`) and **Pandoc-style IALs** (`{#id .class}`). Both formats work identically throughout the document.
+
+**Block-level IALs** appear on the line immediately after the element:
+```markdown
+# Header
+{: #custom-id}
+
+# Another Header
+{#custom-id-2 .highlight}
+
+Paragraph with class.
+{: .important}
+
+## Another Header
+{: #section-2 .highlight title="Section Title" lang="en"}
+```
+
+**Inline IALs** appear immediately after the element within the paragraph:
+```markdown
+Here's a [styled link](url){:.button} with a class.
+
+Here's a [Pandoc-style link](url){#link-id .button} with attributes.
+
+This has **bold text**{:.bold-style} and *italic text*{:.italic-style}.
+```
+
+**Key-value pairs** allow custom attributes:
+```markdown
+Paragraph.
+{: title="Important Note" lang="en" data-custom="value"}
+
+[Link](url){:rel="nofollow" target="_blank"}
+```
+
+**Attribute List Definitions (ALDs)** define reusable attribute sets:
+```markdown
+# Header 1
+{:my-style}
+
+# Header 2
+{:my-style}
+
+{:my-style: #section-title .important .highlight lang="en"}
+```
+
+**ALD references can be combined with additional attributes** in the same IAL. Additional attributes override or extend the ALD:
+
+```markdown
+{:base-style: #main .class1 .class2}
+
+# Heading 1
+{:base-style}
+
+# Heading 2
+{:base-style .class3}
+
+# Heading 3
+{:base-style #override-id}
+
+# Heading 4
+{:base-style .class3 rel="nofollow"}
+```
+
+**Behavior:**
+- **Classes**: Additional classes are appended to the ALD classes
+- **IDs**: If an ID is specified in the IAL, it overrides the ALD's ID
+- **Key-value attributes**: If a key exists in both ALD and IAL, the IAL value overrides the ALD value
+
+For complete documentation with examples, see [Inline Attribute Lists](Inline-Attribute-Lists).
+
+## Table of Contents
+
+Multiple marker formats:
+
+```markdown
+<!--TOC-->              # Basic TOC
+<!--TOC max2 min1-->    # With depth control
+{{TOC}}                 # MMD style
+{{TOC:2-4}}            # With range
+{:toc}                  # Kramdown IAL marker (uses same TOC engine)
+```
+
+Headings with the `.no_toc` class are excluded from the generated TOC:
+
+```markdown
+# Contents
+{:.no_toc}
+
+{:toc}
+```
+
+## Smart Typography
+
+Automatic conversion:
+
+- `"text"` → `"text"` (smart quotes)
+- `'text'` → `'text'` (smart apostrophes)
+- `--` → `–` (en dash)
+- `---` → `—` (em dash)
+- `...` → `…` (ellipsis)
+- `<<` → `«` (left guillemet)
+- `>>` → `»` (right guillemet)
+
+## GitHub Emoji
+
+```markdown
+Success! :rocket: :tada: :sparkles:
+I :heart: Markdown!
+```
+
+Supports 350+ GitHub emoji, converted to Unicode characters.
+
+## Special Markers
+
+**Page breaks:**
+```markdown
+<!--BREAK-->            # HTML comment style
+{::pagebreak /}         # Kramdown style
+```
+
+**Autoscroll pauses:**
+```markdown
+<!--PAUSE:5-->          # Pause for 5 seconds
+```
+
+**End-of-block marker:**
+```markdown
+- Item 1
+
+^
+
+- Item 2
+```
+
+Forces list separation.
+
+## HTML
+
+Raw HTML is supported (when `unsafe` option is enabled, which is default):
+
+```markdown
+<div class="custom">
+  <p>This is raw HTML inside Markdown.</p>
+</div>
+```
+
+### Markdown Inside HTML Blocks
+
+By default, Markdown inside HTML blocks is **not** parsed unless the HTML block contains blank lines. This follows the CommonMark specification:
+
+- **HTML blocks without blank lines**: Content is treated as raw HTML and Markdown is not parsed
+  ```markdown
+  <div>**This is not bold**</div>
+  ```
+  Output: `<div>**This is not bold**</div>`
+
+- **HTML blocks with blank lines**: Content can be parsed as Markdown
+  ```markdown
+  <div>
+
+  **This is bold**
+
+  </div>
+  ```
+  Output: `<div><p><strong>This is bold</strong></p></div>`
+
+To explicitly enable Markdown parsing inside HTML blocks, use the `markdown` attribute (GFM extension):
+
+```markdown
+<div markdown="1">
+## This is a heading
+- List item
+</div>
+```
+
+The `markdown` attribute accepts:
+- `markdown="1"` or `markdown="block"` - Parse block-level Markdown
+- `markdown="span"` - Parse inline Markdown only
+
+### Pandoc Fenced Divs
+
+Apex supports Pandoc's fenced divs extension, which allows you to create HTML `<div>` elements with attributes using a special fence syntax. This feature is available in **unified mode only** and is enabled by default.
+
+**Basic syntax:**
+```markdown
+::::: {#special .sidebar}
+Here is a paragraph.
+
+And another.
+:::::
+```
+
+**Opening fences:**
+- Must contain at least 3 consecutive colons (`:::`)
+- Must have attributes (ID, classes, or custom attributes)
+- Attributes can optionally be followed by another string of consecutive colons
+
+**Closing fences:**
+- Must contain at least 3 consecutive colons (`:::`)
+- No attributes needed
+- Number of colons doesn't need to match the opening fence
+
+**Attributes:**
+Attributes use the same syntax as fenced code blocks:
+- `{#id}` - ID attribute
+- `{.class}` - Class attribute (can have multiple)
+- `key="value"` - Custom attributes with quoted values
+- `key='value'` - Custom attributes with single quotes
+- Single unbraced word is treated as a class name
+
+**Examples:**
+```markdown
+::: {#mydiv .container}
+Content here
+:::
+
+::: sidebar
+Single unbraced word becomes a class
+:::
+
+::::: {#special .warning .important key="value"}
+Div with ID, multiple classes, and custom attribute
+:::::
+
+::::: {#special .sidebar} ::::
+Trailing colons after attributes are allowed
+::::::::::::::::::
+```
+
+**Nested divs:**
+Fenced divs can be nested. Opening fences must have attributes:
+```markdown
+::: Warning ::::::
+This is a warning.
+
+::: Danger
+This is a warning within a warning.
+:::
+::::::::::::::::::
+```
+
+**Block types:**
+By default, fenced divs create `<div>` elements. You can specify different HTML block elements using the `>blocktype` syntax:
+
+```markdown
+::: >aside {.sidebar}
+This creates an <aside> element instead of a <div>.
+:::
+
+::: >article {#post .main}
+This creates an <article> element.
+:::
+
+::: >section {.container}
+This creates a <section> element.
+:::
+```
+
+**Common block types:**
+- `>div` - Default, creates a `<div>` element
+- `>aside` - Creates an `<aside>` element (sidebars, callouts)
+- `>article` - Creates an `<article>` element (main content)
+- `>section` - Creates a `<section>` element (document sections)
+- `>details` - Creates a `<details>` element (collapsible content)
+- `>summary` - Creates a `<summary>` element (for use inside `<details>`)
+
+**Nested block types:**
+You can nest different block types:
+```markdown
+::: >details {.warning} :::
+:::: >summary
+This is a summary
+::::
+This is the content of the details block
+:::
+
+::: >section {.outer}
+Outer section content.
+
+::: >aside {.inner}
+Inner aside content.
+:::
+
+More outer content.
+:::
+```
+
+**Block type with unbraced class:**
+The block type syntax works with unbraced class names:
+```markdown
+::: >aside Warning :::
+Warning content here
+:::
+```
+This creates `<aside class="Warning">...</aside>`.
+
+**Note:** Fenced divs should be separated by blank lines from preceding and following blocks for best results.
+
+**Control:**
+- Fenced divs are enabled by default in unified mode
+- Disable **Settings->Processor->Fenced Divs** to disable fenced divs processing
+
+## Related
+
+- [Modes](Modes) - Which syntax is available in each mode
+- [Header IDs](Header-IDs) - Automatic header ID generation