Which ever solution we do implement, you and other translators will be able > to edit the translation directly from the CMS to correct grammatical > errors. No need to manually create more pages or forked assets. By Rob Weir
As a trial, one of the Tamil pages was translated automatically. All the words are correctly translated. But, while forming a sentence there was a complete failure and the text has become a combination of Tamil words, understandable to none. The option left out is, where ever volunteers are available for any language, let that volunteers decide the best option for their language, instead of forming a general policy across the globe for all the languages, without knowing the structure and grammar of them With Warm Regards V.Kadal Amutham 919444360480 914422396480 On 21 February 2013 14:02, Andrea Pescetti <[email protected]> wrote: > On 20/02/2013 Samer Mansour wrote: > >> Here is a wiki page where I placed two solutions down: >> https://cwiki.apache.org/**confluence/display/OOOUSERS/** >> AOO4+-+Websites+Translation<https://cwiki.apache.org/confluence/display/OOOUSERS/AOO4+-+Websites+Translation> >> Language specific pages could be replaced with a redirection to the new >> solution until Google other search engines pick it up. >> > > A few quick observations here (while it is very good to approach the > problem): > > 1) Unsolicited machine translation must be avoided. You will meet > opposition to an automatic translation, and a strong argument is that > poorly-worded pages will be dangerously similar to scam sites. So, if at > all present, machine translation must come from a visitor's choice (like > clicking on a "Machine translation into: [Select]" link). > > 2) A point that Rob already made: we might have some convergence, but in > general we must keep the flexibility for native-lang subdirectories to > offer different/additional content with respect to the English site. > > 3) The PO approach has already been discussed on the dev list some months > ago. See > http://markmail.org/thread/**4j3dbsfp5trwnycu<http://markmail.org/thread/4j3dbsfp5trwnycu>. > A tool that already supports everything for a HTML-PO-HTML workflow is > GNUN: > http://www.gnu.org/software/**trans-coord/manual/gnun/gnun.**html<http://www.gnu.org/software/trans-coord/manual/gnun/gnun.html>(I'm > not saying it is usable as it is, but it might be something to look > at). > > Regards, > Andrea. >
