I found a way. There's not documented API function that can decline names... I just found out that I have a problem with comparing same strings in UTF-8 is not always true... it's wierd, but I'm gonna find out why.
Well, the question is... Can you suggest a name for RU dedicated addon? I was about to name it Capping_ru, but I guess people will not understand that they have to install it separately. They will think that it's an addition for original capping or something. In other hand... naming it completely different will be not very good to you.
- Registered User
Member for 14 years and 2 months
Last active Fri, Oct, 4 2013 14:29:47
- 0 Followers
- 15 Total Posts
- 0 Thanks
Aug 20, 2008OK. No is no.Posted in: General AddOns
I'll make dedicated version as soon as I'll find a way to fix wsg flag keeper name for the horde side as it appears in log not in naming case.
Your addon works with russian client atm but with these: limitations:
- Timers will not be stopped for some AV towers/GYs when they are defended.
- Labels at those timers are not in naming case so they're looks like spoken by foreign languager ;)
- Nickname of the player that picked up the Alliance flag is not in naming case so it's colored white and don't targeting the player if clicked.
By now, I'll enjoy the fact that I am the only one at RU servers, who got 100% working AV timers ;)
Aug 20, 2008Ah, forgot about this feature here ;)Posted in: General AddOns
I've made "-- NEWCHANGESHERE" mark for you everywhere I made changes, so you can easly find it.
Same new table are in every other locale file, but I'll attach only ruRU one here.
Aug 19, 2008Hello again. I found a way to handle AV problem with russian client. Also this will allow to use custom labels for bars instead of fixed names that have been captured from messages.Posted in: General AddOns
But it will require to fill little table in every localization file (excepting ru and en because I did it). I've inserted templete to every locale file that has to be edited.
Everything works for me here and ready for commit, but I just want ot ask the permission to do so, as it will require additional localization work before it will be able to work for all clients.
Thank you. Waiting for an answer.
Aug 13, 2008Oh, grats on getting woltk betak key! )Posted in: General AddOns
I can't get why empty slots of the bags are colored red? Empty slots of the backpack are normal, but the slots that are in inserted bags are colored red, working fine but... I guess I made some mistake in translation of something, but can't find where exactly... Can you help?
Aug 12, 2008/cryPosted in: General AddOns
Can somebody tell me, when the addon updates with revision number with dot? like xxxxx.xx? Because usually an update like that has no changes at all. But does it means that author bumping it up to be kinda "up-to-date"? If so, how can I contact the author to add the locale? Trying to contact him for about a month now...
Aug 8, 2008Posted in: General AddOnsQuote from Saroz »
Why not just ninja the blizzard format strings? and deformat them
That's not so simple as it appears... I think it's Blizzard still didn't finish the work yet (Reinforcements counters are still bugged for example... and this is already an official release).
Let's take a simple example (I will give translit version so everyone can see it):
"Na Zapadnuyu Bashnyu Severnogo Volka napali! blablabla" - here is the name of the tower NOT in nameing case so when the horde defends it, we will have "Zapadnaya Bashnya Severnogo Volka blablabla" which is in nameing case. The problem is that the addon uses found name as an ID for the counter bar. So it will create a bar with ID "Zapadnuyu Bashnyu Severnogo Volka" but when horde defends it, addon will try to stop the bar with an ID "Zapadnaya Bashnya Severnogo Volka" and there is no such ID as you can guess, and we will have wrong timer bars...
I can see a way to fix it in creating more variables for locale. Also we'll have to separate the strings that we're catching from the messages and the ones that we're displaying at the bars, so more variables again... We can edit addon functions so it can work with our locale, but then we'll have to edit every locale translation for other languages which makes the localization process too complicated for just "localization" I guess...
P.S. Can you tell me where to ninja exact Blizzard strings exepting the manual looking in-game?
Aug 8, 2008Posted in: General AddOns
Looks like I'll have to do it, because it starts to require too many code changes for localization... like now I'm tuning AV and looks like we have to make an ID-node for every tower timer. Because this:Quote from TotalPackage »
...or you can simply make a Russian version of Capping.
node = strmatch(a1, L["avtaken"]) or strmatch(a1, L["avtaken2"]) or strmatch(a1, L["avdestroyed"]) or strmatch(a1, L["avdestroyed2"]) if node then self:StopBar(node)is not working. The name of the same tower in avunderattack message and in avtaken message are not equal because of the language specific...
Any suggestion on how to do it better? just create another addon in svn repository?
Aug 8, 2008Brrr... Sorry for so big wall of text in my last post.Posted in: General AddOns
ruRU client shows two different messages at WSG when somebody picks the flag up. When horde flag is picked up we have one message and when ally flag is picked up - another... and it's completely different... I think we need 2nd lacale variable, because there's name at different places in those messages...
Need some major changes in Capping:WSGFlagCarrier(a1) function. But Iknow that it's not very good to change the code of someone elses addon without any permission...
Aug 8, 2008Hello TotalPackage! =)Posted in: General AddOns
I am the one, who's making commits for ruRU locale. We have a little problem here ;(
As you might know, Russian language has many cases... So with Russian client Blizzard has implemented declension system (if I've translated it right). In different situations we might have names with different endings... When you create a character you have to manually edit all cases as you can see at this screenshot: http://img242.imageshack.us/img242/5459/wowscrnshot080808131950sr3.jpg
So... If we will be looking for a nickname in a message to use it for displaying flag carrier, it won't work for displaying HP-percentage, because in a message the nickname might be in different case... (Sorry for so bad and messed up explanation, but my english is kinda limited when I'm trying to explain something complicated...).
In addition Blizzard using different words for horde and alliance when displaying that flag has been captured.
-- As a possible way to fix it I can guess that it's possible to get all cases of the name in lua code? Or just to use some advanced regular expressions to catch it (then I'll have to read some about it to refresh the knowledge).
-- Also is it possible to use more than one version of the strings that we're looking for for the event?
Another thing. I found a way to catch all events at AB by catching part of the word instead of full word (remember that ending of the word can be different). But the addon uses same text for search and for displaying it... Maybe it is a good thing to separate it? Because displaying part of the word instead of full name is not very good for UI...
["Lumber Mill"] = "Лесопилк"
will work for russian client, but it's not right... the right word is "Лесопилка" (if only you can see the cyrillic... well, here is 1 letter difference)
Jul 2, 2008Hello everyone.Posted in: General Chat
As you might know, there is russian client alpha test with 3 realms are already on the fly. The test will enter beta phase with patch 2.4.3. So we have a problem with addons without ruRU locales that depends on combat log or location names or whatever else text...
Well, my question is how can we (users) cooperate with authors or maybe some people with access to svn to share translations in order to make addons compatible with russian client?
- To post a comment, please login or register a new account.