From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: UTF-8 in path / filename
Date: Mon, 28 Aug 2006 17:55:25 +0200 [thread overview]
Message-ID: <9A4ABCC5-11FA-461E-9CBD-7A7CC7FE552D@Web.DE> (raw)
In-Reply-To: <m3ac5onbdi.fsf@lugabout.jhcloos.org>
Am 28.08.2006 um 17:11 schrieb James Cloos:
> So. Does C-u C-x = claim to be composing for you?
Yes, in GNU Emacs 23:
character: U (85, #o125, #x55)
preferred charset: ascii (ASCII (ISO646 IRV))
code point: 0x55
syntax: w which means: word
category: a:ASCII l:Latin r:Japanese roman
buffer code: #x55
file code: not encodable by coding system utf-8-unix
display: composed to form "Ü" (see below)
Unicode data:
Name: LATIN CAPITAL LETTER U
Category: Letter, Uppercase
Combining class: Lu
Bidi category: Lu
Lowercase: u
Composed with the following character(s) "¨" by the rule:
(?U (tc . bc) ?¨)
The component character(s) are displayed by these fonts (glyph codes):
U: -B&H-LucidaTypewriter-Medium-R-Normal-Sans-10-100-75-75-M-60-
ISO8859-1 (#x55)
¨: -MUTT-ClearlyU-Medium-R-Normal--17-120-100-100-P-123-ISO10646-1
(#x308)
(Here you can see the reason for the large vertical composed
characters: a much too big font.)
In GNU Emacs 22.0.50 they are not composed, they are <vowel><accent>.
Instead of composing a character I would first try to find the pre-
composed form in the font(set) used. It surely would look much better.
--
Greetings
Pete
"We have to expect it, otherwise we would be surprised."
next prev parent reply other threads:[~2006-08-28 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 13:59 UTF-8 in path / filename Grégory SCHMITT
2006-08-24 14:42 ` Noah Slater
2006-08-25 12:08 ` Peter Dyballa
[not found] ` <mailman.5606.1156507702.9609.help-gnu-emacs@gnu.org>
2006-08-25 13:42 ` Grégory SCHMITT
2006-08-25 18:35 ` Peter Dyballa
2006-08-25 22:06 ` Grégory SCHMITT
2006-08-25 22:55 ` Peter Dyballa
[not found] ` <mailman.5656.1156546542.9609.help-gnu-emacs@gnu.org>
2006-08-25 23:06 ` Grégory SCHMITT
2006-08-25 23:09 ` Miles Bader
2006-08-26 9:36 ` Peter Dyballa
2006-08-26 22:13 ` James Cloos
2006-08-27 13:12 ` Peter Dyballa
2006-08-28 15:11 ` James Cloos
2006-08-28 15:55 ` Peter Dyballa [this message]
[not found] ` <mailman.5694.1156630455.9609.help-gnu-emacs@gnu.org>
2006-08-27 8:46 ` Harald Hanche-Olsen
[not found] ` <mailman.5657.1156547377.9609.help-gnu-emacs@gnu.org>
2006-08-25 23:22 ` Grégory SCHMITT
2006-08-25 23:25 ` Miles Bader
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=9A4ABCC5-11FA-461E-9CBD-7A7CC7FE552D@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=miles@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).