Troubleshooting Guide¶
Common issues and solutions for NormaDocs.
Pandoc Not Found¶
Symptom: Error: Pandoc no está instalado en el sistema
NormaDocs will now suggest the correct install command automatically based on your OS. Solutions:
# macOS
brew install pandoc
# Debian/Ubuntu
sudo apt install pandoc
# Windows
choco install pandoc
# or download from https://pandoc.org/installing.html
Verify installation:
Unsupported Citation Style¶
Symptom: Error: Estilo de citación no soportado: '<style>'. Estilos disponibles: apa, apa7, apa7estudiante, icontec, ieee.
Solution:
Use one of the supported values with --style:
normadocs input.md --style apa7estudiante
normadocs input.md --style apa
normadocs input.md --style icontec
normadocs input.md --style ieee
Unsupported Output Format¶
Symptom: Error: Formato de salida no soportado: '<format>'. Formatos disponibles: docx, pdf, all.
Solution:
Use one of the supported values with --format:
APA Validation Fails¶
Symptom: The command generates a DOCX/PDF but exits with a validation
error or the report says FAILED.
Solution: Read the first structure or cover_page issues in the APA
report. The strict academic-report profile requires a cover, repeated title,
Introduction, development, Conclusions and References in that order. New
0.3.x checks also flag stray blank lines (blank_lines), unindented block
quotes, non-Title-Case cover titles and uncited references. Fix the
Markdown headings and metadata, then regenerate; do not patch the generated
DOCX manually.
To inspect the report without terminal output:
Use --no-verify-apa only when the selected output is not an APA submission.
PDF Generation Fails¶
Symptom: PDF is not generated, only DOCX
Solution: NormaDocs supports two PDF backends:
-
LibreOffice (recommended):
-
WeasyPrint (alternative):
Bibliography Not Working¶
Symptom: Citations appear as [?] in the output
Solution:
1. Ensure your .bib file is valid BibTeX format
2. Use the correct path to the CSL file
3. Check that citations in Markdown use correct keys:
Encoding Issues¶
Symptom: Special characters appear wrong in output
Solution: - Ensure input files are UTF-8 encoded - Don't use "smart quotes" in Markdown source
Common Error Messages¶
| Error | Cause | Solution |
|---|---|---|
FileNotFoundError |
Input file doesn't exist | Check file path |
Pandoc conversion failed |
Pandoc error | Check Markdown syntax |
LanguageTool server JAR not found |
LT not installed | Install Java + LanguageTool |
Estilo de citación no soportado |
Invalid --style value |
Use apa7estudiante, apa, icontec, or ieee |
Formato de salida no soportado |
Invalid --format value |
Use docx, pdf, or all |
Code images not rendering¶
Symptom: {code} blocks stay as text instead of images.
Solution: Install the extra plus the renderer: pip install "normadocs[codeimage]" and wkhtmltopdf on PATH. Without them the code is kept as text (graceful degradation, not an error).
Getting Help¶
If you encounter an issue not covered here:
1. Check the GitHub Issues
2. Include a minimal Markdown reproduction and the selected --style
3. Include output of normadocs --help, pandoc --version, and the APA report
when validation is involved