In our last post, we’ve described how to localize the static texts in outputted XSLT reports. You need to open the Report.xslt file placed in the appropriate language lproj folder.
- What if, your lproj folder is not existing in the report template’s package?
- What if the appropriate language folder does not contain an XSLT file just like the other lproj folders do?
1.Your lproj folder is not existing in the report template’s package
Merlin for Mac OS X contains localization files for the following 3 languages; English, French and German. That means, it can only run in one of those 3 available languages. If your Finder runs for example in Dutch and “Français” is set as second language in the order…
Merlin will start in French. In this case, when editing reports for *your* language you should edit the French.lproj folder. It won’t help creating an nl.lproj folder in the report package, as Merlin running in French won’t try to access all of a sudden localization files for another language…
2. Your lproj folder does not contain an XSLT file. How to localize this XSLT report?
This is the case for example in the XSLT report template “Next Due Activities” in the French localization and will also apply for a custom template created out of this report.
To localize this xslt report in French…
- You simply copy the Report.xslt file from the English.lproj folder into the French.lproj folder (English is the fall back language)
- and edit the Report.xslt out of your French.lproj folder
- Save your changes
- Restart Merlin if it is running
- Call Fichier > Nouveau Repport… > and select your report
- It will show the just defined text strings
Adding a report option
See next blog post