Google language word translator

You can translate documents into many languages with Google Docs.

Translate a document

  1. On your computer, open a document in Google Docs.
  2. In the top menu, click Tools and then Translate document.
  3. Enter a name for the translated document and select a language.
  4. Click Translate.
  5. A translated copy of your document will open in a new window. You can also see this copy in your Google Drive.

Tip: If «Translate document» isn’t visible, you’re likely in Microsoft Office editing. To translate, convert your file to Google Docs. Learn about Microsoft Office editing and how to convert Microsoft Office files.

Change your typing language

  1. On your computer, open a document in Google Docs, a presentation in Google Slides, or a sheet in Google Sheets.
  2. When you choose a non-Latin language, the “Input tools menu” will show in the toolbar. To enter non-Latin characters like Hindi or Chinese, click the Down arrowDown arrow next to the “Input tools menu.»  Note: You can also open the “Input tools menu” by pressing Ctrl + Alt + Shift + k (PC) or ⌘ + Option + Shift + k (Mac) on your keyboard.
    • Phonetic input: Type the phonetic spelling of a word in Latin characters, then click the best match from the options on the screen.
    • Keyboard input: To type letters and symbols, click the keys of a virtual keyboard or type matching keys with your physical keyboard.
    • In handwriting input: Draw characters in a panel in the bottom right of your screen, then click the best match from the options on the screen.

Tip: In Workspace, the handwriting input works only when «access to additional services without individual control» is on in the Admin Console.

Was this helpful?

How can we improve it?

Источник

Image of Lance Whitney

on

January 5, 2022, 11:31 AM PST

How to use Google Translate to translate your Microsoft Office documents

Google’s online translator can step in to translate your Office documents for free. Now you can read documents from all over the world with the click of a button.


We may be compensated by vendors who appear on this page through methods such as affiliate links or sponsored partnerships. This may influence how and where their products appear on our site, but vendors cannot pay to influence the content of our reviews. For more info, visit our Terms of Use page.

Image: Andy Wolber / TechRepublic

Google Translate is available as a website, a mobile app and a feature built into Google Docs. But you can also use the online version to translate external documents saved on your computer. The Google Translate webpage supports Word documents, Excel spreadsheets and PowerPoint presentations. After choosing the source and target languages, you point to the file you want translated, and Google takes care of the rest. Let’s see how this works.

SEE: 6 tips for expanding your SMB internationally (TechRepublic)

Open the Google Translate webpage in your browser. Click on the current source and target languages if you need to change them. Click the down arrow to access the full selection of languages. You can also set the source language to automatically be detected, but you may get more accurate results by specifying the language (Figure A).

Figure A

Next, you can simply copy and paste the text you want translated into the window for the source language. But the idea here is to translate an entire document. Click the Documents button and then select the option for Browse Your Computer. You can choose from a variety of Microsoft Office file types, including .doc, .docx, .odf, .pdf, .ppt, .pptx, .ps, .rtf, .txt, .xls and .xlsx (Figure B).

Figure B

Select the document you want translated. Let’s try a Word document in this case. Then click the Translate button (Figure C).

Figure C

The translated version appears on the website. To compare the translation with the original text, hover your mouse over each paragraph. A small window pops up showing the text in the source language (Figure D).

Figure D

If you’re familiar with the target language and feel the translation contains some errors, click the link for Contribute a Better Translation. You can then fix any words in the translation that are inaccurate (Figure E).

Figure E

To translate another file, click the back arrow to return to the Google Translate site. Click the button for Browse Your Computer to select a different file, maybe an Excel spreadsheet. Then click the Translate button. The translated spreadsheet appears. Again, hover over any translated paragraph to see the original text (Figure F).

Figure F

Finally, try translating a PowerPoint presentation. Open the file in the Google Translate site and click the Translate button. The text from the file appears in the translated language. Hover over a translated section to compare it with the source language (Figure G).

Figure G

Also See

  • How to translate documents into different languages with Google Docs (TechRepublic)

  • How to use Apple’s Translate app to translate a real-time conversation (TechRepublic)

  • How to view translations of foreign websites on your iPhone or iPad (TechRepublic)

  • How to use the translation tools in iOS 14 for easier communication and website translation (TechRepublic)

  • Why Wearable Translator 2 earbuds are a must-have for travelers (TechRepublic)

  • Checklist: Securing Windows 10 systems 
    (TechRepublic Premium)

  • More must-read Microsoft coverage
    (TechRepublic on Flipboard)

  • Google

  • Microsoft

  • Software

Источник

Google Language Translator plugin is now a part of GTranslate family!

GTranslate is a leading website translation services provider since 2008 and powers more than 500.000 multilingual websites worldwide.

Please use Google Language Translator Support for your questions and support requests! We are multilingual!

Please check our FAQ to get quick answers.

Features

  • Free Google automatic machine translation
  • Option to hide “Suggest better translation” pop-up
  • Option to hide Google top frame after translation
  • Google Analytics integration
  • Translate the site on the fly
  • Translate posts and pages
  • Translate categories and tags
  • Translate menus and widgets
  • Translate themes and plugins
  • Right to left language support
  • Floating language selector
  • Language bar with flags in menu
  • Translate WooCommerce shop

Paid Features

  • Multilingual SEO – Enable search engine indexing
  • Neural machine translations with human level translation quality
  • Increase traffic and AdSense revenue
  • Search engine friendly (SEF) URLs
  • Yoast SEO compatible
  • WooCommerce compatible
  • You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure
  • Translate URLs aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros)
  • Add hreflang tags for translated alternatives
  • You can manually correct translations
  • In context translation interface (make corrections without losing the context)
  • Translate meta data (meta keywords, meta description)
  • Translating schema.org microdata for better search engine appearance
  • Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side)
  • Translate JSON objects (JSON format translation)
  • Translate AMP pages (Accelerated Mobile Pages translation)
  • Image localization – Translate media
  • Translation Proxy (aka Translation Delivery Network)
  • Centralized Translation Cache – We revise and improve translations over time
  • Language Hosting (example.fr)
  • User Dashboard with Analytics
  • Live Chat Support
  1. Download the zip folder named google-language-translator.zip
  2. Unzip the folder and put it in the plugins directory of your wordpress installation. (wp-content/plugins).
  3. Activate the plugin through the plugin window in the admin panel.
  4. Go to Settings > Google Language Translator, enable the plugin, and then choose your settings.
  5. Copy the shortcode and paste it into a page, post or widget.
  6. Do not use the shortcode twice on a single page – it will not work.

It doesn’t translate, what to do?

Please check Google Language Translator Support Forum and feel free to create a new topic if you cannot find answers.

Is it FREE?

Yes! We have free version and paid versions with advanced features.

What is the quality of translation?

In our free version we use Phrase Based Machine Translations provided by Google Translate, while in our paid versions use Google Translate Neural Translations which are very accurate for popular language pairs.
In the paid versions you can refine the automatic translations yourself or order professional translations or proofreading of a translated content.
You can get a translation cost estimate by using our Website Translation Cost Calculator

Are the translations provided free of charge?

Yes, we use Google Translate widget for website which provides free phrase based machine translations, which makes it possible to make your wordpress website multilingual instantly upon installation.
In our paid versions we use Google Translate state of the art Neural Translations which are included in the service price and there are no limits on the word count.

Besides we offer cost effective automatic translation proofreading service and also professional translation service.
You can get an estimate from our Website Translation Price Calculator

Can I modify the translations?

That feature is available only in our paid version. You will be able to make edits directly on the page without losing the context.

By the way, we can help you to translate your website with a cost effective approach by post-editing your automatic translated content.
The proofreading service will be done by a native speakers and if you want to take the quality to another service, we also have a professional website translation service available.
You can get an instant website translation estimate by using our Website Word Counter tool.

Which languages are supported?

Here is the list: Afrikaans, Albanian, Amharic, Arabic, Armenian, Azerbaijani, Basque, Belarusian, Bengali, Bosnian, Bulgarian, Catalan, Cebuano, Chichewa, Chinese (Simplified), Chinese (Traditional), Corsican, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Filipino, Finnish, French, Frisian, Galician, Georgian, German, Greek, Gujarati, Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi, Hmong, Hungarian, Icelandic, Igbo, Indonesian, Irish, Italian, Japanese, Javanese, Kannada, Kazakh, Khmer, Korean, Kurdish (Kurmanji), Kyrgyz, Lao, Latin, Latvian, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Myanmar (Burmese), Nepali, Norwegian, Pashto, Persian, Polish, Portuguese, Punjabi, Romanian, Russian, Samoan, Scottish Gaelic, Serbian, Sesotho, Shona, Sindhi, Sinhala, Slovak, Slovenian, Somali, Spanish, Sudanese, Swahili, Swedish, Tajik, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Uzbek, Vietnamese, Welsh, Xhosa, Yiddish, Yoruba, Zulu

Is it SEO compatible?

Our free version doesn’t give any SEO advantage. For SEO features and multilingual SEO you need to use our paid versions which have all the SEO advantages.

What is multilingual SEO?

Multilingual SEO is a SEO strategy which uses new content generation technique by translating your original content and making your website multilingual. By translating your website into many languages you are creating many new multilingual keywords targeted for international market. It helps to increase your search appearnce on search engines results pages (SERPs), which can generate more traffic, increase sales and rise the conversion rate.

Is URL Translation available?

In our paid versions we have a feature to translate URL of your website which will give you more SEO advantage. For example http://example.com/about-us → http://example.com/sobre-nosotros

Does it translate emails too?

Email translation feature is in testing stage for our paid version. Please contact our live chat to test email translation now.

How the free version differs from the paid versions?

Free vesion is a nice looking language selector you can place on your website. It has a built in Javascript engine which allows to translate your website automatically to multiple languages. With free version your website URL doesn’t change and the translations are not stored. While paid versions are a translation proxy also known as Translation Delivery Network. We host the translated versions of your website on our cloud network under a language specific domain. In that case every language will have a separate domain and be indexed in search engines, which will help you to increase international traffic and sales.

Do I need to pay for Google Translate API key usage?

No, we provide the automatic translations for free.

In our free version we provide Phrase Based machine translations from Google Translate. While in our paid versions we provide you state of the art Neural Translations from Google Translate. We also do not have limits on the number of words on your website unlike other translate plugins.
By the way we alse offer a cost effective approach for improving the website translations. You can get a automatic translation post-editing service from us, which will be done by a native speaker or order a professional translation. You can get an instant estimate for your website on Website Translation Quote

Can I test before making a payment?

Yes, we have a 15 days free trial for our new customers.

Can I use it on SSL / HTTPS website?

Absolutely! You can use it for our free and paid versions.

Recently we have added support for Let’s Encrypt certificates which are provided for free if you use sub-domain URL structure.

How does the 15 day free trial work?

Trial is available for new customers only. If you do not wish to continue you may cancel any time during the trial period and you will not be charged anything.

How can I be sure that search engines will index my website?

You can check that this website is indexed in Google by searching for site:gtranslate.io.

How I can edit the translations or order professional human translations?

You need to go to the language you want to edit, for instance, French: http://domain.com/fr/ and add ?language_edit=1 to the end of the URL: http://domain.com/fr/?language_edit=1 and you will see the Edit buttons near each text. Read more at How to edit translations?

If you want us to translate your website professionally or provide you a proofreading service for automatic translated content, you can get an instant estimate from Website Translation Quote, where you will get a detailed document with the list of pages, unique word count and prices to translate them.

What should I do if the translate widget does not show on my website?

  1. Make sure that the plugin is installed and activated.
  2. Verify that a check mark is placed in the activation setting located at “Settings > Google Language Translator”.
  3. Verify that the native WordPress function, wp_footer(), is included in your theme’s footer file.
  4. Verify that “Show Language Box?” setting is enabled at “Settings > Google Language Translator”.
  5. Use your browser’s web tools to ensure that CSS styles are not hiding the translation widget.
  6. Contact support at https://gtranslate.io/?xyz=3167#contact

