Recent changes to Plugins translation

Plugins translation modified by Alexey T.

Alexey T. — Sun, 02 Nov 2014 20:52:38 -0000

--- v6
+++ v7
@@ -7,19 +7,33 @@

   Language | Suffix   
   -------- | ------
+  Arabic | Ar
+  Chinese Simplified | Chs
+  Chinese Traditional | Cht
+  Czech | Cz
+  Danish | Da 
+  Dutch | Dut
   English | En
-  Russian | Ru
+  Finnish | Fi
+  French | Fr
   German | De
-  French | Fr
+  Greek | Gr  
+  Hebrew | Heb
+  Hungarian | Hu
   Italian | It
-  Spanish | Sp
-  Czech | Cz
-  Hungarian | Hu
   Japanese | Jp
   Korean | Kr
-  Simplified Chinese | Chs
-  Traditional Chinese | Cht
-
+  Norwegian | Nor
+  Polish | Pol
+  Portuguese | Pt
+  Portuguese Brazil | PtBr
+  Russian | Ru
+  Slovakian | Sk
+  Slovenian | Slo
+  Spanish | Sp
+  Swedish | Sw
+  Turkish | Tk
+  
 Files must have INI format, with UTF-8 encoding. BOM not required, but if you add BOM, make sure you added an empty line at file start.

 Files must contain single section "L" with keys list. For example:

Plugins translation modified by Alexey T.

Alexey T. — Sat, 26 Apr 2014 20:06:43 -0000

--- v5
+++ v6
@@ -1,4 +1,4 @@
-To translate a plugin, you need to make sure plugin does support translation (i.e., Python plugin uses `msg_local` function, and binary plugin uses [cActionGetMsg] action), and then you need to create lang-files.
+To translate a plugin (make sure plugin supports the translation API), you need to create lang-files.

 Lang-files must be placed in the same folder as plugin files:

@@ -20,7 +20,9 @@
   Simplified Chinese | Chs
   Traditional Chinese | Cht

-Lang-files must have INI format with UTF-8 encoding (BOM not required). They must contain single section "L" with keys list. For example:
+Files must have INI format, with UTF-8 encoding. BOM not required, but if you add BOM, make sure you added an empty line at file start.
+
+Files must contain single section "L" with keys list. For example:

     [L]
     id1=Some name

Plugins translation modified by Alexey T.

Alexey T. — Sun, 22 Dec 2013 11:17:40 -0000

--- v4
+++ v5
@@ -1,6 +1,9 @@
-To translate a plugin, you need to make sure plugin does support translation (ie. it uses [cActionGetMsg] action to read UI strings), and then you need to create lang-files.
+To translate a plugin, you need to make sure plugin does support translation (i.e., Python plugin uses `msg_local` function, and binary plugin uses [cActionGetMsg] action), and then you need to create lang-files.

-Lang-files must be placed in the same folder as plugin DLL file. If plugin filename is "NNNN.dll", then lang-file names must be "NNNN.Suffix.lng", where "Suffix" depends on language:
+Lang-files must be placed in the same folder as plugin files:
+
+* For Python plugins: lang-file names must be "Suffix.lng", where possible values of "Suffix" are listed below.
+* For binary plugins: if plugin filename is "Some.dll", then lang-file names must be "Some.Suffix.lng".

   Language | Suffix   
   -------- | ------
@@ -11,8 +14,11 @@
   Italian | It
   Spanish | Sp
   Czech | Cz
+  Hungarian | Hu
   Japanese | Jp
+  Korean | Kr
   Simplified Chinese | Chs
+  Traditional Chinese | Cht

 Lang-files must have INI format with UTF-8 encoding (BOM not required). They must contain single section "L" with keys list. For example:

WikiPage Plugins translation modified by Alexey T.

Alexey T. — Thu, 15 Nov 2012 10:36:30 -0000

--- v3
+++ v4
@@ -1,6 +1,6 @@
 To translate a plugin, you need to make sure plugin does support translation (ie. it uses [cActionGetMsg] action to read UI strings), and then you need to create lang-files.
 
-Lang-files must be placed in the "Plugins\\Lang" subfolder of SW folder. If plugin filename is "NNNN.dll", then lang-file names must be "NNNN.Suffix.lng", where "Suffix" depends on language:
+Lang-files must be placed in the same folder as plugin DLL file. If plugin filename is "NNNN.dll", then lang-file names must be "NNNN.Suffix.lng", where "Suffix" depends on language:
 
   Language | Suffix   
   -------- | ------