Talk:Google Translator Toolkit

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search


Untitled[edit]

Bloated sentence In the part describing which languages that are supported, it is stated that 345 languages and more than 100000 language pairs are supported. Then, there comes a huuuge list of languages. Any sentence exceeding 100 words is badly written, IMNSHO. This should be broken down into some more digestible format, such as "all languages with at least 10 million speakers, and all indoeuropean languages with at least 1 million speakers" - or some such, depending on what actually is true. But - a huge sentence which essentially in nothing but a run-on list is not good. A better solution might be an autosortable list in which all supported languages are listed, together with their language family, # native speakers, inclusion date, etc. other interesting data.

Language list[edit]

@User:Glrx, so state your case. You say it shouldn't be like a user manual, so I adapted to comply with WP:NOTRECIPE. This is hardly an example of WP:PLOT's excessive listing (listing each unique set of languages might be, e.g. "languages available from xx/xx/201x until xx/xx/201x"). This content is specifically encouraged under WP:NOTRECIPE, which states that website articles should include "detail on a website's achievements, impact or historical significance." For translator software, the only thing more applicable than its languages is more detail, e.g. "GTT became the 2nd translator to support Makassarese on xx/xx/2009," but with the absence of publicly released data on the subject, trying to construct that would be WP:OR. Star Garnet (talk) 23:31, 26 March 2017 (UTC)

The list is too detailed. The achievement of interest is translating a few hundred languages. That statement does not need to be backed up with an actual list of the languages; a simple ref for the statement is all that is needed. Such a detailed list is also difficult to maintain. Each time a language is added, there's no guarantee it will be added to the list. Consequently, the list won't stay accurate. Such a list is boring; how many readers will go through the list? Compare that dull list with the interesting comment you made about Makassarese above (but I wonder how different it is from Buginese). WP:NOTCATALOG discourages "simple listings" but permits, "Information about relevant single entries with encyclopedic information should be added as sourced prose." (emphasis in original) The statement is also sourced to Google rather than a reliable secondary source. An RS might not make the 10,000 language pair statement: an MT may translate a "pair" by using common intermediates rather than a direct jump. Glrx (talk) 16:04, 27 March 2017 (UTC)

No longer supported[edit]

I think it is no longer supported. FRom their website [1]

The Google Translate API has been officially deprecated as of May 26, 2011. Due to the substantial economic burden caused by extensive abuse, the number of requests you may make per day will be limited and the API will be shut off completely on December 1, 2011. For website translations, we encourage you to use the Google Translate Element." <http://code.google.com/apis/language/translate/overview.html>

The widget still works and provides automatic translations of your website but you can't contribute your own custom translations.

Robert Walker (talk) 22:45, 19 February 2018 (UTC)