How To…
How to find the source properties dialog?
Source properties dialog contains lot of important settings. We often discuss about those settings in our support forum and our users ask where is this dialog. You could open this dialog via several GUI commands: Open Project menu, go to Edit Source sub-menu and select your source file in the list. Right click on your source node in [...]
Using resource DLLs in MFC application
We always say using resource DLL files is the best solution for localization of your application, but unfortunately some older programming platforms e.g. still very popular Visual C++ don’t support it internally. However, Microsft added partially support for this solution to MFC 7 libraries. If your application use MFC 7 you could use Sisulizer to [...]
Sisulizer and Microsoft Access 2010 64-bit
With Sisulizer you can localize Microsoft Access database files with all four available database localization methods in Sisulizer, including Cloning. You also can use MS Access databases (both old *.mdb and new *.accdb database file types) as Sisulizer’s Translation Memory engine. Here is article with info about creating new a Translation Memory. When you installs [...]
How can I simoultanously build Windows 32-bit, 64-bit and OSX files?
Sisulizer 3 comes out with capacities to build 32-bit, 64-bit Windows and OSX output files for this same source in Sisulizer project. Currently this is possible only for latest Delphi/FireMonkey version, because both WIN32, WIN64 and OSX binaries created by Delphi compiler contains the same identical resources. For this reason you do not need to [...]
Squares instead of foreign language characters on Windows 8
Whenever you encounter squares in Windows 8 software dialogs, file names, menus instead of e.g. Japanese characters like in 火.txt, you do not have the corresponding language pack installed. The solution is fortunately easy. Make sure you are logged in with administrator rights. First open the Windows control panel. If you don’t know how to find it, [...]
How to prevent the lost of translations in source code localization, after including new items…
Sisulizer always requires a context value for translatable items. Context values unambiguously identify strings and should be always unique. This solution allows to identify the same original string with different translations, but also facilitate synchronization of Sisulizer project with updated source files during scan operation. Generally, it works perfectly, if you localize binary C++ files, [...]
Importing TMX file exported by Sisulizer into SDL Trados
Sisulizer can collaborate with SDL Trados (popular CAT tool) via TMX standard. We already published article about this. You can read it here. However, recently an user reported, he can’t import to Trados TMX file exported by Sisulizer for incompatibility reason. This may occur because Trados doesn’t support the value *all* as source culture attribute, [...]
Sisulizer – New row timestamps features in localization project
Timestamps columns Since Build 331 Sisulizer’s scan feature adds date & time to new, and changed rows. This new functionality gives you full control on all changes made in source files during localization process. Before build 331, Sisulizer could mark only new items or changed items detected during scan, but it didn’t give you any [...]
How to validate required strings and custom placeholders?
Sometimes developers want to keep some important items untranslated.Your product’s name is a good example. The name may be in your string ressource, but typically the name is a trademark, and it should not be translated at all. Take a look at the following string: “SUPERCLEANER is very easy to use”. SUPERCLEANER is the name [...]
How to indicate in project which items are imported by context and by value?
We often show By context first then by value as most powerful and flexible import method. With this method Sisulizer tries first to import by context, and if no match exists, it imports by value. This combines the merits of By context (more appropriated results) and By value (more translated items) methods. Usually, items imported by context [...]
