unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: google-translate
Date: Sat, 19 Sep 2015 17:25:39 +0200	[thread overview]
Message-ID: <87lhc2whvw.fsf@debian.uxu> (raw)
In-Reply-To: 20150919041751.GA25867@ahiker.mooo.com

Ian Zimmerman <itz@buug.org> writes:

>> (defun translate (src-lang dst-lang text)
>>   (interactive)
>>   (let ((killed kill-ring))
>>     (google-translate-translate src-lang dst-lang text 'kill-ring)
>>     (let ((translation (string-make-unibyte (current-kill 0))))
>                           ^^^^^^^^^^^^^^^^^^^
> Why do you do that? That may be your problem
> right there.

That was it! The reason I put it there was to get rid
of the properties. I replaced it with
`substring-no-properties' but it seems that isn't
needed either. The reason I thought it was needed is:
put the region around this word: spiderweb - and hit
M-w (`kill-ring-save'). Now evaluate:

    (message "%s" (current-kill 0))

this will show:

    #("spiderweb" 0 9 (fontified t))

now evaluate:

    (message "%s" (substring-no-properties (current-kill 0)))

and get the desired:

    "spiderweb"

however this:

    (progn
      (kill-new "spiderwebs")
      (message "%s" (current-kill 0)) )

also gives no properties! So perhaps it is an
interactive/noninteractive issue as in a string (as
*data*), regardless how it is showed, there aren't
 any properties.

Anyway, thank you. Here is the most recent edition:

    (defun translate (src-lang dst-lang text)
      (interactive)
      (let ((killed kill-ring))
        (google-translate-translate src-lang dst-lang text 'kill-ring)
        (let ((translation (current-kill 0)))
          (setq kill-ring-yank-pointer killed)
          (message "%s: %s" text translation) )))

-- 
underground experts united
http://user.it.uu.se/~embe8573




  parent reply	other threads:[~2015-09-19 15:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  8:29 Is it possible to transform text before feeding it to ispell? Marcin Borkowski
2015-09-08 10:19 ` Alexis
2015-09-08 11:45   ` Tassilo Horn
2015-09-08 22:40   ` google-translate (was: Re: Is it possible to transform text before feeding it to ispell?) Emanuel Berg
2015-09-09  7:18     ` Andrey Tykhonov
2015-09-10  0:51       ` Emanuel Berg
2015-09-16  3:01       ` google-translate Emanuel Berg
2015-09-16 12:22         ` google-translate Alex Kost
2015-09-16 23:29           ` google-translate Emanuel Berg
2015-09-17 22:32           ` google-translate Emanuel Berg
2015-09-19  0:09             ` google-translate Emanuel Berg
2015-09-19  4:17               ` google-translate Ian Zimmerman
2015-09-19 15:03                 ` google-translate Emanuel Berg
2015-09-19 15:25                 ` Emanuel Berg [this message]
2015-09-08 13:06 ` Is it possible to transform text before feeding it to ispell? Michael Heerdegen
2015-09-08 15:24   ` Marcin Borkowski
2015-09-08 17:39     ` Eli Zaretskii
2015-09-08 15:54 ` 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=87lhc2whvw.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).