How To...

We use our native language in source files, while our translators require English resources. Should I re-build all source files?

No, you do not need it if you use Sisulizer to localize your files, because Sisulizer has implemented a feature for using in project a so called “alternative original” language. Usually English is the best choice for original language because it is likely that you can find much more translator from English to your target language as for example from French to your target languages. By setting alternative original language to some other than none Sisulizer does not show the original strings in the original column but translated string in the selected language. This makes it possible to change the translator language pair suitable for your translator.

You can set up alternative original via context menu of “Original” column’s header, or via “Project” menu -> “Options” -> “Alternative Original”.

Project options

If your translator uses Sisulizer for translation of your application, you can set up alternative original also in “Exchange Wizard”, so when translator opens your project, he should to see alternative original in “Original” column. This setting is independent of alternative original setting in your project. However, I don’t recommend send project with alternative original without review it in your native Sisulizer’s project.

Exchange options

You can find alternative original setting also in “Export Wizard”. This setting depends on alternative original’s setting of your project. So, if your project doesn’t use alternative original, this option is not active in Export Wizard. Using this setting can be useful if your translator use other localization tools, or if you would like create your own localization repository for future using (e.g. as CSV or TMX files). For example if you change “real” language of your source files, you can quickly import translations for this changed original language from these external files.

Export options


1. When you use alternative language, in Original column header is displayed name of alternative language

Alternative original column header

2. When you use alternative language, Sisulizer’s filters related to text filtering (Sheet Filter -> Text tab) work with alternative original instead original. For example if you select “Translated strings compared to originals” -> “Identical”, Sisulizer compares contents of currently edited translation column with alternative original language contents.

3. You can use as alternative original only translation languages already added to your Sisulizer’s project

4. You should remember this feature doesn’t switch original language of your source.


5 replies on “We use our native language in source files, while our translators require English resources. Should I re-build all source files?”

What a nice blog.

I use delphi 7 and i want to renew my corrent application.

For each language i have seperate txt files which look like this.

{!beginSec Diag}
StringHello := ‘hello’;

When I select an other new language another file the strings are overwritten like in the example above.

Now i want to use dll files for each language.

Can someone please tell me how to start? Are there any examples?

I appreciate any help.

Kind regards.


But i don’t want to use Sisulizer. Is it then still helpfull?

I want to use it for my current project in delphi 7 does that work aswell regarding the pdf?

The articles in our blog target mainly Sisulizer users. You might be able to adapt the knowledge found on our website to other tools as well, but with Sisulizer it is much easier and faster.

Leave a Reply