On Wed, 2008-04-23 at 10:52 +0100, Daniel Pope wrote:
XML provides i18n through the use of xml:lang. We could just move the inkscape:label attribute to an inkscape:label element with an xml:lang attribute specified.
Yes. The problem is connecting it into our translation infrastructure and builds. The tools don't really support it.
Then all translators need to do is open the SVG file in a different locale, rename the filters using the UI, and save it again. Each locale would only save a label xml:lang="$LANG" but when reading labels would fall back to the first label if there wasn't a label for the current locale.
This isn't really reasonable. We need the translatable strings to make it into the po files. There are a ton of tools based on this, and we don't want to loose the support of those tools.
Parameterisation is a much thornier problem. I don't think it's simply a case of asking what values to insert at which point in a filter; it's more about compiling a filter using configuration options a user specifies. That can already be done with extensions.
Correct. But since extensions aren't built into the filters, the issue becomes integrating them. I think static filters are marginally interesting, the really interesting stuff comes when you can adjust them live (Drop Shadow).
--Ted