[vdr] VDR-core's texts in plugin's .pot files

Darren Salt linux at youmustbejoking.demon.co.uk
Sun Aug 19 15:14:21 CEST 2007


I demand that Matthias Becker may or may not have written...

> plugins can re-use VDR-core translations. With the old "i18n.c" method
> plugin authors just did not provide a plugin specific translation for these
> texts.

> With the new translation method identifying these text got harder for
> plugin translators. xgettext puts all texts into the .pot file - also the
> texts for which the VDR-core translation should be used. A translator now
> cannot see which texts he has to translate and which not.

> Can this be improved?

Each plugin has to handle its own translations and ensure that they're in its
own translation domain. This means that its makefile has to run xgettext,
generate .mo files and install them. Translation has to be done (for
plugin-specific text) using dgettext() and dngettext() instead of gettext()
and ngettext().

[snip]
-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Travel less. Share transport more.           PRODUCE LESS CARBON DIOXIDE.

If at first you don't succeed, you're doing about average.



More information about the vdr mailing list