I'd recommend that we take this discussion to the dev list... On Wed, Feb 20, 2013 at 12:23 PM, Samer Mansour <samer...@gmail.com> wrote: > Kadal, > > That is not a sustainable or scalable solution, not all volunteers have > time to create separate pages for over 60+ languages, we also don't have > the administrative power to support all those pages created. > > 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. > > If we go with Google's you'll be able to feed google with better > translations and improve their service for your community. > If we go with Pootle we potentially would be able to host more languages > than Google can offer. > This is the trade off between the two services. Both would require some > coding on my part, so its negligible. But both solutions scale. >
It might be worth considering the kinds of maintenance (at the content level) that we should think about when designing a new solution: 1) Supporting a new language and creating a new language-specific subsite. 2) Propagating a project wide change across all language subsites and requiring translation, e,g., a project-wide announcement on the home page or a new release that needs to be noted on the download page. 3) Announcements for only a single language page, e.g., announcement of a local user conference in Spain 4) Editing of additional pages that are specific for a given language, e.g., description of bidi/RTL features for Arabic, links to French support forum. I think 1 and 2 above could be handled well with Pootle. That way the translators who already translate the AOO UI and help files could also translate the website pages using the same tools. The challenge is to find a way to do the customizations of points 3 and 4. But note that these are not translations, but content authored originally in the native language. Maybe something in the page generation from the template can discover the existence of additional pages and automatically add them to the navigation? -Rob > I need to take Rob's advice and tackle only a subset of pages we want to > translate by pootle and how we can leverage other less important pages with > Google. > > Samer > > On Wed, Feb 20, 2013 at 12:01 PM, Kadal Amutham <vka...@gmail.com> wrote: > >> I just checked that, it is utterly useless. At least for Tamil, I will >> translate all the pages manually, make it into HTML and give it to you >> >> With Warm Regards >> >> V.Kadal Amutham >> 919444360480 >> 914422396480 >> >> >> On 20 February 2013 21:35, Samer Mansour <samer...@gmail.com> wrote: >> >> > Kadal this is getting off topic. Please use >> > http://translate.google.com/?sl=ta to translate from Tamil to English or >> > any language for your needs. >> > >> > On Wed, Feb 20, 2013 at 10:58 AM, Kadal Amutham <vka...@gmail.com> >> wrote: >> > >> > > Amazing! How did you get that? Even though the translation is not good, >> > it >> > > is a good attempt. We can expect things to improve in the days to >> come. I >> > > could not read it fully the translated version. Can you give me the >> full >> > > translated text? >> > > >> > > With Warm Regards >> > > >> > > V.Kadal Amutham >> > > 919444360480 >> > > 914422396480 >> > > >> > > >> > > On 20 February 2013 21:22, Samer Mansour <samer...@gmail.com> wrote: >> > > >> > > > It is broken up, but it sounds like a story about a guru leaving his >> > > > village. >> > > > >> > > > Tamil is in a alpha, so its not the greatest but Google Translate has >> > the >> > > > ability to override translations. >> > > > eg. We would ask our translators to click "improve this translation", >> > > then >> > > > users will be presented the translation from our translators (not the >> > > > computerized one currently there). >> > > > >> > > > See this for example: >> http://s12.postimage.org/bngjt1xot/Untitled.png >> > > > >> > > > On Wed, Feb 20, 2013 at 9:51 AM, Kadal Amutham <vka...@gmail.com> >> > wrote: >> > > > >> > > > > I have just uploaded a tamil page with google translate service. >> The >> > > page >> > > > > is running at thewink.in/indexTest < >> http://thewink.in/indexTest.html >> > > > >,html >> > > > > with google translate service. Check whether you can read the page >> in >> > > > > English >> > > > > >> > > > > With Warm Regards >> > > > > >> > > > > V.Kadal Amutham >> > > > > 919444360480 >> > > > > 914422396480 >> > > > > >> > > > > >> > > > > On 20 February 2013 19:58, Samer Mansour <samer...@gmail.com> >> wrote: >> > > > > >> > > > > > http://lmgtfy.com/?q=does+google+translate+tamil >> > > > > > http://translate.google.com/about/ >> > > > > > >> > > > > > Yes. >> > > > > > >> > > > > > On Wed, Feb 20, 2013 at 12:20 AM, Kadal Amutham < >> vka...@gmail.com> >> > > > > wrote: >> > > > > > >> > > > > > > Is Tamil one among the 60+ languages google supports? I am not >> > sure >> > > > > > whether >> > > > > > > Tamil can be automatically translated >> > > > > > > >> > > > > > > With Warm Regards >> > > > > > > >> > > > > > > V.Kadal Amutham >> > > > > > > 919444360480 >> > > > > > > 914422396480 >> > > > > > > >> > > > > > > >> > > > > > > On 20 February 2013 10:37, Samer Mansour <samer...@gmail.com> >> > > wrote: >> > > > > > > >> > > > > > > > In communicating with Rob Weir earlier today about the google >> > > > > > experiment >> > > > > > > > for integration of social media, he mentioned we were >> > maintaining >> > > > > > > separate >> > > > > > > > pages for other languages. >> > > > > > > > >> > > > > > > > One of the challenges in maintaining separate pages is making >> > > sure >> > > > > > > content >> > > > > > > > such as announcements are translated and communicated to the >> > > users >> > > > in >> > > > > > > those >> > > > > > > > locales. >> > > > > > > > If missed, a segment of our users could be left out for >> > important >> > > > > > > > information about the AOO project. >> > > > > > > > >> > > > > > > > I'm proposing I find a translation solution with the >> following >> > > > scope: >> > > > > > > > - To make our communication and announcements more uniform. >> eg. >> > > > Home >> > > > > > page >> > > > > > > > and download page. >> > > > > > > > - To make all our oo.org pages available to all users in >> their >> > > > local >> > > > > > > > language. eg.http://www.openoffice.org/why/ >> > > > > > > > - Make our lives easier when we roll out a branding refresh / >> > > > > template. >> > > > > > > > >> > > > > > > > Here is a wiki page where I placed two solutions down: >> > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> 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. >> > > > > > > > >> > > > > > > > One based on Google Translate, I've seen it on a commercial >> > site >> > > > and >> > > > > it >> > > > > > > was >> > > > > > > > really good, only if I remembered what company it was again. >> > > > > > > > The other is based on using our Pootle instance as >> translation >> > > > > > > repository. >> > > > > > > > This might require more initial work but could be more >> > > customizable >> > > > > and >> > > > > > > in >> > > > > > > > our control. >> > > > > > > > >> > > > > > > > Samer >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >>
