Op Do, 2009-01-29 om 15:44 +0100 skryf Stéphane Roucheray:
> Hi there,
> 
> I'm new at Pootle and I need to set it up for one of my agency project 
> but I met some issues. Documentation either on the pootle website or  in 
> comments in the preferences files did not help.

Hallo Stéphane, and welcome to the Pootle community. Thank you for the
detail in your post - it makes it much easier to start answering :-)
More comments inline...

> 
> My environment is :
> 
>     * Ubuntu 8.10
>     * Pootle 1.1.0-1 installed through the repository with all its
>       dependencies +  python-levenshtein package
>     * Apache 2 configured with mod_proxy
> 
>     * Our project to translate :
>           o Is PHP  based on Zend Framework
>           o All the po and mo files are under a subdirectory of the main
>             directory trunk/site/i18n/
>           o po and mo files are under subdirectories in trunk/site/i18n/
>             to match extensions packages names
> 
> The structure looks like this :
> 
>     * trunk/site/i18n/
>           o admin
>                 + fr.po
>                 + en.po
>           o extension1
>                 + fr.po
>                 + en.po
>           o ...

This is a gnu layout, with submudules are resident inside the project.
Pootle should automatically detect it, but as you already discovered,
you can set the treestyle manually to be gnustyle.


> 
> Our project is subversionned (SVN). The Pootle main interface is 
> accessible no problem on this part.
> The problem comes when I want to integrate our project to Pootle.
> 
> I setup a new project in the pootle.prefs file :
> 
> Earl:
>       fullname = "Earl"
>       description = "<div dir='ltr' lang='en'>Interface translations for 
> Earl. <br /></div>"
>       checkstyle = "standard"
>       localfiletype = "po"
>       treestyle = "nongnu"

As discussed above, you want "gnu"

>       checkerstyle = u''

I see there is a typo in the documentation. "checkerstyle" is invalid -
it should be checkstyle as you have up higher.

>       createmofiles = 0
> 
> And I checked out the repository in the /var/lib/pootle/ directory in 
> order to have a /var/lib/pootle/Earl directory containing the 
> trunk/site/i18n/ subtree of our project.
> 
> The project appears well in Pootle Web pages but I don't understand how 
> to setup new languages, 

pootle.prefs contains the languages that are enabled on the server. By
default it contains some 50 odd languages, and you can easily add more
by uncommenting some of those there or adding some yourself. The admin
interface can also be used. To remove languages, just remove their
entries from pootle.prefs and restart the server.

I guess you might talk about adding new language files initialised from
templates, so I'll address that below.


> how po files update, if there should be a 
> template pot file and if so how it should interact with the others and 
> so on. At the end, I did not found a complete documentation on how to 
> setup a real life server.

For the GNU layout, you should have a pot file in each directory (admin,
extention1, etc. in your example). In the project administration page,
you can choose which new languages to add. It will create the empty
files based on these POT files. If you prefer, you can also safely do it
from the commandline with pot2po, msginit or whatever you prefer.

> I tried many other setup like treestyle="gnu" but it never end to work.
> 
> Could you help me to better understand the process of creating a project 
> under Pootle, especially in my environment ?

One outstanding issue for your environment, might be how to commit the
new files to SVN. You need to do "svn add" on the command line for files
that you want Pootle to be able to manage. Users will then be able to
commit from the web interface if they have the appropriate rights.

> 
> Best regards,
> 
> Stephane Roucheray

Feel free to help us extend the documentation on the wiki to make it
easier for those coming after you. The prefs file will mostly disappear
in the next release of Pootle, and the web based administration will
become much easier. Hopefully that already simplifies things for several
admins.

Keep well
Friedel

--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/language-and-dialect-codes


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle

Reply via email to