Folks: This may be the same issue as reported by others recently.
Suddenly, in the past few days, in Firefox 3.6.13 and Safari 5.0.3 on MacOS 10.6.5, translations appear for an instant and then disappear. I'm using Russian --> English, but I checked French --> English and a similar problem occurs, so this appears to be language-independent. Procedure: 1. go to URL translate.google.com 2. Set From: to "Russian" and To: to "English" 3. Paste some Russian text into the text box 4. Click on the Translate button. After a brief pause, the translation appears to the right of the text box under the heading "Russian to English translation". In the brief time it is visible, say, 0.5 second, the translation text appears to be reasonable, but of course it is difficult to tell. Then that page disappears and a new empty one appears. The new page is "clean", that is, contains no text, as if there was a simple re-direct to Google Translator. This issue appears to be sensitive to the length of text entered. It occurs less or not at all with "short" text to be translated, say, 3 short paragraphs of typical text. It occurs more often, possibly always, as the size of the original text is increases. No such problem observed in Chrome 8.0.552.231. Perhaps this is related: During my experiments, sometimes I noticed strangeness with respect to the URL: in seemingly random cases, abbreviations of the "from" and "to" languages (seemingly as usual) _and_ the original text to be translated are be visible at right in the URL. In these cases, entering new, different text to be translated and selecting new "from" and "to" languages has no effect. Here's the beginning of the URL now visible in Chrome for a French to English translation of text beginning "Dans ce musée, il y a deux parcours suivant votre but...": http://translate.google.com/#fr|en|Dans%20ce%20mus%C3%A9e%2C%20il%20y%20a%20deux%20parcours... >From this point, pasting new text to be translated --say, in Russian-- and changing the "From" language to Russian has no effect. That may be technically correct, as URL-encoded information take highest precedence, but when this occurs the translator is effectively broken. I don't know about URL length limits but there must be some, and it seems possible the length sensitivity I noted above might be due to exceeding some limit in cases in which the text to be translated is encoded in the URL. But since the text to be translated is not generally visible in the URL, something else is probably going on. Perhaps there's a usually hidden intermediate step being made visible? It would be great to have this fixed soon. I hope the information above helps. Thanks, hen3ry -- You received this message because you are subscribed to the Google Groups "General" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-translate-general?hl=en.
