Changes between Version 30 and Version 31 of LocalisingEraser


Ignore:
Timestamp:
4/25/2010 2:16:29 PM (4 years ago)
Author:
Joel (IP: 220.255.7.247)
Comment:

Fixed some expression and grammar issues.

Legend:

Unmodified
Added
Removed
Modified
  • LocalisingEraser

    v30 v31  
    1515 
    1616---- 
    17 == Creating new localizations == 
     17== Creating new localisations == 
    1818If you are starting on a new localisation, you need to create a new .resx file to contain the strings used in the Eraser source tree. For this, you need the csgettext.exe binary (attached, digitally signed) and you need to run this at the Eraser Solution directory: 
    1919 
     
    3333 
    3434---- 
    35 == How localize __Strings__ == 
     35== How to localise Strings == 
    3636You'll find Strings.''xx''.resx files in the following projects: 
    3737 
     
    4040 * Eraser.Manager 
    4141 
    42 Localizing these files it's really simple: 
    43  
    44  * open file in !VisualStudio.NET (with simple double clickover the file) 
    45  * A form (see picture below) is showed with 3 (three) columns in the following order (column names are provided in english as a reference): 
    46    1. Name: source language string 
    47    2. Value: __target language string__ (initially set to "(Untranslated)") 
     42Localising these files is simple: 
     43 
     44 * Open the file in Visual Studio.NET (double clicking the file) 
     45 * A form (see picture below) is shown with three columns in the following order (column names are provided in English as a reference): 
     46   1. Name: ''source'' language string 
     47   2. Value: ''target'' language string (initially set to "(Untranslated)") 
    4848   3. Comment: a comment string 
    49  * change the value in the second column with the translated string 
     49 * Change the value in the second column with the translated string 
    5050 
    5151[[Image(wiki:LocalisingEraser:Strings.PNG)]] 
    5252 
    53  
    54 At the end of Build phase you will get a summary of translation in the Output window such the following: 
     53At every project build phase, you will be provided with a summary of the status of translations in the Output window such the following: 
    5554 
    5655{{{ 
     
    5958C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\Eraser6\Eraser\\.\Strings.it.resx: 73 strings, 71 translated, 2 untranslated, 97% complete. 
    6059}}} 
    61 It's then possbile to identify rows related to the language in translation and see if work complete or not. 
    62 [[BR]] 
    63 [[BR]] 
     60It is thus possible to determine the level of completeness of every localisation. 
     61 
    6462---- 
    6563[[Image(Forms&Controls.PNG,align=right,nolink,180)]] 
    66 == How localize __Forms__ and __Custom Controls__ == 
    67 [[BR]] 
    68 Each form has a number of controls that shows text and then that can be localized.[[BR]][[BR]] 
    69 Localization process is basically constituted by: 
    70  1. Choosing form language property as the target localization language (as in the picture on the right) 
    71  2. Choose, by a single click, the form object that required to be localized (it can be a Label, by example) 
    72  3. Select ''Text'' property of the object 
    73  4. Change the value of the property ''Text'' 
    74  5. Repeat from 2 to 4 for each control require licalization 
    75  
    76 Below follows details for each form actually included in the project.[[BR]] 
     64== How to localise Forms and Custom Controls == 
     65Each form has a number of controls that shows text and then that can be localised. 
     66 
     67The localisation process comprises: 
     68 1. Choosing the form's '''Language''' property as the target locale (shown in the screenshot on the right.) 
     69 2. Clicking the form object that requires localisation (it can be a Label, for example.) 
     70 3. Selecting the '''Text''' property of the object. 
     71 4. Changing the value of the '''Text''' property. 
     72 5. And repeating steps 2 through 4 for each control requiring localisation. 
     73 
     74The following section describes the controls that require localisation. 
     75[[BR]] 
    7776[[BR]] 
    7877[[BR]]