Convert Atrise ToHTML: A Complete How-To Guide

Troubleshooting Atrise ToHTML: Common Issues & Fixes

1. Output HTML looks broken or malformed

• Cause: Unsupported input formatting or corrupted RTF source.
• Fix: Open the source document in a rich-text editor (Word, WordPad) and remove unusual styles or embedded objects; save as plain RTF and re-run conversion. If specific elements break, delete them and re-add using basic formatting.

2. Missing images after conversion

• Cause: Images embedded as linked resources, unsupported formats, or path issues.
• Fix: Ensure images are embedded (not linked) in the source RTF; convert images to common formats (PNG/JPEG); check output folder for an images subfolder and confirm relative paths in the produced HTML.

3. Incorrect character encoding / garbled text

• Cause: Mismatch between source encoding and output (UTF‑8 vs ANSI).
• Fix: Force UTF‑8 output in Atrise ToHTML settings if available, or save the source using Unicode encoding before conversion. Verify HTML declares correct charset: .

4. Styles lost or inconsistent CSS

• Cause: Complex or proprietary styles in the source that Atrise doesn’t map to CSS.
• Fix: Export with minimal inline styling, then apply a custom stylesheet: convert basic structure only and use an external CSS to restore appearance. Alternatively, simplify styles in the source document.

5. Tables render incorrectly or split across pages

• Cause: Complex nested tables or page-break markers in RTF.
• Fix: Simplify table structure (avoid nesting), remove manual page breaks, and check table HTML for correct ,

6. Links not preserved or broken

• Cause: Hyperlinks stored in an unsupported format or using relative paths that change.
• Fix: Ensure hyperlinks are proper URLs in the source RTF (http/https), not fields or bookmarks; after conversion, validate and correct href attributes.

7. Conversion crashes or freezes

• Cause: Very large documents, corrupted RTF, or memory limitations.
• Fix: Split the document into smaller parts and convert separately; update to the latest Atrise ToHTML version; run on a machine with more memory; check logs for error details.

8. Output uses inline styles but you want semantic HTML

• Cause: Converter prioritizes visual fidelity over semantic structure.
• Fix: Use the converter to produce basic structural HTML, then post-process: run a cleanup script or use an HTML tidy tool to refactor inline styles into classes and external CSS.

9. Fonts not matching on web

• Cause: Local fonts used in source aren’t available on the web.
• Fix: Use web-safe fonts or include webfonts (Google Fonts or self-hosted) and update CSS font-family accordingly.

10. Unexpected whitespace or line breaks

• Cause: RTF paragraph and line-break markers convert to
  or extra

  tags.

• Fix: Normalize paragraphs in the source (remove manual breaks), or post-process HTML to collapse redundant tags and control spacing via CSS (margin, line-height).

Quick troubleshooting checklist

1. Open the RTF in an editor; simplify formatting.
2. Ensure images are embedded and links are full URLs.
3. Save source with UTF‑8/Unicode encoding.
4. Update Atrise ToHTML to the latest version.
5. Convert a small test file to isolate the issue.
6. Post-process HTML with tidy or custom scripts when needed.

If you want, I can give step-by-step instructions for any specific issue above—tell me which one.