Skip to content
Civic TranslationSan Francisco

Services

Formatting and layout.


A translation that breaks the form it sits in is not finished. We set the translated text back into your layout so the file prints, posts, and gets filled in the way the English does.

Expansion

Translated text does not fit.

Spanish runs 20 to 25 percent longer than the same English. On a flowing page nobody notices. On a form, a sign, or a wallet card it is the whole problem.

Field labels wrap to a second line and push the boxes out of alignment. A table column overflows into its neighbor. A signature block falls onto a second page, so the form now prints on 3 sheets instead of 2. A sign that was legible from the queue gets set 2 points smaller to make room.

We reflow the translated text inside your existing grid, adjust leading and column widths before touching type size, and resize fields rather than shrinking the face below the point where it can be read across a counter. Where the text genuinely will not fit, we say so and propose shorter wording that holds the meaning, rather than quietly dropping a line.

If the form is still being drafted, the cheapest fix is upstream: draw the fields to hold the longest language you publish in, and every later translation drops into a layout that already has room for it.

Scripts

Where the typesetting rules change.

Several of the languages we work in do not set like Latin text, and each one fails in its own way when a file is built as though it does.

Chinese and Korean
CJK text wraps between characters rather than at spaces, and the line-break rules bar certain characters from the start or end of a line: a line cannot open with a closing bracket or a full stop, or end on an opening bracket. Software that ignores them produces text a reader registers as wrong before working out why. We set the rules in the file rather than nudging lines by hand, so the layout survives the next edit.
Arabic
Right-to-left is not a text setting; the page mirrors. Reading order, column order, table columns, list indents, form field order, and directional arrows all flip, while figures and embedded Latin terms do not. The usual failure is right-to-left text dropped into a left-to-right frame: every word correct, the page unusable.
Vietnamese
Vietnamese stacks a tone mark over a vowel that often already carries a diacritic. Tight leading clips the marks, and fonts with incomplete Latin Extended coverage drop or substitute them — usually invisible on screen and obvious once printed. We check the font covers the full character set, embed it in the PDF, and keep the file in UTF-8 from intake through delivery.

Forms and delivery

Forms, tables, and what ships.

Forms are the hard case, because they get filled in by hand. We hold checkbox and label alignment, tab stops and dotted leaders, box heights, and the page-for-page correspondence between the English and the translated version, so a clerk can read one against the other and a resident signs the line they were meant to sign.

Tables keep their structure: figures stay in their columns and stay decimal-aligned, units are carried over rather than converted, and date formats follow the convention of the reading audience instead of being left in the source form.

Delivered

Print-ready
A PDF with fonts embedded, at the trim, bleed, and marks your printer asked for.
Editable
The working file back in its own format — an InDesign package, or the Word document with its styles intact — so your designer can revise it without rebuilding it.
Web-ready
HTML or XLIFF with language and direction attributes set, so the page announces the right language to a screen reader and wraps correctly on a phone.

Send the layout, not just the text.

Attach the working file — InDesign, Word, or the HTML — and we will quote the translation and the layout work together.