New standardized format for content type localizations

In EPiServer 7.5, there is a new standarized way how to add localized texts for content types. In previous versions of EPiServer there was separate section for each content type, for instance:

<language id="en" name="English">

    <pagetypes>

        <pagetype name="PageListBlock">

            <name>Page List</name>

            <description>Displays a list of pages, for example to display recent news</description>

        </pagetype>

    </pagetypes>

</language>

Since the amount of “base” content types has grown significally in EPiServer 7.5, specifically when taking EPiServer Commerce into consideration, we decided to normalize how content localizations are handled. All content types are now added under the top level section named “contenttypes”. The format has also changed a bit as seen below:

<language id="en" name="English">

  <contenttypes>

    <standarpage>

      <name>Standard Page</name>

      <description>A plain vanilla page.</description>

    </standarpage>

    <teaserblockcontrol>

      <name>Teaser</name>

      <description>Used to insert a content teaser</description>

    </teaserblockcontrol>

  </contenttypes>

</language>

Adding localized texts for properties can be done either to a specific content type:

<language name="en">

  <contenttypes>

    <startpage>

      <name>Start page</name>

      <description>A description of the page type</description>

      <properties>

        <searchresultpagelink>

          <caption>Search Result Page Link</caption>

          <help>Link to search result page.</help>

        </searchresultpagelink>

      </properties>

    </startpage>

  </contenttypes>

</language>

Reusing localization for properties between content types

It is also possible to add common translations to an inherited type, for instance pagedata or icontentdata:

<language id="en" name="English">

  <contenttypes>

    <icontentdata>

      <properties>

        <disableindexing>

          <caption>Disable indexing</caption>

          <help>Prevents the page from being indexed by search engines</help>

        </disableindexing>

      </properties>

    </icontentdata>

  </contenttypes>

</language>

Localizing headers

Headers (tabs for instance) can be localized in the top level section “groups”:

<language name="en">

  <groups>

    <advanced>Advanced</advanced>

    <categories>Categories</categories>

  </groups>

</language>

Upgrading existing language files

When using Deployment Center to upgrade a site, the upgrade process will try to convert any xml files in the “lang” and “Resources\LanguageFiles” folders given that that process can write to these files (they cannot be read only for instance). If you have existing files in other locations or want to do the conversion manually for some reason (check in to source control for instance) there is a small program that can be used to convert existing files. Just select the folder where the files you want to convert are located and press “Convert Content Type Sections” and the files should be updated to use the new format. You can download the program here.