Translate: enable against unknown languages with server side detection

chrome/browser/resources/translate.js

Index: chrome/browser/resources/translate.js
diff --git a/chrome/browser/resources/translate.js b/chrome/browser/resources/translate.js
index 07f7113c19098a9aa32ea8a556b26f867bc9702e..047ce7c326eedccda287c9486efd13dd864d5c3b 100644
--- a/chrome/browser/resources/translate.js
+++ b/chrome/browser/resources/translate.js
@@ -135,6 +135,8 @@ cr.googleTranslate = (function(key) {
     get sourceLang() {
       if (!libReady || !finished || error)
         return '';
+      if (!lib.getDetectedLanguage)
+        return 'und';

[Evan Stade, 2013/05/18 23:53:52]

why 'und' and not undefined or 'undefined' or whatever 'und' is supposed to
stand for?

[Takashi Toyoshima, 2013/05/20 06:56:08]

'und' is a magic word defined as chrome::kUnknownLanguageCode and widely used in
Chrome Translate.
I'll add comment here.

       return lib.getDetectedLanguage();

[Evan Stade, 2013/05/18 23:53:52]

you can write this as lib.getDetectedLanguage() || 'und';

[Takashi Toyoshima, 2013/05/20 06:56:08]

It doesn't work.
Undefined one is not returned value, but lib.getDetectedLanguage itself.
So, when call lib.getDetectedLanguage(), JavaScript stops running due to calling
undefined attribute.

[Evan Stade, 2013/05/23 00:53:28]

ah, I misread it

     },