First, many thanks to those who have contributed translations of the gretl "online" help files. Second point, it's time to (re-)explain the mechanism for getting such translations activated, which I'm afraid is not totally transparent. By way of background, I'm talking about translations of the XML files gretl_commands.xml and genr_funcs.xml, which live in the doc/commands subdirectory of the gretl source tree. Translations of these are named with an interpolated two-letter language code, as in genr_funcs_it.xml gretl_commands_pt.xml These files are used as "raw material" for building the marked-up text shown under /Help/Command reference and /Help/Function reference in the GUI program; they can also be used in other ways. Our mechanism for actually showing translations to the user depends on "translations" of the names of the generated help files, to be found (or not) in the relevant .po files. The full set of English help files (for both commands and functions, and for both the GUI and CLI programs) is as follows: gretlcli.hlp gretlcmd.hlp gretlgui.hlp genrcli.hlp genrgui.hlp To activate translations these entries in gretl.pot should be "translated" as in, for example, gretlcli.hlp -> gretlcli.hlp.it gretlcmd.hlp -> gretlcmd.hlp.pt (that is, add the appropriate two-letter extension). In current git, I've ensured that these filenames are translated for the pt files. But if a translator wants to "mask" a translated helpfile ("not really ready yet") it should be enough to enter a null translation in the .po file, e.g., genrgui.hlp -> genrgui.hlp and users will be shown the English-language version. Allin