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 [email protected] [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 > [email protected] [5] > https://lists.sourceforge.net/lists/listinfo/translate-pootle [6] Links: ------ [1] http://p.sf.net/sfu/intel-dev2devmay [2] mailto:[email protected] [3] https://lists.sourceforge.net/lists/listinfo/translate-pootle [4] http://p.sf.net/sfu/intel-dev2devmay [5] mailto:[email protected] [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 [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
