Translating again...

[dietmar]

Hi,

http://wiki.freepascal.org/Step-by-step_instructions_for_creating_multi-language_applications

does not cover how to translate MessageDlg or others.
Does anyone know how to translate the message and the buttion captions?

Thx,
Dietmar

[RAW]

QuestionDlg is multilang able, isn't it?

Just a guess... 

EDIT:
http://wiki.lazarus.freepascal.org/Translations_/_i18n_/_localizations_for_programs#Translating_at_start_of_program

[wp]

You must copy the translations of lclstrconsts.po (in (lazarus)/lcl/languages) to the languages folder of your project. And you must be sure that the strings in unit lclstrconsts are translated - this happens automatically if unit LCLTranslator is in the uses clause of the project.

For a test, try the demo in (lazarus)/examples/translation. Copy the lclstrconsts.*.po from lcl/languages to examples/translation/languages. Compile, run and click on the "What did you select" button which opens a message box.

[dietmar]

Thx for the quick help!

Dietmar

[dietmar]

Hmmm...

do I have to merge the lclstrconsts.*.po into my app.*.po?

And how do I translate the "free text" in the message dialog, like "Do you want to quit?" or whatever?

Sorry if I bother you,
Dietmar

[wp]

No problem. I would not recommend to merge individual po files into a common po file because it is more difficult to maintain the new file. So, just copy lclstrconsts*.po into the folder which contains your project language files app.*.po. Note also that there may be other packages which have their own translation files. If you use TAChart, for example, you should know that it has its own translations in the folder (lazarus)/components/tachart/languages - you should copy its tachartstrconsts.*.po in the same way as you did with lclstrconsts. etc. And in the routine which switches the language for you you must manually trigger translation of the strings by calling one of the TranslateUnitResourcestrings procedures in unit Translations.

The "free text", I suppose, is the text that is displayed in the messagebox? Standard messages such as "The file does not exist" (or similar) are already translated. Look in unit lclstrconsts (or corresponding other language unit) and find the name of the resource string constant which you can use in your application. In above-mentioned example you would find the resource string rsfdFileNotExist = 'The file "%s" does not exist.' - the "%s" tells you that you must pass the filename in a Format instruction:

Code: Pascal  [Select][+][-]

1. uses
2.   lclstrconsts;
3.  
4. procedure OpenFile(AFileName: String);
5. begin
6.   if not FileExists(AFileName) then begin
7.     MessageDlg(Format(rsfdFileNotExist, [AFileName], mtError, [mbOK], 0);
8.     exit;
9.   end;
10.   ...

[dietmar]

Hm... whether I copy all the lclstrconsts.*.po files to the example/language directory or not, it does not change anything when I click the mentioned button. It just displays "None selected" in the chosen language.

What should change when I add the lclstrconsts files?

Dietmar

[wp]

No idea what you are doing wrong here. I just repeated my test with Laz 1.6.4/fpc3.02 (the version of your signature, 32-bit and 64-bit) where the lclstrconsts never had been in the translations directory. I copied the files to this folder, compiled the demo project, selected a non-English language, and the messagedlg was in the translated language.

[jc99]

IMHO the .po files are for editing, to make the executeble use them they have to be compiled to .mo files. Did you compile all .po files to .mo ?

[dietmar]

I don't think the .mo files are necessary.

@wp: The MessageDlg in my example is translated correct, although I don't have the lclstrconsts.* installed... so it looks the same behaviour.

Dietmar