WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Tagged: google translate Toggle Comment Threads | Keyboard Shortcuts

  • pcgaldo 11:46 pm on January 13, 2013 Permalink | Log in to leave a Comment
    pcgaldo • gl.wordpress.org validator
    Tags: , , google translate,   

    Hi,

    We have a little problem: automatic traslation is not working in GlotPress for galician language, although our language is supported in the Google tool.

    Error in translating via Google Translate: undefined!

    Can you solve this problem, please?

     
  • Safareli 2:59 pm on October 15, 2012 Permalink | Log in to leave a Comment
    safareli
    Tags: , google translate, ,   

    i am translating twenty eleven 3.4.x to Georgian language and in some cases when i edit some fields i can’t correct them :( why ?
    and altho Translation from Google doesn’t work

     
  • jenialaszlo 8:10 pm on April 12, 2011 Permalink | Log in to leave a Comment
    jenialaszlo
    Tags: google translate, machine translation   

    Do the translations approved and stored in GlotPress feed back into http://translate.google.com/? Does Google’s machine translation engine learn from the translations entered by WordPress community volunteers (thus potentially making better suggestions for us in the future)?

     
    • 8:49 pm on April 12, 2011 Permalink | Log in to Reply

      They aren’t and as far as I can tell, Google’s API has no method for doing that. It would be nice, though.

      • Jenia 9:30 pm on April 12, 2011 Permalink | Log in to Reply

        Thank you! I searched around and found some further information:

        From http://translate.google.com/about/: “If you notice that one of our translations could be better, click the “Contribute a better translation” link on the results page to suggest improvements. You can also help improve translation quality by using Translator Toolkit for translating or by uploading your translation memories into Translator Toolkit. ”

        And then from http://translate.google.com/toolkit/TOS.html: “By submitting or creating your content through the Service, you grant Google permission to use your content to improve or make available the Services pursuant to these additional terms….”

        But then Google Translator Toolkit only takes files in .tmx format, and I believe that while there is a way to convert .po into .tmx, it’s not so trivial… Another option is to suggest better translations manually on the Google Translate page which is not feasible, of course.

        Why not consider WordPress sites as important translation repositories, alongside with UN sites? That’s what Gogle Translate really ought to think about.

        • 9:51 pm on April 12, 2011 Permalink | Log in to Reply

          Found this, later:
          http://code.google.com/intl/en/apis/gtt/docs/1.0/developers_guide_protocol.html#UploadingTms but it seems to indicate that albeit we’d be contributing translation memories to a “public pool”, said pool would only be “public” in the sense that it can be read by any other user through the API, not the world at large (i.e. the main Google Translate website/API). I’ll dig some more.

          Also, UN?!?

          • Jenia 9:57 pm on April 12, 2011 Permalink | Log in to Reply

            Ah! Good point on distinction between the Google Translator Toolkit and Google Translate API.

            (The UN reference is because I’ve just watched the intro video – it said that the engine is trained on translations from “UN and other important websites”.)

            • 10:00 pm on April 12, 2011 Permalink

              Agreed. It should read “WordPress and other important websites” :D

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel