Best practices to translate assets best-practices-for-translating-assets-efficiently

Adobe Experience Manager Assets supports multilingual workflows to translate binaries, metadata, and tags for digital assets into multiple locales and to manage the translated assets. For details, see Multilingual Assets.

For efficient management of assets to ensure that different translated versions stay synchronized, create language copies of assets before running translation workflows.

A language copy of an asset or a group of assets is a language sibling (or a version of the assets in a cognate language) with a similar content hierarchy.

Each language copy is an independent asset. Therefore, translating assets into multiple locales can drastically increase the size of the CRX repository. For example, translating assets with a combined size of 10 GB into two languages can increase the repository size by approximately 20 GB (10 GB for each language).

Asset binaries occupy much larger storage space compared to metadata and tags. Therefore, if translating metadata and tags only serves your purpose, omit to translate the binaries. You can retain the original copy of the binaries in the repository for association with metadata and tags translated to different locales. Maintaining a single copy of binaries, instead of multiple translated versions, minimizes the impact on repository size.

File Data Store and Amazon S3 Data Store provide a storage infrastructure that is best suited for these scenarios. These storage repositories store a single copy of asset binaries (including renditions) that can be shared by metadata and tags in multiple locales. Therefore, creating asset language copies and translating metadata and tags does not affect repository size.

You can also make a few configuration changes to a couple of workflows and the translation integration framework to further streamline the process.