On 2/20/2013 9:23 AM, Samer Mansour 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.
At least initially, I think the Google solution will cover significantly
more languages.
Wouldn't the best workflow for this be:
* A small number of manually translated pages (why, download, ?)
(with Google translated versions of these for languages without a
manual translation)
* Google translate for additional pages we want to cover - with a link
on the page to flag it as a suspect translation.
* Interested translators improve/fix pages by proposing an improved
translation to the google.
My question is whether we can insure suggestions up stream to the google
will always flow back down stream?
If we could guarantee that, then we could even use this process for the
'important' pages.
A.
This is the trade off between the two services. Both would require some
coding on my part, so its negligible. But both solutions scale.
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 <[email protected]> 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 <[email protected]> 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 <[email protected]>
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 <[email protected]> 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 <[email protected]>
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 <[email protected]>
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 <
[email protected]>
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 <[email protected]>
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
