From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Problems in Displaying endash in Emacs-w3m
Date: Wed, 4 Oct 2006 12:34:21 +0200 [thread overview]
Message-ID: <13B2285C-7750-4E84-BF8A-67BC4ABCAAF0@Web.DE> (raw)
In-Reply-To: <87ac4cjw4e.fsf@MagnumOpus.khem>
Am 03.10.2006 um 20:12 schrieb Charles philip Chan:
> It does on other characters that I have tried, but not the endash. I
> forget to mention that I am using an iso10646-1 font as my default
> font. Now it look more and more like a bug in CVS Emacs.
No. When I launch GNU Emacs 22.0.50 with -Q and look into an UTF-8
file from Kermit I get:
character: – (342387, #o1234563, #x53973, U+2013)
charset: mule-unicode-0100-24ff (Unicode characters of the range
U+0100..U+24FF.)
code point: #x72 #x73
syntax: _ which means: symbol
buffer code: #x9C #xF4 #xF2 #xF3
file code: #xE2 #x80 #x93 (encoded by coding system mule-utf-8-unix)
display: by this font (glyph code)
-B&H-LucidaTypewriter-Medium-R-Normal-Sans-10-100-75-75-M-60-
ISO10646-1 (#x2013)
which looks OK. How is the output when you launch GNU Emacs 22.0.50
with -Q?
Check particularly the "buffer code!" Yours is different. I am using
a simple text buffer, mode-line starts with ``-u:´´. (Although I've
seen ``-E:´´ also – which is a bug in GNU Emacs 22.0.50: the first
UTF-8 encoded file it opens it does *not* open in UTF-8, but in
Japanese, at least for me).
--
Greetings
Pete
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny..."
Isaac Asimov
next prev parent reply other threads:[~2006-10-04 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:29 Problems in Displaying endash in Emacs-w3m Charles philip Chan
2006-10-03 15:00 ` Kevin Rodgers
[not found] ` <mailman.7697.1159887811.9609.help-gnu-emacs@gnu.org>
2006-10-03 18:12 ` Charles philip Chan
2006-10-04 10:34 ` Peter Dyballa [this message]
[not found] ` <mailman.7724.1159958067.9609.help-gnu-emacs@gnu.org>
2006-10-04 11:24 ` Charles philip Chan
2006-10-04 11:48 ` Peter Dyballa
2006-10-07 13:24 ` Dieter Wilhelm
2006-10-07 17:44 ` Peter Dyballa
2006-10-07 19:26 ` Dieter Wilhelm
2006-10-08 9:34 ` Peter Dyballa
2006-10-08 13:21 ` Reiner Steib
[not found] ` <mailman.7859.1160227519.9609.help-gnu-emacs@gnu.org>
2006-10-08 16:54 ` Charles philip Chan
2006-10-08 21:06 ` Peter Dyballa
[not found] ` <mailman.7906.1160341664.9609.help-gnu-emacs@gnu.org>
2006-10-09 1:19 ` Charles philip Chan
2006-10-09 9:30 ` Peter Dyballa
2006-10-09 10:47 ` Jim Ottaway
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=13B2285C-7750-4E84-BF8A-67BC4ABCAAF0@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@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.
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).