What should I do if there are no languages being displayed in the language box?

  1. Make sure that the plugin is installed and activated.
  2. Verify that a check mark is placed in the activation setting located at “Settings > Google Language Translator”.
  3. Contact support at https://gtranslate.io/?xyz=3167#contact

Can I exclude certain areas of my website from being translated?

Yes! Add the “notranslate” class to the HTML element containing your text. For example, the following text will be excluded from translation: Hello World!

I love this plug-in. So grateful for it as I live in France but need to have an English translation for my blogs also. Now I don’t have to pull my hair out!

Thanks

basically sets itself up hassle free. embeds from gui setup menu. seems to translate correctly. happy with it…

Shortcode suddenly not working and not showing anything. Slow and unhelpful response from tech support, with no attempt to troublshoot and fix the issue.

This solution apparently works very well. I will leave for native speaking users to determine if translations are adequate or good. Hopefully they are.

Read all 513 reviews

“Translate WordPress – Google Language Translator” is open source software. The following people have contributed to this plugin.

Contributors


  • edo888

6.0.19

  • Fix for invisible dropdown selector

6.0.18

  • Fixed going back to original language issue introduced with recent changes to Google Translate widget

6.0.17

  • Google Translate toolbar visibility fix

6.0.16

  • Converted get parameters encoding from rfc1738 to rfc3986
  • Replaced gzdecode with zlib_decode to be zlib encoding type independent

6.0.15

  • Avoid minification of external Google Translate javascript library by WP Rocket cache plugin

6.0.14

  • Fixed information disclosure security issue through url_addon/debug.txt
  • Added admin notification when translation debug mode is on
  • Added is_readable check for config.php file before modifying it
  • Added conflict notice for Advanced Google Translate, My WP Translate and WPML Multilingual CMS plugins

6.0.13

  • Fix for PHP 8
  • CSS added to hide Google Translate popup on text hover

6.0.12

  • Sanitize admin HTML input with wp_kses_post to avoid self hurting
  • Avoid minification of Google Translate javascript library by LiteSpeed Cache and WP Rocket cache plugins

6.0.11

  • New server added into our Translation Delivery Network
  • Tested with new WordPress 5.8 version

6.0.10

  • Possible Cross-site scripting (XSS) vulnerability fixed
    User with Author role can possibly execute javascript code via glt shortcode
    Kudos to pluginvulnerabilities.com for reporting
  • Possible Cross-site scripting (XSS) vulnerability fixed, only possible for sub-domain, sub-directory paid options:
    An attacker can generate a malicious link and if followed by a victim with an old browser without proper URL encoding support (<= IE 9) then javascript code can be executed on victim’s computer.
    Kudos to Ram Gall @ Wordfence for notifying

6.0.9

  • New server added into our Translation Delivery Network
  • Tested with new WordPress 5.7 version

6.0.8

  • Tested with new WordPress 5.6 version
  • Ground up rebuild of our Translation Proxy cloud network for paid customers, now page translations are 3x faster on average.
    • New proprietary spec-compliant HTML parser which is 8x faster than PHP SimpleHTMLDom library used by TranslatePress Multilingual and Weglot Translate plugins
    • In case of invalid HTML, it will be fixed after page translation
    • New caching layer to cache translated pages, previously only original pages were cached
    • Optimized caching with option to clear all original and translated page caches
    • Better error reporting
    • New top of the line hardware with Intel Xeon multi-core processors with up to 5 Ghz clock speed

6.0.7

  • Servers list updated, minor changes

6.0.6

  • Added more servers into the list of our growing Translation Delivery Network

6.0.5

  • Cross-site scripting (XSS) vulnerability fixed: Only possible for sub-domain, sub-directory paid options with hreflang tags enabled:
    An attacker can generate a malicious link and if followed by a victim then javascript code can be executed on victim’s computer

6.0.4

  • Missing closing li tag issue fixed in flags only language switcher
  • Readme updated

6.0.3

  • Solved issue with http Refresh header which was not redirecting to correct URL in translated version
  • Email translation is coming: we need volunteers to test translation of emails, please contact live chat

6.0.2

  • Added translate support for MyHome IDX Broker plugin

6.0.1

  • Bug fixed preventing language selection for some cases

6.0.0

  • Added SEO features (paid only): search engines can index translated pages, URL/slug translation, define hreflang tags
  • Added Live Chat support by GTranslate support team directly in the plugin settings page
  • Google Analytics feature is now on by default
  • Settings page updated for better user experience

5.0.49

  • Added new contributor to the plugin’s readme.txt.

5.0.48

  • Added new setting: Floating Widget Text Color.

5.0.47

  • Fixed an undefined index error in google-language-translator.php.

5.0.46

  • Added new setting: Language Switcher Background Color.

5.0.45

  • Added new setting: Floating Widget background color.
  • Removed border-radius from the floating widget for a more standard look and feel. Please email me if you need the CSS to add back rounded edges.

5.0.44

  • Added new setting: Language Switcher Text Color.

5.0.43

  • Added new setting: Floating Widget position.

5.0.42

  • Added new setting: langauge switcher width.
  • Removed most javascript away from the document body, and into an external javascript file, scripts.js.
  • Added plugin version information to be appended to script and stylesheet files.

5.0.41

  • Re-factored code in google-language-translator.php to remove the duplicate id “flags”.

5.0.40

  • Fixed a minor ‘undefined index’ error in google-language-translator.php

5.0.39

  • Fixed a CSS issue associated with the settings panel changes from the previous update.

5.0.38

  • Fixed a CSS issue associated with the settings panel changes from the previous update. Flags were not aligning properly with align left/right settings.

5.0.37

  • Made some additional adjustments in code for the settings page.

5.0.36

  • Removed undefined variable PHP errors.

5.0.35

  • Updated the plugin to delete an unused option from the database, used in the settings panel.

5.0.34

  • Updated the settings panel to function more logically. Now users choose the languages they want, and can turn on/off flags associated with those langauges.

5.0.33

  • Removed a deprecated jQuery function, and replaced with updated code in the footer_script() function.

5.0.32

  • Fixed the issue with menu translation not working on some mobile devices.
  • Moved element.js script to the footer.

5.0.31

  • Fixed an issue with menu shortcode not displaying the correct flag choice (i.e. for English/Spanish/Portuguese flags).

5.0.30

  • Organized the settings page into sections.
  • Upgraded WordPress.org plugin banner.
  • Added additional attributes to single language shortcodes. Users now have ability to display flag images, change flag sizes, or show/hide the text label.
  • Changed Chinese (Traditional) language flag to the Flag of Taiwan.
  • Fixed a minor display issue with the Google Analytics setting in WordPress Dashboard.

5.0.29

  • Fixed CSS display issues with the floating widget.

5.0.28

  • Fixed CSS display issues with the floating widget.

5.0.27

  • Removed toolbar.js and flags.js and combined to existing files (to improve efficiency of page load and http requests).
  • Added new setting to allow or prevent floating widget text to translate.

5.0.26

  • Fixed a small error in adding the setting for Floating Widget text.

5.0.25

  • Added new setting for custom text in the Floating Widget.
  • Removed “notranslate” class from the Floating Widget text to allow for translation.

5.0.24

  • Improved functionality for flags. Users are now returned to original language when the flag is displayed. The Google Toolbar will be hidden once returning back to the original language. The Google Toolbar will appear again when another translation is made.
  • Fixed the issue with flags not functioning with SIMPLE layout.
  • Removed SIMPLE layout option (which was not working properly) for browsers not using English browsers. The coding challenge for implementing this option is difficult and must be postponed until we find a practical solution.

5.0.23

  • Reverted back to an older version of flags.js. We still have some bugs to work out before releasing the updated version. We apologize for the inconvenience.

5.0.22

  • Changed a line of text on the settings page.
  • Removed a line of redundant javascript to reduce unnecessary page load.
  • Fixed an HTML attribute issue displaying in the menu shortcode.
  • Improved functionality for flags. The flag for default language will now be disabled once users click it’s flag. Flag will be re-enabled once user makes another translation.

5.0.21

  • Added 6 new languages with their associated flags: Hawaiian, Kurdish, Kyrgyz, Luxembourgish, Pashto, and Shona. You can now use these langauges using the menu shortcode, as well.
  • Added a “Select All / Clear All” feature to the settings page. No more finger cramps!

5.0.20

  • Added Corsican as a new language with its associated flag.

5.0.19

  • Added Frisian as a new language with its associated flag.

5.0.18

  • Added Sindhi as a new language with its associated flag.

5.0.17

  • Added Samoan as a new language with its associated flag.
  • Added mobile-responsive CSS to the GLT settings page.

5.0.16

  • Added Xhosa as a new language with its associated flag.

5.0.15

  • Added Amharic as a new language with its associated flag.

5.0.14

  • Fixed a file naming error in google-language-translator.php. This caused flags not to display – we apologize for the inconvenience.

5.0.13

  • Renamed some of the wp_enqueue_script calls to include more unique file names, thus avoiding conflict with other plugins overriding these files.
  • Corrected some file paths to be more accurate/secure.
  • Removed WP Helpdesk logo from the settings page. We are no longer offering these services officially.

5.0.12

  • Revert malicious changes made in 5.0.10

5.0.11

  • Fixed incorrect link

5.0.10

  • Tested up to 4.6

5.0.09

  • Turned off error reporting. I apologize for the inconvenience.

5.0.08

  • Added a new popup-style layout”. You can find this new layout in the settings page located in “Settings > Google Language Translator”.

5.0.07

  • Changed the flag for Chinese(Traditional) to the Taiwanese flag. Requested long ago by a few users – thanks for your months of patience!

5.0.06

  • Fixed a XSS Cross Scripting Vulnerability in the plugin, as requested by WordPress.org. Unnecessary code (during testing) was being posted to the settings page, so the code was removed.

5.0.05

  • Added 3 new options to the settings page: English, Spanish, and Portuguese flag image variations.
  • Fixed an error with the Floating Widget: order of flags was not being honored in certain cases.

5.0.04

  • Corrected the text on the settings page to reflect 91 total flags, instead of 81 flags.

5.0.03

  • Added 10 new languages and associated flags: Chichewa, Kazakh, Malagasy, Malayalam, Myanmar(Burmese), Sesotho, Sinhala, Sundanese, Tajik, and Uzbek.

5.0.02

  • Updated the Tamil flag to use the Indian flag, instead of Tamil Tigers flag.

5.0.01

  • Updated style.css to reflect the syntax error connecting to the Chinese flag.

5.0.0

  • WordPress security updates added to the settings page [wp_nonce_field()].
  • Removed 3 outside Javascript files – these files are now called upon directly from WordPress CMS.
  • Unpacked flags.js p,a,c,k,e,r code. Unknowingly, this method of coding violated WordPress plugin policy.

4.0.9

  • Replaced: incorrect Catalonian flag image, with the correct image. I apologize for any inconvenience.
  • Fixed: Floating Widget issue – previously it loaded 2 times when shortcode was added, which caused it not to work.

4.0.8

  • Fixed the small syntax issue related to the Google Analytics tracking number – it was another cause of the language box not displaying.

4.0.7

  • Fixed a CSS error in the settings panel display.
  • Fixed the coding issue when “Specific Languages” option is chosen – the shortcode was not displaying the language dropdown.

4.0.6

  • Removed: “onclick” events from diplaying directly inside HTML. Converted those events to jQuery.
  • Fixed the shortcode that allows adding single languages to WordPress menus. (New example is shown on settings page.)
  • Consolidated all flag images into image sprites!
  • Re-designed 10 flag images to match the quality of the other flags.
  • Fixed the incorrect “alt” tags associated with flag images. The “alt” tag now displays the language name.
  • Modified text on the settings page – also added some lightbox pop-ups to help explain settings.

