About: Tool Evaluation

In this section it will be discussed which tool should be taken for the i18n work.

What should the tool be able to do

Tasks

The tools we should analyse have several tasks:

• find the strings into the source code and extract them
• find "information" about specific formats (time, measure units,...) in the code
• give the possibility to translate in a friendly environment
• replace the string with a function(string) construct

Here you'll find the advantages and drawbacks of every tool we evaluate.

Writing our own tools

That could be a good idea to write our own tools to do these tasks, in particular for a distributed translation (everybody can help on internet). With this I mean a little website that allows us to do the actual translation directly via the web, and it should automatically create the new version of the language file to be downloaded from all the users.

Another thing that this tool can do for us is scanning the entire source code looking for new translations to be done, and propose them to the users... can be interesting because we than only have to click on a link and all the work (not the translations) is done for us.

Advantages

• independent from the architecture
• independent from the language file format

Drawbacks

• can be a lot of work

Problems, Ideas, Further Development

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)
• A 2nd 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
• Unicode problem