This question has been asked on and off a couple of times. How do I get the most recent catalog files from the translation server. So far the answer (afaik) has been to wait for Collaboraid to move them from the translation server to CVS.
Is this really the process we want to follow in the future? This would create a serious bottleneck and I'm not sure if Peter is happy in doing this for the next couple of years (moving catalog files from the translation server to the distribution).
Let me give you some ideas ;):
- Automatically update the catalog files from the translation server using some bash magic (to only update the catalog files and nothing else).
- Distributed translations. Not sure if and how this would work, but the idea is to have a repository for OpenACS with the default language English and whenever someone says "enable language", this language is downloaded from the translation server (of choice). This also enables the use of multiple translation servers and multiple translations, just in case you are not happy with the translation given by party A and prefer party B's translation instead (e.g. if I were to translate into German, I'm sure everyone would choose the translation provided by Anja, *but* maybe someone likes my style better for his/her website).
- Tar Files for download from the translation server. For each lanuage there could be a tar file, rooted at the serverroot, which contains the latest catalog files of this language. To install, go to /var/lib/aolserver/serverroot and untar it.
I'm willing to work on and test out 1 & 3.
P.S.: If there is already a different process that is easy to handle in place, accept my apologies for my ignorance. In this case I hope, this could show up in the documentation.
P.P.S.: Talking about documentation. Is it a bug or intention that the documentation at /doc/acs-lang is out of date and does not include everything needed (like installation instructions for new languages) ?
