You determine which Windows resources you want to localize, including icons, menus, dialog boxes, strings, accelerators, versions, and manifest resources. Sisulizer can work directly with:
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 .NET platforms 1.0, 1.1, 2.0, 3.0, 3.5, 4.0, 4.5x and higher as well as WPF, Silverlight, and the Compact Framework.
Sisulizer supports all Delphi and C++ Builder applications. It scans all properties and visually shows all components. Sisulizer even supports UNICODE components. Sisulizer has built-in support for all official UNICODE encodings.
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.
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.
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.
Learn more about Sisulizer in: Second, translate the text with Sisulizer's visual editor
|.NET assembly file||.NET assembly file such as an application (.exe) or a library (.dll) file|
|.NET resource file||.NET resource files (.resx).|
|Android||Android project files (.apk)|
|C++Builder binary file (32-Bit and 64-Bit)||Windows PE file (.exe, .dll, .bpl, .ocx) that has been compiled with C++Builder (Win32) and uses VCL component library|
|Delphi binary file (32-Bit and 64-Bit)||Windows PE file (.exe, .dll, .bpl, .ocx) that has been compiled with Delphi (Win32)|
|Delphi form file||Delphi form file (.dfm)|
|Delphi Prism||Delphi's ObjectPascal for .NET project files (.oxygene)|
|Embarcadero .NET project file||Embarcadero Developer Studio project file (.bdsproj)|
|Embarcadero .NET project group file||Embarcadero Developer Studio project group file (.bdsgroup)|
|Embedded Visual Basic project file||Embedded Visual Basic project file|
|FireMoney||FireMonkey project files for Windows, and Mac (.exe, .app)|
|Guiliani||GUIs for embedded systems in the Guiliani text format|
|HTML (and variants) file||HTML file (.html, .htm) and other files that use HTML markup language such as ASP, JSP and PHP files.|
|HTML Help (Enterprise Edition)||Compiled HTML Help .chm files|
|Ini (and variants) file||Ini file (.ini) and other file that uses section/key format such as InstallShield string table file (.shl)|
|iOS String resource (.strings) file||iOS apps string resources can now be localized.|
|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)|
|JSON||lightweight text-based JSON files|
|PO/POT/MO file||Linux/GNU gettext files, also popular for PHP server applications, and WordPress PlugIns|
|ReportBuilder file||ReportBuilder report file (.rtm)|
|Salesforce translation files||Salesforce translation files (.stf or .zip)|
|Source code file||Source code file (.c, .cpp, .pas, .vb, .java, .bas, etc)|
|TBX file||TermBase eXchange files can be imported to translation memory or project|
|TMX file||Translation Memory Exchange files can not only be used as translation memory but also localized themself.|
|Text file||Text file (.txt) that contains key/value lines|
|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)|
|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)|
|Windows screen saver (.scr) file||Windows screen saver can now be localized.|
|XLIFF file||XML Localization Interchange File Format file|
|XML file||XML file|
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.
|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|
|Firebird||Sisulizer can access and localize Firebird 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|
|NexusDB||Sisulizer can access and localize NexusDB databases.||yes||yes|
|Paradox*||Sisulizer can access and localize Paradox databases if Borland Database Engine is installed on the computer.*||yes||yes|
|SQLite||Sisulizer can access and localize SQLite databases.||yes||yes|
|SQL Server||Sisulizer can access and localize SQL Server databases.||yes||yes||yes|
|SQL Server Compact||Sisulizer can access and localize SQL Server Compact databases.||yes||yes|
* For scanning and building dBASE or Paradox databases, the Embarcadero (former CodeGear, 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/2010/2013 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.