Source language is Dutch, but I want to use another language for not translated items in my localized application

Sometimes developers don’t manage to receive translations for all strings in an application before their deadlines. Than the localized software is released with partially localized resources, e.g. without some messages about internal errors etc. When you build your localized file in this case your project don’t contain all translations, so Sisulizer will use the original strings in the localized file. Currently, most popular worldwide language is English and probably (if you have another language as original language in your application) your first fully translated localization is for this language. Additionally, chances are high that more of your target users in other countries speak English than your original language e.g. Dutch (Gert – I hope you aren’t angry for this opinion). So personally I think better solution in this case is using English resources instead of Dutch or German in localized application.

With Sisulizer it is possible to use above solution. Go to “Project” menu -> “Edit source” -> select your source file or right click on your source node in Project Tree and click on “Properties” item in context menu. Next, go to “Encoding” tab and select desired language from list in  “Default language” combo box (in our example English). This list contains all translation languages included to your project. Next, repeat this operation for other not fully translated sources in your project.

With this setting, Sisulizer uses the selected language for not translated items in localized file. Of course, for translated items Sisulizer uses translations in target language. If the default language doesn’t contain some translations, Sisulizer use for these items original language. If your project contains both main language and not fully translated sub-language for this same language, for example “German” and “German (Austria)”, Sisulizer automatically use for this sub-language translations from main (neutral) language. When translations not exist for main language too, Sisulizer uses translations from default language.



  1. Hi Janusz,

    I see one problem with this approach, namely you may now have a program showing three different languages to the user. For example, a translated program, targeting Spanish may have

    English: the default language you have set
    Spanish: the desired language
    Dutch: the original language (for text not yet translated to English or Spanish)

    This may be very confusing to customers.

  2. Hi Gert,

    It is a question like if the glass of water (or beer 😉 is half full or half empty. Pooh, I have no idea if this is understandable in English.

    Anyway, naturally the best option is to have everything translated in your target language. But life is not perfect.

    So the second best option is to show the text at least in a language where chances are high that user may understand it, too. In our sample this was English.

    And the last exit may be confusing for the user. But I believe you will agree that this is still better than showing no text at all.
    Sure it is way better to prevent this situation. And yes, I agree that it is preferable to have at least in the selected second language everything translated.


  3. Of course, full mug of beer 🙂 is better than half empty mug, but as Renate told “life is not perfect”, so developers often release not fully translated software. Solution with default language is imperfect, but usually English localization is first fully translated version and it allows avoid described above case with 3 UI languages.


Leave a Reply