gted Tutorial

Written by Pavel Mendl, 15. July 2008. Thanks a lot!

1. xgettext Keywords is name of the macro for translatable string, thus typically "_" (underscore) and NOT e.g. "gettext"
    
2. gted depends on concrete subdirectories structure:
   • [FOLDER]/po
     This is the folder configured as xgettext Output folder property
      
   • [FILE]/po/messages.pot
     gets generated/updated automatically on right-click on project (! not any project file) gted->Update PO files
      
   • [FOLDER]/po/<ISO 639-1 country code>
     e.g. /po/cs or /po/fr; create any number of them you need and copy messages.pot in renamed to messages.po
      
   • [FILE]/po/<ISO 639-1 country code>/messages.po
     Here you can do translation into actual language; gets updated (actualized) each time you use gted->Update PO files
     Yes, all of them - see resolved bug report on this
      
3. Given the above, you can configure other folder (e.g. /mo) into msgfmt Output folder property.
   You NEED NOT fill in Path to Java compiler if using for C++ (e.g. CDT) projects.
   Create the same language(s) subdirectory(ies) as below /po (did not test, if folders must exist or will be created; did not test, if you could use simply "/po" to mix .po and .mo files in same tree).
    
4. Now right-clicking on project gted->Make MO files generates one messages.mo file for each messages.po from step 2.