Both solutions are good for different things. The online service for providing an interface to do translations and to make sure that every change in the english rc is also merged into the other languages. Marcs solution is to keep track of the rc files and their translation status. I think both should work together quite well. I even think that Marc's solution is kinda needed for the online translation service. Or how does it keep track of the rc files? You would probably need to update the pathes everytime you change something, like moving a module. If rbuild can produce an xml output, this wouldn't be neccesary.
How will it work if you want to add a new translation online? In the current way of handling rc files it would need to change the rsrc file, with Marc's solution it would need to change the rbuild file (at least if I understood it correctly).
If you update the English rc file online, it would be neccessary that all other .rc files are somehow marked dirty, because the file date wouldn't work anymore when the changes are merged into all other rc's.

Another advantage of Marc's solution is that it would make it possible to compile only those languages that you want. If you don't want a translation for some languages, switch them off in the config.rbuild.

Regards,
Timo

Colin Finck schrieb:

The open question would be: What happens with the already planned/prepared online translation service?

It also had a plan to improve the whole translation process, but as far as I know it differs much from your solution.

Klemens, Magnus, any comments on this?

Regards,

Colin