Many thanks to Matisk for updating most of the French translations.
We still need Spanish (EU and latin mxES) verions
and Italian.
Speaking of translations
-
bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
-
bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
Working on integrating the new French translations and saw some funky stuff from Blizzard.
No other languages have new translation updates. (sigh)
triggered an api function to display PTR RC WoW version number and UI TOC number.
Running a script macro from the chat line trigger a pop up box to warn that the script might be harmful.
Then a number of addon's that I enabled (munged the TOC to allow them to load) started failing with something like "Addon can not use protected Blizzard functions" or something like that.
the good new is CensusPlus continued running a census with no issue during this event.
This was on a prebuilt 100 level character I used for the invasion testing.
Logged out and used my copied character (used to check WoD stuff) and had no pop up or other issue when I triggered the same macro that runs the api script.
Have no clue why this happened... just thought it was odd.. i.e. normal Blizzard PTR foolishness.
No other languages have new translation updates. (sigh)
triggered an api function to display PTR RC WoW version number and UI TOC number.
Running a script macro from the chat line trigger a pop up box to warn that the script might be harmful.
Then a number of addon's that I enabled (munged the TOC to allow them to load) started failing with something like "Addon can not use protected Blizzard functions" or something like that.
the good new is CensusPlus continued running a census with no issue during this event.
This was on a prebuilt 100 level character I used for the invasion testing.
Logged out and used my copied character (used to check WoD stuff) and had no pop up or other issue when I triggered the same macro that runs the api script.
Have no clue why this happened... just thought it was odd.. i.e. normal Blizzard PTR foolishness.