4.0.5

  • Fixed: Display bug when using single language shortcode.
  • Added: New link on the Plugins menu page, which links directly to Google Language Translator settings.

4.0.4

  • Added NEW shortcode! Allows placement of single languages into the navigation menu, pages, and posts. See settings panel for usage details.
  • Re-factored code in googlelanguagetranslator.php which reduced code to around 950 lines.
  • Removed the “de-activation” hook, which previously deleted options when plugin de-activated. Added “uninstall” hook instead, so that settings will be preserved only when user deletes the plugin completely.
  • Updated CSS styles for the flags area to prevent themes from overriding layouts.

4.0.3

  • Adjusted CSS styles for the flag display.

4.0.2

  • Eliminated all (or most) HTML validation errors. Big improvement!
  • Re-factored more code to increase efficiency.
  • Added de-activation hook to reset all plugin settings when plugin is de-activated. (CSS Overrides and Google Analytics ID setting will remain in place and won’t be deleted.)
  • Fixed the issue with flag language checkboxes. Users can remove English flag if so desired. Previously, English flag was alway required to stay checked, which was not most user-friendly.

4.0.1

  • Fixed PHP errors that were neglected in upgrade to 4.0.
  • Added conditionals to prevent scripts from loading when the floating widget is turned off.

4.0

  • Added 2 new features: 1) Drag/drop flags to re-arrange their order, and 2) Custom flag sizes (16px to 24px).
  • Re-factored code in google-language-translator.php. Languages are now loaded dynamically and are not hard-coded.

3.0.9

  • Added a title field to the Google Language Translator widget.
  • Removed “unexpected text characters” error upon activation (due to error in activation hook).

3.0.8

  • Added 9 new languages into the plugin (Hausa, Igbo, Maori, Mongolian, Nepali, Punjabi, Somali, Yoruba, Zulu).
  • Corrected an “undefined variable” error that was being generated in Vertical and Horizontal layouts.
  • Re-structured coding once again into an Object-Oriented approach.
  • Moved all functions of the base class into ‘googlelanguagetranslator.php’ and the widget into ‘widget.php’.
  • Moved all javascript files into it’s own JS folder.
  • Fixed an display issue with “Edit Translations” – they were being hidden when “No branding” option was chosen.
  • Corrected various “comma” errors in the string that outputs the script for loading the translator.
  • Changed Changelog in readme.txt to show most recent changes first, instead of last.

3.0.7

  • Removed an unnecessary CSS file, left over from development. Sorry for any inconvenience if you received display errors.

3.0.6

  • Corrected a small display error in displaying the floating widget correctly.

3.0.5

  • Added new Floating Widget (see settings page). The Floating Widget is simply another way for allowing website visitors to translate languages. The functionality is built-in with the existing flag preferences, and can be turned on or off at the administrator’s preference. The floating widget can also function in full with both the language box and/or flags showing OR hiding, so the administrator has full control of how it displays. The floating widget is placed at bottom right of the website in the free version, but can be placed in other locations by changing CSS styles associated with the box.
  • Fixed the issue with Dashboard styles loading on the wrong pages. This was causing some annoying display issues on the WordPress Dashboard.

3.0.4

  • Re-factored/re-arranged more code in google languagetransltor.php by placing them into separate files.
  • Fixed the issue of Custom CSS box not displaying it’s styles to the website. This was only missed in this last update, due to re-arrangement of the files. Sorry for any inconvenience.
  • Removed style2.php file, which is unnecessary and was being used in testing.

3.0.3

  • Re-factored/re-arranged some of the code in googlelanguagetranslator.php by placing them into separate files.
  • Fixed a minor coding issue in glt_widget.php – this was generating an error in WordPress when debugging.
  • Moved all CSS code into a single file. The result is nice, clean inline CSS code that is now called only once.
  • Fixed some additional CSS display issues.

3.0.2

  • Adjusted additional minor invalid HTML issues on the settings page, and also in the front-end plugin display.

3.0.1

  • Changed the url request to Google to allow both unsecured and secured page translations. Previously, some users experienced errors when trying to use the translator on “https://” (secured) pages.
  • Adjusted some minor spacing issues in the settings page HTML (caused some annoying red HTML errors when using “View Source” in right-click menu).
  • Removed old CSS styles that were added in the previous 3.0 update – the styles were added when Google servers were being updated, and were producing major translation dislay issues until their update was complete. Now the styles I added are no longer needed.

3.0

  • Correct a small CSS error that affected the showing/hiding of the Google toolbar.

2.9

***IMPORTANT: Google’s most recent server update is producing display issues for website translation tool. There are major display issues with the translation toolbar and also the translations editing interface. Version 2.9 temporarily hides the edit translation functionality until Google decides to fix this issue, although you can still edit translations directly through your Google account at translate.google.com. Please direct any support requests through WordPress.org and we will be happy to assist you.
* Fixed Google Translation toolbar display issue
* Fixed the Edit Translation interface by hiding it temporarily until Google fixes this
* Removed some unneeded styles from the style sheet.
* Fixed some CSS issues for the Google Branding display, which was affected by Google’s most recent update

2.8

  • Added an option to allow users to manage their own translations directly through their Google Translate account (free). When activated, users can hover over the text of their website, and edit the translations from the webpage directly. Google will remember these translations, and then serve them to users once the edits are made. Users must install the Google Translate Customization meta tag provided through Google Translate here: translate.google.com/manager/website/settings. To obtain this meta tag, users need to configure the Google Translate tool directly from this website (although they will not use this because the plugin provides it), then the user can obtain the meta tag on the “Get Code” screen, which is displayed after configuring the Google Translate tool on this webpage.
  • Added an option to allow users to turn on/off Google’s multilanguagePage option, that when activated, the original website content will be a forced translation, instead of original content (but only after a translation is made.)
  • Added more flexible styles to the settings page, so that left and right panels display nicely to the user.

2.7

  • Added Google Analytics tracking capability to the plugin.
  • Added a “CSS Styles” box in the settings panel.
  • Changed the Catalonian flag to its correct flag image.
  • Fixed coding issues that previously updated options incorrectly, which is why many users experienced display issues. All options are now initialized upon plugin activation, which should fix this issue permanently.
  • Fixed a glitch in our usage of the translate API. Previously, when the user clicked the default language, it would toggle back and forth between the default language and “Afrikaans” language. Now, users will see the correct language displayed at all times, no matter how many times it is clicked.

2.6

  • Added defaults to all options to ensure there are no more issues with the translator displaying upon installation. Again, sorry for any inconvenience.

2.5

  • Eliminated an internal WordPress error being generated from a coding mistake.
  • Added a default option for the Translator alingment. Previously, this was causing the plugin to disapppear.

2.4

  • Found a couple of small display errors in the settings page after uploading version 2.3. Sorry for any inconvenience!

