Yibelin
PDF translation with layout preservation
Over the past year, I've been building a PDF translation tool and talking with users who regularly translate papers, manuals, and scanned documents.
One thing surprised me:
Translation quality was rarely the biggest complaint.Most frustrations came after the translation was finished.
For example:
- Two-column academic papers often lose their reading order.
- Tables become misaligned or unreadable.
- Scanned PDFs need OCR before translation can even begin.
- Users still need to fix terminology, labels, numbers, or awkward paragraphs before the document is actually usable.
The more feedback I received, the more it felt like a document reconstruction problem rather than a translation problem.
That observation led me to build a PDF translator that focuses less on raw translation quality and more on making translated documents usable.
The main areas I've been working on are:
- Preserving layout as much as possible
- OCR for scanned PDFs
- Paragraph-level editing before export
The editing feature turned out to be much more important than I originally expected.
Many translation tools stop at "translation complete." In practice, people often want one more step: reviewing and correcting the translated content before generating the final document.
Right now, the product seems most useful for:
- Academic papers, especially two-column PDFs
- Scanned documents that cannot be copied as text
- Manuals and technical documents with structured layouts and tables
Some early signals so far:
- Core landing pages have started getting indexed by Google
- We're seeing users upload real papers and documents instead of test files
- Some users are paying to export the final translated PDFs
I'm still very much in the validation stage and trying to understand where the strongest demand exists.
I'd love to hear from people who regularly work with PDFs:
1. What type of PDF tends to break most often after translation?
2. Which matters most to you: layout preservation, terminology editing, OCR, speed, or pricing?
3. If you only translate PDFs occasionally, would you prefer pay-per-download over a subscription?
If there's interest, I'm happy to share screenshots of:
- Two-column paper translation
- OCR results for scanned PDFs
- The paragraph editing workflow after translation
If people are interested, I can share the product link and a few examples in the comments.
2 Comments
The real shift here isn’t translation quality—it’s the realization that users are actually paying for post-translation usability, not translation itself.
Once layout breaks, tables drift, and reading order collapses, the problem stops being linguistic and becomes structural. The real value is in preserving document intent after transformation, not just converting text between languages.
Yes , exactly