On 2/21/07, Ted Gould <ted@...11...> wrote:
On Tue, 2007-02-20 at 22:36 +0100, Romain Thouvenin wrote:
So, even if it seems feasible (at least for linux and windows), isn't that a pity that extensions do this independently ?
Well, it's a pity that scripts have to parse the XML file too :)
Parameters are given to extensions as arguments, there's no need to parse the xml. I was thinking about a way to do that without asking the user for the value of the parameter.
I think for that, we'll have to get the translators involved in saying that the webpage is in a good state for that language. But, do we want them doing that in Inkscape itself, or on the webpage? If it was on the web with appropriate fallback, then we could "update" live, and users would get translations without having to update their Inkscape installations.
I agree we need the help of translators. Since it is possible to use gettext within a script (and it is easy to do), couldn't we include strings from extensions in po files ? In the script, we ask the browser to open _("http://.../FAQ"), and translators translate it in po files as "http://.../FrFAQ", deFAQ and so on. They do it only if there is a translation. I'll investigate that today.
Romain