Curse

I have a new alpha version on the project site:

http://www.wowace.com/addons/grid-status-raid-debuff/files/

That reduces the need for libBabble translations.  It no longer requires libBabble translations at all if you just use debuff detection in GridStatusRaidDebuff.   If you use a debuff library like GridStatusRD_Cata it requires the correct zone translation in libBabble to be able to load that zone into GridStatusRaidDebuff, but boss names no longer need to be translated for functionality (although they will show up in English in the debuff list if they are not translated).

As I only have access to the English client, if someone who is currently having issues can give it a try and please let me know if it helps, that would be much appreciated.

I went ahead and marked r300 as release as it does seem to help at least for anyone running debuff detection.

Are you sure "Âme des dragons" is correct for French?  According to wowhead "L'Âme des dragons" is correct.   r24 was the alpha version I was talking about, it was updated to release status when 4.3 came out.

You may want to contribute the correct translations to libBabble:

http://www.wowace.com/addons/libbabble-zone-3-0/localization/frFR/?page=30

This seems to be a common issue if you are running in a language that is currently missing libBabble translations.  I have uploaded an alpha version that I hope solves this issue for most users.  The new version only requires a translated zone (and no longer boss names) in libBabble if you are using a debuff library (like GridStatusRD_Cata).  If you use not using a debuff library, the new version should not require libbabble translations at all.

Please give the alpha version 300 a try and let me know if it solves the problems or not, as I don't have access to a non-English WoW client I am limited in the testing I can do for other languages.

If I ever do a rewrite of this addon, I'll definitely do it that way.  I've had the same idea.  However, the current addon has no support for doing it that way.

If on a specific fight, you really want to monitor a separate buff, you can add the debuff manually to Grid and then assign it to that icon slot on Grid and then disable the debuff in GridStatusRaidDebuff. 

Unfortunately, I don't have a better suggestion for now.

Just as an fyi, this addon is dependent on libbabble-zone and libbabble-boss and gives lua errors until they are updated for a new patch.  As of this moment, those libraries still haven't been updated for patch 4.3.  I had a working and updated version of GridStatusRaidDebuff and GridStatusRD_Cata that worked on the PTR for 4.3 when I manually edited libbabble-zone and libbabble-boss to add the new zone and bosses.

I may have to do some editing to match up the names of bosses with how they are entered into libbabble-boss (like if it is just the boss's name or whether the full title is used) once they are released.  New debuff detection won't work and will likely give lua errors until those libraries are updated.

Hopefully a new version of libbabble-zone and libbabble-boss come out some time today for the patch.  If you want to work around it some work is involved until those libraries are updated, debuff detection will work if you just add "Dragon Soul" to the BaseTranslations and your language if non-English in libbabble-zone.  If you want to use GridStatusRD_Cata download the alpha version from

http://wow.curseforge.com/addons/gridstatusrd_cata/files/

and edit the GridStatusRD_Cata.toc, uncomment DragonSoul.lua by removing the "#" then you will need to open up the DragonSoul.lua and look at how the bosses are entered and then add them to libbabble-boss library under BaseTranslations and your language if non-English.

Sorry for the inconvenience, but I just took over maintenance of this addon and it was designed to use those libraries and I haven't had time to do a redesign to eliminate them (they don't ever seem to update until after the patch hits).

If they aren't updated today, I'll try to at least get some work arounds in to remove any lua errors, but it's kind of pointless to add code to work around non-updated libraries if they do end up getting updated today.