GNOME Bugzilla – Bug 398067
plugin.in files are not localized
Last modified: 2009-08-15 18:40:50 UTC
The plugin.in files contain translatable strings, but the files are not recognized by intltool-update, therefore they can not be translated. Adding the files to potfiles.in doesn't solves the problem, also the existing makefile.am macros don't seem to work, as the manually added translations to hu.po are not used in plugin.in files.
(In reply to comment #0) > The plugin.in files contain translatable strings, but the files are not > recognized by intltool-update, therefore they can not be translated. Adding the > files to potfiles.in doesn't solves the problem, also the existing makefile.am > macros don't seem to work, as the manually added translations to hu.po are not > used in plugin.in files. > So what do you suggest we do?
Well, after a little more investigation, i have found that the problem is not serious at all. After renaming a plugin.in file to plugin.desktop.in, the translation process worked fine: messages appeared in hu.po and after translating them and make, they were merged back to plugin.desktop. So, the solution is trivial now. The files must be renamed, the plugin parsing should be changed to search for renamed files and they must be added to POTFILES.in.
Thanks for your investigation, Gabor. But isn't there a better way? Such as writing an autoconf macro or something? Calling a file .desktop when it is not could be a source of huge problem later. Everyting that parses .desktop expects it to be a Desktop file. Our .plugin files, although uses the same format, is not even remotely similar to Desktop files. I would prefer to wait for a better solution.
I have found bug #319609, which says there is a better way: adding some tags to the beginning of lines does the trick. Attaching patch.
Created attachment 80897 [details] [review] Add plugin.in files to POTFILES.in, with type: tags
Created attachment 80898 [details] [review] Corrected patch The plugins/project-wizard/templates/anjuta-plugin/src/plugin.plugin.in file is not a "real" plugin, removing it.
Thanks! that's much better :). Committed.
Closed all old bugs since last release