Skip to content
KRAUSMEDIA

Full-stack localization

One contract. The whole job done.

Project-scope localization for end clients — from source file analysis through terminology, translation, QA, and delivery in whatever format your CMS, repo, or workflow expects. Czech and Slovak in-house; other pairs sourced from my vetted network.

Request a Quote

What I localize

Software UI Marketing websites Technical manuals Help center articles In-product onboarding Email campaigns Subtitles & dubbing scripts Clinical trial documentation Legal contracts e-Learning content Game dialog Investor communications

How a project actually goes

  1. 1

    Scoping

    You send me your source files. I analyze them (word count, segment count, repetition rate, format complexity, any source-side issues I can spot from years of reading these files). Within two business hours you have a quote, a delivery date, and a list of any clarifying questions.

  2. 2

    Terminology setup

    Before translation begins, I build or extend your glossary. If you don't have one, I extract candidate terms from your source content and propose a starter glossary for your sign-off. This is the single highest-leverage step in any project — and the one most often skipped.

  3. 3

    Translation

    Czech and Slovak: my hands. Other pairs: handed to a vetted senior linguist from my network, with my QA. CAT tool of your choice — memoQ, Trados, Smartling, Phrase, Smartcat. I work in your environment, not mine.

  4. 4

    QA

    Two passes minimum: linguistic (terminology, register, locale conventions) and technical (tags, placeholders, length constraints, encoding). I run automated checks AND read every segment with my own eyes.

  5. 5

    Delivery

    Whatever format you need. Translated XLIFF or TMX back to your TMS. DOCX or PDF for review-friendly delivery. Direct push to GitHub if you prefer. Plus: the assets I built along the way — updated TM, glossary, style notes — handed to you for your next project.

Tools I work in fluently

CAT tools: memoQ, SDL Trados Studio, Smartling, Memsource / Phrase, Smartcat, Across, Transit XV, Wordfast, Passolo. Five years of active Smartling project experience.

File formats: XLIFF 1.2 and 2.0, TMX 1.4, TBX, DOCX/XLSX/PPTX, IDML (InDesign), HTML, JSON, .properties, .po (gettext), Markdown, SRT, VTT, EBU-STL, .stl.

Automation: Python scripts for batch file conversion, segmentation rule enforcement, terminology cross-validation, QA automation. When standard CAT tool features fall short, I script around them.

What 30,000 words across four markets looks like

A realistic timeline for a 30k-word marketing website translation, EN → CS / SK / DE / FR:

Week 1

Scoping, source review, glossary build, kickoff with your team

Week 2

Czech and Slovak first-pass translation (mine), German and French sourcing & briefing

Week 3

All-language first-pass complete, internal QA, your review

Week 4

Revisions integrated, final QA, delivery, glossary handover

Faster is possible (and frequently happens). Slower is sometimes wiser. I'll be candid about what's realistic when I quote.

Request a Quote Describe your project →