![]() ![]() Rather than finding (or using) a by its name, you could instead use its item id: 6948. Avoid using text that would be localized by the client. This method has a disadvantage: you'll end up distributing and maintaining massive lists of localizations, only a small subset of which is only ever useful to a particular user. This would involve maintaining a list of translations to all supported languages of all translatable strings which your addon requires for instance, you could keep the information that "Frostbolt" is called "Frostblitz" in german, and "Ледяная стрела" in Russian. Localize all text that would be localized by the client. Ignore the whole problem Your addon will work for the locale it was written for, somewhat limiting its target audience. There are three main approaches to solving this problem: This should in theory enable any addon to run on any WoW client however if the addon relies on the names of spells, abilities, NPCs, items, professions, or even the text or format strings of system messages, it may not function properly when those are translated to another language. ![]() The World of Warcraft API stays consistent across all client localizations - all the normal API functions are available regardless of the client's locale. 2.4 Character Encoding in World of Warcraft. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |