On Mon, 2005-09-26 at 17:39 +1000, Peter Moulder wrote:
The rest of the UI appears localized.
I believe this is because those strings don't appear anywhere in the source code (other than in one big string of XML in menus-skeleton.h), and consequently these strings aren't appearing in the po files.
Yeah, and I'm not sure what to do with the problem. It is the same one that we have with the .inx files, but I think this comes to a different solution. I'm thinking about making the whole XML file translatable... I realize that this has some issues, let me try to put pros and cons here:
Cons - Translators have to know and create valid XML in a particular format - Translators can significantly change the menu layout in Inkscape, and may create usability issues. - I really wanted to make it so that Effects would dynamically modify the internal XML for menu placement, that'd be impossible if all menus are not direct translations (which isn't always reasonable, see below)
Pros - All strings can be translated - Menus can be moved with the translation. I'm having a hard time trying to explain this, and I think it is partially because I'm basically mono-lingual. Here's my best effort. Let's say Inkscape had a "Free" menu where we had things that were zero cost and personal freedoms (I'm trying here). If you were to translate this into Spanish directly, the menu would have to be the "Gratis y libre" menu. It would make more sense in a Spanish translation to have two menus.
I'm not sure how the pros and cons weigh out here, I'd love to know what other people think. I think the 0.43 fix is to add "N_()" to the strings in menu-skeleton.h, which I think will still cause them to concatenate (anyone know?)
--Ted