|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| In a Moodle User meeting here in Finland we talked about the possibility of translating strings directly from the user interface. Short texts are sometimes hard to translate without the user interface context. Locating the spots where the text is used can be cumbersome. Some web application have the option of translating strings "on the fly": when you see a screen with untranslated information, you could go into "translation mode" and then click on a string to translate it. Ajax could handle this quite unobtrusively, but it would require that the output functions produce the exact name and module of the string (as html tag attributes for example) that the Ajax translation functions can use. These extra strings make the pages heavier so they should be produced only in the "translation mode". --[[User:Samuli Karevaara|Samuli Karevaara]] 01:28, 29 April 2008 (CDT)
| | {{Moved_to_dev_docs}} |
Latest revision as of 05:49, 15 September 2011
