/
documentation-html-00712.xml
16 lines (15 loc) · 1.57 KB
/
documentation-html-00712.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
<?xml version="1.0" encoding="UTF-8"?>
<DocumentationHtmls xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="opencms://system/modules/com.alkacon.opencms.documentation/schemas/documentation-html.xsd">
<DocumentationHtml language="en">
<Html name="Html0">
<links>
<link name="link0" internal="true" type="A">
<target><![CDATA[/sites/default/opencms-documentation/localization/multilingual-websites/]]></target>
<uuid>b278890c-b2a1-11e4-b42e-0242ac11002b</uuid>
<anchor><![CDATA[sec_supported_locales]]></anchor>
</link>
</links>
<content><![CDATA[<p>Additionally to the system wide configuration of the available locales as described in Section <a href="%(link0)">[supported_locales]</a>, one can restrict the number of locales that are available for a specific content (type). If at the XML file containing the content, or one of the parent folders of that file, the property <code>locale-available</code> is set, than only the locales given there are selectable in the content editor. E.g., if you set <code>locale-available</code> to <code>en,es</code>, only English and Spanish will be available. But not German, even if configured. This is in particular helpful, if you have contents used for configuration. They usually need only one language version. Thus, you set <code>locale-available</code> to that one language at the content's XML files. This is done best by configuring default properties for newly generated contents.</p>]]></content>
</Html>
</DocumentationHtml>
</DocumentationHtmls>