Add ergonomics to the translator

    All translators (translate.ru, translate.google.com, lingvo.ru) are good in their own way: someone has the best parser, somewhere pictures on buttons delight fans of true painting, someone has the fastest translation result ( perhaps expensive and nimble servers are working), somewhere more is invested in the development of an accessible API.

    There will be no pivot tables, and even “This translator is the best!” Will not even be expressed. Let's leave it all to holivars.

    I use Google Translate .


    Often covering the page"Google Translator", I am faced with the problem of choosing the language of translation (Russian to English / English to Russian). To achieve the equivalent combination of the current language on the desktop and in the translator, you need to switch the layout on the keyboard, and then click on the “switch” link. In practice - 2 mandatory actions for one result, but you can reduce it to one.

    I solved this problem for myself: I wrote a little code in user defined javascript in Opera (I have version 10.10 Beta 1833):

    if (location.hostname == "translate.google.com") {

      var onready = function() {
        // textarea    
        document.getElementById("source").addEventListener(
          "keydown",
          function(event) {
            // SHIFT + ALT // SHIFT + CTRL
            if (event.shiftKey && event.altKey && event.keyCode == 16 || event.shiftKey && event.ctrlKey && event.keyCode == 17)
              // from google code
              ctr._swap();
          },
          false
        );
      };

      window.addEventListener("load", onready, false);
    }

    Designed for fans of ALT + SHIFT language switching combinations.

    It works as follows:
    1. Press ALT + SHIFT, the keyboard simultaneously switches on the desktop and in the translator to the opposite language to the current
    2. If different languages ​​are indicated on the desktop and in the translator at the same time, then press SHIFT + CTRL to synchronize the languages ​​in both programs

    And one more (last) requirement - all this will work when the text input field has cursor focus.

    Also popular now: