I made <option>, <_option>, <item> and <_item> all work. The underscored ones will be translated, the non-underscored ones won't. Please test if this is really the case.
Johan
-----Original Message----- From: Ted Gould [mailto:ted@...11...] Sent: dinsdag 13 november 2007 19:56 To: Engelen, J.B.C. (Johan) Cc: jcoswell@...1414...; alexandre.prokoudine@...400...; inkscape-devel@lists.sourceforge.net; aaron@...749... Subject: RE: [Inkscape-devel] perfect bound cover
On Tue, 2007-11-13 at 19:44 +0100, J.B.C.Engelen@...1578... wrote:
Ted Gould:
Yes, there is a problem. The "_option" is required for
gettext to
know that the string should be translated by translators.
It's not
required for the code, it's required to pull the string
out into the
.po file.
Should both <option> and <_option> be allowed and have the same functionality? Or should I remove <option>, such that all
options will
be translatable? (such that the extension developer cannot make the mistake of having it untranslatable?)
I've left both in, for the argument that it gives control further down the line. I think that there are some cases where you wouldn't want it translatable, I'm not sure if they're all good cases, but I don't see it as a bad thing to leave. If nothing else, all the other parameters allow it as much for backwards compatibility as anything.
--Ted