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 :)
But I don't know how hard it would be to change .inx DTD, Ted's solution may well be the best for now.
It isn't as much hard, as I'm looking for the "right" solution. Here's what I see as issues right now.
Goal: Localize webpages for help menus.
Issues:
1) Need to figure out the locale that Inkscape is running in. 2) Need to find out if the webpage is even translated into that locale.
I was hoping that we could have a generic way to handle 1 that would avoid having the translators have more work. But, in thinking more about it, I think the really hard problem is 2. It is totally possible with that Inkscape could be running in a locale that doesn't have translated webpages.
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.
--Ted