unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Sébastien Kirche" <sebastien.kirche.no@spam.free.fr.invalid>
Subject: Re: different codings of a char in the same litteral
Date: Mon, 11 Apr 2005 15:54:49 +0200	[thread overview]
Message-ID: <m23btxs9jq.fsf@seki.fr> (raw)
In-Reply-To: mailman.1060.1113223198.2895.help-gnu-emacs@gnu.org

Le 11 Apr 2005, Peter Dyballa a formulé :

> These should work:
> 
> unify-8859-on-decoding-mode: t
> unify-8859-on-encoding-mode: t

I used  to define this  until some recent  tests where I determined  that it
causes some  mess with  OSX and  fontsets for displaying  at least  the euro
char.

I keep only unify-8859-on-encoding-mode.

Maybe it is only relative to the current cvs version ?

-- 
Sébastien Kirche

      parent reply	other threads:[~2005-04-11 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 12:49 different codings of a char in the same litteral Sébastien Kirche
2005-04-11 13:09 ` Peter Dyballa
     [not found] ` <mailman.1060.1113223198.2895.help-gnu-emacs@gnu.org>
2005-04-11 13:54   ` Sébastien Kirche [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=m23btxs9jq.fsf@seki.fr \
    --to=sebastien.kirche.no@spam.free.fr.invalid \
    --cc=sebastien.kirche@free.fr \
    /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).