unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: wikipedia and UTF8 coding (emacs21)
Date: Tue, 22 Nov 2005 14:46:52 -0500	[thread overview]
Message-ID: <87hda4fp0n.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 87fyqdmuxo.fsf@mat.ucm.es

> I presume you don't a difference in 
> Brüder and Brüder 
  ^^^^^^^
This shows that the utf-8 format was not treated as such and instead Emacs
read the file as if it were encoded in latin-1 or binary.

> I did your C-u C-x = which tells me:

> character: Ã (0303, 195, 0xc3)
>     charset: eight-bit-graphic (8-bit graphic char (0xA0..0xFF))
               ^^^^^^^^^^^^^^^^^

This means "unknown char, thus treated as a byte".

If you tell your Emacs to use utf-8 for this file (try C-x RET u utf-8 RET
before C-x C-f, or set file-coding-system-alist so it's done automatically
everytime), your char's charset should be either latin-8859-1 or
mule-unicode-nnnn.

All the above assumes you're not using Emacs in unibyte mode.  Unibyte mode
(which you sadly get if you have a lingering `special-display-european' in
your .emacs) can't handle UTF-8.


        Stefan

  parent reply	other threads:[~2005-11-22 19:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 14:37 wikipedia and UTF8 coding (emacs21) Uwe Brauer
2005-11-03 15:49 ` Peter Dyballa
2005-11-03 16:33 ` Stefan Monnier
2005-11-03 18:45   ` Uwe Brauer
2005-11-03 19:04     ` Peter Dyballa
2005-11-03 19:09       ` Uwe Brauer
2005-11-03 19:43         ` Peter Dyballa
     [not found]         ` <mailman.13846.1131047004.20277.help-gnu-emacs@gnu.org>
2005-11-03 20:30           ` Uwe Brauer
2005-11-04 12:35           ` Reiner Steib
     [not found]       ` <mailman.13841.1131044962.20277.help-gnu-emacs@gnu.org>
2005-11-22 19:49         ` Stefan Monnier
2005-12-02 17:58           ` font problem persists (was: wikipedia and UTF8 coding (emacs21)) Uwe Brauer
2005-12-02 20:08             ` Peter Dyballa
2005-12-03  2:21             ` font problem persists Stefan Monnier
2005-12-05 17:30               ` Uwe Brauer
     [not found]             ` <mailman.17688.1133554097.20277.help-gnu-emacs@gnu.org>
2005-12-05 17:25               ` Uwe Brauer
2005-11-04 12:34     ` wikipedia and UTF8 coding (emacs21) Reiner Steib
2005-11-22 19:46     ` Stefan Monnier [this message]
2005-11-23 20:55       ` Reiner Steib
     [not found]       ` <mailman.16628.1132865580.20277.help-gnu-emacs@gnu.org>
2005-11-25  4:29         ` Stefan Monnier
2005-11-03 17:09 ` Denis H. G.
     [not found] ` <mailman.13812.1131033002.20277.help-gnu-emacs@gnu.org>
2005-11-03 18:32   ` Reiner Steib
2005-11-04 20:22     ` Uwe Brauer
2005-11-22 19:40       ` Stefan Monnier
2005-11-06 10:16     ` using emacs 21 (was: " Uwe Brauer
2005-11-06 10:48       ` Peter Dyballa
2005-11-06 10:59       ` Peter Dyballa
2005-11-04 14:05   ` Encodings in message (was: wikipedia and UTF8 coding (emacs21)) Marc Girod
2005-11-04 15:25     ` Encodings in message Reiner Steib

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=87hda4fp0n.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    /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).