unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dan Espen <despen@verizon.net>, help-gnu-emacs@gnu.org
Subject: RE: Changing the language of gnus menu entries
Date: Thu, 26 Sep 2013 11:31:18 -0700 (PDT)	[thread overview]
Message-ID: <e36f6c83-9f62-4cde-b779-4c8f1ad4732f@default> (raw)
In-Reply-To: <icd2nvo5uq.fsf@home.home>

> http://www.emacswiki.org/emacs/TextTranslator
> Which allows for an Emacs user to get pretty easy access to machine
> translation, (which might get better over time).  So, despite not being
> automatic, there is an existing interface to translation.

Great!  That does indeed provide on-the-fly Google (and other) translation
of text in Emacs.

I gave it a quick try.  Had to customize a few options for my context:
`text-translator-proxy-server' (company firewall),
`text-translator-default-engine' (test Japanese-to-English, instead of
the default, which is English-to-Japanese, so set to "google.com_jaen",
not "google.com_enja").

Works like a charm.  Just select some text in the Japanese Emacs tutorial
or some other buffer with Japanese text, and then hit `C-x M-t'.  You
get the output in buffer `*translated* [google.com_jaen]'.

One odd thing that would need to be massaged: The displayed output
from Google shows a few untranslated Japanese phrases followed by this:

 " onmouseover="this.style.backgroundColor='#ebeff9'
 " onmouseout="this.style.backgroundColor='#fff'">

Dunno whether that represents a Google translation web-site bug or is
an artifact of the text-translator.el code.  When you use the web site
interactively both the untranslated phrase and the Javascript are not
shown.  Perhaps the text-translator.el code just needs to strip this
stuff out.



  reply	other threads:[~2013-09-26 18:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  7:29 Changing the language of gnus menu entries Uwe Scholz
2013-09-24 14:16 ` Peter Dyballa
2013-09-24 15:14 ` Joost Kremers
2013-09-24 16:41   ` Uwe Scholz
2013-09-24 19:48     ` Stefan Monnier
2013-09-24 20:07       ` Eli Zaretskii
     [not found]       ` <mailman.2807.1380053246.10748.help-gnu-emacs@gnu.org>
2013-09-24 21:48         ` Stefan Monnier
2013-09-25 13:30           ` Michael Heerdegen
2013-09-25 15:51             ` Eli Zaretskii
2013-09-25 18:29               ` Michael Heerdegen
2013-09-25 19:14                 ` Eli Zaretskii
2013-09-25 20:45                   ` Michael Heerdegen
     [not found]                   ` <mailman.2878.1380138900.10748.help-gnu-emacs@gnu.org>
2013-09-25 21:15                     ` Joost Kremers
2013-09-26  8:56                   ` Óscar Fuentes
2013-09-26  9:32                     ` Eli Zaretskii
     [not found]                 ` <<8338oshfy5.fsf@gnu.org>
2013-09-25 19:54                   ` Drew Adams
2013-09-25 20:08                     ` Drew Adams
2013-09-25 20:24                     ` Peter Dyballa
2013-09-25 23:09                       ` Drew Adams
     [not found]                       ` <mailman.2886.1380150595.10748.help-gnu-emacs@gnu.org>
2013-09-26  4:05                         ` Joost Kremers
2013-09-26 17:02                           ` Drew Adams
2013-09-26 17:09                           ` Peter Dyballa
2013-09-26 19:15                           ` Dale Snell
     [not found]                           ` <mailman.2935.1380214979.10748.help-gnu-emacs@gnu.org>
2013-09-26 17:22                             ` Dan Espen
2013-09-26 18:31                               ` Drew Adams [this message]
2013-09-26 20:37                             ` Joost Kremers
     [not found]                               ` <mailman.2964.1380232675.10748.help-gnu-emacs@gnu.org>
2013-09-26 22:21                                 ` Joost Kremers
     [not found]                             ` <<slrnl496os.2vt.joostkremers@j.kremers4.news.arnhem.chello.nl>
2013-09-26 21:57                               ` Drew Adams
     [not found]                           ` <mailman.2936.1380215384.10748.help-gnu-emacs@gnu.org>
2013-09-26 20:44                             ` Joost Kremers
     [not found]                           ` <mailman.2954.1380222979.10748.help-gnu-emacs@gnu.org>
2013-09-26 20:46                             ` Joost Kremers
2013-09-25 20:50                     ` Michael Heerdegen
     [not found]                 ` <mailman.2876.1380136471.10748.help-gnu-emacs@gnu.org>
2013-09-27  6:26                   ` Jason Rumney
2013-09-27  9:00                     ` Eli Zaretskii
2013-09-25 19:00             ` Stefan Monnier
2013-09-26  0:37               ` Stefan Monnier
     [not found]             ` <mailman.2861.1380124268.10748.help-gnu-emacs@gnu.org>
2013-09-25 19:13               ` Uwe Scholz
2013-09-24 20:08   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e36f6c83-9f62-4cde-b779-4c8f1ad4732f@default \
    --to=drew.adams@oracle.com \
    --cc=despen@verizon.net \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).