Recent changes to translations

translations modified by bzame

bzame — Tue, 10 Mar 2015 14:09:49 -0000

--- v52
+++ v53
@@ -1 +1 @@
-Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. >UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. >To be sure of the result please use html fortmatting and html encoding.>
Compare two translations
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.>From WesWorkshop go to the Tool menu and select the Translations checker option.>A window will be opened. The window is vertically divided into two blocks. >
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The translations comparator is the right block, titled "Compare translations".
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The default reference is the english translation. You can change it by clicking the left button marked with an opened>folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.>To select a translation you have to select the folder containing it.>The translations comparison will begin as soon as you have set the second translation.>The tool will scan the two translations looking for differences. The translation comparison works as follow:>
The tool scans the two translation folders;
If a file is stored in the first folder but not in the second one it's signaled as an error for the second >translation: file X is missing;
If a file is stored in the second folder but not in the first one it's signaled as an error for the first t>ranslation: file X is missing;
If both translations contain the file X the tool opens the two files and checks the two key sets:
Each key stored in the first file but not in the second one is signaled as an error for the second >translation: filed Y is missing,
Each key stored in the second file but not in the first one is signaled as an error for the first >translation: filed Y is missing,
If the field is stored in both files no message is shown;
If both files have the same keys the files are signaled as ok.
>Use a translation released outside the program
If you want to add a translation which wasn't included with the program you have to follow the following steps:
copy the translation folder to your locale folder;>
edit the file locale.xml stored in the locale folder by adding the following fields before the last line >(</locale>):><language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language >(ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. >Usually translation folder names are the first three letters of the proper language name >(ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. >A complete list of available flags can be found in the >image folder, >flag file names start with "flag_".  If the language flag of the new translation is not available leave >this field empty;
</icon>;
</language>;
An example is:
<language>
 <name>Italiano</name>
 <file>ita</file>
 <icon>flag_italy.png</icon>
</language>>
+Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. To be sure of the result please use html fortmatting and html encoding.
Compare two translations
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks. 
The translations comparator is the right block, titled "Compare translations".
The default reference is the english translation. You can change it by clicking the left button marked with an openedfolder. By clicking the right button marked with an opened folder you can choose the translation to be compared.To select a translation you have to select the folder containing it.The translations comparison will begin as soon as you have set the second translation.The tool will scan the two translations looking for differences. The translation comparison works as follow:
The tool scans the two translation folders;
If a file is stored in the first folder but not in the second one it's signaled as an error for the second translation: file X is missing;
If a file is stored in the second folder but not in the first one it's signaled as an error for the first translation: file X is missing;
If both translations contain the file X the tool opens the two files and checks the two key sets:
Each key stored in the first file but not in the second one is signaled as an error for the second translation: filed Y is missing,
Each key stored in the second file but not in the first one is signaled as an error for the first translation: filed Y is missing,
If the field is stored in both files no message is shown;
If both files have the same keys the files are signaled as ok.
Use a translation released outside the program
If you want to add a translation which wasn't included with the program you have to follow the following steps:
copy the translation folder to your locale folder;
edit the file locale.xml stored in the locale folder by adding the following fields before the last line (</locale>):<language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language (ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. Usually translation folder names are the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. A complete list of available flags can be found in the image folder, flag file names start with "flag_".  If the language flag of the new translation is not available leave this field empty;
</icon>;
</language>;
An example is:
<language>
 <name>Italiano</name>
 <file>ita</file>
 <icon>flag_italy.png</icon>
</language>

translations modified by bzame

bzame — Tue, 10 Mar 2015 14:06:44 -0000

--- v51
+++ v52
@@ -1 +1 @@
-Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. >UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. >To be sure of the result please use html fortmatting and html encoding.>
Compare two translations
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.>From WesWorkshop go to the Tool menu and select the Translations checker option.>A window will be opened. The window is vertically divided into two blocks. >
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The translations comparator is the right block, titled "Compare translations".
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The default reference is the english translation. You can change it by clicking the left button marked with an opened>folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.>To select a translation you have to select the folder containing it.>The translations comparison will begin as soon as you have set the second translation.>The tool will scan the two translations looking for differences. The translation comparison works as follow:>
The tool scans the two translation folders;
If a file is stored in the first folder but not in the second one it's signaled as an error for the second >translation: file X is missing;
If a file is stored in the second folder but not in the first one it's signaled as an error for the first t>ranslation: file X is missing;
If both translations contain the file X the tool opens the two files and checks the two key sets:
Each key stored in the first file but not in the second one is signaled as an error for the second >translation: filed Y is missing,
Each key stored in the second file but not in the first one is signaled as an error for the first >translation: filed Y is missing,
If the field is stored in both files no message is shown;
If both files have the same keys the files are signaled as ok.
>Use a translation released outside the program
If you want to add a translation which wasn't included with the program you have to follow the following steps:
copy the translation folder to your locale folder;>
edit the file locale.xml stored in the locale folder by adding the following fields before the last line >(</locale>):><language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language >(ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. >Usually translation folder names are the first three letters of the proper language name >(ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. >A complete list of available flags can be found in the >image folder, >flag file names start with "flag_".  If the language flag of the new translation is not available leave >this field empty;
</icon>;
</language>;
An example is:
<language>
 <name>Italiano</name>
 <file>ita</file>
 <icon>flag_italy.png</icon>
</language>>
+Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. >UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. >To be sure of the result please use html fortmatting and html encoding.>
Compare two translations
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.>From WesWorkshop go to the Tool menu and select the Translations checker option.>A window will be opened. The window is vertically divided into two blocks. >
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The translations comparator is the right block, titled "Compare translations".
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The default reference is the english translation. You can change it by clicking the left button marked with an opened>folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.>To select a translation you have to select the folder containing it.>The translations comparison will begin as soon as you have set the second translation.>The tool will scan the two translations looking for differences. The translation comparison works as follow:>
The tool scans the two translation folders;
If a file is stored in the first folder but not in the second one it's signaled as an error for the second >translation: file X is missing;
If a file is stored in the second folder but not in the first one it's signaled as an error for the first t>ranslation: file X is missing;
If both translations contain the file X the tool opens the two files and checks the two key sets:
Each key stored in the first file but not in the second one is signaled as an error for the second >translation: filed Y is missing,
Each key stored in the second file but not in the first one is signaled as an error for the first >translation: filed Y is missing,
If the field is stored in both files no message is shown;
If both files have the same keys the files are signaled as ok.
>Use a translation released outside the program
If you want to add a translation which wasn't included with the program you have to follow the following steps:
copy the translation folder to your locale folder;>
edit the file locale.xml stored in the locale folder by adding the following fields before the last line >(</locale>):><language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language >(ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. >Usually translation folder names are the first three letters of the proper language name >(ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. >A complete list of available flags can be found in the >image folder, >flag file names start with "flag_".  If the language flag of the new translation is not available leave >this field empty;
</icon>;
</language>;
An example is:
<language>
 <name>Italiano</name>
 <file>ita</file>
 <icon>flag_italy.png</icon>
</language>>

translations modified by bzame

bzame — Tue, 10 Mar 2015 14:04:07 -0000

--- v50
+++ v51
@@ -1,88 +1 @@
-Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

-                            

-                            Which result is shown depends on the translated file char encoding. 
-                            UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. 
-                            To be sure of the result please use html fortmatting and html encoding.
-                        
-                    
-                    
-                        Compare two translations
-                        

-                            From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.
-                            From WesWorkshop go to the Tool menu and select the Translations checker option.
-                            A window will be opened. The window is vertically divided into two blocks. 
-                        
-                        
-                        
-                            The translations comparator is the right block, titled "Compare translations".

-                        
-                        
-                        
-                            The default reference is the english translation. You can change it by clicking the left button marked with an opened
-                            folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.
-                            To select a translation you have to select the folder containing it.
-                            The translations comparison will begin as soon as you have set the second translation.
-                            The tool will scan the two translations looking for differences. The translation comparison works as follow:
-                            

-                                The tool scans the two translation folders;
-                                If a file is stored in the first folder but not in the second one it's signaled as an error for the second 
-                                    translation: file X is missing;
-                                If a file is stored in the second folder but not in the first one it's signaled as an error for the first t
-                                    ranslation: file X is missing;
-                                If both translations contain the file X the tool opens the two files and checks the two key sets:
-                                
-                                Each key stored in the first file but not in the second one is signaled as an error for the second 
-                                    translation: filed Y is missing,
-                                Each key stored in the second file but not in the first one is signaled as an error for the first 
-                                    translation: filed Y is missing,
-                                If the field is stored in both files no message is shown;
-                                
-                                If both files have the same keys the files are signaled as ok.
-                            
-                        

-                        
-                    
-                    
-                        Use a translation released outside the program
-                        
If you want to add a translation which wasn't included with the program you have to follow the following steps:
-                        
-                            
-                                copy the translation folder to your locale folder;
-                            
-                            
-                                edit the file locale.xml stored in the locale folder by adding the following fields before the last line 
-                                (</locale>):
-                                
-                                    <language>;
-                                    <name>;
-                                    language proper name, this value will be shown in the locale menu. Use the proper name of the language 
-                                        (ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
-                                    </name>;
-                                    <file>;
-                                    translation file name, use the folder name or your translation won't be loaded. 
-                                        Usually translation folder names are the first three letters of the proper language name 
-                                        (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
-                                    </file>;
-                                    <icon>;
-                                    the name of the flag file, this is used to set the icon of the language in the locale menu. 
-                                        A complete list of available flags can be found in the 
-                                        image folder, 
-                                        flag file names start with "flag_".  If the language flag of the new translation is not available leave 
-                                        this field empty;
-                                    </icon>;
-                                    </language>;
-                                
-                            
-                        
-                        An example is:
-                        
-                            <language>

-                             <name>Italiano</name>

-                             <file>ita</file>

-                             <icon>flag_italy.png</icon>

-                            </language>
-                        
-                    
-                
+Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. >UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. >To be sure of the result please use html fortmatting and html encoding.>
Compare two translations
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.>From WesWorkshop go to the Tool menu and select the Translations checker option.>A window will be opened. The window is vertically divided into two blocks. >
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The translations comparator is the right block, titled "Compare translations".
class="default" height="400px" width="auto" style="margin-left: auto; margin-right: auto; clear: both">The default reference is the english translation. You can change it by clicking the left button marked with an opened>folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.>To select a translation you have to select the folder containing it.>The translations comparison will begin as soon as you have set the second translation.>The tool will scan the two translations looking for differences. The translation comparison works as follow:>
The tool scans the two translation folders;
If a file is stored in the first folder but not in the second one it's signaled as an error for the second >translation: file X is missing;
If a file is stored in the second folder but not in the first one it's signaled as an error for the first t>ranslation: file X is missing;
If both translations contain the file X the tool opens the two files and checks the two key sets:
Each key stored in the first file but not in the second one is signaled as an error for the second >translation: filed Y is missing,
Each key stored in the second file but not in the first one is signaled as an error for the first >translation: filed Y is missing,
If the field is stored in both files no message is shown;
If both files have the same keys the files are signaled as ok.
>Use a translation released outside the program
If you want to add a translation which wasn't included with the program you have to follow the following steps:
copy the translation folder to your locale folder;>
edit the file locale.xml stored in the locale folder by adding the following fields before the last line >(</locale>):><language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language >(ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. >Usually translation folder names are the first three letters of the proper language name >(ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. >A complete list of available flags can be found in the >image folder, >flag file names start with "flag_".  If the language flag of the new translation is not available leave >this field empty;
</icon>;
</language>;
An example is:
<language>
 <name>Italiano</name>
 <file>ita</file>
 <icon>flag_italy.png</icon>
</language>>

translations modified by bzame

bzame — Tue, 10 Mar 2015 14:01:45 -0000

--- v49
+++ v50
@@ -1,21 +1,4 @@
-Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from the SourceForge project wiki.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.

-                            
-                                VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.
-                            An example:

-                            Original:

-                            Choose which specials are associated to this attack.

-                            Translated (it):

-                            <html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>

-                            Result:

-                            Scegli quali specialità sono associate a questo attacco.

-                            

-                            Without the html encoding the result is not assured. The same example can produce different results:

-                            Without html (it):

-                            Scegli quali specialit&agrave; sono associate a questo attacco.

-                            Result (bad parsing):

-                            Scegli quali specialit¿ù? sono associate a questo attacco.

-                            Result (good parsing):

-                            Scegli quali specialità sono associate a questo attacco.

+
Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from http://wesworkshop.altervista.org/translation.php.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.
VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

                             

                             Which result is shown depends on the translated file char encoding. 
                             UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing.

translations modified by bzame

bzame — Tue, 10 Mar 2015 13:58:43 -0000

--- v48
+++ v49
@@ -1,29 +1,105 @@
-Translations
-This page is divided into three sections:
-How to create a new translation;
How to use a translation released outside the program;
Check locale folder;
Compare two translations;
Published translations
-
-
-Create a new translation
-Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-). Copy the folder you have chosen and translate each file.
-Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded.
-To add a completed translation read the next paragraph.
-VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html. An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. To be sure of the result please use html fortmatting and html encoding.
-
-
-Use a translation released outside the program
-
-If you want to add a translation which wasn't included with the program you have to follow the following steps:copy the translation folder to your locale folder;
edit the file locale.xml stored in the locale folder by adding the following fields before the last line (</locale>):
<language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language (ex. English -> English,   German -> Deutch,   Italian -> Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. Usually translation folder names are the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. A complete list of available flags can be found in the image folder, flag file names start with "flag_". If the language flag of the new translation is not available leave this field empty;
</icon>;
</language>.
-
-An example is:
-<language>
-<name>Italiano</name>
-<file>ita</file>
-<icon>flag_italy.png</icon>
-</language>
-
-
-
-Published translations
-The following translation are already available:
-
English (available with the program distribution);
Italian (available with the program distribution);

-
+Published Translations
The following translations are already available:
English (English)*
Italian (Italiano)*
Starred elements are distributed with the program.
How to...
Check the translations folder;
Create a new translation;
Compare two translations;
Use a translation released outside the program;
Note: the following paragraphs have been copied from the SourceForge project wiki.
Check the translation folder
From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.From WesWorkshop go to the Tool menu and select the Translations checker option.A window will be opened. The window is vertically divided into two blocks.
The translations folder checker is the left block, titled "Check translations folder".
The translations folder checking process scans the locale.xml file and the translations folder.It signals as error languages registered in the locale.xml file with no corresponding folder.Languages folder extra files are signaled as errors too. Non ini files are signaled as errors too. Languages folder sub-directories which are not registered in the locale.xml file are signaled as warnings.
By default the tool checks WesWorkshop locale folder. You can change the checked translations by clicking the button marked with an opened folder. The scan process starts as soon as you have selected a folder.
Create a new translation
Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-). Copy the folder you have chosen and translate each file. Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded. To add a completed translation read the next paragraph.

+                            
+                                VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html.
+                            An example:

+                            Original:

+                            Choose which specials are associated to this attack.

+                            Translated (it):

+                            <html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>

+                            Result:

+                            Scegli quali specialità sono associate a questo attacco.

+                            

+                            Without the html encoding the result is not assured. The same example can produce different results:

+                            Without html (it):

+                            Scegli quali specialit&agrave; sono associate a questo attacco.

+                            Result (bad parsing):

+                            Scegli quali specialit¿ù? sono associate a questo attacco.

+                            Result (good parsing):

+                            Scegli quali specialità sono associate a questo attacco.

+                            

+                            Which result is shown depends on the translated file char encoding. 
+                            UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. 
+                            To be sure of the result please use html fortmatting and html encoding.
+                        
+                    
+                    
+                        Compare two translations
+                        

+                            From v1.2 -Black Pawn- you can compare two translations. This option has been thought to help translators.
+                            From WesWorkshop go to the Tool menu and select the Translations checker option.
+                            A window will be opened. The window is vertically divided into two blocks. 
+                        
+                        
+                        
+                            The translations comparator is the right block, titled "Compare translations".

+                        
+                        
+                        
+                            The default reference is the english translation. You can change it by clicking the left button marked with an opened
+                            folder. By clicking the right button marked with an opened folder you can choose the translation to be compared.
+                            To select a translation you have to select the folder containing it.
+                            The translations comparison will begin as soon as you have set the second translation.
+                            The tool will scan the two translations looking for differences. The translation comparison works as follow:
+                            

+                                The tool scans the two translation folders;
+                                If a file is stored in the first folder but not in the second one it's signaled as an error for the second 
+                                    translation: file X is missing;
+                                If a file is stored in the second folder but not in the first one it's signaled as an error for the first t
+                                    ranslation: file X is missing;
+                                If both translations contain the file X the tool opens the two files and checks the two key sets:
+                                
+                                Each key stored in the first file but not in the second one is signaled as an error for the second 
+                                    translation: filed Y is missing,
+                                Each key stored in the second file but not in the first one is signaled as an error for the first 
+                                    translation: filed Y is missing,
+                                If the field is stored in both files no message is shown;
+                                
+                                If both files have the same keys the files are signaled as ok.
+                            
+                        

+                        
+                    
+                    
+                        Use a translation released outside the program
+                        
If you want to add a translation which wasn't included with the program you have to follow the following steps:
+                        
+                            
+                                copy the translation folder to your locale folder;
+                            
+                            
+                                edit the file locale.xml stored in the locale folder by adding the following fields before the last line 
+                                (</locale>):
+                                
+                                    <language>;
+                                    <name>;
+                                    language proper name, this value will be shown in the locale menu. Use the proper name of the language 
+                                        (ex. English ⇒ English, German ⇒ Deutch, Italian ⇒ Italiano);
+                                    </name>;
+                                    <file>;
+                                    translation file name, use the folder name or your translation won't be loaded. 
+                                        Usually translation folder names are the first three letters of the proper language name 
+                                        (ex. English ⇒ eng, Deutch ⇒ deu -German-, Italiano ⇒ ita -Italian-);
+                                    </file>;
+                                    <icon>;
+                                    the name of the flag file, this is used to set the icon of the language in the locale menu. 
+                                        A complete list of available flags can be found in the 
+                                        image folder, 
+                                        flag file names start with "flag_".  If the language flag of the new translation is not available leave 
+                                        this field empty;
+                                    </icon>;
+                                    </language>;
+                                
+                            
+                        
+                        An example is:
+                        
+                            <language>

+                             <name>Italiano</name>

+                             <file>ita</file>

+                             <icon>flag_italy.png</icon>

+                            </language>
+                        
+                    
+

translations modified by bzame

bzame — Sun, 08 Mar 2015 17:55:47 -0000

--- v47
+++ v48
@@ -1,6 +1,6 @@
 Translations
 This page is divided into three sections:
-How to create a new translation;
How to use a translation released outside the program;
Published translations
+How to create a new translation;
How to use a translation released outside the program;
Check locale folder;
Compare two translations;
Published translations
 

 Create a new translation

translations modified by bzame

bzame — Sat, 28 Feb 2015 08:30:05 -0000

--- v46
+++ v47
@@ -7,6 +7,7 @@
 Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-). Copy the folder you have chosen and translate each file.
 Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded.
 To add a completed translation read the next paragraph.
+VERY IMPORTANT: if your string contains non ascii characters (such as accented letters) format the string using html. An example:
Original:
Choose which specials are associated to this attack.
Translated (it):
<html>Scegli quali specialit&agrave; sono associate a questo attacco.</html>
Result:
Scegli quali specialità sono associate a questo attacco.

Without the html encoding the result is not assured. The same example can produce different results:
Without html (it):
Scegli quali specialit&agrave; sono associate a questo attacco.
Result (bad parsing):
Scegli quali specialit¿ù? sono associate a questo attacco.
Result (good parsing):
Scegli quali specialità sono associate a questo attacco.

Which result is shown depends on the translated file char encoding. UTF encoding will lead to bad parsing, ASCII encoding will lead to good parsing. To be sure of the result please use html fortmatting and html encoding.

 
 Use a translation released outside the program

translations modified by bzame

bzame — Fri, 16 May 2014 16:52:10 -0000

--- v45
+++ v46
@@ -1,15 +1,15 @@
-Translations
+Translations
 This page is divided into three sections:
 How to create a new translation;
How to use a translation released outside the program;
Published translations
 

-Create a new translation
+Create a new translation
 Creating new translations is quite easy. Go to your locale folder and choose the folder from which you will translate. The folders are named using the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-). Copy the folder you have chosen and translate each file.
 Each folder contains some ini files. Each file contains rows like key=value. To make your own translation you have to change the strings value. You mustn't change the key value nor the file names because your strings would not be loaded.
 To add a completed translation read the next paragraph.

 
-Use a translation released outside the program
+Use a translation released outside the program

 If you want to add a translation which wasn't included with the program you have to follow the following steps:copy the translation folder to your locale folder;
edit the file locale.xml stored in the locale folder by adding the following fields before the last line (</locale>):
<language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language (ex. English -> English,   German -> Deutch,   Italian -> Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. Usually translation folder names are the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. A complete list of available flags can be found in the image folder, flag file names start with "flag_". If the language flag of the new translation is not available leave this field empty;
</icon>;
</language>.

@@ -22,7 +22,7 @@
 

 
-Published translations
+Published translations
 The following translation are already available:
 
English (available with the program distribution);
Italian (available with the program distribution);

translations modified by bzame

bzame — Sat, 05 Apr 2014 07:06:41 -0000

--- v44
+++ v45
@@ -22,5 +22,7 @@
 

 
-Published translations
Work in progres... :)
+Published translations
+The following translation are already available:
+
English (available with the program distribution);
Italian (available with the program distribution);

translations modified by bzame

bzame — Sat, 05 Apr 2014 07:04:00 -0000

--- v43
+++ v44
@@ -11,7 +11,7 @@
 
 Use a translation released outside the program

-If you want to add a translation which wasn't included with the program you have to follow the folloing steps:copy the translation folder to your locale folder;
edit the file locale.xml stored in the locale folder by adding the following fields before the last line (</locale>):
<language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language (ex. English -> English,   German -> Deutch,   Italian -> Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. Usually translation folder names are the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. A complete list of available flags can be found in the image folder, flag file names start with "flag_". If the language flag of the new translation is not available leave this field empty;
</icon>;
</language>.
+If you want to add a translation which wasn't included with the program you have to follow the following steps:copy the translation folder to your locale folder;
edit the file locale.xml stored in the locale folder by adding the following fields before the last line (</locale>):
<language>;
<name>;
language proper name, this value will be shown in the locale menu. Use the proper name of the language (ex. English -> English,   German -> Deutch,   Italian -> Italiano);
</name>;
<file>;
translation file name, use the folder name or your translation won't be loaded. Usually translation folder names are the first three letters of the proper language name (ex. English -> eng,   Deutch -> deu -German-,   Italiano -> ita -Italian-);
</file>;
<icon>;
the name of the flag file, this is used to set the icon of the language in the locale menu. A complete list of available flags can be found in the image folder, flag file names start with "flag_". If the language flag of the new translation is not available leave this field empty;
</icon>;
</language>.

 An example is:
 <language>