Difference between revisions of "Internationalization/tool evaluation"
(→Tool Evaluation) |
(→Par2) |
||
| Line 8: | Line 8: | ||
* another database can be placed on the user's pc and autoupdate eiffel and the additional content one may have when needed (when a new version of Eiffel or a new tool is available for example), with this system one doesn't need to download every time a new file containing some information already downloaded before | * another database can be placed on the user's pc and autoupdate eiffel and the additional content one may have when needed (when a new version of Eiffel or a new tool is available for example), with this system one doesn't need to download every time a new file containing some information already downloaded before | ||
| − | == | + | == Tasks == |
| + | |||
| + | The tools we should analyse have several tasks: | ||
| + | * finding the strings into the source code and extract them | ||
| + | * give the possibility to translate in a friendly environment | ||
Revision as of 02:16, 26 April 2006
About: Tool Evaluation
edited by Stian
some problems/ideas that may go with the other parts of this project as well:
- the i18n can be put online as a database that everyone can update (thus helping translation in many more languages)
- the main database can be updated as soon as something new for eiffel comes out (by updated here is meant simply adding the new messages, not their translations)
- another database can be placed on the user's pc and autoupdate eiffel and the additional content one may have when needed (when a new version of Eiffel or a new tool is available for example), with this system one doesn't need to download every time a new file containing some information already downloaded before
Tasks
The tools we should analyse have several tasks:
- finding the strings into the source code and extract them
- give the possibility to translate in a friendly environment