2.3

  • Added a “Preview” area on the settings page that allows you to see your settings in action.
  • Added custom flag support for all languages (custom flags available ONLY when selecting the “ALL Languages” setting.
  • Added an option that allows left/right alignment of the translation tool.
  • Added the “Google Language Translator” widget.
  • Updated googlelanguagetranslator.php to properly register setting in the admin settings panel.

2.2

  • Added language “Portuguese” and “German” to the Original Language drop-down option on the settings page.
  • Changed flag image for the English language (changed United States flag to the United Kingdom flag).
  • Added link in the settings panel that points to Google’s Attribution Policy.

2.1

  • Added language “Dutch” to the Original Language drop-down option on the settings page.
  • Added a new CSS class that more accurately hides the “Powered by” text when hiding Google’s branding. In previous version, the “Powered by” text was actually disguised by setting it’s color to “transparent”, but now we have set it’s font-size to 0px instead.

2.0

  • Corrected some immediate errors in the 1.9 update.

1.9

  • Added 7 flag image choices that, when clicked by website visitors, will change the language displayed, both on the website, AND in the drop-down box (flag language choices are limited to those provided in this plugin).
  • Added 6 additional languages to the translator, as provided in Google’s most recent updates ( new languages include Bosnian, Cebuano, Khmer, Marathi, Hmong, Javanese ).
  • Corrected a minor technical issue where the Czech option (on the backend) was incorrectly displaying the Croatian language on the front end.
  • Added jQuery functionality to the settings panel to improve the user experience.
  • Added an option for users to display/hide the flag images.
  • Added an option for users to display/hide the translate box when flags are displayed.
  • Removed the settings.css file – I found a better way of displaying the options without CSS.

1.8

  • Modified google-language-translator.php to display the correct output to the browser when horizontal layout is selected. Previously, it was not displaying at all.

1.7

  • Modified google-language-translator.php so that jQuery and CSS styles were enqueued properly onto the settings page only. Previously, jQuery functionality and CSS styles were being added to all pages of the WordPresss Dashboard, which was causing functionality and display issues for some users.

1.6

  • Added “Specific Language” support to the plugin settings, which allows the user to choose specific languages that are displayed to website visitors.

1.5

Added “Original Language” support to the plugin settings, which allows the user to choose the original language of their website, which ultimately removes the original language as a choice in the language drop-down presented to website visitors.

1.4

Corrected display problems associated with CSS styles not being placed correctly in wp_head.

1.3

  • HTML display problem in the sidebar area now fixed. Previously, inserting the [google-translator] plugin into a text widget caused it to display above the widget, instead of inside of it.

1.2

  • Shortcode support is now available for adding [google-translator] to text widgets. I apologize for any inconvenience this may have caused.

1.1

  • The shortcode supplied on the settings page was updated to display ‘[google-translator]’.
Источник
Google Translate

Google Translate logo.svg
Screenshot of Google Translate.png

Google Translate website homepage

Type of site

 Neural machine translation
Available in 133 languages; see below
Owner Google
URL translate.google.com
Commercial Yes
Registration Optional
Users Over 500 million people daily
Launched April 28, 2006; 16 years ago (as statistical machine translation)[1]
November 15, 2016; 6 years ago (as neural machine translation)[2]
Current status Active

Google Translate is a multilingual neural machine translation service developed by Google to translate text, documents and websites from one language into another. It offers a website interface, a mobile app for Android and iOS, and an API that helps developers build browser extensions and software applications.[3] As of April 2023, Google Translate supports 133 languages at various levels,[4] and as of April 2016, claimed over 500 million total users, with more than 100 billion words translated daily,[5] after the company stated in May 2013 that it served over 200 million people daily.[6]

Launched in April 2006 as a statistical machine translation service, it used United Nations and European Parliament documents and transcripts to gather linguistic data. Rather than translating languages directly, it first translates text to English and then pivots to the target language in most of the language combinations it posits in its grid,[7] with a few exceptions including Catalan-Spanish.[8] During a translation, it looks for patterns in millions of documents to help decide which words to choose and how to arrange them in the target language. Its accuracy, which has been criticized on several occasions,[9] has been measured to vary greatly across languages.[10] In November 2016, Google announced that Google Translate would switch to a neural machine translation engine – Google Neural Machine Translation (GNMT) – which translates «whole sentences at a time, rather than just piece by piece. It uses this broader context to help it figure out the most relevant translation, which it then rearranges and adjusts to be more like a human speaking with proper grammar».[2]

History

Google Translate is a web-based free-to-user translation service developed by Google in April 2006.[11] It translates multiple forms of texts and media such as words, phrases and webpages.

Originally, Google Translate was released as a statistical machine translation service.[11] The input text had to be translated into English first before being translated into the selected language.[11] Since SMT uses predictive algorithms to translate text, it had poor grammatical accuracy. Despite this, Google initially did not hire experts to resolve this limitation due to the ever-evolving nature of language.[11]

In January 2010, Google introduced an Android app and iOS version in February 2011 to serve as a portable personal interpreter.[11] As of February 2010, it was integrated into browsers such as Chrome and was able to pronounce the translated text, automatically recognize words in a picture and spot unfamiliar text and languages.[11]

In May 2014, Google acquired Word Lens to improve the quality of visual and voice translation.[12] It is able to scan text or a picture using the device and have it translated instantly. Moreover, the system automatically identifies foreign languages and translates speech without requiring individuals to tap the microphone button whenever speech translation is needed.[12]

In November 2016, Google transitioned its translating method to a system called neural machine translation.[13] It uses deep learning techniques to translate whole sentences at a time, which has been measured to be more accurate between English and French, German, Spanish, and Chinese.[14] No measurement results have been provided by Google researchers for GNMT from English to other languages, other languages to English, or between language pairs that do not include English. As of 2018, it translates more than 100 billion words a day.[13]

In 2017, Google Translate was used during a court hearing when court officials at Teesside Magistrates’ Court failed to book an interpreter for the Chinese defendant.[15]

At the end of September 2022, Google Translate was discontinued in mainland China, which Google said was due to «low usage».[16][17] (see Internet censorship in China)

Functions

Google Translate can translate multiple forms of text and media, which includes text, speech, and text within still or moving images.[18][19] Specifically, its functions include:

  • Written Words Translation: a function that translates written words or text to a foreign language.[20]
  • Website Translation: a function that translates a whole webpage to selected languages.[21]
  • Document Translation: a function that translates a document uploaded by the users to selected languages. The documents should be in the form of: .doc, .docx, .odf, .pdf, .ppt, .pptx, .ps, .rtf, .txt, .xls, .xlsx.[21]
  • Speech Translation: a function that instantly translates spoken language into the selected foreign language.[22]
  • Mobile App Translation: in 2018, Google introduced its new Google Translate feature called «Tap to Translate», which made instant translation accessible inside any app without exiting or switching it.[23]
  • Image Translation: a function that identifies text in a picture taken by the users and translates text on the screen instantly by images.[24]
  • Handwritten Translation: a function that translates language that are handwritten on the phone screen or drawn on a virtual keyboard without the support of a keyboard.[25]
  • Bilingual Conversation Translation: a function that translates conversations in multiple languages.[26]
  • Transcription: a function that transcribes speech in different languages.[27]

For most of its features, Google Translate provides the pronunciation, dictionary, and listening to translation. Additionally, Google Translate has introduced its own Translate app, so translation is available with a mobile phone in offline mode.[18][19]

Features

Web interface

Google Translate produces approximations across languages of multiple forms of text and media, including text, speech, websites, or text on display in still or live video images.[18][19] For some languages, Google Translate can synthesize speech from text,[20] and in certain pairs it is possible to highlight specific corresponding words and phrases between the source and target text. Results are sometimes shown with dictional information below the translation box, but it is not a dictionary[28] and has been shown to invent translations in all languages for words it does not recognize.[29] If «Detect language» is selected, text in an unknown language can be automatically identified. In the web interface, users can suggest alternate translations, such as for technical terms, or correct mistakes. These suggestions may be included in future updates to the translation process. If a user enters a URL in the source text, Google Translate will produce a hyperlink to a machine translation of the website.[21] Users can save translation proposals in a «phrasebook» for later use, and a shareable URL is generated for each translation.[30][31] For some languages, text can be entered via an on-screen keyboard, through handwriting recognition, or speech recognition.[25][22] It is possible to enter searches in a source language that are first translated to a destination language allowing one to browse and interpret results from the selected destination language in the source language.

Texts written in the Arabic, Cyrillic, Devanagari and Greek scripts can be transliterated automatically from phonetic equivalents written in the Latin alphabet. The browser version of Google Translate provides the option to show phonetic equivalents of text translated from Japanese to English. The same option is not available on the paid API version.

Accent of English that the «text-to-speech» audio of Google Translate of each country uses:

  British (Received Pronunciation) (female)

  General American (female)

  General Australian (female)

  Indian (female)

  No Google translate service

Many of the more popular languages have a «text-to-speech» audio function that is able to read back a text in that language, up to a few dozen words or so. In the case of pluricentric languages, the accent depends on the region: for English, in the Americas, most of the Asia-Pacific and Western Asia, the audio uses a female General American accent, whereas in Europe, Hong Kong, Malaysia, Singapore, Guyana and all other parts of the world, a female British (Received Pronunciation) accent is used, except for a special General Australian accent used in Australia, New Zealand and Norfolk Island, and an Indian English accent used in India; for Spanish, in the Americas, a Latin American accent is used, while in the other parts of the world, a Castilian accent is used; for Portuguese, a São Paulo accent is used around the world, except in Portugal, where their native accent is used instead; for French, a Quebec accent is used in Canada, while in the other parts of the world, a standard European accent is used; for Bengali, a male Bangladeshi accent is used, except in India, where a special female Indian Bengali accent is used instead. Until March 2023, some less widely spoken languages used the open-source eSpeak synthesizer for their speech; producing a robotic, awkward voice that may be difficult to understand.

Browser integration

Google Translate is available in some web browsers as an optional downloadable extension that can run the translation engine, which allow right-click command access to the translation service.[32][33][34] In February 2010, Google Translate was integrated into the Google Chrome browser by default, for optional automatic webpage translation.[35][36][37]

Mobile app

Google Translate

Google Translate logo.svg

Screenshot

Google Translate iOS app screenshot.png

A screenshot of the iOS app of Google Translate, showing an English translation of «Coffee» to Simplified Chinese «咖啡» or «Kāfēi«
Developer(s) Google
Initial release January 1, 2010; 13 years ago (for Android)
February 8, 2011; 12 years ago (for iOS)
Stable release(s) [±]
Android 6.35.29.444893127.4 / April 28, 2022; 11 months ago[38]
iOS 6.34.0 / April 19, 2022; 11 months ago[39]
Platform
  • Android 6.0 and later
  • iOS 12.4 and later
Size 37.44 MB (Android)
123.7 MB (iOS)
Available in 133 languages; see below
Type Neural machine translation
Website translate.google.com/m?hl=en

The Google Translate app for Android and iOS supports 133 languages and can propose translations for 37 languages via photo, 32 via voice in «conversation mode», and 27 via live video imagery in «augmented reality mode».[40][41]

The Android app was released in January 2010, and for iOS on February 8, 2011,[42] after an HTML5 web application was released for iOS users in August 2008.[43] The Android app is compatible with devices running at least Android 2.1, while the iOS app is compatible with iPod Touches, iPads, and iPhones updated to iOS 7.0+.[44]

A January 2011 Android version experimented with a «Conversation Mode» that aims to allow users to communicate fluidly with a nearby person in another language.[45] Originally limited to English and Spanish, the feature received support for 12 new languages, still in testing, the following October.[46][47]

The ‘Camera input’ functionality allows users to take a photograph of a document, signboard, etc. Google Translate recognises the text from the image using optical character recognition (OCR) technology and gives the translation. Camera input is not available for all languages.

In January 2015, the apps gained the ability to propose translations of physical signs in real time using the device’s camera, as a result of Google’s acquisition of the Word Lens app.[48][49][12] The original January launch only supported seven languages, but a July update added support for 20 new languages, with the release of a new implementation that utilizes convolutional neural networks, and also enhanced the speed and quality of Conversation Mode translations (augmented reality).[40][41][50][51][52] The feature was subsequently renamed Instant Camera. The technology underlying Instant Camera combines image processing and optical character recognition, then attempts to produce cross-language equivalents using standard Google Translate estimations for the text as it is perceived.[53]

On May 11, 2016, Google introduced Tap to Translate for Google Translate for Android. Upon highlighting text in an app that is in a foreign language, Translate will pop up inside of the app and offer translations.[54]

API

On May 26, 2011, Google announced that the Google Translate API for software developers had been deprecated and would cease functioning.[55][56][57] The Translate API page stated the reason as «substantial economic burden caused by extensive abuse» with an end date set for December 1, 2011.[58] In response to public pressure, Google announced in June 2011 that the API would continue to be available as a paid service.[55][56][59]

Because the API was used in numerous third-party websites and apps, the original decision to deprecate it led some developers to criticize Google and question the viability of using Google APIs in their products.[60][61]

Google Assistant

Google Translate also provides translations for Google Assistant and the devices that Google Assistant runs on such as Google Nest and Pixel Buds.

Supported languages

As of April 2023, the following 133 languages are supported by Google Translate.[4]

  1. Afrikaans
  2. Albanian
  3. Amharic
  4. Arabic
  5. Armenian
  6. Assamese
  7. Aymara
  8. Azerbaijani
  9. Bhojpuri
  10. Basque
  11. Belarusian
  12. Bengali
  13. Bambara
  14. Bosnian
  15. Bulgarian
  16. Burmese (Myanmar)
  17. Catalan
  18. Cebuano
  19. Chewa (Chichewa)
  20. Chinese (Simplified)
  21. Chinese (Traditional)
  22. Corsican
  23. Croatian
  24. Czech
  25. Danish
  26. Dogri
  27. Dutch
  28. English
  29. Esperanto
  30. Estonian
  31. Ewe
  32. Finnish
  33. French
  34. Galician
  35. Georgian
  36. German
  37. Greek
  38. Guarani
  39. Gujarati
  40. Haitian Creole
  41. Hausa
  42. Hawaiian
  43. Hebrew
  44. Hindi
  45. Hmong
  46. Hungarian
  47. Icelandic
  48. Igbo
  49. Ilocano
  50. Indonesian
  51. Irish
  52. Italian
  53. Japanese
  54. Javanese
  55. Kannada
  56. Kazakh
  57. Khmer
  58. Kinyarwanda
  59. Konkani
  60. Korean
  61. Krio
  62. Kurdish (Kurmanji)
  63. Kurdish (Sorani)
  64. Kyrgyz
  65. Lao
  66. Latin
  67. Latvian
  68. Lingala
  69. Lithuanian
  70. Luganda
  71. Luxembourgish
  72. Macedonian
  73. Maithili
  74. Malagasy
  75. Malay
  76. Malayalam
  77. Maldivian (Dhivehi)
  78. Maltese
  79. Māori (Maori)
  80. Marathi
  81. Meitei (Manipuri, Meiteilon)
  82. Mizo
  83. Mongolian
  84. Nepali
  85. Northern Sotho (Sepedi)
  86. Norwegian (Bokmål)
  87. Odia (Oriya)
  88. Oromo
  89. Pashto
  90. Persian
  91. Polish
  92. Portuguese
  93. Punjabi (Gurmukhi)
  94. Quechua
  95. Romanian
  96. Russian
  97. Samoan
  98. Sanskrit
  99. Scottish Gaelic (Scots Gaelic)
  100. Serbian
  101. Shona
  102. Sindhi
  103. Sinhala
  104. Slovak
  105. Slovenian
  106. Somali
  107. Sotho (Sesotho)
  108. Spanish
  109. Sundanese
  110. Swahili
  111. Swedish
  112. Tagalog (Filipino)
  113. Tajik
  114. Tamil
  115. Tatar
  116. Telugu
  117. Thai
  118. Tigrinya
  119. Tsonga
  120. Turkish
  121. Turkmen
  122. Twi
  123. Ukrainian
  124. Urdu
  125. Uyghur
  126. Uzbek
  127. Vietnamese
  128. Welsh
  129. West Frisian (Frisian)
  130. Xhosa
  131. Yiddish
  132. Yoruba
  133. Zulu

Stages

Languages in development and beta version

The following languages are not yet supported by Google Translate, but are available in the Translate Community. As of April 2023, there are 103 languages in development, of which 9 are in beta version.[82]

The languages in beta version are closer to their public release and have an exclusive extra option to contribute that allows evaluating up to 4 translations of the beta version by translating an English text of up to 50 characters.

There is currently a petition for Google to add Cree to Google Translate, but as of April 2023, it is not one of the languages in development yet.[83][84]

  1. Acehnese
  2. Adyghe
  3. Afar BETA
  4. Aragonese
  5. Avar (Avaric)
  6. Bagheli
  7. Balochi (Baluchi)
  8. Bangala
  9. Baoulé
  10. Bashkir
  11. Berber (Tamazight) BETA
  12. Betawi
  13. Boro (India) (Bodo) BETA
  14. Breton
  15. Cantonese
  16. Chechen
  17. Cherokee
  18. Chhattisgarhi
  19. Chittagonian
  20. Chuvash
  21. Deccani
  22. Dholuo
  23. Dyula
  24. Dzongkha
  25. Edo
  26. Efik
  27. Esan
  28. Fon
  29. Fula (Fulah) BETA
  30. Gagauz
  31. Garhwali
  32. Greenlandic (Kalaallisut)
  33. Haryanvi
  34. Hiligaynon
  35. Inuktitut
  36. Isoko
  37. Kamba
  38. Kanuri
  39. Kapampangan (Pampanga)
  40. Karachay-Balkar
  41. Karakalpak (Kara-Kalpak)
  42. Kashmiri
  43. Kedah Malay
  44. Khakas
  45. Khandeshi (Ahirani)
  46. Khorasani Turkic
  47. Kikuyu
  48. Kokborok (Tripuri)
  49. Kumyk
  50. Kʼicheʼ
  51. Lakota
  52. Lhasa Tibetan (Tibetan) BETA
  53. Luba-Kasai (Tshiluba)
  54. Luba-Katanga
  55. Madurese
  56. Magahi
  57. Marwari
  58. Mazanderani
  59. Minangkabau
  60. Montenegrin
  61. Mooré (Mossi)
  62. Navajo
  63. Newar (Nepalbhasa) BETA
  64. Nigerian Pidgin
  65. Northern Sami
  66. Occitan
  67. Pattani Malay
  68. Qashqai
  69. Rajasthani
  70. Rangpuri (Kamtapuri)
  71. Rohingya
  72. Romansh
  73. Sadri
  74. Salar
  75. Samogitian
  76. Sango
  77. Santali BETA
  78. Saraiki BETA
  79. Serrano
  80. Shor
  81. Siberian Tatar
  82. Sicilian
  83. Southern Altai
  84. Southern Ndebele
  85. Surjapuri
  86. Swahili Congo
  87. Sylheti
  88. Tiv
  89. Toba Batak (Batak Toba)
  90. Tok Pisin
  91. Tonga (Zambia and Zimbabwe) (Chitonga)
  92. Tswana (Setswana)
  93. Tswa
  94. Tuvan (Tuvinian)
  95. Urhobo
  96. Urum
  97. Varhadi (Varhadi-Nagpuri)
  98. Venda (Tshivenda)
  99. Wolof
  100. Yakut
  101. Yucatec Maya (Yucateco) BETA
  102. Zaza (Zazaki)
  103. Zhuang

Translation methodology

In April 2006, Google Translate launched with a statistical machine translation engine.[1]

Google Translate does not apply grammatical rules, since its algorithms are based on statistical or pattern analysis rather than traditional rule-based analysis. The system’s original creator, Franz Josef Och, has criticized the effectiveness of rule-based algorithms in favor of statistical approaches.[85][86] Original versions of Google Translate were based on a method called statistical machine translation, and more specifically, on research by Och who won the DARPA contest for speed machine translation in 2003. Och was the head of Google’s machine translation group until leaving to join Human Longevity, Inc. in July 2014.[87]

Google Translate does not translate from one language to another (L1 → L2). Instead, it often translates first to English and then to the target language (L1 → EN → L2).[88][89][90][7][91] However, because English, like all human languages, is ambiguous and depends on context, this can cause translation errors. For example, translating vous from French to Russian gives vous → you → ты OR Bы/вы.[92] If Google were using an unambiguous, artificial language as the intermediary, it would be vous → you → Bы/вы OR tu → thou → ты. Such a suffixing of words disambiguates their different meanings. Hence, publishing in English, using unambiguous words, providing context, using expressions such as «you all» may or may not make a better one-step translation depending on the target language.

The following languages do not have a direct Google translation to or from English. These languages are translated through the indicated intermediate language (which in most cases is closely related to the desired language but more widely spoken) in addition to through English:[citation needed]

  • Belarusian (be ↔ ru ↔ en ↔ other);
  • Catalan (ca ↔ es ↔ en ↔ other);
  • Galician (gl ↔ pt ↔ en ↔ other);
  • Haitian Creole (ht ↔ fr ↔ en ↔ other);
  • Korean (ko ↔ ja ↔ en ↔ other);
  • Slovak (sk ↔ cs ↔ en ↔ other);
  • Ukrainian (uk ↔ ru ↔ en ↔ other);[91]
  • Urdu (ur ↔ hi ↔ en ↔ other).

According to Och, a solid base for developing a usable statistical machine translation system for a new pair of languages from scratch would consist of a bilingual text corpus (or parallel collection) of more than 150-200 million words, and two monolingual corpora each of more than a billion words.[85] Statistical models from these data are then used to translate between those languages.

To acquire this huge amount of linguistic data, Google used United Nations and European Parliament documents and transcripts.[93][94] The UN typically publishes documents in all six official UN languages, which has produced a very large 6-language corpus.

Google representatives have been involved with domestic conferences in Japan where it has solicited bilingual data from researchers.[95]

When Google Translate generates a translation proposal, it looks for patterns in hundreds of millions of documents to help decide on the best translation. By detecting patterns in documents that have already been translated by human translators, Google Translate makes informed guesses (AI) as to what an appropriate translation should be.[96]

Before October 2007, for languages other than Arabic, Chinese and Russian, Google Translate was based on SYSTRAN, a software engine which is still used by several other online translation services such as Babel Fish (now defunct). From October 2007, Google Translate used proprietary, in-house technology based on statistical machine translation instead,[97][98] before transitioning to neural machine translation.

Google has crowdsourcing features for volunteers to be a part of its «Translate Community», intended to help improve Google Translate’s accuracy.[99][100][101][102][103] Volunteers can select up to five languages to help improve translation; users can verify translated phrases and translate phrases in their languages to and from English, helping to improve the accuracy of translating more rare and complex phrases. In August 2016, a Google Crowdsource app was released for Android users, in which translation tasks are offered.[105][106] There are three ways to contribute. First, Google will show a phrase that one should type in the translated version.[101] Second, Google will show a proposed translation for a user to agree, disagree, or skip.[101] Third, users can suggest translations for phrases where they think they can improve on Google’s results. Tests in 44 languages show that the «suggest an edit» feature led to an improvement in a maximum of 40% of cases over four years.[107]

Statistical machine translation

Although Google deployed a new system called neural machine translation for better quality translation, there are languages that still use the traditional translation method called statistical machine translation. It is a rule-based translation method that utilizes predictive algorithms to guess ways to translate texts in foreign languages. It aims to translate whole phrases rather than single words then gather overlapping phrases for translation. Moreover, it also analyzes bilingual text corpora to generate statistical model that translates texts from one language to another.[108][109]

Google Neural Machine Translation

In September 2016, a research team at Google announced the development of the Google Neural Machine Translation system (GNMT) to increase fluency and accuracy in Google Translate[2][110] and in November announced that Google Translate would switch to GNMT.

Google Translate’s neural machine translation system uses a large end-to-end artificial neural network that attempts to perform deep learning,[2][111][112] in particular, long short-term memory networks.[113][114][14][115] GNMT improves the quality of translation over SMT in some instances because it uses an example-based machine translation (EBMT) method in which the system «learns from millions of examples.»[111] According to Google researchers, it translates «whole sentences at a time, rather than just piece by piece. It uses this broader context to help it figure out the most relevant translation, which it then rearranges and adjusts to be more like a human speaking with proper grammar».[2] GNMT’s «proposed architecture» of «system learning» has been implemented on over a hundred languages supported by Google Translate.[111] With the end-to-end framework, Google states but does not demonstrate for most languages that «the system learns over time to create better, more natural translations.»[2] The GNMT network attempts interlingual machine translation, which encodes the «semantics of the sentence rather than simply memorizing phrase-to-phrase translations»,[111][90] and the system did not invent its own universal language, but uses «the commonality found in between many languages».[116] GNMT was first enabled for eight languages: to and from English and Chinese, French, German, Japanese, Korean, Portuguese, Spanish and Turkish.[2][110] In March 2017, it was enabled for Hindi, Russian and Vietnamese,[117] followed by Bengali, Gujarati, Indonesian, Kannada, Malayalam, Marathi, Punjabi, Tamil and Telugu in April.[118]

Accuracy

Google Translate is not as reliable as human translation. When text is well-structured, written using formal language, with simple sentences, relating to formal topics for which training data is ample, it often produces conversions similar to human translations between English and a number of high-resource languages.[119][13] Accuracy decreases for those languages when fewer of those conditions apply, for example when sentence length increases or the text uses familiar or literary language. For many other languages vis-à-vis English, it can produce the gist of text in those formal circumstances.[120] Human evaluation from English to all 102 languages shows that the main idea of a text is conveyed more than 50% of the time for 35 languages. For 67 languages, a minimally comprehensible result is not achieved 50% of the time or greater.[10] A few studies have evaluated Chinese,[citation needed] French,[citation needed] German,[citation needed] and Spanish[citation needed] to English, but no systematic human evaluation has been conducted from most Google Translate languages to English. Speculative language-to-language scores extrapolated from English-to-other measurements[10] indicate that Google Translate will produce translation results that convey the gist of a text from one language to another more than half the time in about 1% of language pairs, where neither language is English.[121] Research conducted in 2011 showed that Google Translate got a slightly higher score than the UCLA minimum score for the English Proficiency Exam.[122] Due to its identical choice of words without considering the flexibility of choosing alternative words or expressions, it produces a relatively similar translation to human translation from the perspective of formality, referential cohesion, and conceptual cohesion.[123] Moreover, a number of languages are translated into a sentence structure and sentence length similar to a human translation.[123] Furthermore, Google carried out a test that required native speakers of each language to rate the translation on a scale between 0 and 6, and Google Translate scored 5.43 on average.[13]

When used as a dictionary to translate single words, Google Translate is highly inaccurate because it must guess between polysemic words. Among the top 100 words in the English language, which make up more than 50% of all written English, the average word has more than 15 senses,[124] which makes the odds against a correct translation about 15 to 1 if each sense maps to a different word in the target language. Most common English words have at least two senses, which produces 50/50 odds in the likely case that the target language uses different words for those different senses. The odds are similar from other languages to English. Google Translate makes statistical guesses that raise the likelihood of producing the most frequent sense of a word, with the consequence that an accurate translation will be unobtainable in cases that do not match the majority or plurality corpus occurrence. The accuracy of single-word predictions has not been measured for any language. Because almost all non-English language pairs pivot through English, the odds against obtaining accurate single-word translations from one non-English language to another can be estimated by multiplying the number of senses in the source language with the number of senses each of those terms have in English. When Google Translate does not have a word in its vocabulary, it makes up a result as part of its algorithm.[29]

Google Translate’s inaccuracy can be illustrated by translating from one language to another then back to the original language. This will often result in nonsensical constructions, rather than recovering the original text.[citation needed]

Limitations

Google Translate, like other automatic translation tools, has its limitations. The service limits the number of paragraphs and the range of technical terms that can be translated, and while it can help the reader understand the general content of a foreign language text, it does not always deliver accurate translations, and most times it tends to repeat verbatim the same word it is expected to translate. Grammatically, for example, Google Translate struggles to differentiate between imperfect and perfect aspects in Romance languages so habitual and continuous acts in the past often become single historical events. Although seemingly pedantic, this can often lead to incorrect results (to a native speaker of for example French and Spanish) which would have been avoided by a human translator. Knowledge of the subjunctive mood is virtually non-existent.[125][unreliable source?] Moreover, the formal second person (vous) is often chosen, whatever the context or accepted usage.[126][unreliable source?] Since its English reference material contains only «you» forms, it has difficulty translating a language with «you all» or formal «you» variations.

Due to differences between languages in investment, research, and the extent of digital resources, the accuracy of Google Translate varies greatly among languages.[13] Some languages produce better results than others. Most languages from Africa, Asia, and the Pacific, tend to score poorly in relation to the scores of many well-financed European languages, Afrikaans and Chinese being the high-scoring exceptions from their continents.[10][127] No languages indigenous to Australia are included within Google Translate. Higher scores for European can be partially attributed to the Europarl Corpus, a trove of documents from the European Parliament that have been professionally translated by the mandate of the European Union into as many as 21 languages. A 2010 analysis indicated that French to English translation is relatively accurate,[128] and 2011 and 2012 analyses showed that Italian to English translation is relatively accurate as well.[129][130] However, if the source text is shorter, rule-based machine translations often perform better; this effect is particularly evident in Chinese to English translations. While edits of translations may be submitted, in Chinese specifically one cannot edit sentences as a whole. Instead, one must edit sometimes arbitrary sets of characters, leading to incorrect edits.[128] A good example is Russian-to-English. Formerly one would use Google Translate to make a draft and then use a dictionary and common sense to correct the numerous mistakes. As of early 2018 Translate is sufficiently accurate to make the Russian Wikipedia accessible to those who can read English. The quality of Translate can be checked by adding it as an extension to Chrome or Firefox and applying it to the left language links of any Wikipedia article. It can be used as a dictionary by typing in words. One can translate from a book by using a scanner and an OCR like Google Drive, but this takes about five minutes per page.

In its Written Words Translation function, there is a word limit on the amount of text that can be translated at once.[20] Therefore, long text should be transferred to a document form and translated through its Document Translate function.[20]

Moreover, like all machine translation programs, Google Translate struggles with polysemy (the multiple meanings a word may have)[131][13] and multiword expressions (terms that have meanings that cannot be understood or translated by analyzing the individual word units that compose them).[132] A word in a foreign language might have two different meanings in the translated language. This might lead to mistranslations.

Additionally, grammatical errors remain a major limitation to the accuracy of Google Translate.[133]

Open-source licenses and components

Language WordNet License
Albanian Albanet CC BY 3.0/GPL 3
Arabic Arabic WordNet CC BY-SA 3.0
Catalan Multilingual Central Repository CC BY 3.0
Chinese Chinese Wordnet (Taiwan) Wordnet
Danish DanNet Wordnet
English Princeton WordNet Wordnet
Finnish FinnWordNet Wordnet
French WOLF (WOrdnet Libre du Francais) CeCILL-C
Galician Multilingual Central Repository CC BY 3.0
Haitian Creole MIT-Haiti Initiative CC BY 4.0
Hebrew Hebrew Wordnet Wordnet
Indonesian Wordnet Bahasa MIT
Italian MultiWordNet CC BY 3.0
Japanese Japanese Wordnet Wordnet
Malay Wordnet Bahasa MIT
Norwegian Norwegian Wordnet Wordnet
Persian Persian Wordnet Free-to-use
Polish plWordNet Wordnet
Portuguese OpenWN-PT CC BY-SA 3.0
Spanish Multilingual Central Repository CC BY 3.0
Thai Thai Wordnet Wordnet

Irish language data from Foras na Gaeilge’s New English-Irish Dictionary (English database designed and developed for Foras na Gaeilge by Lexicography MasterClass Ltd.)

Welsh language data from Gweiadur by Gwerin.

Certain content is copyright Oxford University Press USA. Some phrase translations come from Wikitravel.[134]

Reviews

Shortly after launching the translation service for the first time, Google won an international competition for English–Arabic and English–Chinese machine translation.[135]

Translation mistakes and oddities

Since Google Translate used statistical matching to translate, translated text can often include apparently nonsensical and obvious errors,[136] often swapping common terms for similar but nonequivalent common terms in the other language,[137] as well as inverting sentence meaning.[138] Novelty websites like Bad Translator and Translation Party have utilized the service to produce humorous text by translating back and forth between multiple languages,[139] similar to the children’s game telephone.[140]

See also

  • Apertium
  • Babel Fish (discontinued; redirects to the main Yahoo! site)
  • Comparison of machine translation applications
  • DeepL Translator
  • Google Dictionary
  • Google Translator Toolkit
  • Jollo (discontinued)
  • List of Google products
  • Microsoft Translator
  • Reverso
  • Smartcat
  • Speech Services
  • SYSTRAN
  • Word Lens (discontinued; merged into Google Translate app)
  • Yandex Translate

References

  1. ^ a b c Och, Franz Josef (April 28, 2006). «Statistical machine translation live». Google AI Blog. Google Inc. Retrieved February 15, 2011.
  2. ^ a b c d e f g Turovsky, Barak (November 15, 2016). «Found in translation: More accurate, fluent sentences in Google Translate». The Keyword Google Blog. Google Inc. Retrieved December 1, 2016.
  3. ^ «Translations Made Simple: The Usefulness of Translation Apps». Ulatus. April 8, 2020. Retrieved April 29, 2020.
  4. ^ a b «See which features work with each language». Google Translate. Google Inc. Retrieved July 13, 2015.
  5. ^ Turovsky, Barak (April 28, 2016). «Ten years of Google Translate». Google Translate Blog. Google Inc. Retrieved December 24, 2019.
  6. ^ Shankland, Stephen (May 18, 2013). «Google Translate now serves 200 million people daily». CNET. Red Ventures; CBS Interactive (at the time of publication). Retrieved October 17, 2014.
  7. ^ a b Benjamin, Martin (April 1, 2019). «How GT Pivots through English». Teach You Backwards. Retrieved December 24, 2019.
  8. ^ Benjamin, Martin (April 1, 2019). «Catalan to Spanish Translations». Teach You Backwards. Retrieved December 24, 2019.
  9. ^ Hofstadter, Douglas (January 30, 2018). «The Shallowness of Google Translate». The Atlantic. Emerson Collective. Retrieved March 24, 2020.
  10. ^ a b c d Benjamin, Martin (March 30, 2019). «Source data for Teach You Backwards: An In-Depth Study of Google Translate for 108 Languages». Teach You Backwards. Retrieved December 24, 2019.
  11. ^ a b c d e f Sommerlad, Joe (June 19, 2018). «Google Translate: How does the search giant’s multilingual interpreter actually work?». The Independent. Archived from the original on November 2, 2020. Retrieved November 28, 2018.
  12. ^ a b c Petrovan, Bogdan (January 14, 2015). «Google Translate just got smarter: Word Lens and instant voice translations in the latest update». Android Authority. Retrieved May 28, 2017.
  13. ^ a b c d e f McGuire, Nick; Argondizzo, Peter (July 26, 2018). «How accurate is Google Translate in 2018?». ARGO Translation. Archived from the original on January 25, 2021. Retrieved November 29, 2018.
  14. ^ a b Wu, Yonghui; Schuster, Mike; Chen, Zhifeng; Le, Quoc V.; Norouzi, Mohammad; Macherey, Wolfgang; Krikun, Maxim; Cao, Yuan; Gao, Qin; Macherey, Klaus; Klingner, Jeff; Shah, Apurva; Johnson, Melvin; Liu, Xiaobing; Kaiser, Łukasz; Gouws, Stephan; Kato, Yoshikiyo; Kudo, Taku; Kazawa, Hideto; Stevens, Keith; Kurian, George; Patil, Nishant; Wang, Wei; Young, Cliff; Smith, Jason; Riesa, Jason; Rudnick, Alex; Vinyals, Oriol; Corrado, Greg; Hughes, Macduff; Dean, Jeff (October 8, 2016). «Google’s Neural Machine Translation System: Bridging the Gap between Human and Machine Translation». arXiv:1609.08144 [cs.CL]. Retrieved May 14, 2017
  15. ^ Corcoran, Kieran (August 11, 2017). «A British court was forced to rely on Google Translate because it had no interpreter». Business Insider. Axel Springer SE. Retrieved August 11, 2017.
  16. ^ Wiggers, Kyle (September 30, 2022). «Google appears to have disabled Google Translate in parts of China». TechCrunch. AOL. Retrieved October 1, 2022.
  17. ^ Strumpf, Dan (October 3, 2022). «Google Pulls Translation App From China». The Wall Street Journal. Dow Jones & Company. Retrieved October 3, 2022.
  18. ^ a b c «Google Translate — A Personal Interpreter on Your Phone or Computer». Google Translate. Google Inc. Retrieved May 28, 2013.
  19. ^ a b c «Google Translate Help». Google Inc. Retrieved June 4, 2014.
  20. ^ a b c d «Translate written words». Google Translate Help. Google Inc. Retrieved December 1, 2016.
  21. ^ a b c «Translate documents & webpages». Google Translate Help. Google Inc. Retrieved December 1, 2016.
  22. ^ a b «Translate by speech». Google Translate Help. Google Inc. Retrieved December 1, 2016.
  23. ^ «Translate text in other apps». Google Translate Help. Google Inc. Retrieved February 4, 2022.
  24. ^ «Translate images». Google Translate Help. Google Inc. Retrieved November 20, 2018.
  25. ^ a b «Translate with handwriting or virtual keyboard». Google Translate Help. Google Inc. Retrieved December 1, 2016.
  26. ^ «Translate a bilingual conversation». Google Translate Help. Google Inc. Retrieved February 4, 2022.
  27. ^ «Transcribe in Google Translate». Google Translate Help. Google Inc. Retrieved February 4, 2022.
  28. ^ Benjamin, Martin (March 30, 2019). «Dictionary — When & How to Use Google Translate». Teach You Backwards. Retrieved December 25, 2019.
  29. ^ a b Benjamin, Martin (April 1, 2019). «Ooga Booga: Better than a Dictionary — Qualitative Analysis of Google Translate across 108 Languages». Teach You Backwards. Retrieved December 25, 2019.
  30. ^ «Save translations in a phrasebook». Google Translate Help. Google Inc. Retrieved May 28, 2017.
  31. ^ AK, Sony (December 5, 2019) [December 3, 2019]. «Practical Puppeteer: Playing with Google Translate to translate a text». DEV.to. Retrieved January 25, 2022.
  32. ^ «Search results for «Google Translate»«. Add-ons for Firefox. Mozilla Foundation. Retrieved August 7, 2009.
  33. ^ «Google Translate». Chrome Web Store. Google Inc. Retrieved July 23, 2010.
  34. ^ Baldwin, Roberto (October 16, 2014). «Google introduces Google Translate Chrome Extension for inline translations of text». TNW. Financial Times. Retrieved May 28, 2017.
  35. ^ Brinkmann, Martin (July 19, 2016) [February 7, 2010]. «Google Translate Integrated In Google Chrome 5». Ghacks Technology News. Ghacks. Retrieved July 23, 2010.
  36. ^ «Google Chrome 5 features an integrated Google Translate service». TechWhack. February 15, 2010. Archived from the original on July 26, 2010. Retrieved July 23, 2010.
  37. ^ Wauters, Robin (February 14, 2010). «Rant: Google Translate Toolbar In Chrome 5 Needs An ‘Off’ Button». TechCrunch. AOL. Archived from the original on July 28, 2017. Retrieved May 28, 2017.
  38. ^ «Google Translate APKs». APKMirror.
  39. ^ «Google Translate». App Store.
  40. ^ a b Turovsky, Barak (July 29, 2015). «See the world in your language with Google Translate». The Keyword Google Blog. Google Inc. Retrieved July 30, 2015.
  41. ^ a b Setalvad, Ariha (July 29, 2015). «Google Translate adds 20 new languages to video text translation». The Verge. Vox Media. Retrieved July 30, 2015.
  42. ^ Zhu, Wenzhang (February 8, 2011). «Introducing the Google Translate app for iPhone». Google Mobile Blog. Google Inc. Retrieved February 15, 2011.
  43. ^ Hutchison, Allen (August 7, 2008). «Google Translate now for iPhone». Google Mobile Blog. Google Inc. Retrieved March 23, 2017.
  44. ^ «Google Translate on the App Store». Google. Retrieved July 29, 2015.
  45. ^ Hachman, Mark (January 12, 2011). «Google Translate’s New ‘Conversation Mode’: Hands On». PCMag. Ziff Davis. Archived from the original on July 4, 2018. Retrieved May 28, 2017.
  46. ^ Kim, Ryan (October 13, 2011). «Google Translate conversation mode expands to 14 languages». Gigaom. Retrieved November 16, 2011.
  47. ^ Velazco, Chris (October 13, 2011). «Google Translate For Android Gets Upgraded «Conversation Mode»«. TechCrunch. AOL. Retrieved May 28, 2017.
  48. ^ Turovsky, Barak (January 14, 2015). «Hallo, hola, olá to the new, more powerful Google Translate app». The Keyword Google Blog. Google Inc. Retrieved January 14, 2015.
  49. ^ Russell, Jon (January 14, 2015). «Google Translate Now Does Real-Time Voice And Sign Translations On Mobile». TechCrunch. AOL. Retrieved May 28, 2017.
  50. ^ Good, Otávio (July 29, 2015). «How Google Translate squeezes deep learning onto a phone». Google AI Blog. Google Inc. Retrieved July 30, 2015.
  51. ^ Gush, Andrew (July 29, 2015). «Google Translate adds video translation support for 25 more languages». Android Authority. Retrieved May 28, 2017.
  52. ^ Olanoff, Drew (July 29, 2015). «Google Translate’s App Now Instantly Translates Printed Text In 27 Languages». TechCrunch. AOL. Retrieved May 28, 2017.
  53. ^ Benjamin, Martin (March 30, 2019). «Instant Camera Translation — Introduction: Into the Black Box of Google Translate». Teach You Backwards. Retrieved December 25, 2019.
  54. ^ Kastrenakes, Jacob (May 11, 2016). «Google Translate now works inside any app on Android». The Verge. Vox Media. Retrieved May 13, 2016.
  55. ^ a b Feldman, Adam (June 3, 2011) [May 26, 2011]. Knaster, Scott (ed.). «Spring cleaning for some of our APIs (Google Code Blog)». Official Google Code Blog. Google Inc. Archived from the original on May 28, 2011. Retrieved May 28, 2011.
  56. ^ a b Feldman, Adam (June 3, 2011). Knaster, Scott (ed.). «Spring cleaning for some of our APIs (Google Developers Blog)». Google Developers Blog. Google Inc. Retrieved February 4, 2022.
  57. ^ Grunwald, Dave (May 27, 2011). «BREAKING NEWS! Google to shut down Translate API». GTS Blog. Archived from the original on May 31, 2011. Retrieved May 6, 2016.
  58. ^ «Google Translate API (deprecated)». Google Code. Google Inc. Archived from the original on August 22, 2011. Retrieved May 28, 2011.
  59. ^ Grunwald, Dave (June 4, 2011). «Google cancels plan to shutdown Translate API. To start charging for translations». GTS Blog. Archived from the original on June 30, 2011. Retrieved June 4, 2011.
  60. ^ Wong, George (May 27, 2011). «Google gets rid of APIs for Translate and other services». Ubergizmo. Retrieved May 28, 2011.
  61. ^ Burnette, Ed (May 27, 2011). «Google pulls the rug out from under web service API developers, nixes Google Translate and 17 others». ZDNet. Retrieved May 28, 2011.
  62. ^ Henderson, Fergus (May 11, 2010). «Giving a voice to more languages on Google Translate». Google Translate Blog. Google Inc. Retrieved May 12, 2010.
  63. ^ Venugopal, Ashish (May 13, 2010). «Five more languages on translate.google.com». Google Translate Blog. Google Inc. Retrieved May 14, 2010.
  64. ^ Uszkoreit, Jakob (September 30, 2010). «Veni, Vidi, Verba Verti (Official Google Blog)» [I came, I saw, I turned the words]. Official Google Blog (in Latin). Google Inc. Retrieved September 30, 2010.
  65. ^ Uszkoreit, Jakob; Bayer, Ben (October 1, 2010). «Veni, Vidi, Verba Verti (Google Translate Blog)» [I came, I saw, I turned the words]. Google Translate Blog (in English and Latin). Google Inc. Retrieved December 11, 2021.
  66. ^ «Google picks SVOX for Translate and Dictionary services». Zürich, Switzerland: SVOX. December 17, 2010. Archived from the original on December 26, 2010. Retrieved January 20, 2011.
  67. ^ Venugopal, Ashish (June 21, 2011). «Google Translate welcomes you to the Indic web». Google Translate Blog. Google Inc. Retrieved June 21, 2011.
  68. ^ Brants, Thorsten (February 22, 2012). «Tutmonda helplingvo por ĉiuj homoj» [A global auxiliary language for all people]. Google Translate Blog. Google Inc. Retrieved September 24, 2015.
  69. ^ Brants, Thorsten (September 13, 2012). «Translating Lao». Google Translate Blog. Google Inc. Retrieved September 19, 2012.
  70. ^ Crum, Chris (September 13, 2012). «Google Adds Its 65th Language To Google Translate With Lao». WebProNews. Retrieved September 19, 2012.
  71. ^ Ong, Josh (April 19, 2013). «Google Translate Now Supports 66 Languages After Adding Khmer». TNW News. Financial Times. Retrieved December 25, 2021.
  72. ^ Noda, Tam (May 10, 2013). «Google Translate goes Cebuano». The Philippine Star. Retrieved December 25, 2021.
  73. ^ Liyanage, Vimukthi (December 12, 2014). «Google සිංහල පරිවර්ථන සේවය අද සිට ක්‍රියාත්මකයි !» Google siṁhala parivarthana sēvaya ada siṭa kriyātmakayi ! [Google Sinhala translation service is active from today !]. TechGuru.lk (in Sinhala). Retrieved August 1, 2021.
  74. ^ «Google can now translate text into Sindhi, Pashto and vice versa». Dawn. Dawn Media Group. February 19, 2016. Retrieved March 2, 2016.
  75. ^ «Google adds Sindhi to its translate language options». DNA India. Essel Group. February 18, 2016. Retrieved March 2, 2016.
  76. ^ «Google adds Sindhi to its translate language options». Yahoo! News. Yahoo!. Asian News International. February 18, 2016. Archived from the original on April 13, 2021. Retrieved March 2, 2016.
  77. ^ Ahmed, Ali (February 18, 2016). «Google Translate now includes Sindhi and Pashto». Business Recorder. Archived from the original on April 26, 2016. Retrieved March 2, 2016.
  78. ^ Shu, Catherine (February 17, 2016). «Google Translate Now Has More Than 100 Languages And Covers 99 Percent Of The Online Population». TechCrunch. AOL. Retrieved December 25, 2021.
  79. ^ Sandilo, Tariq (February 21, 2016). «گوگل تي سنڌي ٻولي» [Sindhi language on Google]. Sarwan.pk (in Sindhi). Retrieved March 2, 2016.
  80. ^ Humphries, Matthew (February 27, 2020). «Google Translate Adds 5 New Languages». PCMag. Ziff Davis. Retrieved December 25, 2021.
  81. ^ Wilde, Damien (May 11, 2022). «Google Translate adds support for 24 new languages, now supports over 130». 9to5Google. Retrieved May 11, 2022.
  82. ^ «Google Translate — Contribute». Google Translate. Google Inc. Retrieved December 14, 2014.
  83. ^ Chidley-Hill, John (February 21, 2021). «Online petition asks for Cree language to be added to Google Translate». CTV News, Bell Media (owner). The Canadian Press. Retrieved February 26, 2021.
  84. ^ Beattie, Samantha (February 23, 2021). «Google Translate’s Exclusion Of Indigenous Languages A ‘Squandered’ Opportunity». HuffPost Canada. BuzzFeed. Retrieved February 26, 2021.
  85. ^ a b Och, Franz Josef (September 12, 2005). «Statistical Machine Translation: Foundations and Recent Advances» (PDF). mt-archive.com. Phuket, Thailand: Asia-Pacific Association for Machine Translation. Archived from the original (PDF) on February 25, 2021. Retrieved December 19, 2010.
  86. ^ MT Summit X: The Tenth Machine Translation Summit (proceedings). Phuket, Thailand: Asia-Pacific Association for Machine Translation. September 12–16, 2005. ISBN 9789747431261. Retrieved February 4, 2022.
  87. ^ «Franz Och, Ph.D., Expert in Machine Learning and Machine Translation, Joins Human Longevity, Inc. as Chief Data Scientist» (Press release). La Jolla, CA: Human Longevity, Inc. July 29, 2014. Archived from the original on August 7, 2020. Retrieved January 15, 2015.
  88. ^ French to Russian translation translates the untranslated non-French word «obvious» from pivot (intermediate) English to Russian le mot ‘obvious’ n’est pas français → «очевидными» слово не французское
  89. ^ We pretend that this English article is German when asking Google to translate it to French. Google, because it does not find the English words in the German dictionary, leaves those words unchanged as one can show it with this spelllling misssstake. But it translates them to French nonetheless. That’s because Google translates German → English → French and that the unchanged English words undergo the second translation. The word «außergewöhnlich» however will be translated twice.
  90. ^ a b Boitet, Christian; Blanchon, Hervé; Seligman, Mark; Bellynck, Valérie (January 31, 2011). «MT on and for the Web» (PDF). clips-imag.fr. Archived from the original (PDF) on March 29, 2017. Retrieved October 23, 2011.
  91. ^ a b P.Y. (October 25, 2010). «Wrong translation to Ukrainian language». Google Inc. Archived from the original on July 10, 2012. Retrieved October 23, 2011.
  92. ^ Google Translation mixes up «tu» and plural or polite «vous» Je vous aime. Tu es ici. You are here. → Я люблю тебя. Вы здесь. Вы здесь.
  93. ^ Adams, Tim (December 19, 2010). «Can Google break the computer language barrier?». The Guardian. Retrieved May 28, 2017.
  94. ^ Tanner, Adam (March 28, 2007). «Google seeks world of instant translations». Reuters. Thomson Reuters. Retrieved December 17, 2008.
  95. ^ Google was an official sponsor of the annual Computational Linguistics in Japan Conference («Gengoshorigakkai») in 2007. Google also sent a delegate from its headquarters to the meeting of the members of the Computational Linguistic Society of Japan in March 2005, promising funding to researchers who would be willing to share text data.
  96. ^ «Inside Google Translate (old)». Google Translate. Google Inc. Archived from the original on August 22, 2010. Retrieved May 28, 2013.
  97. ^ Chitu, Alex (October 22, 2007). «Google Switches to Its Own Translation System». Unofficial Google Blog. Google Inc. Retrieved February 15, 2011.
  98. ^ Schwartz, Barry (October 23, 2007). «Google Translate Drops Systran For Home Brewed Translation». Search Engine Land. Retrieved July 23, 2010.
  99. ^ Southern, Matt (July 28, 2014). «Google Seeks Community Help To Improve Google Translate». SEJ. Retrieved May 26, 2017.
  100. ^ Kelman, Sveta (July 25, 2014). «Translate Community: Help us improve Google Translate!». Google Translate Blog. Google Inc. Retrieved May 26, 2017.
  101. ^ a b c «Help Us Improve the Google Translate Tool». Google Translate. Google Inc. Retrieved November 20, 2018.
  102. ^ Lardinois, Frederic (July 25, 2014). «Google Wants To Improve Its Translations Through Crowdsourcing». TechCrunch. AOL. Retrieved July 13, 2017.
  103. ^ Summers, Nick (July 25, 2014). «Google sets up a community site to help improve Google Translate». TNW. Financial Times. Retrieved July 13, 2017.
  104. ^ Whitwam, Ryan (August 29, 2016). «New Google Crowdsource app asks you to help with translation and text transcription a few seconds at a time». Android Police. Retrieved October 11, 2016.
  105. ^ Shankland, Stephen (August 29, 2016). «New Crowdsource app lets you work for Google for free». CNET. Red Ventures; CBS Interactive (at the time of publication). Retrieved July 13, 2017.
  106. ^ Benjamin, Martin (April 1, 2019). «Myth 5: Google Translate learns from its users — Qualitative Analysis of Google Translate across 108 Languages». Teach You Backwards. Retrieved December 25, 2019.
  107. ^ Lange, William (February 7, 2017). «Statistical Vs Neural Machine Translation». United Language Group. Archived from the original on November 15, 2018. Retrieved November 27, 2018.
  108. ^ «Statistical Vs. Neural Machine Translation». United Language Group. Archived from the original on March 28, 2019. Retrieved February 4, 2022.
  109. ^ a b Le, Quoc V.; Schuster, Mike (September 27, 2016). «A Neural Network for Machine Translation, at Production Scale». Google AI Blog. Google Inc. Retrieved October 11, 2016.
  110. ^ a b c d Schuster, Mike; Johnson, Melvin; Thorat, Nikhil (November 22, 2016). «Zero-Shot Translation with Google’s Multilingual Neural Machine Translation System». Google AI Blog. Google Inc. Retrieved January 11, 2017.
  111. ^ Fewster, Gil (January 5, 2017). «The mind-blowing AI announcement from Google that you probably missed». freeCodeCamp. Retrieved January 11, 2017.
  112. ^ Hochreiter, Sepp; Schmidhuber, Jürgen (November 15, 1997). «Long short-term memory». Neural Computation. 9 (8): 1735–1780. doi:10.1162/neco.1997.9.8.1735. PMID 9377276. S2CID 1915014. Retrieved May 14, 2017.
  113. ^
  114. ^ Cade, Metz (September 27, 2016). «An Infusion of AI Makes Google Translate More Powerful Than Ever». Wired. Retrieved May 14, 2017.
  115. ^ McDonald, Chris (January 7, 2017). «Ok slow down». Medium. Retrieved January 11, 2017.
  116. ^ Davenport, Corbin (March 6, 2017). «Google Translate now uses neural machine translation for some languages». Android Police. Retrieved April 26, 2017.
  117. ^ Hager, Ryne (April 25, 2017). «Google adds Indonesian and eight new Indian languages to its neural machine translation». Android Police. Retrieved April 26, 2017.
  118. ^ Benjamin, Martin (March 30, 2019). «The 5 conditions for satisfactory approximations with Google Translate — Conclusions: Real Data, Fake Data & Google Translate». Teach You Backwards. Retrieved December 26, 2019.
  119. ^ Benjamin, Martin (March 30, 2019). «Empirical Evaluation of Google Translate across 107 Languages». Teach You Backwards. Retrieved December 26, 2019.
  120. ^ Benjamin, Martin (March 30, 2019). «Non-English Pairs — Empirical Evaluation of Google Translate across 107 Languages». Teach You Backwards. Retrieved December 26, 2019.
  121. ^ Aiken, Milam; Balan, Shilpa (April 2011). «An Analysis of Google Translate Accuracy». Translation Journal. 16 (2). Retrieved November 29, 2018.
  122. ^ a b Li, Haiying; Graesser, Arthur; Cai, Zhiqiang (May 3, 2014). «Comparison of Google Translation with Human Translation» (PDF). Proceedings of the Twenty-Seventh International Florida Artificial Intelligence Research Society Conference. FLAIRS Conference. S2CID 14905135. Archived from the original (PDF) on December 5, 2018. Retrieved November 29, 2018.
  123. ^ Benjamin, Martin (April 1, 2019). «Polysemy in top 100 Oxford English Corpus words within Wiktionary». Teach You Backwards. Retrieved December 26, 2019.
  124. ^ Subjunctive Mood (@IfIwerejudgingU) (May 15, 2013). «Subjunctive Mood». Twitter. Retrieved March 21, 2015.
  125. ^ «Google Translate doesn’t really understand ‘tu’ and ‘vous’. Particularly «tu»«. Reddit. December 2, 2013. Retrieved March 21, 2015.
  126. ^ Freitas, Connor; Liu, Yudong (December 15, 2017). «Exploring the Differences between Human and Machine Translation». Western Washington University: 5. Retrieved December 5, 2018.
  127. ^ a b Shen, Ethan (June 2010). «Comparison of online machine translation tools». TCWorld. Archived from the original on February 10, 2011. Retrieved July 23, 2010.
  128. ^ Pecoraro, Christopher (August 17, 2011). «Microsoft Bing Translator and Google Translate Compared». chrispecoraro.com. Retrieved April 8, 2012.
  129. ^ Pecoraro, Christopher (January 30, 2012). «Microsoft Bing Translator and Google Translate compared (update)». chrispecoraro.com. Retrieved April 8, 2012.
  130. ^ Benjamin, Martin (April 1, 2019). «Polysemy – words with multiple meanings — The Astounding Mathematics of Machine Translation». Teach You Backwards. Retrieved December 26, 2019.
  131. ^ Benjamin, Martin (April 1, 2019). «Party terms (or multiword expressions) – words that play together — The Astounding Mathematics of Machine Translation». Teach You Backwards. Retrieved December 26, 2019.
  132. ^ Rahmannia, Mia; Triyono, Sulis (May 31, 2019). «A Study of Google Translate Translations: An Error Analysis of Indonesian-to-English Texts». SSRN 3456744. International Journal of Linguistics, Literature and Translation (IJLLT) 2(3):196-200, 2019. Retrieved August 26, 2020
  133. ^ «Open source components and licenses». Google Translate. Google Inc. Retrieved February 4, 2022.
  134. ^ Nielsen, Michael A. (October 3, 2011). Reinventing discovery: the new era of networked science. Princeton, NJ: Princeton University Press. p. 125. ISBN 978-0-691-14890-8. Retrieved February 24, 2012.
  135. ^ Gomes, Lee (July 22, 2010). «Google Translate Tangles With Computer Learning». Forbes. Retrieved July 22, 2010.
  136. ^ Weinberg, Nathan (September 10, 2007). «Google Translates Ivan the Terrible as «Abraham Lincoln»«. Blog News Channel. Archived from the original on September 12, 2007. Retrieved July 22, 2010.
  137. ^ Twisted Translations (February 10, 2015). «Google Translate Sings: «Bohemian Rhapsody» by Queen». YouTube. Google Inc. Retrieved April 26, 2016.
  138. ^ Topolyanskaya, Alyona (January 28, 2010). «Google Lost in Translation». The Moscow News. Archived from the original on August 13, 2010. Retrieved July 22, 2010.
  139. ^ Kincaid, Jason (August 7, 2009). «Translation Party: Tapping Into Google Translate’s Untold Creative Genius». TechCrunch. AOL. Retrieved March 17, 2017.

External links

  • Official website
  • Contribute
Источник

Для мультиязычности сайтов на CMS WordPress я рекомендую использовать плагин Polylang – наиболее удобный, гибкий и простой плагин для создания различных языков на вашем сайте.Единственный его минус – что нужно переводить все тексты самостоятельно и для каждого текста, для каждой страницы, записи или категории необходимо создавать аналогичные страницы для каждого языка.

Что же делать Если у вас нет талантливого и грамотного переводчика, нет времени переводить свой сайт самостоятельно, или на вашем сайте несколько тысяч страниц? Вот для такого случая – быстро и просто перевести сайт на несколько десятков языков – отлично подойдет плагин Google Language Translator.

Плюсы плагина Google Language Translator:

  • Простая установка и настройка.
  • Вам не нужно ничего переводить, плагин все переводит за вас через Google Translate.
  • Не нужно создавать десятки-сотни-тысячи страниц для других языков.
  • После удаления плагина в базе данных не останется никакого мусора как например от плагина qTranslate.
  • Скорость работы плагина вполне приемлемая.
  • Десятки доступных языков для перевода вашего сайта.
  • Даже шаблон может не быть подготовлен к переводу.
  • Простота использования для пользователя сайта.
  • И еще раз – Моментальный перевод всего вашего сайта на десятки языков!!!

Минусы плагина Google Language Translator:

  • Качество перевода такое же как в Google Translate, то есть, для сайта МИД или Президента такой плагин наверное использовать не солидно, но для простого контентного сайта вполне годный вариант.
  • Небольшие задержки на мобильных устройствах.
  • Пока не разобрался, как получить прямую ссылку на статья в нужном языке.

Простой пример настройки плагина Google Language Translator:

Устанавливаем плагин из официальной директории Google Language Translator.

Активируем и идем в настройки

Main Settings

Активация плагина

  • Отмечаем чекбокс для активации плагина.
  • Выбираем язык по умолчанию – это должен быть обязательно тот язык, на котором написан контент вашего сайта. Например, если вы выберете английский язык, а контент сайта на самом деле написан на русском, тогда плагин не сработает, так как будет пытаться выполнить перевод с англ. языка на любой другой язык.

Layout Settings

У меня такие настройки:

Тут надо немного объяснить и попробовать самостоятельно все настройки.

  • Если выбрать All Languages, то в выпадающем списке языков у вас будут отображаться все языки
  • Если выбрать Specific Languages, то в выпадающем списке языков будут только выбранные Вами языки.
  • Только при выбранном All Languages, доступно поле Show flag images.
  • При выборе Yes, show flag images, у вас появляется возможность выбрать, какие языки вы хотите вывести отдельно флагами. Соответственно при выборе No, hide flag images такая возможность пропадает.
  • Show or hide the langauge switcher – Hide language switcher сработает только если выбрано All Languages и Yes, show flag images, тогда пропадет выпадающий список всех языков, и выбор языков будет доступен только выбранными флагами, а иначе и переключатель языков пропадет и флагов не будет.
  • Show Google Toolbar при включении будет выводить в самом верху страницы Google Toolbar для управления переводами.
  • Show Google Branding будет отображать ссылку на https://translate.google.com/ справа от переключателя.

Floating Widget Settings

С этим блоком я не разобрался

При любых настройках этого блока ничего не меняется, а виджет в Виджетах все равно отображается.

Behavior Settings

Поведенческие настройки

  • Turn on multilanguage mode – по идее, позволяет переводить страницу сайта, даже если на ней используется несколько языков.
  • Activate Google Analytics tracking – подключает код аналитики.

Usage

Как добавить переключатель языков на сайт.

  • Можно вывести с помощью шорткода [google-translator] на странице или виджете.
  • Можно вывести в коде шаблона в любом месте<?php echo do_shortcode('[google-translator]'); ?>
  • Можно вывести шорткодом один определенный язык [glt language="Spanish" label="Español" image="yes" text="yes" image_size="24"]
  • Можно вывести переключатель языков виджетом:

Preview

Визуальное отображение настроек, то есть вы сразу увидите, как переключатель языков будет отображаться на вашем сайте без необходимости выходить из админской части. Но для отображения результатов нужно Сохранить Изменения.

Advanced Settings

Расширенные настройки.

Можно выбрать размер флага (ширину), а так же выбрать флаги определенной страны для некоторых языков.

Кстати, я задал ширину флага – 24px, мне так больше понравилось.

Add CSS Styles

Добавление кастомных стилей.

По умолчанию у блока #flags задана ширина 165px, меня это не устроило, и чтобы не лезть в шаблон я сразу задал ширину 100%, очень удобно, но сюда лучше писать только те стили, которые относятся только к этому плагину.

Видео по настройке плагина

А вот еще полезное видео Translate your Website with Javascript & Google Translate

У меня плагин на момент написания статьи установлен и переключатель языков выведен в сайдбар под меню.
Протестировать его работу можно на моем сайте.

Источник

Понравилась статья? Поделить с друзьями:
  • Google forms and excel
  • Google finance for excel
  • Google finance api to excel
  • Google excel что это такое
  • Google excel формула если