Difference between revisions of "Talk:Internationalization/tool evaluation"
| Line 12: | Line 12: | ||
I think it is only worth discussing the first category. Once we find a handy tool we can write a filter for it's file format to/from our own and use it for any "demo" localisations we produce. | I think it is only worth discussing the first category. Once we find a handy tool we can write a filter for it's file format to/from our own and use it for any "demo" localisations we produce. | ||
Ideally we should be able to export to a variety of popular formats. How does Windows do it? What are the preferred tools for localisation in the Microsoft world? [[User:Leo|Leo]] 02:11, 27 April 2006 (CEST) | Ideally we should be able to export to a variety of popular formats. How does Windows do it? What are the preferred tools for localisation in the Microsoft world? [[User:Leo|Leo]] 02:11, 27 April 2006 (CEST) | ||
| + | |||
| + | |||
| + | It would be nice to see how the VisualStudio handle this. --[[User:Carlo|Carlo]] 08:20, 27 April 2006 (CEST) | ||
Revision as of 21:20, 26 April 2006
If you have suggestions on the tool to be used contact us!
Every experience will help us a lot.
Ok, here are my thoughts: there are two sets of tools needed.
- Translation tools - they will let you edit a file containg strings/templates in a friendly manner.
- Extraction tools - they will let you pull all strings to be localised from the source code. Such a tool will possibly need to be Eiffel-specific, and we will probably have to do this ourselves.
I think it is only worth discussing the first category. Once we find a handy tool we can write a filter for it's file format to/from our own and use it for any "demo" localisations we produce. Ideally we should be able to export to a variety of popular formats. How does Windows do it? What are the preferred tools for localisation in the Microsoft world? Leo 02:11, 27 April 2006 (CEST)
It would be nice to see how the VisualStudio handle this. --Carlo 08:20, 27 April 2006 (CEST)
