How locale variants are used by Author-it


Variant objects are used by Author-it while you are working in the library and when you publish.

Preview variant content in the library while authoring

While working with a book it is good proofing practice to filter the book to view a representation of the variant content that you'll be publishing. Filtering the book prior to publishing gives a good indication of the state of the content. Where variants do not exist, based on the structure in the variant criteria, filtering shows the fall-back content that will be used instead.

You can also compare two variants side-by-side to quickly see the difference between them.

See also: Filtering Objects in the Library Explorer

Publishing with variants

Use variant criteria values during publishing to select the variation of the content to publish for that job. Publishing uses translated content and, in many cases, localized object templates. Like book filtering, if variants do not exist, the filtering for publishing defines the content and objects that will be used to create the output. Localized templates provide many of the special settings and options that are needed by your publishing jobs.

IMPORTANT When publishing a variant book via the primary book (that is, when selecting variant book criteria from the Publish Job Variant Assignment window), the book settings of the primary are always applied in the published output instead of in the variant book settings. To work around this issue, publish the Locale variant book by selecting the Locale variant book itself, and then publishing.

Language pairs are specially configured for localization jobs

The language pairs in Translations are separate from the variant criteria values used in the library for filtering. The language pairs are configured in Translations Settings > Service Providers. They describe the source and target languages for a translation job. For example, creating a localization job for translating source content from US English to Canadian French.