Desktop file translations #3

This is the first example of using the tde_create_translated_desktop macro to create desktop files translated using PO files – see TDE/tde-common-cmake#33.

The translations were separated from the original desktop file into separate PO files. POT template for desktop file was created. The desktop file in the source code now contains no translations and these are merged during build.

Hi Slavek, a few notes.

lane numbers in .pot/.po files seems to be off by one
in pot/po files we lose the context of the string. For example in the original desktop file we have something like "GenericName" or similar to explain what a string is. In the new pot/po files, this info is lost making the translation more difficult. It would be good if we can add the context as a comment before the string
as previously discussed on IRC, we will have lot of po files since now each desktop file will end up in a long list of po files

We can discuss further on IRC

Hi Slavek, a few notes.

lane numbers in .pot/.po files seems to be off by one

Yes, I know - this is probably a bug in xgettext. So far I have not searched whether the bug is already reported and corrected on upstream. I use the Debian version - 0.19.8.1.

in pot/po files we lose the context of the string. For example in the original desktop file we have something like "GenericName" or similar to explain what a string is. In the new pot/po files, this info is lost making the translation more difficult. It would be good if we can add the context as a comment before the string

This is also a question of xgettext and its possibilities. I can try to build a newer upstream version. The second option would be not to use the ability to process desktop files in xgettext and create your own desktop file preparation to extract strings.

as previously discussed on IRC, we will have lot of po files since now each desktop file will end up in a long list of po files

Yes, there will be many files. As we have already discussed, this seems to be the only viable way to maintain the correct context for translation.

At the same time, users using Weblate do not have to worry about the number of PO files or their specific location. They simply translate the respective component. And there it seems good to have the belonging of the individual component to a single desktop file.

We can discuss further on IRC

For point 2, if xgettext can't do what we need we should consider do some scripts/code ourselves

Great, now it looks good!