Another problem is that there is no boundary character between the tab and the "Rear Combination Lamp" part, so the regex won't be applied. Your regular expression is good, it's just that the tab special character \t is not supported (it's treated as a literal character 't'). Sorry about the late reply, just getting back from the holidays. If you fill all three fields, you get a rule that works with both new and fuzzy segments and that checks for the existence of the first field's pattern in the source segment before replacing the third field's content in the target segment. In most rules filling two fields is enough to get the desired effect. I also see that the third field need not be entered? In my attempts I wasįilling the third field as well and perhaps it was blocking it from working.
You can have both of the rules active at the same time, if you want to use the hyphen replacement in both new and fuzzy segments. Replacement need to be entered the other way round? That's right, for fuzzy match replacement you specify the pattern to be replaced in the third field and the replacement in the second field. That for it to work in fuzzy matches the pattern being replaced and the Your regex for new segment works, thanks. If that's the case, you can enter the rules in the editor (with concordance search key) or restart Studio (I think there might a bug in 2011, everything works fine in 2009). You might want to add another rule covering those cases as well, if it's necessary.īy the way, if you are using 2011 the Reload files button may not work. In that case the complex regexp won't be used, as there is no string of non-spaces before the space. One exception is a segment starting with a hyphen surrounded by spaces. These rules should take care of most cases. This rule works only with new segments, if you want to convert hyphens in fuzzy matches, also add this rule: In the second field the hyphen is converted to n-dash but the rest of match is copied as it is. The regex in the first field matches strings of non-spaces followed by a space, hyphen a space and another string of non-spaces. The second rule is more complicated but only converts hyphens between two spaces: The drawback is that the rule is applied for every hyphen surrounded by word boundary characters, so some hyphens might be incorrectly changed (this is probably fairly rare, though). Since TermInjector applies each rule to every string surrounded by spaces (or other word boundary characters), all hyphens surrounded by spaces will be turned into n-dashes both in constructed proposal and fuzzy proposals. You can do this with two different rules. I don't mind doing support, it's good to know there are people giving TermInjector a try.
0 kommentar(er)
