Hi Vaclav, On August 29, 2011 02:01:53 AM Vaclav Cerny - vatoz wrote: > I have added translation branch to hugin-web site. Main script g.php > is meant to be run offsite, to generate translated pages, it includes > process documentation.
Thanks. I have looked into it, which means I could read and understand the PHP code and the files committed, but I have no time/resources available to test/run it. The good news is that it does not cause extra server load and it could actually work for Hugin on SourceForge. The bad news is that I fail to see the benefits of this, and I do see plenty of drawbacks. I look at the committed .po files and compare with direct HTML editing: 1. In the .po files text is split into a random collection of out of context paragraphs. IMHO translation is critically dependent on context and the .po file takes that critical component away. Moreover, if the original page evolves and a new paragraph is left untranslated, the newly generated translation will look like Babel towers. 2. I see HTML markup in the translateable "units". Links, but also emphasis. This will make the translated pages less robust and more prone to errors since the markup is taken out of context as well and can't be checked syntactically prior to upload/translation. Beyond that, there are some technicalities. I find the directory layout to be unclean, but that's easy to fix. Last but not least there is a process issue. The process is entirely manual and add an extra burden on each editor and translator to trigger the "g.php" script. This requires the fully fledged web server and can't be done locally, so whoever edits / adds to the website is being handled an extra dependency. Sorry for the negative feedback, but IMHO the addition of this kind of translation mechanism would do a disservice to a relatively static website like Hugin. > Each language can be translated independently and translate different > set of pages. How does this differ from the existing website? If you want me (or anybody else) to buy into this concept, you need to show advantages. I see only disadvantages at this point. Yuv
signature.asc
Description: This is a digitally signed message part.
