Printing is not an afterthought
In Letter Builder, printing is the final operational proof that all previous steps worked. A request can look fine, a template can validate, and a letter can exist in the database, but the real test is whether the final output is readable, complete, and in the right language.
How printing works today
- Employees print from My Letters.
- The print action opens a modal asking for the desired language.
- The chosen language is passed to the language-specific print route.
- The printable page opens in a new tab.
Routes involved
/letters/{letter}/print/letters/{language_code}/{letter}/print
Why language-specific printing matters
Multilingual support is only valuable if output can actually be produced in those languages at the end of the process. The language-specific print route makes language choice explicit instead of hidden.
Pre-print checklist
- The letter exists and is approved.
- The requested language exists on the template.
- No required placeholders are still unresolved.
- The company layout and branding are acceptable for the audience.
- The reference number is formatted as expected.
Output edge cases
- Missing values at print time: usually a sign the template or approval flow needs review.
- Language available in the template but awkward in output: this often points to incomplete user translations or poor phrasing in the localized content.
- Reference looks wrong: check company-level reference formatting and sequence rules.
- Layout looks off: inspect the company-level template studio configuration.
Professional print review checklist
- Read the final output once as if you were the recipient.
- Check date and reference formatting visually, not only logically.
- Confirm line breaks and spacing are acceptable for print/PDF output.
- Test at least one localized print for every language you actively support.