Three simple steps to localize
The German and French Online-Help pages have been created with the help of machine translation. In doubt please read the English original.
Sisulizer can localize reports. In order to do that it localizes the report template data and the database that the report uses. Together this produces multilingual reports feature where the same report can be produced in several languages.
Report tools use report templates. They define the report layout and bind data to the report. Report tools combine report template with the actual data from database to produce reports. The first step of report localization is to localize the template data. The data can be either embedded to the report component on the user interface form or it can be a separate file. If it is embedded Sisulizer will automatically localize the report template when localizing the form where the report component exist. If you use external report file you have to add the report file to your Sisulizer project. On build process Sisulizer will create localized report files.
Most reports contains data that need to be localized. For example if we create a product report the report might contains "How to use" field that describes how to use the product. This data contains text that needs to be localized. in order to do that you have to localize the database itself. This is called database localization. Sisulizer support several different ways to localize database data. We recommend to use row localization because then you don't have to modify your SQL queries that much. It is enough that you add WHERE part to your query.
Let's have an example. You have Country table that contains data that you use in your report. When the table contains only one language (e.g. English) your SQL query is simple.
SELECT * FROM Country
Let's suppose that we localize the your English database to German and Japanese using row localization method. Our database contains each row in English, German and Japanese. When we create English report we only use English rows and this is why we have to add WHERE part to the SQL statement.
SELECT * FROM Country WHERE Language='en'
In a similar way we can select German data for German report.
SELECT * FROM Country WHERE Language='de'
Sisulizer contains several sample applications that generate localized reports. See the table below to see sample location for your reporting tool.
Sisulizer supports the following report tools:
|Ace Reporter||VCL||Sisulizer localizes report data embedded to the form.||<sldir>\VCL\DelphiWin\Report\Ace|
|QuickReport||VCL||Sisulizer localizes report data embedded to the form.||<sldir>\VCL\DelphiWin\Report\QuickReport|
|ReportBuilder||VCL||Sisulizer localizes both report data embedded to the form and ReportBuilder report files (.rtm).||<sldir>\VCL\DelphiWin\Report\ReportBuilder|
If your reporting tool is not included in the above list you have two choices. If the reporting tool uses components to define report templates just map your report components to Sisulizer report components. If you reporting tool uses standalone report files contact Sisulizer.