Author Topic: Translating Components  (Read 5832 times)


  • New member
  • *
  • Posts: 7
Translating Components
« on: May 15, 2008, 01:37:02 pm »
Hi, I am trying to provide translations for my project, and I am able to (by following the wiki), create po files and translate resourcestrings in the code.  However, the automatic po file generation seems to create some entries at  the top of the po file with the captions etc for the components, eg button captions, label captions etc like so for example:

Code: [Select]
msgid "Test App"
msgstr ""

These do not seem to be read in along with the resourcestring ones.  
I have tried both:

Code: [Select]
TranslateUnitResourceStrings('main', PODirectory + 'i18n.%s.po', Lang, FLang)

which works, and:

Code: [Select]
TranslateUnitResourceStrings('TFRMMAIN', PODirectory + 'i18n.%s.po', Lang, FLang)

as an attempt to get it working, in case this is what it expects, but this does not seem to work.

So, my question essentially is - is this possible or do I need to create resourcestrings for all of the component captions etc. and then set them at FormCreate?  If this is the case then why do the Lazarus tools create these entries at the top of the po files??



  • Hero Member
  • *****
  • Posts: 597
  • Lazarus original cheetah.The cheetah doesn't cheat
RE: Translating Components
« Reply #1 on: May 21, 2008, 04:44:19 pm »
Is it possible to translate my apps through .po files? Post the wiki link please


TinyPortal © 2005-2018