Split FAQ into 2 parts due to string truncation. Update esES with new strings.

2008-11-01 22:27:43 +08:00
parent fb1d9f352a
commit 717d351ce0
9 changed files with 117 additions and 18 deletions
@@ -226,6 +226,8 @@ L["Right"] = "Rechts"
 -- FAQ
 L["Help File"] = "Hilfe"
 L["A collection of help pages"] = "Eine Sammlung von Hilfestellungen"
+L["FAQ Part 1"] = true
+L["FAQ Part 2"] = true
 L["Frequently Asked Questions"] = "Häufig gestellte Fragen"
 L["Warrior"] = "Krieger"

@@ -259,7 +261,8 @@ Die Blizzard Threat API gibt keine Bedrohungsdaten zurück wenn Sie nicht im dir
 There is no way around this limitation short of us doing the guessing for you (which is exactly how Omen2 did it).

 The goal of Omen3 is to provide accurate threat data, we no longer intend to guess for you and in the process lower your FPS. Have some confidence in your pet/tank, or just wait 2 seconds before attacking and use a low damage spell such as Ice Lance so that you can get initial threat readings.
-
+]]
+L["GENERAL_FAQ2"] = [[
 |cffffd200Can we get AoE mode back?|r

 Again, this is not really possible without guessing threat values. Blizzard's threat API only allows us to query for threat data on units that somebody in the raid is targetting. This means that if there are 20 mobs and only 6 of them are targetted by the raid, there is no way to obtain accurate threat data on the other 14.