Localize Packages

Some CMS Packages - for example, Newsletter, News or Blog - come "localization-ready". Their data types are localized and strings are kept in the resource files. In this case, to localize the package-related content, you need to translate data as well as translate the strings in localized versions of the resource files.

If the package is not "localization-ready" (for example, strings are hard-coded in XSLT functions that appear on the frontend), or if you are creating your own package, you need to make sure to:

• Localize data types whose data appears on the frontend
• Keep all the strings used as labels on forms in the resource files
  
• Keep all the strings used in CMS Functions and templates in the resource files