Software Localization with Sisulizer
Third, build the localized version
Now that your translator has finished translating all of your
strings, and you've received your updated file, simply
run Sisulizer to build the new version of your program in the
new language.
It's that easy! You're in control throughout the project,
and localization has never been simpler.
Sisulizer easily handles all languages, including right-to-left
and double-byte languages. And the program keeps
track of what has already been translated,
making the process fast and inexpensive for you to translate later
versions of your application.
Localization in the 21st century is binary localization
The state-of-the-art localization method for
Windows applications in the 21st century is binary localization.
You do not have to recompile your application
to get the localized version. Just build the new EXE, DLL, OCX
and so on with Sisulizer. That's it!
All you need is an application using standard Windows
resources. All major development systems do this operation
right away or at least support it actively. Your original code
or binary is never changed. Sisulizer always works with
copies of your work. Whenever a platform, such as Windows,
supports multiple languages in one EXE or DLL,
Sisulizer supports it as well.
Of course, Sisulizer also supports resource source code
localization. But once you see the advantages of binary
localization, resource source code localization becomes less important.
Translation reuse - Never translate something twice
Every developer knows: A software is never perfect. There is always something
to do better and there are always features to add. And everytime
a new feature is added there will be new dialogs and strings to be translated. Forget about tracking yourself what is new and what is changed. Let Sisulizer project management handle this time consuming task. Sisulizer finds all changes to the project. It is as easy as pressing F5 to rescan your application for changes and reuse existing translations to the new version of your software. For
more information please watch our Scan for Changes movie.
Make Sisulizer part of your build process
If you work with a huge software project, you will be happy to
hear that you can use Sisulizer as a command
line tool (Enterprise Edition). You can easily include
it in your build process and incorporate it into
your makefile or use some fine build tool like FinalBuilder, or
Visual
Build Pro.
Sisulizer’s project file is not in a proprietary
binary format like in other tools; it uses UTF-8 encoded
XML. This format makes it possible to view and edit the
file with any text editor. You can also store the file in version
control software.
With these features, Sisulizer localization becomes an easy-to-maintain
part of your software development process.
And, if you have ever lost work because
of a proprietary format, you will understand how important it
is to store data in the open XML format.
Status for every item
In Sisulizer, every item has its own status
throughout the whole localization process. This status gives you
an overview about the process: items to be translated,
already translated, checked,
and so on. You have complete information about
the quality of your localized build.
Reports
With Sisulizer's reports, you can print out
all translations on a piece of paper. This feature is very handy
for proofreaders who prefer to correct errors
on paper rather than on the screen. Sisulizer even has a print
preview for reports.
|
English
