I can't tell if it's a good idea but having a seperate repository should lead to some crucial changes, the only way it will be possible is this:

This repository will have only the translations with a POT/PO file from the original project (will be updated every couple of hours).

This repository will include only the English source and all the translations, once in a while (Every month or week) the changes will be merged back as one commit, the problem is I'm not sure git will enable that...

It's like having a seperate module outside Wine tree...

Kind regards,

Yaron Shahrabani

<Hebrew translator>

On Mon, Mar 19, 2012 at 11:52 AM, Michal Čihař <michal@cihar.com> wrote:

jects where I use Weblate I don't consider this as an issue
as merging commits would probably cause more problems than it would
solve. With current approach, you simply merge weblate branch to master
and everything works nicely. With some sort of merging of commits
things get more complex.

For example for merging in intermediary repository you need to rebase
weblate's working repository and keep possible changes made meanwhile.
I'm not saying it can not be solved, but changing Git history (what
merging of commits actually is) can be tricky.