Skip to content
docs Search these pages /

Résumé language

Understand how ATSReady keeps each résumé language separate from interface language and how export language is chosen when translated versions exist.

Languages and market · about 1 minute

On this page
  1. Where résumé language is decided
  2. What export selection does
  3. What changing résumé language does not do
  4. Market and language are separate
  5. Related pages

Each résumé has its own language context. It is not just a reflection of the language you read the app in.

Where résumé language is decided

ATSReady uses the language already set on the résumé first, then falls back to market defaults when needed.

The control is not in Preferences. It sits with the market settings for that document, which open over the résumé itself.

The market and language controls open over a résumé preview, with the language selector among them.
The language controls sit over the preview rather than in the editor form, which is why a document that reads correctly while you are editing it can still leave in a different language than you expected.

What export selection does

When ATSReady decides which résumé language variant to render for export, it uses this order:

  1. an explicit export-language pick
  2. your current UI language, if that résumé already has a translation in it
  3. the résumé's own language

What changing résumé language does not do

Changing the résumé language setting does not translate your text by itself. For translated copies, use content translation.

Market and language are separate

Target market controls market presentation rules such as page size and document conventions. It is not the same decision as the viewer's current UI language.