|
| |
|
| |
|
Call Sisulizer
☎ (213) 984-4945
Outside the USA please dial +1 (213) 984-4945 |
| |
|
|
| |
|
Software Localization with Sisulizer
First, scan the application and locate all of the text
Sisulizer can work directly with your C++ Builder,
Delphi, Visual C++, Visual
Basic, Java, or Windows binary
files, or with XLIFF,
or with your .NET assembly.
Background Info
|
Binary localization
If you are new to software localization, you will often
read about binary localization. But what does binary mean
in this context?
Binary localization reads all strings that should be localized
from the compiled application. This is
possible because modern Windows programming systems store
dialog boxes, menus, shortcuts, and strings in what is called
"resources". Resources are special sections in
the compiled program that systems can read without de-compiling
the binary file. Sisulizer can perfectly read and
write these sections without touching the
program code.
|
You determine which Windows resources you
want to localize, including icons, menus, dialog boxes, strings, accelerators, versions, and manifest resources.
The software works visually with HTML,
HTML Help (.chm) and XML.
Sisulizer can also grab text from text files
and databases.
Sisulizer also operates in the mobile world.
It supports .NET Compact Framework, Pocket
PC, Symbian,
and J2ME.
Sisulizer is a format genius
Just see for yourself. The tables
below give you an overview of the supported formats. For all visual
formats, you can find a built-in visual editor
in Sisulizer. You do not need third-party tools.
Even the XML format is scanned by a parser
to avoid importing problems into Sisulizer. All official XML encodings
are supported.
Databases are supported with native
drivers for the best possible performance. No
ODBC or third-party client software is needed.
If you use your own visual components, you can customize Sisulizer
to display and handle them.
- Sisulizer supports all Delphi and C++ Builder
applications. It scans all properties and visually shows all
components. Sisulizer even supports UNICODE
components.
- Sisulizer supports all .NET platforms: 1.0,
1.1, 2.0, 3.0, 3.5, and higher as well as the Compact
Framework.
- Sisulizer supports all Symbian
platforms.
- Sisulizer has built-in support for all
official UNICODE encodings.
Sisulizer has safe source code localization.
This means that Sisulizer automatically creates
localized source code files when you change your original source
code. This is also true for XML localization.
Scan your own text format
Do you have a text format not covered by our list? This is not
a problem because you can just create new format rules
in Sisulizer. Combine these rules with your file extension and
use it with Sisulizer.
Upgrade: Translate only what has changed
Sooner or later, your software projects will need some polishing.
An upgrade or update must be released. With Sisulizer localizing,
upgrades are a snap. Sisulizer scans your whole project, including
all applications, databases, XML/HTML files, and so on, for changed
and new items. Sisulizer remembers all of your existing
translations, making updating and
upgrading fast and convenient.
Supported Formats in Detail
Sisulizer works with all Delphi versions and is successfully tested
with these new CodeGear (former Borland) Turbo products:
Supported File
Formats
| File format |
Description |
| .NET assembly file |
.NET assembly file such as an application (.exe) or a
library (.dll) file |
| .NET resource file |
.NET resource files (.resx). |
| CodeGear .NET project file |
CodeGear Developer Studio project file (.bdsproj) |
| CodeGear .NET project group file |
CodeGear Developer Studio project group file (.bdsgroup)
|
| C++ Builder binary file |
Windows PE file (.exe, .dll, .bpl, .ocx) that has been
compiled with C++Builder (Win32) and uses VCL component
library |
| Delphi binary file |
Windows PE file (.exe, .dll, .bpl, .ocx) that has been
compiled with Delphi
(Win32) |
| Embedded Visual Basic project file |
Embedded Visual Basic project file |
| HTML (and variants) file |
HTML file (.html, .htm) and other files that use HTML
markup language such as ASP, JSP and PHP files. |
| Ini (and variants) file |
Ini file (.ini) and other file that uses section/key format
such as InstallShield string table file (.shl) |
| Java archive file |
Jar file (.jar) that contains resource (.properties)
files |
| Java resource file |
Java resource file (.properties or .java) or files |
| JBuilder project file |
JBuilder project file (.jpx, .jpr) |
| PO/POT/MO file |
Linux/GNU gettext files |
| ReportBuilder file |
ReportBuilder report file (.rtm) |
| Source code file |
Source code file (.c, .cpp, .pas, .vb, .java, .bas, etc)
|
| Symbian project file |
Symbian project file (.mmp) that contains resource files
(.rss) |
| Text file |
Text file (.txt) that contains key/value lines |
| Windows binary file |
Windows PE file (.exe, .dll, .ocx) that has been compiled
with a C/C++ compiler and uses standard Win32 resources
such as dialog boxes, menus, and string resources. |
| Windows resource file |
Windows resource file (.rc, .rc2) |
| Visual Basic binary file |
Windows PE file (.exe, .dll, .ocx) that has been compiled
with Visual
Basic (Win32) |
| Visual Basic form file |
Visual
Basic (Win32) form file |
| Visual Basic project file |
Visual
Basic (Win32) project file |
| Visual Studio .NET project file |
Visual Studio .NET project file (.csproj, .vbproj) containing
a managed code project (e.g. C# or Visual Basic) |
| Visual Studio .NET solution file |
Visual Studio .NET solution file (.sln) |
| XLIFF
file |
XML Localization Interchange File Format file |
| XML file |
XML file |
| CHM file |
HTML Help (Enterprise Edition) |
| TMX file |
Translation Memory Exchange files can not only be used as translation memory but also localized themself. |
Database
formats
Sisulizer supports the following database formats. If you are
mainly interested in database localization you should also read
our information about the four different localization methods.
| 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 Translation 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.
Learn more about Sisulizer in: Second,
translate the text with Sisulizer's visual editor
|
|
|
Platforms |
HTML
JSP/ASP/PHP
JavaScript
Visual C++
Java
Windows Binaries
DLL/EXE/OCX
Windows Vista
32+64 Bit PE files
Reports
XML
XLIFF/TMX
INI/Text
Symbian
Pocket PC
.NET Compact Framework
J2ME
PO/POT/MO
|
|
|
|