I was doing a Shadow Labyrinth having LittleWigs running and I notice that "bombs" aren't announce on our first try.
I put transcript on to verify the string in LittleWigs. What I discovers is that a lot of announce have the word "de" change to "|2" in the transcript stopping recognition in LittleWigs (and perhaps other addon).
After doing a full string search on my addon directory I find this string ("|2") in Parser-3 :
elseif CurrentLocale == "frFR" then
-- de is the main seperator
return str:gsub("(%%%d?$?s) de (%%%d?$?s)", "%1 DE %2"):gsub("|2", "DE")
-- ckknight note: I may use 'd', 0-width character, 'e' instead of 'DE'.
I don't know what this do, but this mislead detection in other addon such as LittleWigs and perhaps BigWigs and others. More competent person than me could perhaps correct the problem ?
touch_trigger = "^([^%s]+) ([^%s]+) les effets de Toucher de Marmon."
When a log parser library is loaded (being Parser-1.1, Parser-3.0, SW_FixLogString or FixLogString), it changes the corresponding log string to :
touch_trigger = "^([^%s]+) ([^%s]+) les effets DE Toucher de Marmon."
to prevent ambiguity.
You need to make the trigger independant of this, like this :
touch_trigger = "^([^%s]+) ([^%s]+) les effets .* Toucher de Marmon."
Edit: To be complete on the subject :
This pattern is not ambiguous. The wow client does not use "de" or "DE" but the strange string "|2". This is done on purpose, so that it is correctly changed into "de" or "d'" if the first letter of the following name is a vowel. (i.e. : "Vous subissez les effets d'Attaque mentale" instead of "Vous subissez les effets de Attaque mentale").
So why does Parser-3.0 change this ? It's most probably because SW_FixLogStrings (part of SW_Stats) does it, and it's more simple to do the same transformation.