![](https://secure.gravatar.com/avatar/a56927c4a87b3293d94b3e98922e2cbe.jpg?s=120&d=mm&r=g)
On Sat, 30 Jul 2005 matiphas@...8... wrote:
Date: Sat, 30 Jul 2005 11:07:35 +0200 From: matiphas@...8... To: Ted Gould <ted@...11...> Cc: Alexandre Prokoudine <alexandre.prokoudine@...400...>, Inkscape Devel List inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] effects menu
Actually, all of the menu items are set up to look up the translation, I just haven't figured out how to get the entires into the .po files for the translators. "Grid" must be translated for something else in Inkscape, thus the translation gets picked up for the effect also. Theoretically, one could put all the Effect names in the .po files by hand and it would work, but we really need to figure out how to automate getting the entires out.[1]
--Ted
1 -- This really has to be the first step, eventually we need to be able to store translations in the .inx files themselves as they might come from other sources than the Inkscape codebase. But I have no idea how to do that at all...
Hi Ted and all,
as a translator, let me comment on this :
- I'd prefer not to split translation of extensions and core Inkscape string :
- managing one file is easier than lots of them (and I hope the number of
If extensions are ever going to get translated it will be very important to make it as easy as possible for translators.
It will also help if there are standardised user interface widgets where possible (like Script-Fu from the GIMP only better). If there are standard widgets that can be used conveniently and are pretranslated there is a better chance of developers using them and extensions having a fairly consistent user interface as much as possible. (I've always liked how consistent the plugins are in Jasc Paint Shop Pro.)
extensions will increase) - a lot of vocabulary is shared between core Inkscape and extensions
the more the better, might be good to start creating a selection of INK_STOCK for buttons, menu items, and labels.
- However, for some very short, or ambiguous strings, extensions developper
should add a context prefix to the strings (it's what it's done for)
BTW : extensions are great and fun ! Thanks to Aaron, you and some others for this.
Sincerely
Alan Horkan http://advogato.org/person/AlanHorkan/