5.4. Localizing Active Query Builder VCL and ActiveX Edition
We recommend the following way to localize Active Query Builder VCL and ActiveX Edition:
Download and install the component and find the 'English.lng' file in 'Languages' directory.
Download and install IniTranslator application for fast and easy translation.
Open 'English.lng' file as Original. We also recommend you to set highlighted IniTranslator options as shown on the screenshot:
Now you can start to translate. Below are the form screenshots intended to ease translation process. Each section of .lng file represents a form (window), except the [Active Query Builder] section that contains common strings used in Active Query Builder (popup menus, grid captions, error messages, etc.).
If you find that some of translated strings doesn't fit the form, try to cut the string, or tell us about this case so we can allocate more space on the form for it.
There are two strings in the [General Settings] section that should be set in exact matching to your language: 'CharSet' and 'BiDiMode'. First item specifies required character set of the font and second specifies the bi-directional mode of controls. All possible values are listed in the comments in 'English.lng' file, so all you need is to uncomment settings that fit your language and copy them to your translation file.
Sections of .lng file
[TacDatasourcePropsForm] - This form represents properties of any data source object in the query.
[TacLinkPropsForm] - This form represents options of JOIN clause.
[TacQueryPropsFbForm], [TacQueryPropsIbForm] - These forms represent common properties of InterBase and Firebird SQL queries.
[TacQueryPropsSbForm] - This form represents common properties of Sybase SQL queries.
[TacQueryPropsMSForm] - This form represents common properties of MS SQL Server queries.
[TacQueryPropsMYForm] - This form represents common properties of MySQL queries.
[TacAddObjectForm] - This form is used to add objects to the query.
[TacProcedureParams] - This form required to get input parameter values of stored procedures and functions.
Actually, this will be enough to localize end-user interface of Active Query Builder, so you can stop here, if you don't want to show any of setup windows listed below to end-users. Just copy the rest of the original file to your translation, and that's all.
[TfMetadataContainerEditor] - This form is used to manage objects stored in Metadata Container.
[TfacQBMetadataContainerLoad] - This wizard is used to load metadata to Metadata Container. It consists of the following steps:
Step 1. Welcome message.
Step 2. Selecting SQL Syntax.
Step 3. Selecing Connection Type.
Step 4. Specifying connection options.
Step 5. Selecting databases.
Step 6. Specifying additional fintration.
Step 7. Loading Metadata.
[TfrAcQBBDEConnectionEdit] - BDE Connection Options. This frame is used internally in the Load Metadata Wizard on the fourth step.
[TfrAcQBADOConnectionEdit] - ADO Connection Options. This frame is used internally in the Load Metadata Wizard on the fourth step.
[TfrAcQBdbExConnectionEdit] - dbExpress Connection Options. This frame is used internally in the Load Metadata Wizard on the fourth step.
[TfrAcQBIBExConnectionEdit] - IbExpress Connection Options. This frame is used internally in the Load Metadata Wizard on the fourth step.
[TfrFilterEditor], [TfEditMetadataFilter] - This form is intended to define metadata filters. You should call the EditMetadataFilter method to open this form.
[TfmAQBOptions] - This form is the second page of the Properties window. You should call the EditProperties method to open this form.
[TSQLFormatFrame], [TfmSQLBuilderOptions] - This form and its frame are the third page of the Properties window.
[TfmAQBOptions2] - This form is the first page of the Properties window.