From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode@gnu.org, Ulf Stegemann <ulf-news@zeitform.de>
Subject: Re: org-protocol and encoding
Date: Thu, 9 Apr 2009 15:29:52 +0200 [thread overview]
Message-ID: <CEA8BD82-D1C4-43CE-AFDB-51EDA9320B7B@gmail.com> (raw)
In-Reply-To: <87y6ue3sms.fsf@kassiopeya.MSHEIMNETZ>
On Apr 6, 2009, at 1:53 PM, Sebastian Rose wrote:
> Ulf Stegemann <ulf-news@zeitform.de> writes:
>> org-protocol is really a great extension for org-mode! However, I
>> experience an annoyance regarding non-ascii character encoding.
>>
>> When using org-protocol with remember and firefox, all non-ascii
>> characters get b0rked in the remember buffer (on linux, with emacs 23
>> and org-mode as of today and latest ff 3.0). It doesn't matter if the
>> source page uses html entities or literal non-ascii-characters. Does
>> anyone share this experience and has a suggestion on where to look
>> for
>> the cause?
>
>
> Yes. Same here.
>
> This seems to be a emacs/remember problem though.
>
>
> If I open a file `xy.txt' and select this text:
>
> lkäüüäüpüpjüpjsf
>
> and then 'C-x r' to remember it, I get this in my remember buffer:
>
> [[file:~/xy.txt::lk%20p%20pj%20pjsf][file:~/xy.txt::lk p pj pjsf]]
>
>
This problem might be partially resolved by pulling from git and then
seting
(setq org-url-encoding-use-url-hexify t)
This is for testing only right now.
- Carsten
prev parent reply other threads:[~2009-04-09 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 10:37 org-protocol and encoding Ulf Stegemann
2009-04-06 11:53 ` Sebastian Rose
2009-04-07 11:20 ` Sebastian Rose
2009-04-15 22:22 ` Sebastian Rose
2009-04-15 22:33 ` Sebastian Rose
2009-04-16 6:39 ` Carsten Dominik
2009-04-16 8:48 ` Ulf Stegemann
2009-04-09 13:29 ` Carsten Dominik [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CEA8BD82-D1C4-43CE-AFDB-51EDA9320B7B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
--cc=ulf-news@zeitform.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).