Hello,

I apologize for posting this bug here, but I really didn't know where else to put it. I also doubt that this is something new, even thou I didn't find anything similar, nor did I figure out which keywords I should use to find it. So here it is.

I have two big problems with svn. They are quite simple. It takes too much space and leaves me with too much work for something so simple as updating translations is.
- I checked and found that for 16MB of *.po files in my language, I have 958MB of files on my disc. And this is only for GNOME unstable branch and few others packages. Since stable branch rarely stays stable for more than a week, I need to keep also (momentarily 2-24) older branches.
- Since every project is safely kept in it's own folder, it's really a lot of work to update them all and of course not make a mistake and copy the wrong file to the wrong folder. All the names are the same. Translators work with numerous project and do not keep only a few of them like developers, I presume.

This could be solved in a very simple manner, by introducing into the svn tree another project called "translations". Folders inside this project would be country codes of different languages in which all HEAD po files of the projects that specific language was added to, is present. If accerciser was ever translated in *de*, the folder would have this file. If nobody ever tried to translate it to *sv* the sv folder would not have that file. The project would also have only one ChangeLog.
Translator would easily update the files and the submit them to the server, there a nice little script that one of you developers would make :) , could check the consistency of the changed files and if everything is ok, another nice little script would automatically copy and rename the files to their original project folders. If the language folder would hold also the latest *.pot, it would be perfect.

If the project is located at accerciser/trunk/po/, the file name would simply be accerciser.trunk.po.

I'm sure there are cons to this, but I see many, many pros.
- less space on the local machine
- less bandwidth consumption
- faster updating
- faster translation synchro of words in all the projects
- no multiple ChangeLogs for minimal changes
- possible wider range of covered project translations
- easier maintenance

Hopefully something like that is already possible, but I just didn't know about it. Please, do consider making the svn usage easier for the translators. Not like developers, the translators only need good po files, but usually keep an eye of many of them

Thanks
Matej