Publish Setup publish-setup

Adobe Dynamic Media Classic servers deliver assets by default to websites or applications, as determined by the Publish Setup page settings. If no setting is specified, the Adobe Dynamic Media Classic server delivers an asset according to a default setting on a Publish Setup page. For example, a request to deliver an image that does not include a resolution attribute yields an image with the Default Object Resolution setting on the Image Server page.

Administrators can change the default settings on the Image Server, Image Renderer, and Vignette pages to establish default settings for delivering assets from servers.

To open the pages of Publish Setup, go to Setup > Application Setup > Publish Setup.

Image Server image-server

The Image Server page establishes default settings for delivering images from Image Servers. Settings are available in these five categories (see the Image Server page itself for detailed descriptions of the settings).

Change these settings only with the assistance of an Adobe Dynamic Media Classic support team member.

Considerations when setting up localization of assets considerations-when-setting-up-localization-of-assets

A common way to use Adobe Dynamic Media Classic is to manage the product imagery on eCommerce websites. International businesses face the challenge that assets for similar products vary by region. Usually the differences are for a few components of the media. Managing such differences by copying all assets for each country and overwriting the differences is a complex task and is inconsistent with the single primary asset principle. Differences for assets can range from country-specific videos with different audio tracks to subtle but important differences in a power cord that is used with the product. Adobe Dynamic Media Classic uses a basic search mechanism. You define an order of asset suffixes in which the Image Server looks, starting from the required locale.

How assets are localized

The locale for an IS (Image Serving) request is identified with the following IS/IR (Image Rendering) command:

locale=

This command accepts a locale id (locId) string that is not case-sensitive. The locale id is typically a 2-6 character string composed of letters and “_.”

IS supports arbitrary printable ASCII strings. The locale= command applies globally to the entire request, including nested requests, templates, and layers. Multiple locales per request, such as a different locale for each layer, are not supported. However, it is conceivable to allow explicit overrides in nested requests.

If locale= is not specified, attribute::DefaultLocale is passed to the translation engines. Limited input validation is applied to the locale= value. Empty locale= values are permitted. Because locale= has a global scope, the main catalog provides attribute::DefaultLocale for the entire request.

Some of the benefits of using locale= and attribute::DefaultLocale include the following:

Application scenarios

Implement asset localization

Adobe Dynamic Media Classic and Image Serving have an interface that allows for the localization of images and static content.

Without localization, an Image Server URL looks like the following:

https://server/is/image/company/image

With localization, an Image Server URL adds the locale= parameter to the path, as in the following:

https://server/is/image/company/image?locale=de_DE

On receipt of the http call by the Image Server, the locale= parameter is parsed through the localeMap field found in Setup > Application Setup > Publish Setup > Image Server > Localization Support group.

The Locale Map field contains a list of entries that are separated using the pipe symbol (|).

Each entry consists of a comma-separated list of values. The first value is the search value that is passed through the locale= parameter. The remaining values are suffix/replacement values that are then tried until one results in an existing image.

Whether a suffix value or a replacement value is applied depends on the Global Locale setting in Setup > Application Setup > Publish Setup > Image Server > Localization Support group.

Suffix example:

Replacement example:

If no locale is defined in the URL, the Image Server takes the DefaultLocale, if it is defined, and applies it to the URL.

If an unknown or empty locale parameter is supplied with locale=, then the localeMap is scanned for the empty value “starting with.” It is important to have a default locale applied for unknown locales.

About defaultImage

The Image Server tries the options for the requested locale, one after the other. If no match is found, the locale options are applied to defaultImage, and the matching version is returned. Therefore, either each locale must include an option for the image without localization, or localized defaultImage versions are made available in Adobe Dynamic Media Classic.

Scenarios for finding the localeMap

Suppose you want to support the following locales:

en, en_us, en_uk, de, de_at, de_de, fr

You map these locales to the suffixes _E (English), _G (German), and _F (French). For all examples, the generic input image ID is myImg.

Standard behavior for finding the localeMap

The locale IDs are mapped to their corresponding suffixes. If no locale-specific ID is found in the catalog, the generic ID is tried. Note the empty locSuffix values that map to the generic ID.

attribute::LocaleMap=en,_E,|en_us,_E,|en_uk,_E,|fr,_F,|de,_D,|de_at,_D,|de_de,_D,

Finding the localeMap when the locale is unknown

You can map unknown locales to specific IDs or to generic IDs. For example, you can map unknown locales to the English IDs, or if they do not exist, to the generic IDs.

attribute::LocaleMap=en,_E,|en_us,_E,|en_uk,_E,|fr,_F,|de,_D,|de_at,_D,|de_de,_D,|,_E,

Use a dedicated locSuffix for unknown locales and force to the default image if no _U exists, as in the following:

attribute::LocaleMap=en,_E,|en_us,_E,|en_uk,_E,|fr,_F,|de,_D,|de_at,_D,|de_de,_D,|,U

Or, you can map directly to the generic ID, as in the following:

attribute::LocaleMap=en,_E,|en_us,_E,|en_uk,_E,|fr,_F,|de,_D,|de_at,_D,|de_de,_D,|,

Find the localeMap using a multi-tiered lookup

Group locales to address regional standards like skin exposure. You can do this using a multi-tiered lookup.

For example, suppose you want to support collections for Western and Middle Eastern use. Both collections are based on the generic image collection, and both add or modify some images. Both collections are then further refined for specific locales. For example, m1, m2 for two Middle Eastern variants, and w1, w2 and w3 for three Western locales, except that images are shared for w1 and w3. Unknown locales are mapped only to the generic collection and do not have access to locale-specific images. The following is the map:

attribute::LocaleMap=w1,-W,|w2,-W2,-W,|w3,-W,|m1,-M1,-M,|m2,-M2,-M,|,

Find the localeMap by searching for specific IDs

Some image-naming conventions do not support generic image IDs. The generic IDs from the request must be mapped to a specific ID in the catalog. However, there are instances where the exact specific ID is not known.

Using the first example as a basis, images for all languages have the suffixes _1, _2, or _3. Images specific to French locales have the suffixes _22 or _23. And images that are specific to German locales have the suffixes _470 or _480.

attribute::LocaleMap=,_1,_2,_3|fr,_22,_23,_1,_2,_3|de,_470,_480,_1,_2,_3|de_at,_470,_480,_1,_2,_3|de_de,_470,_480,_1,_2,_3

Important considerations when implementing localization support

Image Renderer image-renderer

The Image Renderer page establishes default settings for delivering Image Sets from image-rendering servers. Settings are available in these five categories (see the Image Server page itself for detailed descriptions of the settings):

Vignette vignette

The Vignette page offers settings for establishing the default appearance of vignettes (see the page itself for detailed descriptions of options).