What is Episerver XML and how does it work for Episerver-based web applications?
File Extensions | .xml |
API Extension | episerver |
Format Options | No |
Import | Yes |
Export | Yes |
Pluralization supported? | No |
Descriptions supported? | No |
Episerver is a content management service provider. Episerver XML is its standard localization file format that is used to load translated/localized strings. The localized XMLs are typically saved in the “lang” folder under the web root directory. With a predefined Localization Provider, strings loaded from the XML will override default UI texts.
Each Episerver XML has at least one locale nested in the <languages> tag. Therefore, it is possible that an Episerver XML is multilingual.
Code Sample
<?xml version="1.0" encoding="UTF-8"?>
<languages>
<language name="English" id="English">
<boolean_key>--- true
</boolean_key>
<empty_string_translation/>
<key_with_line-break>This translations contains
a line-break.</key_with_line-break>
<nested>
<deeply>
<key>I'm a deeply nested key.</key>
</deeply>
<key>This key is nested inside a namespace.</key>
</nested>
<null_translation/>
<pluralized_key>
<one>Only one pluralization found.</one>
<other>Wow, you have %s pluralizations!</other>
<zero>You have no pluralization.</zero>
</pluralized_key>
<simple_key>simple key, simple message, so simple.</simple_key>
<unverified_key>This translation is not yet verified and waits for it. (In some formats we also export this status)</unverified_key>
</language>
</languages>