|
Sisulizer
is the database localization specialist
Complete
your software localization experience with database localization
Sisulizer's Professional and Enterprise packages have built-in
support for major local database formats. The
Enterprise version adds access to remote
database servers. You do not need any converters or plug-ins.
Just install Sisulizer and start to localize your databases*.
There are many reasons why databases are an important part of
your software localization:
- You may retrieve strings for your GUI
localization from a database.
- Your databases may contain data
for your application that need to be localized
as well as the application itself. One example is a product
database for an online shopping system.
- The information in your database is the
product you sell. When you localize this information,
you can offer it in new markets and increase your revenues.
Sisulizer
is as flexible as your database localization needs
There are many ways to understand database localization. Sisulizer
covers them at all levels: clone (database), table, row (2 flavours),
and field. The four methods Sisulizer offers to localize your
databases
are
as follows:
Clone Database Localization Method
Using this method, Sisulizer creates a complete clone of the
database. The result is an exact copy of the original
structure. The structure, including all table and field
names of the database of the clone, is the same. The databases
differ only in the database name.
The clone method creates one database for each
localization language, here German and Japanese.
Advantage: No need to change the database structure;
only the database content differs.
Row
Database Localization Method
With this method (in 2 flavours), Sisulizer copies the original table row for
each language. The copied rows are equal to the original
one, except the language field value is different. The
field value matches the language of the row. Those fields that
have been marked to be localized contain a localized value.
The
result might look like this:
The translation is spread across multiple rows.
ID and Language fields together are the unique database index.
Advantage: Just a small change in database
structure which is very easy for a software developer who accesses
the database content to implement.
New: Sisulizer now offers the possibility to use a foreign
key as unique database index to identify translations. Therefore
the new row localization method does not need a combined index
of ID
and Language. To create new ID values Sisulizer calls your stored
procedure. Please refer the Sisulizer online-help for detailed
instructions.
Table
Database Localization Method
This method adds localized tables for those tables that you want
to localize. The localized tables contain only the primary
key and those fields that are localized. The result is
written to new tables with the same structure.
The database tables only have different names, like description
and description_ja:
On the left, you see the original table description
and, on the right, the translated table description_ja.
The difference with the clone method is that the language tables
are in the same database. The clone method creates a database
for each language.
Advantage: Just a small change is required in
the database structure which is very easy for a software developer
who accesses the database content to implement.
Field
Database Localization Method
In this method, Sisulizer updates the values of the localized
fields in the same database row. The localized
fields are equal to the original field, except that they contain
data in a different language and their names differ, of course.
For example, if the original language is English and you want
to localize the database in German and Japanese, you can add German
and Japanese fields for those fields that contain strings for
localization.
Picture shows a database table with original value and translated
fields for German and Japanese language. Not all fields occur
three times, because the Population field i.e. does not need to
be translated.
The fields Name_de and Name_ja
contain the translations.
Advantage: You need to change only the database
structure of all tables with localizable content. The implementation
is easy for a software developer who accesses the database content.
The best advantage is that you do not need to keep redundant data.
Translation Memory
Segmentation that breaks paragraphs into sentences
for smarter re-use of translated information is fully supported.
Sisulizer supports SRX
segmentation rules for databases, XML and HTML where
long text passages are common.
Supported Database Formats
| Database |
Description |
Import |
Localize |
TM |
| Access |
Sisulizer can access and localize Access databases. |
yes |
yes |
yes |
| Access 2007* |
Sisulizer can access and localize
Access 2007 databases if Microsoft Data Connectivity Components is installed
on
the computer*. |
yes |
yes |
yes |
| ADO/ODBC compatible |
Sisulizer can access ADO/ODBC-compatible databases. |
yes |
|
|
| dBase* |
Sisulizer can access and localize dBase databases if Borland Database
Engine is installed on the computer.* |
yes |
yes |
|
| DBISAM |
Sisulizer can access and localize DBISAM databases. |
yes |
yes |
yes |
| Interbase |
Sisulizer can access and localize Interbase databases. |
yes |
yes |
yes |
| MySQL |
Sisulizer can access and localize MySQL databases. |
yes |
yes |
yes |
| Oracle |
Sisulizer can access and localize Oracle databases. |
yes |
yes |
yes |
| Paradox* |
Sisulizer can access and localize Paradox databases if Borland Database
Engine is installed on the computer.* |
yes |
yes |
|
| SQL Server |
Sisulizer can access and localize SQL Server databases. |
yes |
yes |
yes |
| Firebird |
Sisulizer can access and localize Firebird databases. |
yes |
yes |
yes |
TM = Translation Memory
* For scanning and building dBASE or Paradox databases, the
CodeGear (former Borland) (tm) BDE needs to be installed. For translating dBASE
or Paradox, e.g. in the Sisulizer Free and Translator Edition, the BDE is not
needed. Download
and install the BDE only if: a) You do not have Delphi or C++ Builder installed
(both install BDE to your machine) and b) You need to localize dBASE or Paradox
(and not the other supported database formats).
* For scanning and building Access 2007 databases (.accdb), the
Microsoft
Data Connectivity Components needs to be installed. It also gets installed with Office 2007. If you already have Office 2007 installed you do not have to download an install it.
The product names used on this website are for
identification purposes only – all trademarks and registered
trademarks are the property of their respective owners.
|
