Export Options

This guide explains how to export content in Notez to PDF or Word (.docx), what formatting is supported, plus common questions.

1. Overview

When you need to share, archive, submit, or hand over your work, you can export the current document as an offline file. Currently supported:

• PDF: good for distribution, printing, formal archiving
• Word (.docx): good for continued collaboration in traditional office suites

2. Where to Find It

1. Open any document in the editor
2. In the left sidebar locate the “Document” section
3. Click the “More” (three dots) icon
4. Choose:
   • Export as PDF
   • Export as Word

(If you do not see the options, ensure the document has editable content.)

3. Supported Content Types

The export renderer currently covers:

• Heading levels (# ~ ######)
• Paragraphs / line breaks
• Bold, italic, strikethrough, inline code
• Ordered / unordered lists
• Blockquotes
• Code blocks (with syntax highlighting; theme follows current in‑app style)
• Tables (wide tables may scroll horizontally or be scaled)
• Images (local or remote URL; local images must have finished loading)
• Horizontal rules
  (Unsupported / partially supported elements may gracefully fall back to plain text or simpler styling.)

4. Generic Export Steps

1. Open the target document
2. Click the File area MoreHorizontal menu in the sidebar
3. Pick a format (PDF / Word)
4. Choose a save path
5. Wait for processing (time depends on length and image count)
6. Open the file in your system file manager

5. PDF Notes

• Pagination: automatic continuous flow
• Fonts: prefers available system CJK / Latin fonts; falls back to default serif/sans
• Code blocks: monospaced; long lines may wrap
• Images: embedded at original size; oversized images scale to page width
• Best for: read‑only distribution / formal archiving / immutable records

6. Word (.docx) Notes

• Structure: headings map to Word Heading 1–6 styles (TOC friendly)
• Lists, tables, blockquotes remain editable
• Code blocks: monospaced paragraphs / styled blocks (syntax colors may simplify)
• Images: embedded inline
• Best for: further collaboration / reformatting / editorial review

7. Style Consistency

Element	PDF	Word
Heading levels	Fixed styling	Editable styles
Code highlighting	Preserved	May downgrade
Tables	Wide tables auto-scale	Fully editable
Images	Fit to page width	Inline replaceable
Links	Clickable (viewer dependent)	Clickable

8. Images & Assets

• Remote images: fetched at export time; ensure network availability
• Local images: must be properly inserted (avoid temporary paths)
• Video / audio not inlined yet (shown as links)

9. Fonts & CJK Support

• If font substitution alters layout, future versions will allow explicit font selection (planned)
• To fix tofu / missing glyphs: ensure common CJK fonts (e.g., PingFang, Source Han Sans) are installed

10. FAQ

Q: Export button disabled / missing?
A: No content or not in an editable document. Open or create a document first.

Q: Table squashed in PDF?
A: Reduce column count/width or split into multiple tables; current scaling prioritizes preventing overflow.

Q: Long code lines wrap badly?
A: A “horizontal scroll” option is planned; meanwhile manually split lines.

Q: Image not showing?
A: Check path correctness / remote accessibility / that it fully loaded before export.

Q: Word styles differ from in‑app styles?
A: Word applies its native style system; style templates will be added later.

11. Best Practices

• Preview before export to remove placeholders
• Split very large documents (>50 pages) into sections to reduce failure risk
• For code‑heavy docs prefer PDF (higher fidelity)
• For formal submissions keep both PDF + DOCX

12. Roadmap (Planned)

• Custom header/footer
• Cover page & auto-generated TOC
• Batch / merged export
• Optional sensitive data redaction
• Theme selection (e.g., dark → light conversion)

If you encounter unsupported scenarios, please send feedback so we can improve.
Thanks for