From: Kenichi Handa <handa@m17n.org>
To: Thomas Christensen <christensenthomas@gmail.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 21.1.50; [Gnus] Broken characters in iso-8859-15 formatted emails
Date: Mon, 10 Sep 2007 16:38:57 +0900 [thread overview]
Message-ID: <E1IUdrF-0002ht-0U@etlken.m17n.org> (raw)
In-Reply-To: <20070910072629.GA12677@foobar> (message from Thomas Christensen on Mon, 10 Sep 2007 09:26:29 +0200)
In article <20070910072629.GA12677@foobar>, Thomas Christensen <christensenthomas@gmail.com> writes:
> On Mon, Sep 10, 2007 at 11:41:06AM +0900, Kenichi Handa wrote:
> > In article <871wd9ebxv.fsf@foobar.localdomain>, Thomas Christensen <christensenthomas@gmail.com> writes:
> >
> > > I must apologize for the noise. It appears to be that Gentoo is
> > > hardcoded to only generate iso-8859-1 fonts in modular X.
> >
> > Does it mean that the problem was solved by installing
> > iso-8859-15 fonts?
> Yes, it solved the problem completely. I puzzles me a bit though,
> that Emacs is the only application that could not handle the
> iso-8859-15 without these fonts, and also how the others applications
> *did* handle this. But I know little of these matters.
Emacs still doesn't uses Unicode character codes internally,
thus iso-8859-1 characters and iso-8859-15 characters are
treated differently. In many cases, user don't notice this
difference because they are automatically converted from/to
each other. The emacs-unicode-2 branch of Emacs CVS
repository does uses Unicode internally and doesn't have
such a problem.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-09-10 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 14:20 21.1.50; [Gnus] Broken characters in iso-8859-15 formatted emails Thomas Christensen
2007-09-08 1:02 ` Thomas Christensen
2007-09-08 9:36 ` Thomas Christensen
2007-09-10 2:41 ` Kenichi Handa
2007-09-10 7:26 ` Thomas Christensen
2007-09-10 7:38 ` Kenichi Handa [this message]
2007-09-10 8:31 ` Thomas Christensen
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=E1IUdrF-0002ht-0U@etlken.m17n.org \
--to=handa@m17n.org \
--cc=christensenthomas@gmail.com \
--cc=emacs-pretest-bug@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.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).