Mapping file locations for deployment
Contents
Mapping file locations for deployment
Configuration of the file chooser
Mapping file locations for deployment |
Contents |
| Mapping file locations for deployment |
|
| Configuration of the file chooser |
If you need to publish your reports and documents in different languages, then it is not effective to create copies of the templates for each language. Rather it is desirable to replace the text strings in the template before a run. ReportsAnywhere allows you to do this. It is recommended to use flexible layout, when using localisation because the legth of text may change between languages. Flexible layout prevents cropping of the text and always generates an optimized space distribution among columns.
Use the menu Tools/localisation Setup... to edit the localisation settings. Localisation consists of writing all text resources (Strings, prefixes, number/date formatting, propmpts etc) to external files where they can be translated.
Translation can be done completely inside ReportsAnywhere, but the task can also be delegated to staff, who does not need a ReportsAnywhere license.
Localisation consists of a set of files (one for each language) that follow certain naming conventions and that are stored in one directory.
The file names consist of a base name (the start of each file name), the iso language/country codes and the extension (.properties) So in the example below the default texts are stored in a file called:
textresources.properties German translations would be stored in textresources_de.properties French translation would use textresources_fr.properties. Canadian French can have its own language set specified as textresources_fr_ca.properties.
| 1. | Check this if you want to use localisation |
| 2. | The base name (the string that every language file starts with. (best named like your template set) |
| 3. | The directory where the files are stored. (The dot indicates the directory of your template set, which is the recommended place) |
| 4. | Once you press save, the defaults file will be generated and you are ready for translation. |
Use the menu Tools/Manage localisation Keys... to edit the localisation keys and translations.
| 1. | The first column indicates the key. Initially it is just the text extracted from the template. (You can edit the key here. This will update all templates to use the changed key value) |
| 2. | This shows how often the key is used in the template set. |
| 3. | The following colums show the translations that currently exist. (Click into the cells to edit the translation) |
| 4. | This creates another language file, which is initialized with the default values. |
| 5. | This adds a new key. You can translate it and then use it in your templates. (You do not need to create the keys first, any static text used in a template will automatically become a key) |
| 6. | For a selected key, this will po up a list of the places where the key is used. |
| 7 | This will remove unused keys from all files. |
| 8 | This will save all keys and translations into their repective files. |
| 9 | This will close the dialog without saving. |
Localisation files resemble java property files. They have the form of key value pairs each on its own line. Keys and values that contain blanks or other special (non alphanumeric) characters must be enclosed in quotes. To write a quote, it must be preceded by a backslash. Comment lines are preceeded by a hash mark, but will be overwritten by the next automatic update.
This is a sample localisation file.
# Default localisation strings for ReportsAnywhere project C:\joria\support\qint\localetest\lt.rwts generated at Mon Oct 22 18:51:47 CEST 2007
# Values can be edited manualy. Keys are managed from {0}
"Click here to edit the title." = "Hier klicken um den titel zu bearbeiten."
"MasterData 10/22/07 5:54:46 PM" = "MasterData 10/22/07 5:54:46 PM"
| Configuration of the file chooser |
Contents |
Mapping file locations for deployment |