Comment 11 for bug 171007

That's great.

I have just been updating the extension to handle replacements within selections only. Here are some answers to your questions:

1) Despite my saying that replacements for the font-family and -inkscape-font-specification were made independently, i.e. it will replace none, either or both, regardless of the other. It *should* be that it counts any replacement for each element (either or both style attributes) as just the one replacement. If this is not what you're seeing, could you post an svg file for me to test with and I'll see what's going wrong? thanks.

Of course for tspan elements and other text objects that can be nested, it will always look like one replacement per element, even if there are many elements per line (entirely possible). Perhaps this is what's happening for you, if you're seeing more replacements than there should be? I'm not sure of the best way around this, I think if it's something I can't improve on much, it might be a case of removing the substitution count altogether, bad information is worse than no information.

2) I just tried importing a PDF file that was created elsewhere (a DHL shipping label), and it replaced the text successfully. With the caveat that it was full of manual kerns, as documented at this bug: https://bugs.launchpad.net/inkscape/+bug/188794

I also tried page 1 of the PDF ebook "The Joy of Clojure", again text replacement worked fine - apart from kerning issues.

Sorry - I don't have any AI or other files to test, just PDF at the moment.

3) I've updated the code so that actions that have no effect (listing all fonts, replacing specific fonts where there were none of that font found) do not dirty the document.

PS: I found another text element that can be styled: flowSpan