apex-ruby 1.0.17 → 1.0.20

data/ext/apex_ext/apex_src/documentation/shared_styles.css

@@ -1,4 +1,10 @@
-/* Base styles */
+:root {
+  /* border-box width of the fixed sidebar; body offset includes a small gap */
+  --sidebar-width: 250px;
+  --sidebar-offset: 270px;
+}
+
+/* Base styles — override Apex standalone centering (max-width + margin: auto) */
 body {
   -webkit-font-smoothing: antialiased;
   -moz-osx-font-smoothing: grayscale;
@@ -8,6 +14,11 @@ body {
   line-height: 1.65;
   color: #1e293b;
   background-color: #fff;
+  max-width: none;
+  width: auto;
+  margin: 2rem 2rem 2rem var(--sidebar-offset);
+  padding: 0 1rem;
+  box-sizing: border-box;
 }
 
 /* Sidebar / Main TOC - wider on larger screens */
@@ -16,9 +27,10 @@ body {
   position: fixed;
   left: 0;
   top: 0;
-  width: auto;
-  min-width: 180px;
-  max-width: 250px;
+  box-sizing: border-box;
+  width: var(--sidebar-width);
+  min-width: var(--sidebar-width);
+  max-width: var(--sidebar-width);
   height: 100vh;
   overflow-y: auto;
   background: #1e293b;
@@ -27,7 +39,6 @@ body {
   padding: 24px 20px 130px;
   font-size: 14px;
   z-index: 100;
-  margin-right: 1rem;
   box-shadow: 4px 0 24px rgba(0, 0, 0, 0.08);
   transition: transform 0.3s ease;
 }
@@ -76,11 +87,6 @@ body {
   font-weight: 500;
 }
 
-/* Body margin for sidebar */
-body {
-  margin-left: 270px;
-}
-
 /* Hamburger menu button */
 .hamburger-menu {
   display: none;
@@ -96,6 +102,7 @@ body {
   color: rgba(255, 255, 255, 0.9);
   font-size: 20px;
   line-height: 1;
+  box-sizing: border-box;
   width: 44px;
   height: 44px;
   align-items: center;
@@ -113,9 +120,7 @@ body {
 
 /* Move hamburger to the right of the sidebar when menu is open */
 .hamburger-menu.active {
-  left: calc(
-    250px + 12px
-  ); /* Position just to the right of sidebar (max-width 250px + 12px padding) */
+  left: calc(var(--sidebar-width) + 12px);
 }
 
 .hamburger-menu.active {
@@ -211,7 +216,7 @@ body {
 .floating-toc {
   position: fixed;
   top: 0;
-  left: 270px;
+  left: var(--sidebar-offset);
   right: 0;
   z-index: 50;
   opacity: 0;
@@ -637,7 +642,7 @@ ol ul {
   }
 
   body {
-    margin-left: 0;
+    margin: 2rem 1rem;
   }
 
   .floating-toc {

data/ext/apex_ext/apex_src/documentation/transform_for_app.md

@@ -0,0 +1,55 @@
+# Transform Documentation for App Usage
+
+You are transforming Apex documentation from command-line focused to app-focused. The target audience is users of a Markdown processing app (like Marked.app) rather than command-line users.
+
+## Your Task
+
+Transform the provided Markdown documentation to be app-focused by:
+
+1. **Remove all command-line code blocks** - Any code blocks that show `apex` commands should be removed entirely. These commands are run by the app automatically, not by the user.
+
+2. **Replace CLI references with app descriptions** - When documentation mentions command-line flags like `--mode` or `--plugins`, replace them with descriptions of how to access these features in the app's Settings menu.
+
+3. **Rewrite examples for app context** - Instead of showing command-line examples, describe what happens in the app or what settings to configure.
+
+4. **Keep technical content** - Preserve all syntax explanations, feature descriptions, and technical details. Only remove or rewrite the command-line usage parts.
+
+5. **Maintain structure** - Keep all headings, lists, and formatting. Only modify content that relates to command-line usage.
+
+## Examples
+
+**Before (CLI-focused):**
+```bash
+apex document.md --mode gfm --standalone -o output.html
+```
+
+**After (App-focused):**
+Set the processor mode to GFM in **Settings->Processor->Mode** and enable **Settings->Output->Standalone HTML**, then export your document.
+
+**Before:**
+```bash
+apex --combine intro.md chapter1.md chapter2.md | apex --standalone --title "My Book" -o book.html
+```
+
+**After:**
+Use **Settings->Processor->Combine Files** to combine multiple files. The app will automatically process includes and generate standalone HTML with your configured title.
+
+**Before:**
+To enable plugins, use:
+```bash
+apex --plugins input.md
+```
+
+**After:**
+Enable plugins by checking **Settings->Processor->Include Plugins**.
+
+## Guidelines
+
+- Remove code blocks that are purely command-line examples
+- Keep code blocks that show Markdown syntax examples
+- Keep code blocks that show configuration files (YAML, etc.)
+- Replace CLI flag mentions with Settings menu paths
+- Use natural language to describe app workflows instead of command syntax
+- Maintain all technical accuracy about features and syntax
+
+Now transform the following Markdown content:

data/ext/apex_ext/apex_src/escaping-repro.md

@@ -0,0 +1,103 @@
+# Apex: escaping & Unicode repro cases
+
+Use this file in the Apex test harness or `Apex.convert(..., mode: .unified)` to verify behavior and drive fixes.
+
+**Automated coverage:** the same scenarios are exercised in `tests/test_escaping_repro.c`. From the build directory run `./apex_test_runner escaping` (or `escaping_repro`).
+
+**Reference:** [CommonMark spec — Escaping](https://spec.commonmark.org/0.31.2/#backslash-escapes) (inlines), [Images](https://spec.commonmark.org/0.31.2/#images).
+
+---
+
+## 1. Backslash before `[` after `!` (false image opener)
+
+**Intent:** `!\[` should render as literal `!` + `[`, not start an image.
+
+### 1a — Escaped bracket (spec expectation)
+
+```markdown
+Not an image: !\[literal bracket after bang]
+```
+
+**Expected (typical cmark):** Plain text: `Not an image: ![literal bracket after bang]` (no `<img>`, no swallowed tail).
+
+---
+
+### 1b — Same as blog HTML→MD glitch (sentence + link)
+
+```markdown
+I'm so glad you're all here![ Now that the update is slowing down, I will continue.
+```
+
+**Problem:** If `![` is parsed as an image, the parser may consume until a far `]` and drop or merge paragraphs.
+
+**Workaround in consumers:** Insert a separator between `!` and `[` (e.g. narrow no-break space U+202F) so `![` is not contiguous.
+
+---
+
+## 2. Unicode double prime U+2033 (`″`) after ASCII (inches)
+
+**Note:** The inch mark below is **U+2033 DOUBLE PRIME** (not ASCII `0x22`).
+
+```markdown
+Height in parentheses: (He's 5'7″ if you're wondering.) More text after the parens.
+```
+
+**Things to check:**
+
+- Full sentence through `More text after the parens.` appears in HTML.
+- No truncation immediately after `″` or after the word `if`.
+- If output stops early, compare with the same line using ASCII inch mark only:
+
+```markdown
+Height in parentheses: (He's 5'7" if you're wondering.) More text after the parens.
+```
+
+---
+
+## 3. Minimal line — prime only
+
+**U+2033 only:**
+
+```markdown
+X″ Y
+```
+
+**ASCII control:**
+
+```markdown
+X" Y
+```
+
+If `X″ Y` truncates or errors but `X" Y` does not, isolate UTF-8 / lexer / serializer around U+2033.
+
+---
+
+## 4. True image (sanity check)
+
+Should still parse as an image:
+
+```markdown
+![alt text](https://example.com/image.png)
+```
+
+---
+
+## 5. Glued bold after paragraph (optional stress test)
+
+Some pipelines truncate when `**` is glued without a newline:
+
+```markdown
+End of paragraph with a closing paren. (He's 5'7″ if you're wondering.) Hope this helps.**Next section** starts here.
+```
+
+**Check:** Entire line preserved; `**Next section**` renders as strong, not broken emphasis across the whole block.
+
+---
+
+## Summary for implementers
+
+| # | Topic | What to verify / fix |
+|---|--------|----------------------|
+| 1 | `!\[` | Matches CommonMark escape rules in unified mode. |
+| 2 | `″` (U+2033) | No truncation vs ASCII `"` for otherwise identical strings. |
+| 3 | False `![` | Document that unescaped `![` is an image opener; optional lenient mode is non-standard. |

data/ext/apex_ext/apex_src/examples/quick-actions/Markdown to RTF.workflow/Contents/Info.plist

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>CFBundleName</key>
+	<string>Markdown to RTF</string>
+</dict>
+</plist>