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
function FixLogString(str)
-- 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'.
end
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.
I'm using an frFR version of WoW.
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 function FixLogString(str) -- 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'. endI 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 ?
Thanks,
Faerian
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe problem was in LittleWigs' trigger :
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 :
to prevent ambiguity.
You need to make the trigger independant of this, like this :
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.
The solution, if I understand correctly, is just to put a "*." in the trigger string when we find a "|2" in the transcript.
I will try to see if it works and publish in the forum the correct trigger string if it works.
Thanks for your help :)
Faerian
Mot de l'ombre : Douleur de PLAYER inflige a MONSTRER 345 points de degats |2 Ombre.
The DOT is 'Mot de l'ombre : Douleur", and is not intercepted by the parser.
lines : 3286
return str:gsub("(%%%d?$?s) de (%%%d?$?s)", "%1 DE %2"):gsub("|2", "DE")don't work for this example.