w

Author: lenis2000

.claude/commands/mathml-general-exam.md

@@ -93,10 +93,30 @@ Use this entity mapping:
 - Greek letters: α (α), β (β), γ (γ), δ (δ), ε (ε), η (η), θ (θ), λ (λ), μ (μ), ν (ν), π (π), σ (σ), τ (τ), φ (φ), ω (ω), Γ (Γ), Δ (Δ), Θ (Θ), Λ (Λ), Σ (Σ), Φ (Φ), Ω (Ω)
 - Other: ∞ (∞), × (×), ⋅ (⋅), ± (±), ∠ (∠), ⊕ (⊕), ⊗ (⊗)
 
-### Step 6: Save to final location
+### Step 6: Add proper indentation for exam problems
+Use the Python script `scripts/add_exam_indentation.py` to add proper visual indentation:
+
+```bash
+python3 scripts/add_exam_indentation.py /tmp/output_fixed.html /tmp/output_indented.html
+```
+
+This script:
+1. Adds CSS classes for problem structure (`.problem`, `.problem-number`, `.subproblem`)
+2. Adds double line breaks (`<br /><br />`) between main problems (2), (3), (4), etc.
+3. Wraps problem numbers in `<span class="problem-number">` for consistent spacing
+4. Wraps sub-problems (a), (b), (c), etc. in `<span class="subproblem">` tags
+5. Applies 2em left margin to sub-problems for visual indentation
+
+**Why this matters:**
+- Preserves the visual hierarchy and spacing from the PDF
+- Makes it easier to distinguish main problems from sub-parts
+- Adds proper vertical spacing between problems
+- Improves readability and accessibility
+
+### Step 7: Save to final location
 Save the processed HTML file next to the original PDF with the same name but .html extension.
 
-### Step 7: Add accessible HTML link to the generals page
+### Step 8: Add accessible HTML link to the generals page
 After saving the HTML file, you MUST update the link in `graduate/general_exams.md` to follow accessibility best practices:
 
 1. Read the file `graduate/general_exams.md`
@@ -125,6 +145,36 @@ After saving the HTML file, you MUST update the link in `graduate/general_exams.
 - Clearly labeling the PDF as "for printing" to indicate its purpose
 - Using ARIA labels to communicate that PDFs may have accessibility limitations
 
+### Step 9: Final Review - Read Both Files
+After completing all processing steps, you MUST read both the original PDF and the generated HTML file to provide a final quality assessment:
+
+```bash
+# Read both files
+Read <PATH_TO_PDF>
+Read <PATH_TO_HTML>
+```
+
+**Review and report on:**
+1. **Content Accuracy**: Verify that all mathematical expressions, problems, and text from the PDF are correctly represented in the HTML
+2. **MathML Quality**: Confirm that math expressions render correctly as MathML (not SVG or Unicode)
+3. **Accessibility**: Check that all accessibility features are present and correct:
+   - Proper title and H1 heading
+   - Breadcrumb and back button navigation
+   - ARIA labels on math elements
+   - Semantic HTML structure
+4. **Formatting and Spacing**: Ensure the HTML preserves the PDF's visual structure:
+   - Proper spacing between main problems
+   - Sub-problems (a), (b), (c) are visually indented
+   - Problem hierarchy is clear and readable
+5. **Completeness**: Verify nothing was lost or corrupted during conversion
+
+**Provide a concise summary stating:**
+- ✓ What looks correct
+- ⚠️ Any issues found (and fix them if possible)
+- Overall assessment: "Ready for production" or "Needs fixes"
+
+This final human-in-the-loop check ensures quality before the files go live.
+
 ## Important Notes
 - Do NOT use the direct .html download from Mathpix - it uses MathJax SVG rendering
 - Always use the tex.zip → pandoc → post-processing pipeline
@@ -146,3 +196,4 @@ The output HTML must have:
 ✓ Valid, well-formed HTML5 document with proper semantic structure
 ✓ HTML file saved next to the PDF with .html extension
 ✓ Link in graduate/general_exams.md updated with HTML as primary, PDF as secondary with aria-label
+✓ Both PDF and HTML reviewed side-by-side with final quality assessment provided