Jürgen: I can see that you have updated the document, can you give me a hint on the chapter:
"Update to new templates" I am confused: first we update the pootle server (sdf to po) using manage_py update_from_templates ... then the translators do their magic. We then update the po files with manage_py sync_stores .. does this have to done for each language, or if language it not given it does it for all ? The po files make their way back to sdf files. Now comes my confusion: why take the template files again (they have not changed) which are older than the po files we just generated ? is there a step missing, to generate pot files from the NEW sdf files ? I hope you can give me a quick answer, so I can finish the document and publish it. have a nice day JanI On 16 October 2012 10:42, jan iversen <[email protected]> wrote: > thanks, I will correct the documentation. > > Do you know where manage.py is stored in SVN ? it does not seem to be part > of AOO > > have a nice day > jan > > > On 16 October 2012 09:14, Jürgen Schmidt <[email protected]> wrote: > >> On 10/16/12 12:04 AM, jan iversen wrote: >> > I am analyzing the current localization process and writing a detailed >> > dcoument as a first step to change the process. >> > >> > The wiki page "localization for developers" states that: >> > >> > solenv/bin/localize_sl >> > >> > (description is without parameters) >> > >> > should be called to generate the central sdf file needed to generate >> .pot >> > and .po files. >> > >> >> that is a mistake, it should be solenv/bin/localize. I changed it already >> >> >> > However doing so, I get an error message stating that the executable >> misses >> > options. I looked at the source (localize.cxx) and it do expect options. >> > >> > The wiki page states that the executable can be called directly as: >> > >> > localize -e -l en-US -f foo.sdf. >> >> This one is called >> >> Juergen >> >> > >> > THIS WORKS, and foo.sdf is generated at trunk level. >> > >> > I cannot find calls to localize* in the build scripts, which seems >> correct >> > since the build is concentrating on the opposite direction. >> > >> > Can someone please enlighten me: >> > - what is actually called to generate the central sdf file ? >> > - is that (and the following calls) stored somewhere in a script ? >> > >> > thanks in advance. >> > >> > jan I. >> > >> >> > >
