From: "William Henney" <whenney@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug with Unicode text on properties
Date: Mon, 3 Sep 2007 11:08:01 -0500 [thread overview]
Message-ID: <41c818190709030908l69ea382fqc363df75d84b46ff@mail.gmail.com> (raw)
In-Reply-To: <906a3edbc4c30459580acf14825eaa5a@science.uva.nl>
On 9/3/07, Carsten Dominik <dominik@science.uva.nl> wrote:
> On Sep 2, 2007, at 23:42, William Henney wrote:
> > On 9/2/07, Carsten Dominik <dominik@science.uva.nl> wrote:
> >> I agree, but it is a fact that text you sent me did not look at all
> >> like spanish, but pretty much garbled.
> >
> > Daniel's file (bug-properties.org) looked fine to me (although it did
> > have strange German-style speech marks). My emacs (22.1.1)
> > automatically recognised it as utf8. Strange that yours didn't...
> >
>
> Yes, strange. 22.1 here as well, under Mac OSX.
>
To be more precise, I am using Aquamacs 1.1 on OS X 10.4.10 PPC G4.
However, I also tried it from the command line using the "-Q" option,
which supposedly turns off all the aquamacs-specific stuff, and it
still works (correctly identifies file as unicode).
Have you added an entry for org files to auto-coding-alist? Perhaps
"C-h C" (describe-coding-system") might help you debug it. Look at
"Priority order for recognizing coding systems when reading files".
Alternatively, maybe your mailer garbled the file when you saved it.
Cheers
Will
--
Dr William Henney, Centro de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
next prev parent reply other threads:[~2007-09-03 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 1:42 Bug with Unicode text on properties Daniel Clemente
2007-09-01 10:29 ` Carsten Dominik
2007-09-01 20:30 ` Daniel Clemente
2007-09-02 17:55 ` Carsten Dominik
2007-09-02 21:42 ` William Henney
2007-09-03 7:26 ` Carsten Dominik
2007-09-03 16:08 ` William Henney [this message]
2007-09-03 16:20 ` Daniel Clemente
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=41c818190709030908l69ea382fqc363df75d84b46ff@mail.gmail.com \
--to=whenney@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@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.
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).