Hi Everybody, Thanks for the Pootle 2 release, and some helpful person esp. Alaa for offering some helpful hints trying to assist me in setting up Pootle 2 SVN in my environment. I really enjoy working on Pootle, and I believe it is a really convenient way for translation team collaboration.
No big issues so far, but I have several questions in mind. 1. What is the best strategy to merge message updates from POT so that the interface will spontaneously reflect the updated status? Right now, I generate the POT for our project with a mixture of xgettext and dynamically generated messages offline, then the POTs are copied to the expected directories at the remote Pootle server. However, then, I found myself having to manually login as admin to update messages from template to get a more up-to-date view of the new messages every time. Sometimes the views are not updated at all even though I know the POT have been updated, even if I chose to rescan project files or update from templates. Basically, I rely on "XXX words need attention" to quickly locate what the new messages are just to find they are very often stale. Am I not expected to do msgmerge myself on Pootle server? I'm asking this because I expect no admin will be online locally to refresh the message list for each round of message change once I release the portal to the actual translation teams. We are thinking about having an automated process that publishes POT updates to Pootle on schedule, but I'm not sure whether there is anything we can do to let translation teams know about changes easily that allow them to work on new/updated strings with a short turnaround time. I think the easiest is to have translators visit Pootle regularly but still they need to see something actually has changed. I noticed Pootle 2 front page has an RSS. I think it may be great if notifications for message updates to specific languages and/or projects can be published over it, though I guess right now that is not intended to be used that way? 2. Exactly, what is the best way to configure so that I can prevent most users seeing specific projects? Specifically, I would like to hide Pootle and Terminology from all users except admin. I saw 'default' and 'nobody'. Are they reserved for this kind of purpose? 3. If someone manages to mess up the POT or translated POs on Pootle or whatever messy as that, we may need to rollback to some safe past revision. I know this is not directly related to Pootle, but what is the typical strategy to safeguard thess kinds of mishaps on Pootle? To version control the entire po directory? If we rollback on the filesystem, will there be any consistency concern if something is cached at Pootle? I'm currently on an Apache WSGI integration, and have activated memcached support. 4. I would like to experiment with whether Lucene can help with efficiency in my environment, but so far did not have much luck with it. Can Pootle pickup pyLucene without installing it? It will be great if Pootle can use Lucene straight from the pyLucene build directory by whatever means. By the way, I am having much headache recently with certain aspects of Gettext, and specific language binding. I believe some users here are quite knowledgeable about Gettext in general (well, that's what Pootle is all about), and I would like to have some important concepts clarified as I found some feedback about Gettext from some package maintainers very confusing. Of course, I know that specific issues about 3rd party packages should go elsewhere. But may I discuss some general I18N topics here on this list (that involves mostly Gettext plural in general), in the hope that someone here may shed some light for me? Regards, Bernard Chan. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
