From: Glauber Alex Dias Prado <smade4@gmail.com>
To: Andrea Crotti <andrea.crotti.0@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Translate-mode
Date: Tue, 07 Sep 2010 12:17:15 -0300 [thread overview]
Message-ID: <87occ9y45g.fsf@gmail.com> (raw)
In-Reply-To: <m162yhhh5k.fsf@gmail.com> (Andrea Crotti's message of "Tue, 07 Sep 2010 14:28:23 +0200")
Andrea Crotti <andrea.crotti.0@gmail.com> writes:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>>
>> http://www.emacswiki.org/emacs/TextTranslator
>>
>> But I do not believe in doing the translation on each space char...
>
> I think is not exactly what I was looking for, what I would really love
> is as I said something auto-updating, not much for real translation of
> course but for experimentation.
>
> Even better would be to also have another buffer below which gives the
> dictionary definition of the word (even monolingual).
> For example I write in X my text in German, I see in y the translation
> and in z the definition of every word.
>
> Is something like that doable also?
> Any advice on what to use (a minor/major mode, how to map the keyboard etc...)?
>
> | x | y |
> |--------|
> | z |
I guess you want an asynchronous update of the translated buffer called
on post-command-hook and checking for a space getting the thing at point
every-time to translate, if you want to use google service this is a
nice lib:
http://www.emacswiki.org/emacs/TextTranslator
about minor/major mode i think you will need both but im not a
experienced elisp programmer, minor for the buffer to be translated and
major for the translated content buffer. If i was you i would
concentrate on translation first as the definitions are not that simple
in any language except english i think.
HTH,
glauber.
prev parent reply other threads:[~2010-09-07 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 18:41 Translate-mode Andrea Crotti
2010-09-06 18:46 ` Translate-mode Lennart Borgman
2010-09-07 12:28 ` Translate-mode Andrea Crotti
2010-09-07 15:17 ` Glauber Alex Dias Prado [this message]
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=87occ9y45g.fsf@gmail.com \
--to=smade4@gmail.com \
--cc=andrea.crotti.0@gmail.com \
--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).