Op Di, 2009-12-15 om 18:29 +0800 skryf Bernard Chan: > 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.
Hallo. Good to hear your feedback. > No big issues so far, but I have several questions in mind. > 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? As Alaa mentioned, you can work on the permissions. with previous versions of Pootle, the 'pootle' project was required for the localised interface. This is not necessary anymore - you can use .mo files if you want, and then you can remove the Pootle project if you don't want anyone to touch it. > 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. Pootle should react well to file changes on-disk, especially if no files were added/removed. If files were added/removed, you need to rescan from the web interface. > 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. You can try to put the correct directory in your PYTHONPATH environment variable. All directories in the Pootle/ directory is automatically in your environment, so you could try to just create a symbolic link, as Alaa suggested. > 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? Sure, you can ask here. Maybe there is a slightly more technical audience in the translate-devel mailing list, whereas this has previously been somewhat more for Pootle users. It doesn't really matter either way. Of course the gettext project also has a mailing list if you want to ask for help there. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/pootle-200-released ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
