For those who aren't experienced with i18n issues, this is an important one. I think that's it's helpful to see the diffs that Jon made. Please take a second to look at them, they're small.
http://inkscape.svn.sourceforge.net/inkscape/?rev=18701&view=rev http://inkscape.svn.sourceforge.net/inkscape/?rev=18702&view=rev
Thanks Jon!
On Wed, 2008-05-21 at 21:12 -0700, Jon A. Cruz wrote:
On Tue, 2008-05-20 at 14:23 +0200, Maximilian Albert wrote:
No, this time it's not an unclosed tag. At first I thought this, too, but closer investigation revealed that the string to be translated is split across several lines (because for some reason a string returned by another function is supposed to be rendered in boldface). Thus the translation tool cannot find the closing tag because it appears in a separate string.
One solution would be to move the <b> tag outside the translateable string and only mark "Color" as translateable (BTW, strings as "</b>" and "; " really shouldn't be marked translateable as they currently are in ui/dialogs/swatches.cpp, should they?). What do the translation people think?
AHA!!!
I've tracked it down and looked at the code where those strings are coming from. The root cause of the problem is bad i18n code in the source.
The source is concatenating the result of several i18n string calls. This is a big no-no, and if the code is fixed then then problems should go away out of the .po files.