sepehr
526c87348f
Translation quality & format preservation: - Word: merge adjacent same-format runs into one unit (sentence-level coherence like inline-tag handling); translate comments/balloons; dedupe textbox collection (was translated twice); RTL no longer overrides center/justify alignment; CJK/Arabic font hints (eastAsia/cs) - PPTX: chart translations now actually reach the output file (ChartPart.blob is read-only — rewrite chart XML in the saved ZIP); CJK typeface hints (a:ea) - Excel: sheet renames no longer break references — rewrite cell formulas (3D/quoted), defined names, data validations, cond. formats - PDF: bold/italic honored (hebo/heit/hebi); table cells never merge; unchanged blocks left untouched (typography preserved, fixes duplicate hyperlinks); attempted/changed stats + route gate now cover PDF; CJK font paths; scanned PDFs via Mistral OCR (detection + admin settings) Features: - formality param (formal/informal) + automatic regional-variant prompts - output_mode=bilingual docx (source above translation) - per-user translation memory on Redis (falls back to LRU), context-hashed - QA report + 0-100 confidence score in job status; L0 on by default - OpenAI-compatible providers: whole chunk in ONE numbered-JSON request (~15x fewer calls) with per-item fallback; base prompt always present (custom prompt no longer replaces translation instructions) Infra & marketing alignment: - plan-based engine gating + vision gating (closes paid-engine leak); /providers/available filtered per plan; 107 languages exposed - zh-CN/zh-TW validation fixed; libmagic disabled on Windows (native crash) - admin: Mistral OCR settings + engine status dashboard; httpx<0.28 pin (TestClient breakage); Prometheus test fixture fixed - marketing docs aligned with code (PDF+OCR, retention, engines, pricing) - security: .env.ionos/.env.production/provider_settings.json removed Tests: 1173 passed / 0 failed (6 network tests deselected: free Google endpoint temporarily blocked from this machine)
4.2 KiB
Reddit — 3 Posts de Lancement
Statut : prêts à publier (Phase 2). Adapter le ton par subreddit. Pas de lien brut dans le 1er post sur r/SideProject (shadowban) — lien en commentaire.
1. r/SideProject
Titre : I built a tool that translates Excel/Word/PowerPoint without destroying the formatting. Free plan = 2 docs/mo.
Corps :
Hi all — I've been building Office Translator for a while and I'm launching it this week.
The problem: every translation tool I tried (Google, DeepL) flattens your file into plain text. Merged cells gone, formulas replaced by their computed values, slide layouts destroyed. You end up spending more time fixing the format than the translation saved you.
What I did instead: the pipeline parses the document structure, extracts only the translatable content, translates it, and writes it back into the same structure. Merges, formulas, fonts, borders, headers/footers, table styles — untouched. Text inside images is handled by vision models.
Tech: FastAPI (async), openpyxl / python-docx / python-pptx, 7 translation engines the user picks per document (Google, DeepL, Google Cloud, OpenRouter éco & premium, OpenAI, Grok/xAI), Stripe billing, Docker/Postgres/Redis.
Pricing: Free (2 docs/mo, no card) → Starter €9 → Pro €19 → Business €49 (API included).
I'd love feedback from anyone who deals with international documents. What's the nastiest format you've tried to translate?
(Link in comments to avoid the filter.)
Commentaire n°1 (lien) :
Here's the landing page: [URL]. Free plan, no card. The /docs page has the full API reference if you want to poke at the API.
2. r/translator
Titre : We built a document translator that preserves formatting — curious how you'd use it (or wouldn't)
Corps :
Hi, I'm the dev behind Office Translator (Wordly.art). Before I pitch anything: we know translators are the ones who actually feel the pain when a machine mangles a layout, so I'd rather ask than sell.
The tool translates .xlsx / .docx / .pptx in place — structure, formulas, tables and styles are preserved — and supports custom glossaries, which is the feature I'd value your opinion on most:
- Is glossary-based consistency (e.g. a fixed HVAC or legal term list) actually useful to you, or do you already solve this differently?
- For which document types is the format preservation worth paying for, vs. where a human review still beats any tool?
- What would make you trust an output enough to skip a full re-read? (confidence scores? diff view? per-segment override?)
It's aimed at agencies and in-house teams as a first pass to cut turnaround — not to replace the translator. I'd genuinely like to hear what would make it a tool you'd recommend to a colleague.
⚠️ Ce subreddit est hostile au self-promo : publier en tant que dev transparent, répondre à chaque commentaire, jamais de lien dans le post.
3. r/smallbusiness
Titre : How do you translate client documents (Excel/Word/PowerPoint) without losing the formatting? We built a tool for this.
Corps :
Running a business that works internationally means a lot of documents that need translating — pricing sheets, contracts, slide decks, training files.
The usual options all hurt somewhere:
- Human translators: great quality, 50–100× the cost and a multi-day turnaround
- Google/DeepL: cheap and fast, but they flatten the file — merged cells, formulas, slide layouts get destroyed, so someone has to rebuild the document
We built Office Translator to kill that middle step: it translates the document in place and gives you back a file that looks like it was written in the target language from the start. You pick the engine (7 options, from free Google to premium LLMs), and you can lock your company terminology with a custom glossary so "unité de froid" is never suddenly "cold unit".
Free plan: 2 documents/month, no card. From €9/mo after that. Uploads are deleted after 30 minutes and results within 2 hours.
If you handle international documents, what's your current workflow and where does it break? Curious what I'm missing.