2008/12/11 Ted Gould wrote:

Okay,

So I think I just committed everything to make it so that filters.svg is translatable. Since I'm not a translator, it's hard to be 100% sure. Could a translator please try to translate the filters and reply?

He couldn't :)

avp@...998...:~/soft/svn/inkscape/po$ intltool-update -pot xgettext: error while opening "./../share/filters/filters.svg.h" for reading: No such file or directory ERROR: xgettext failed to generate PO template file. Please consult error message above if there is any.

Alexandre

2008/12/11 Ted Gould wrote:

Hmm, I don't know a way to work around this, but I think you're going to have to build inkscape before building the inkscape.pot. I don't think that this is a huge problem as the pot file isn't built regularly.

Well, we were asked multiple times to actually make regular updates of inkscape.pot :)

So if you do:

$ cd inkscape/trunk $ make $ cd po $ make inkscape.pot

Can you try that please?

That works.

However, applied filter's name in Filter Effects dialog is still in English.

Can't say I'm a big fan of having to compile Inkscape (1-1.5 hours on my laptop) just find out if update is required, but if everybody else is fine with that, then no more bitching from me here :)

Alexandre

2008/12/12 Ted Gould wrote:

...

However, applied filter's name in Filter Effects dialog is still in English.

Okay, I'll fix that.

Thanks :)

...

Can't say I'm a big fan of having to compile Inkscape (1-1.5 hours on my laptop) just find out if update is required, but if everybody else is fine with that, then no more bitching from me here :)

I'm not happy, but I can't find another way to make the filters translatable :-/

Just a week ago bulia mentioned to me that it could be done the very same way we seem to be able to extract translatable data from markers.svg

Alexandre

On Sat, Dec 13, 2008 at 4:34 PM, Ted Gould <ted@...11...> wrote:

I don't think that we do extract data from markers... though we could do it the same way that we're extracting the data from the filters :) Bulia?

What I said was just, _if_ we extract it from markers.svg, we can do the same for filters.svg. (Also we have patterns.svg, at least.) I'm honestly not up to date on the i18n machinery, it was asking more than proposing :)

On Sun, 2008-12-14 at 22:18 +0300, Alexandre Prokoudine wrote:

ANyway, it would be handy to also have some sort of UI for saving Existing filters. E.g. choose "Save as preset" or the like in context menu in Filter Effects dialog and see a dialog like this:

Name of filter: [entry field] Hint: [entry field] Category: [combobox]

[Cancel] [OK]

And just importing filters (same Filter Effects dialog) from existing documents without saving them to $FILTERS directory would be awesome.

Well the names are the same names that you put on them in the filters editor. So at least that part is done :)

I'm curious what we should do here. I feel that the "File" menu is too cluttered but I think we should really have a "Save to Filters" and a "Save to Templates" options. I'd both of those features to be more discoverable.

--Ted

On Sun, 2008-12-14 at 11:45 -0500, bulia byak wrote:

On Sat, Dec 13, 2008 at 4:34 PM, Ted Gould <ted@...11...> wrote:

...

I don't think that we do extract data from markers... though we could do it the same way that we're extracting the data from the filters :) Bulia?

What I said was just, _if_ we extract it from markers.svg, we can do the same for filters.svg. (Also we have patterns.svg, at least.) I'm honestly not up to date on the i18n machinery, it was asking more than proposing :)

So, are we generally happy with the i18n of filters.svg? Should I do the same for markers?

--Ted