Hi Gio,
In my Japanese environment, shorthand classes \\w and \\W cannot be used (I don't know why). But I think your regular expression is equivalent to this:
.*:\\s*(.*)
And the StringSearcher with the expression was able to extract words after the colon correctly. i.e. _matched_parts{0} = "gebakken klinkers"
How did your StringSearcher work?
Takashi
Hi Takashi,
I spent some time on the the tcl site:
"Within bracket expressions, `\\d', `\\s', and `\\w' lose their outer brackets, and `\\D', `\\S', and `\\W' are illegal"
.*:\\s*(*\\w\\s]*\\W*) works. I just had to take the \\W out of the brackets.
of course that will only get sequences up to a nonword character, dissalowing me to enter nonwordcharacter in a character class (range).
I now use
value:
@Evaluate(/regexp {.*:s*(eg:alpha:]\\s-]*)} "@Value(CLASSIFICATIE)" matched match])!=0?"$match":""
This way i dont have to use te stringsearcher, expose and and setattribute routine at all.
regexp .*:\\s*(.*) is the same, but i wanted .*:s*( b:alpha:]\\s-]*)
i mistook \\w for /:alpha:]
Apparently there is no shorthand for e:alpha:]
a tip for the fme boys.
How about not having the creator automaticaly put an evaluation on stuff one enters.
Like when i enter a concatanation in creator this way @Value(sting1)@Value(string2)..it automatticaly tries to evaluate it....
Even changing an attribute causes it to put an evaluation on it, can this be turned of?
very annoying. Im forced to go back and remove the evaluation.
"[:alpha:]" is equivalent to a frequently used character class "a-zA-Z"?
-----
If you entered "@Value(string1)@Value(string2)" using the Arithmetic Editor, indeed "@Evaluate" would be appended automatically.
Otherwise (using the Text Editor - Base / Advanced or typing directly), I don't think it would be evaluated.
Yes character class [a-zA-Z] is the same as the bracketclass [:alpha:]
But there is no shorthand for it. Shorthand is like \\w which is same as bracket t:alphanum:] including "_".