Document translation that respects the layout instead of wrecking it.
The value is not just translated text. It's getting a file back that still looks professional, still reads properly, and does not force someone to spend an afternoon repairing tables, spacing, and RTL typography.
Built around the failure case most tools ignore: complex documents that have to survive translation looking intact
Right-to-left languages get deliberate handling instead of generic post-processing
Delivered as a pay-per-page product, which makes it easy to use without a subscription ritual
Document translation tools translate text. They don't translate documents. The layout — tables, headers, spacing, page breaks, RTL typography — gets wrecked in the process. The last mile of rebuilding the layout after translation takes longer than the translation itself.
Polyglot is built around the failure case most tools ignore: complex documents that have to survive translation looking intact. The system preserves layout structure through the translation pipeline, handles RTL languages with deliberate typographic care, and delivers as a pay-per-page product so there's no subscription ritual.
Preserving document layout through translation requires understanding the document's structure before translating — Pandoc handles the heavy lifting, but pre- and post-processing required custom pipeline work
RTL languages expand and contract differently than LTR — table cells, headers, and text blocks all need to reflow without breaking visual integrity
Pay-per-page billing means accurate page count estimation, graceful partial failure handling, and enough preview that users trust the result before paying
Document translation that preserves professionalism. Users get back a file that still looks like the original, just in a different language. RTL handling is deliberate, not an afterthought.