Table of Contents
Property files can adjust FOP editor's look and functionality. One of main task of the property file is to adjust Editor for different users - fully customizables of property files. Functionality of property files are devide into two separate property files: one (so called main), with the functionality of FOP editor's look, and other (so called language), with the definitions of labels.
FOP editor applet is the same for all users, but WEB administrator (or some responsible person) can put one property file for some user group and other file for other users. FOP editor is fully customizable which is mean that responsible person may sets them. Property files are used to set the applet depending on the users group and language that users want to use.
For example, let TextEditor.properties be the main property file for one group of users, then depending of user's choice of language (by choosing appropriate HTML document designed for that language) he will use the "language" property file for chosen language. For example, the language property file for German language is Text_de.properties, but for Spanish language is Text_es.properties. If the Editor can't find the match (if there is no property file for that language) then it uses the default "language" property file named Text.properties which is English.
As it is said before, there are two types of property files.
The first type is the main property file. Within the "main" property file, WEB Administrator defines menubar's content (which menus makes menubar), menu's content (which menu items makes some menu), menu item's properties (actions, images), toolbar content (which buttons and combos makes toolbar), buttons and combos properties (actions, images) and default font and color values.
The second type is the language property file. Within the "language" property file, WEB Administrator defines the labels for all menus and menu items and tooltip texts for all buttons. These labels and tooltip texts are supposed to be written in different languages for different "language" property files.
Default "language" property file must have a name "Text.properties" and within this file all labels and tooltips for default (English) language must be defined. This labels and tooltips are always used if there is no appropriate labels and tooltips within the property file for chosen language. Property files for other languages must have names that follow this rule:
name = "Text_" + language + ".properties"which means that property file for Italian language will be "Text_it.properties", for German language will be "Text_de.properties", etc.(NOTE: it is not strictly defined that language property files must have above mentioned names for language part; you can for e.g. give the name "Text_German.properties" for German language property file, but then you also must define the parameter "Language" in appropriate HTML document as "German").
For every group of users that should have different setup for menus and toolbar there should be a different "main" property file, for e.g. Group 1 should have "TextEditor1.properties", Group 2 should have "TextEditor2.properties". Suppose that inside every group of users there are users that uses different languages (for e.g. English, France, German, Spanish, ...). Then every English user will use "Text.properties" (default) "language" property file along with his "main" property file, every French user will use "Text_fr.properties" "language" property file along with his "main" property file, etc. For this to be done, there must be defined two parameters within the appropriate HTML document, for e.g. for Franch user from fourth group there should be HTML document which will contain following:
<PARAM NAME = "Resource" VALUE = "TextEditor4"> <PARAM NAME = "Language" VALUE = "fr">
NOTE: The HTML document will be explained in following section of this document
You can comment lines in property file by putting '#' at beginning of line. In that case content of this line is not considered by applet.