|Number of votes:||1|
EPiServer localization xml files structure
In CMS7 there are a couple of new things that can be localized. I hadn’t had the time to check it out but a question in the forums about localization of “GroupName” on page types got me curious.
Localization of page types and properties are the same as for earlier versions of EPiServer.
Blocks are new to CMS7. Thomas Krantz blogged about block localization over here but I will include it in the example below just for completeness. The example for blocks in the Alloy demo package ContentTypeNames.xml is incorrect at least in the first production release.
Groups then. The DisplayAttribute.GroupName is localized via heading elements. These headings localizes the tab names in edit mode.
I couldn’t find anything about ContentTypeAttribute.GroupName so I fired up good old reflector. It turned out that you can localize GroupName via specifying groups in the xml file.
I expected this to localize the labels for the different groups of page types you get when creating a new page. This is not the case. What’s actually localized is the bracketed prefix on the page type when you view them in admin mode. I can’t see much use for this so I’ve checked with the support and they have an existing bug regarding that page type information localization doesn’t work so hopefully this will be fixed soon.
Below is an example lang file for reference.
<?xml version="1.0" encoding="utf-8" ?>
<language name="English" id="en">
<!-- Blocks -->
<!-- Tab headings aka GroupName in Displayattribute for a property-->
<!-- PropertyNames -->
<!-- Page types -->
<!-- Groupname in ContentTypeAttribute-->
Please login to comment.