Changes between Version 4 and Version 5 of BluePrint/Translation

Timestamp:

03/12/12 11:15:07 (13 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Translation

@@ -5 +5 @@
 
 == Changes to the core translation functionality ==
-The standard web2py function should be extended to support an optional comment, ideally this would be done with the call to T() but a alternative separated solution may be acceptable.
+The standard web2py function should be extended to support an optional comment, ideally this would be done with the call to T() but an alternative solution may be acceptable.
 
-When an instance of Sahana-Eden is deployed it may require translation, if this is during an emergency their may not be a lot of time and so only a select subset of strings need to be translated. This subset might be the front facing part of the deployment or it may include just the modules that have been deployed. However, when the files for translation are created their is no link back to the code and so it is difficult to know where the string came from. What is required is for the function to extract the location of the string this can then be used to determine which module the string belongs to. This functionality may have several iterations but with the final goal of being able to download strings for translation that belong to various modules, this might involve a UI that allows the translation administrator to select which modules (or parts) of the system they want to translate.
+When an instance of Sahana-Eden is deployed it may require translation, if this is during an emergency there may not be a lot of time and so only a select subset of strings need to be translated. This subset might be the front facing part of the deployment or it may include just the modules that have been deployed. However, when the files for translation are created there is no link back to the code and so it is difficult to know where the string came from. What is required is for the function to extract the location of the string this can then be used to determine which module the string belongs to. This functionality may have several iterations but with the final goal of being able to download strings for translation that belong to various modules, this might involve a UI that allows the translation administrator to select which modules (or parts) of the system they want to translate.
 
 == Round-trip translation UI ==
-The journey from a untranslated string to a translated one can involve several different tools and can take different paths. The idea here is to integrate these tools (so this is not ''really'' about replacing them) into a single portal. One such route is as follows:
+The journey from an untranslated string to a translated one can involve several different tools and can take different paths. The idea here is to integrate these tools (so this is not ''really'' about replacing them) into a single portal. One such route is as follows:
  * Extract the strings from Eden
  * build a spreadsheet that can be given to the translators
@@ -17 +17 @@
 Then the code changes and a string needs to be modified. At this point the person managing the translation doesn't specifically know that a string is no longer required and so redundant strings hang around in the translated files (and some that may not yet have been translated which have since been superseded are still awaiting translation)
 
-A second, and different, approach to translating the string it to use the Pootle tool, the integration of this would be nice but the key area is to be able to identify the strings for translation.
+A second, and different, approach to translating the string is to use the Pootle tool, the integration of this would be nice but the key area is to be able to identify the strings for translation.
 
 Once the strings for translation have been identified then the UI needs to provide a seamless mechanism to integrate them back into Sahana-Eden.
+
 == Technical help ==
 For the translation process see the chapter in the book on [http://en.flossmanuals.net/sahana-eden/localisation/ Localisation]
-For the translation code see web2py gluon/langauges.py file
+For the translation code see {{{web2py/gluon/languages.py}}}