Comparison
|
iFix versions prior to 4.0 do not have native multilanguage management.
FXInterpreter has been tested with iFix 3.5, 4.0 and 4.5.
| |
|
|
iFix without FXInterpreter |
iFix with FXInterpreter |
Notes |
|
|
Multilingual |
 |
 |
It is possible to manage multiple foreign languages. |
|
|
Global language |
 |
 |
For all pictures. |
|
|
Local language |
 |
 |
It is possible to translate a picture in a local language, different from the global one. |
|
|
Picture text and captions translation
(Fix2DText and CommandButton) |
 |
 |
Tooltips are included. |
|
|
Picture objects translation in “development mode”. |
 |
 |
Allows you to replace the development language of pictures for easier maintenance by the end user. |
|
|
A text CSV file for each picture and each language |
 |
|
Eg. 30 pictures with 2 foreign languages -> 60 files ! |
|
|
NOT unique strings in each CSV file |
 |
|
Eg. 10 identical strings in 30 pictures with 2 foreign languages
-> 600 rows to edit * |
|
|
Manual export |
 |
|
For each new picture or change (in a existing picture) or new language, it is necessary to export all the strings and to type all the translations. |
|
|
Single Excel file |
|
 |
A single file for ALL pictures and ALL languages. |
|
|
Unique strings |
|
 |
Each string appears once in the dictionary. Eg. 10 identical strings in 30 pictures with 2 foreign languages
-> only 1 row to edit. |
|
|
Original dictionary is compiled automatically |
|
 |
The list of the original strings to translate is simply generated by browsing the project in runtime or with a specific global command. |
|
|
Dictionary is reusable in other projects |
|
 |
Strings already in the dictionary are immediately translated without any further intervention. The dictionary can be expanded over time. |
|
|
User global language |
|
 |
The global language can be automatically changed on the basis of the user name at login. |
|
|
User local language |
|
 |
The local language of a picture can be automatically set on the basis of the registered user name. |
|
|
Translation of default VBA objects (all) |
|
 |
Tooltips are included. |
|
|
Strings translation in MsgBox and InputBox |
|
 |
It is also possible to translate strings with variables inside. |
|
|
Historical alarms translation |
|
 |
It is possible to translate historical alarms and to restore descriptions if they are partially cut off by log process. |
|
|
Translation without pictures reopening |
|
 |
It is NOT necessary to close and to reopen the pictures after language change. |
|
|
Selection of the objects to be translated on the basis on an optional prefix |
|
 |
The prefix can be set by the developer (eg. “TR_”). The dictionary is further reduced. |
|
|
Third part ActiveX translation |
|
 |
Quotation on request. Textual properties must be accessible. |
|
|
Recognition of spaces before and after the strings |
|
 |
The dictionary contains only “clean” strings, while in runtime it is possible to see all the spaces added for aesthetic reasons. ** |
|
|
Implementation time
– 90%
|
|
 |
Realistic estimate. |
|
|
Maintenance time
– 99% |
|
 |
Realistic estimate. |
|
|
NOT necessary to prepare a document for a translation service |
|
 |
It is not necessary to extrapolate a unique document to send to an external translation service. |
|
|
Simplification of changes by the end user (without any risk to the application) |
|
 |
The uniqueness of the dictionary makes any changes both fast and easy. |
|
|
(*) With iFix CSV files it is NOT possible to use the automatic function “Search and replace” of a textual editor (like Notepad), because translations don’t replace original strings, but they have to be added.
(**) For example the string “ Historical archive” is registered as “Historical archive”, translated in the Italian dictionary as “Archivio storico” and shown as “ Archivio storico”.
|
|