WoW:Localizing an addon: Difference between revisions

Typo fixing, typos fixed: softwares → software, german → German, english → English (4) using AWB
m (replace SeeAlso, Replaced: SeeAlso → AlsoSee AWB)
(Typo fixing, typos fixed: softwares → software, german → German, english → English (4) using AWB)
Line 7: Line 7:
         -- things for the french client
         -- things for the french client
     else
     else
         -- for the rest, usually english since it's the default language
         -- for the rest, usually English since it's the default language
     end
     end


Line 25: Line 25:
     <Script file="GatherIcons.lua"/>
     <Script file="GatherIcons.lua"/>


If this is a modification on an existing addon and you want to submit it to the author, it's better to use english for the variables names and to prefix them with the addon name (to prevent conflicts with existing variables from the game or from other addons), keep the original strings and put them in variables too so that the author can match them with his original code (don't forget to comment).
If this is a modification on an existing addon and you want to submit it to the author, it's better to use English for the variables names and to prefix them with the addon name (to prevent conflicts with existing variables from the game or from other addons), keep the original strings and put them in variables too so that the author can match them with his original code (don't forget to comment).


Example:
Example:
Line 54: Line 54:
         GATHERER_TRADE_MINING="Minage";
         GATHERER_TRADE_MINING="Minage";
     else
     else
         -- default, english
         -- default, English
         GATHERER_TRADE_HERBALISM="Herbalism";
         GATHERER_TRADE_HERBALISM="Herbalism";
         GATHERER_TRADE_MINING="Mining";
         GATHERER_TRADE_MINING="Mining";
Line 103: Line 103:


For a list of codes corresponding to various accentuated characters see
For a list of codes corresponding to various accentuated characters see
http://www.allegro-c.de/unicode/zcodes.htm (page is in german but the table allows to find what's needed quite easily).
http://www.allegro-c.de/unicode/zcodes.htm (page is in German but the table allows to find what's needed quite easily).


For our earlier chest example, a string that will match the ingame data would look like:
For our earlier chest example, a string that will match the ingame data would look like:
Line 130: Line 130:
In order to edit any text file in utf-8, you need a text editor which supports utf-8. By default, the normal encoding for text files is usually iso8859-1. Some older editors might use the ANSI character set instead though.
In order to edit any text file in utf-8, you need a text editor which supports utf-8. By default, the normal encoding for text files is usually iso8859-1. Some older editors might use the ANSI character set instead though.


My preference in text file editing goes to [http://www.editpadpro.com/editpadlite.html EditPad Lite]. By default, it edits using the ANSI charset, but it can convert the whole buffer to UTF-8 using the Convert/Unicode/ANSI->UTF-8 function. There are of course lots of other commercial softwares around which are able to save files in UTF-8 encoding.
My preference in text file editing goes to [http://www.editpadpro.com/editpadlite.html EditPad Lite]. By default, it edits using the ANSI charset, but it can convert the whole buffer to UTF-8 using the Convert/Unicode/ANSI->UTF-8 function. There are of course lots of other commercial software around which are able to save files in UTF-8 encoding.


== The single quote case ==
== The single quote case ==
Line 156: Line 156:


Example:  
Example:  
zone names in english clients (UK and US) for Kalimdor continent:
zone names in English clients (UK and US) for Kalimdor continent:
     Ashenvale, Azshara, Darkshore, etc.
     Ashenvale, Azshara, Darkshore, etc.


Anonymous user