Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

How to localize product's

...

Name (same for descriptions)

This is handled through the alternate locale feature of the Content Manager. Each ProductContent will point to the content for the "default" locale, and that Content can have other

...

contents associated with it as alternate locale

...

contents. There are various reasons for this structure, but the main one is to be able to create a tree of defaults and to use a generic structure rather than one for each place Content is used in the system.
For clarification it goes like this:Product
-> ProductContent
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
-> ContentAssoc (type: ALTERNATE_LOCALE)
-> Content -> DataResource
...

...

Step by step guide (for Product Name, same for descriptions):

  1. In Catalog Manager, go to the Edit product content tab

...

  1. .
  2. Clear the Product Name

...

  1. entry (respectively descriptions) in the "Override Simple Fields". When localizing, these fields must be

...

  1. empty. They have precedence over the localized product name content.
  2. Create a "Product Name content" (actually four entity values get created: ProductContent, Content, DataResource, ElectronicText) in your preferred

...

  1. locales.
  2. In the Content Manager create a new Content (type "Template") with a different locale and a DataResource (Type "Long Text") belonging to

...

  1. the new

...

  1. content

...

  1. , ie :

----Problems:

  • Step 3, New Content no Template type
  • Step 4, ProductContent is not a Content, how can I associate themCan somebody carify?

----I've have it figure out.

  1. Step 3a,
      1. create a new DataResource
      Step 3b,
      1. create a new Content with the dataResourceId set to the DataResource
      created in (3a).
      1. just created
    1. Associate the new content to the product content as "Alternate Locale"
    2. Goto the the content page for the content created in (23), click the Association tab, set the "contendId To" to the contentId created in (3b)
      Attachments:| setting-up-multi-lingual-product.zip | | 495763 bytes | |4b)

    Now, in ecommerce, the product name (respectively descriptions) should be displayed in diffent locales depending on the browser settings.

    An alternative (without UI) is to follow the content of DemoProductI18nData.xml, see also DemoProductCategoriesI18nData.xml