It's not a bug in the script, it's the way the selection is computed by path-to-selection. I thought there would be a workaround by asking the script to keep the path of individual letters and then adding each of them to the selection, but the script has a real bug in that area. Looks like I'm in for a new version

Yaaaay !

EDIT:

here is another idea:
would it be possible to add info to the layer information, as G'MIC does ?
so that i can look up what values i used

you know doing the text around the angular path took a lot of effort, to find the right values
and if i ever want to come back to the effect, i will have to do it all over again
but if i had the information stored in the layer-information line, that would make life a lot easier

I'd definitely wanna try that thanks for making a tutorial.

Please, what kerning means?

http://en.wikipedia.org/wiki/Kerning

@Carlos, Here is an example of kerning. When you want to make your spacing wider between your text, use the arrows beside the kerning tool.

Technically, this widget only changes the spacing, which applies to all letters. With kerning some pairs of letters receive a different spacing ("AV" being the canonical example). There is code in TAP to obtain the kerning defined by the font using fairly devious ways.

When too narrow, the kerning is jokingly known as "keming".

Of course you can obtain keming if you select individual letters