The preferred means of Author-it Localization has changed from the use of Windows-based software with multiple Jet or SQL target libraries to a web-based system that functions with a single SQL library, based on variants.
Localized content is managed from multiple target libraries.
All localized content is managed in a single library.
Content is copied from the source library into target libraries, and then localized.
Variants are used for managing the localized content, and there is no longer a need to lock / unlock objects.
Manage the process in <ALM>.
Manage the process in Localize.
Only one language at a time can be viewed in Author and Contribute.
All languages can be seen side by side.
Functions with both Jet and SQL databases.
Functions with SQL databases only (users cannot log in to Jet, and will need to Export the Jet database to SQL to function with Localize).
<ALM> uses multiple target libraries:
When the initial <ALM> was developed, software limitations at the time made it necessary to use a separate target library for each language translation.
With <ALM>, the source content in the main library is copied to all target libraries, and localizations are then conducted on the copied content per target library.
Localization tasks between target libraries and translators are handled from the <ALM> interface.
Localize Single library:
With the introduction of Author-it Variants, it has become possible, and preferable, to use a single variant-based library.
Each localization is a variant of the primary (source) content. To use the software effectively, you need to understand Variants and associated functionality.
You can use the Localization Migration Plug-in to migrate content from your existing target libraries to your Author-it source library.
Once functional, you can manage all localization life-cycle tasks from Localize's browser interface.