At first, I put in some checking so that '[' and ']' characters in a regular expression will always be escaped, which I think should be ok in the envisaged scenarios. So, if an escape is accidentally left off, it will be automatically restored. Woof commit:
Then I tracked down exactly what caused the problem that rodin.s experienced, and fixed it. Woof commit:
Comments:Posted on 25 Nov 2012, 7:28 by BarryK
Commit 'b85f127121' reverted
I decided to revert commit 'b85f127121', as I am not 100% certain about side-effects.
The other commit is the essential one, that fixes the bug the rodin.s reported.
Posted on 25 Nov 2012, 23:53 by rodin.s
0setup and SSS
I have made translation for 0setup and it stopped working after being translated with error:
/usr/local/petget/0setup: line 9: syntax error: unterminated quoted string
I found it myself with help of geany syntax highlighting. One quote was missing at the end of line 370. I added that quote and script seems to be working now. But I cannot put this translation into langpack because automatic translation will break the script. I guess I put translated script itself into langpack.
One thing about sed translation. It works strange.
It translates what it shouldn't and point replaces any character (lines 638, 639).
Posted on 25 Nov 2012, 24:32 by rodin.s
0setup and SSS
I guess I have fixed it. I have removed dot after "success" (line 71 script_strings):
Actually I removed it from translation file script_strings.ru. Now langpack installation doesn't break 0setup.
Posted on 26 Nov 2012, 7:56 by BarryK