Changes between Version 30 and Version 31 of LocalisingEraser

Timestamp:

4/25/2010 2:16:29 PM (3 years ago)

Author:

Joel (IP: 220.255.7.247)

Comment:

Fixed some expression and grammar issues.

LocalisingEraser

@@ -15 +15 @@
 
 ----
-== Creating new localizations ==
+== Creating new localisations ==
 If 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:
 
@@ -33 +33 @@
 
 ----
-== How localize __Strings__ ==
+== How to localise Strings ==
 You'll find Strings.''xx''.resx files in the following projects:
 
@@ -40 +40 @@
  * Eraser.Manager
 
-Localizing these files it's really simple:
-
- * open file in !VisualStudio.NET (with simple double clickover the file)
- * A form (see picture below) is showed with 3 (three) columns in the following order (column names are provided in english as a reference):
-   1. Name: source language string
-   2. Value: __target language string__ (initially set to "(Untranslated)")
+Localising these files is simple:
+
+ * Open the file in Visual Studio.NET (double clicking the file)
+ * A form (see picture below) is shown with three columns in the following order (column names are provided in English as a reference):
+   1. Name: ''source'' language string
+   2. Value: ''target'' language string (initially set to "(Untranslated)")
    3. Comment: a comment string
- * change the value in the second column with the translated string
+ * Change the value in the second column with the translated string
 
 [[Image(wiki:LocalisingEraser:Strings.PNG)]]
 
-
-At the end of Build phase you will get a summary of translation in the Output window such the following:
+At every project build phase, you will be provided with a summary of the status of translations in the Output window such the following:
 
 {{{
@@ -59 +58 @@
 C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\Eraser6\Eraser\\.\Strings.it.resx: 73 strings, 71 translated, 2 untranslated, 97% complete.
 }}}
-It's then possbile to identify rows related to the language in translation and see if work complete or not.
-[[BR]]
-[[BR]]
+It is thus possible to determine the level of completeness of every localisation.
+
 ----
 [[Image(Forms&Controls.PNG,align=right,nolink,180)]]
-== How localize __Forms__ and __Custom Controls__ ==
-[[BR]]
-Each form has a number of controls that shows text and then that can be localized.[[BR]][[BR]]
-Localization process is basically constituted by:
- 1. Choosing form language property as the target localization language (as in the picture on the right)
- 2. Choose, by a single click, the form object that required to be localized (it can be a Label, by example)
- 3. Select ''Text'' property of the object
- 4. Change the value of the property ''Text''
- 5. Repeat from 2 to 4 for each control require licalization
-
-Below follows details for each form actually included in the project.[[BR]]
+== How to localise Forms and Custom Controls ==
+Each form has a number of controls that shows text and then that can be localised.
+
+The localisation process comprises:
+ 1. Choosing the form's '''Language''' property as the target locale (shown in the screenshot on the right.)
+ 2. Clicking the form object that requires localisation (it can be a Label, for example.)
+ 3. Selecting the '''Text''' property of the object.
+ 4. Changing the value of the '''Text''' property.
+ 5. And repeating steps 2 through 4 for each control requiring localisation.
+
+The following section describes the controls that require localisation.
+[[BR]]
 [[BR]]
 [[BR]]