 |
|
|
|
|
|
|
|
 |
|
 |
|
Sisulizer supports source
code localization for the following Classic Visual
Basic editions:
|
|
 |
|
 |
|
| WYSIWYG |
Complete
Visual editor for forms, user controls, menus ... |
|
 |
| Visual Inheritance |
Visual mapping
for user controls |
|
 |
| TM |
Yes
incl. Trados translation memory access (Enterprise) |
|
|
 |
 |
 |
|
| Source Localization |
Recommended
|
|
| Database support |
Yes,
Sisulizer can localize databases, incl.
Access |
|
| Edit Resources |
Yes,
but VB only knows a very few types of resources
|
|
|
 |
|
 |
 |
|
| File Formats |
| All common Visual basic files like vbp,
.frm, .frx, .cls, .bas, etc. |
|
| Third party |
| control mapping, well
known controls are automatically mapped |
|
| Your Source Code |
| Translator does not need to see your source
code |
|
|
 |
 |
 |
|
| Support |
Yes,
we still care for Classic VB |
|
| Languages |
If Windows supports a language,
then
Sisulizer supports it |
|
| VB.NET |
| Please see .NET platform for infos about
VB.NET |
|
|
 |
 |
 |
|
Read
why Sisulizer is the right localization tool
for all classic Visual Basic programmers
Sisulizer localizes classic Visual Basic
in three ways
- Visual Basic source code localization
Sisulizer analyzes the complete Visual Basic source files and
can display and edit all forms and user controls in a visual
environment.
- Visual Basic localization using Windows resources
The software support Visual Basic projects that store the string
in Windows resources.
- Visual Basic database localization
If you build a mechanism to store all strings in databases,
you can use Sisulizer's database translation option.
Visual Basic Source Code Localization
In source code mode, Sisulizer supports visual inheritance
of Visual Basic. User controls that are defined in the same project
are automatically mapped to the forms that use those controls.
This allows you to get the best possible visual editing
experience for classic Visual Basic.
A usercontrol providing visual inheritance
in Visual Basic
Display in Sisulizer (Classic View, untranslated).
The small markers in User Data Path mean that this control is
defined somewhere else in the project. In this case, the control
is the Usercontrol automatically mapped by Sisulizer into the
form, similar to the Visual Basic IDE. You should not ask for
less comfort.
Does my translator see my source code?
While Sisulizer sees your Visual Basic source files, your translator
does not see them in the free Translation Edition (optional
he can see it if you want). Of course, the translators see all
forms and user controls in Sisulizer's great What-You-See-Is-What-You-Get
display (see the previous example). And the translator does
not require a run-time or database driver to install the software.
Does Sisulizer change my source code?
There is no need to change source code or to
add any kind of component to your project. Good to know - Sisulizer
never changes a line of code or a property inside
your source code originals.
I store my strings already in a database or resource. Why should
I localize with Sisulizer?
While Visual Basic has a specific format for forms, you might
already have localized your Visual Basic with a home-brewed solution.
Some developers might store strings in resource files or in databases.
With Sisulizer you can use the storage method that you started
with. Use Sisulizer's luxurious editor to maintain your
resource files and database --and forget about translating
things twice. Sisulizer stores all translations.
Re-use your existing translation efforts easily in updates and
new projects.
Sisulizer does not forget any translation.
If you update a large project, you do not lose control of what
is already translated, what has changed, and what is new.
- Forget about teaching your translators how to
work with databases.
- Forget about editing your resources in that small
and glitchy Visual Basic resource editor using tiny fonts.
Upgrade to a state-of-the-art editor with Translation
Memory, a luxury editor with undo
and redo and full What-You-See-Is-What-You-Get
with visual inheritance (if Sisulizer
is used with your classic Visual Basic source code).
Have we mentioned that if you translate Classic Visual Basic
with Sisulizer and you port later to VB.NET, you are not
going to lose your translation? It's true!
There is no reason to wait with your software localization until
you port some day. Your Sisulizer License covers all listed
platforms
with no extra costs. Start now with Classic Visual Basic and switch
later to .NET, or use both platforms at the very same time. You
can even have multiple platforms in one Sisulizer project.
Enjoy the profits of multi-national and multi-language sales now.
For us Classic Visual Basic is still alive
For the Sisulizer team, classic Visual Basic is not a
legacy product that we list merely to have a long platform
list for marketing reasons.
Classic Visual Basic is still a platform used in myriads
of existing solutions. It is impossible to convert them
all economically to .NET platform. A lot of them must remain in
classic Visual Basic.
While Sisulizer's developers are Delphi guys, you might think:
"Hey, do they understand VB?"
They do, because they are pushed and supported by active
and experienced Visual Basic developers, who fell in
love with Visual Basic Version 1 a long way back 1991 and kept
developing in Visual Basic for the past 15 years.
Sisulizer is tested with their Visual Basic projects who reaching
the limits of the VB 6 IDE. So, as long as there is a strong Visual
Basic user base maintaining huge enterprise solutions, we say:
"Classic VB users - you are not alone and we still
care about your day-to-day programming needs!"
The product names used on this website are for
identification purposes only – all trademarks and registered
trademarks are the property of their respective owners.
|
