You can localize the names of document types and document properties by means of property
files as described in Section 5.7, “Localization”. To this end, you provide property files
and use them to override the properties defined in
com.coremedia.cms.editor.ContentTypes_properties. Typically, this is done while
initializing a Studio plugin.
public function init(editorContext:IEditorContext):void {
ResourceBundle.overrideProperties(ContentTypes_properties, MyDocumentTypes_properties);
}Example 7.12. Localizing document types
There are several kinds of property keys to overwrite when localizing document types:
<ContentTypeName>_text: the name of the content type<ContentTypeName>in the given language;<ContentTypeName>_toolTip: the tooltip shown for the content type<ContentTypeName>;<ContentTypeName>_icon: the CSS class to attach to the HTML <div> elements that show the type icons for the content type<ContentTypeName>(see Section 7.3.2, “Defining Content Type Icons” for details about these style classes);<ContentTypeName>_<PropertyName>_text: the name of the property<PropertyName>of a document of type<ContentTypeName>or a subtype thereof;<ContentTypeName>_<PropertyName>_toolTip: the tooltip shown for the property<PropertyName>of a document of type<ContentTypeName>or a subtype thereof.<ContentTypeName>_<PropertyName>_emptyText: the text to shown in the field when the property<PropertyName>of a document of type<ContentTypeName>is empty. This message typically prompts the user to enter a value.
When multiple localizations are defined for a single property, but different content types, the most specific type is used.
Content Types in Blueprint Studio
The CoreMedia Studio Blueprint plugin contains two property files
BlueprintDocumentTypes.properties and
BlueprintDocumentTypes_de.properties for localizing document type names and
property names in the
studio/blueprint-forms/src/main/joo/com/coremedia/blueprint/studio directory.
You can simply change the value of any of the properties as needed.
 |  |  |
 |