Re: [translate-pootle] Format of PHP arrays for initial upload?
Thanks! Now I understand. Unfortunately I stumbled upon a bug in the parser for PHP arrays (I reported it as #1929 in bugzilla). After doing a temporary workaround to get the parser right for that specific problem I also found another problem, again with the parser. I will do an initial investigation and when I have some more facts will report that as well (since it seems to be a different bug from the already confirmed #1929 issue). Right now this is a showstopper for me since the PHP data importer is broken (from my point of vew). The core of the problem seems to be in the "php2po" translatiopn script which gets confused by the use of HTML as message-index (which will happen for most PHP applications since translations keys are often the source language strings) Rgds Johan On Sun, 15 May 2011 22:19:54 +0200, Dwayne Bailey wrote: > On 2011-05-15 21:28, Johan Persson wrote: > >> When I upload a PHP array I assumed that the format would be $php_array['message_key'] = 'translated_message_string'; But when I upload such a file with those kinds of definitions the 'translated_message_string' is shown as original language > > You need to upload the English or source language files to a given > language. Pootle will allow you define which language is the reference > language. All other translations will treat that as the template. So > usually that would be your English files. > > Pootle handles the translations internally and only writes out the > translated PHP file. It can't parse the existing translated PHP files to > create your bilingual pairs. If you have that scenario you might want > to consider php2po to create bilingual files. > >> I wasn't able to find any more information on this in the Wiki. (apart from a page on php2po which seems to indicate that it would not be possible to use such an original translation file.) Can someone help me understand what the upload format should be? /Johan -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay [1] ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net [2] https://lists.sourceforge.net/lists/listinfo/translate-pootle [3] > > -- > regards > Dwayne > > -- > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay [4] > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net [5] > https://lists.sourceforge.net/lists/listinfo/translate-pootle [6] Links: -- [1] http://p.sf.net/sfu/intel-dev2devmay [2] mailto:Translate-pootle@lists.sourceforge.net [3] https://lists.sourceforge.net/lists/listinfo/translate-pootle [4] http://p.sf.net/sfu/intel-dev2devmay [5] mailto:Translate-pootle@lists.sourceforge.net [6] https://lists.sourceforge.net/lists/listinfo/translate-pootle -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Format of PHP arrays for initial upload?
When I upload a PHP array I assumed that the format would be $php_array['message_key'] = 'translated_message_string'; But when I upload such a file with those kinds of definitions the 'translated_message_string' is shown as original language I wasn't able to find any more information on this in the Wiki. (apart from a page on php2po which seems to indicate that it would not be possible to use such an original translation file.) Can someone help me understand what the upload format should be? /Johan -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
Re: [translate-pootle] SOLVED: Hint for troubleshoot Apache config with error "..client denied.." ?
After one more reading through the config file it dawned upon me that the template shown in the Wiki (which I just copied with my brain turned off) is not enough. There only the "/Pootle/po" and "/Pootle/html" directories are given permissions to read. Since I by default deny everything in my basic apachce config one must also add the Pootle root (of course..) with a new Directory statment in order to execute wsgi.py Order deny,allow Allow from all Can I suggest that this is added to the wiki config example (since now adays the deny all is standard for most Apache installations) /J On Thu, 12 May 2011 14:58:09 +0200, Johan Persson wrote: > I have installed Pootle (+mysql) and everything seems to work fine > when I run the standaone server. > > However, when I try to run Pootle > under Apache with the wcgi module I get an access denied error, i.e. > > .. client denied by server configuration: > /usr/local/share/pootle/wsgi.py ... > > So clearly I have something wrong. > > I'm fairly used to Apache configuration files but I have no technical > knowledge on Python nor Django (end hence the wsgi module) > > So far I > have double checked that: > > * File are accessible by Apache (a plain > index.html dummyfile in the Pootle direcory is accessible from browser) > > * dbs and po is writable (even though as I understand should not be > necessary since I use mysql) > * there is no hidden .htaccess overriding > the standard settings in the Apache config module > * Access control in > the Apache module for pootle is set to "Allow from all" > * No spelling > mistakes in path names etc > > So I suspect there is some issue with > running i the Django framework for the wsgi.py file. But unfortunately > > I don't have any technical knowledge of Django (nor the wsgi module). > > Can anyone give some hints on where I should look further? > > Cheers! > > Johan > > -- > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay [1] > ___ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net [2] > https://lists.sourceforge.net/lists/listinfo/translate-pootle [3] Links: -- [1] http://p.sf.net/sfu/intel-dev2devmay [2] mailto:Translate-pootle@lists.sourceforge.net [3] https://lists.sourceforge.net/lists/listinfo/translate-pootle -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
[translate-pootle] Hint for troubleshoot Apache config with error "..client denied.." ?
I have installed Pootle (+mysql) and everything seems to work fine when I run the standaone server. However, when I try to run Pootle under Apache with the wcgi module I get an access denied error, i.e. .. client denied by server configuration: /usr/local/share/pootle/wsgi.py ... So clearly I have something wrong. I'm fairly used to Apache configuration files but I have no technical knowledge on Python nor Django (end hence the wsgi module) So far I have double checked that: * File are accessible by Apache (a plain index.html dummyfile in the Pootle direcory is accessible from browser) * dbs and po is writable (even though as I understand should not be necessary since I use mysql) * there is no hidden .htaccess overriding the standard settings in the Apache config module * Access control in the Apache module for pootle is set to "Allow from all" * No spelling mistakes in path names etc So I suspect there is some issue with running i the Django framework for the wsgi.py file. But unfortunately I don't have any technical knowledge of Django (nor the wsgi module). Can anyone give some hints on where I should look further? Cheers! Johan -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
