From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; Bugs with ftx font-backend
Date: Fri, 1 Feb 2008 22:27:35 +0100 [thread overview]
Message-ID: <4B24BD27-1368-4912-9B0C-31240FA5158A@Freenet.DE> (raw)
[-- Attachment #1: Type: text/plain, Size: 3044 bytes --]
Hello!
In dired-mode file names and directory names are displayed in
different faces, for file names:
There are text properties here:
auto-composed t
fontified t
help-echo "mouse-2: visit this file in other window"
mouse-face highlight
for directory names:
auto-composed t
face dired-directory
fontified t
help-echo "mouse-2: visit this file in other window"
mouse-face highlight
When the cursor is on the same character, x, I get for the directory
name's x:
character: x (120, #o170, #x78)
preferred charset: ascii (ASCII (ISO646 IRV))
code point: 0x78
syntax: w which means: word
category: a:ASCII graphic characters 32-126 (ISO646 IRV:1983
[4/0]) l:Latin
r:Japanese roman
buffer code: #x78
file code: not encodable by coding system utf-8-unix
display: by this font (glyph code)
lucidatypewriter:pixelsize=10:foundry=b&h:weight=medium:slant=r:width=no
rmal (#x59)
and for the file name's x:
character: x (120, #o170, #x78)
preferred charset: ascii (ASCII (ISO646 IRV))
code point: 0x78
syntax: w which means: word
category: a:ASCII graphic characters 32-126 (ISO646 IRV:1983
[4/0]) l:Latin
r:Japanese roman
buffer code: #x78
file code: not encodable by coding system utf-8-unix
display: by this font (glyph code)
lucidatypewriter:pixelsize=10:foundry=b&h:weight=medium:slant=r:width=no
rmal (#x59)
It looks quite equal. But when I look at both names in dired buffer I
see differences that obviously come from different fonts used, which
is not reported as can be seen above:

Another effect is that text file names get scrambled or partly
extinguished thought that green background when the mouse cursor
moves over the names:

And then the names of directories are completely wrong when the mouse
cursor hovers above such an item. The change in name happens
simultaneously with the appearing of the green background:

All tests done with src/emacs -Q. The different background colours
come from default- and initial-frame-alist settings done in *scratch*
buffer. Looking with an electronic magnifier glass I can see that the
glyphs of the directory and sym-link names are anti-aliased (as are
the italic names of the text properties items in *Help* buffer, or
the incredibly RED group Write permission), while the other glyphs
seem to come from a bitmapped font: every pixel has the same
intensity level.
BTW, de-composed characters in Mac OS X HFS+ file names are shown as
their basic Latin glyphs without further "decoration."
--
Greetings
Pete
Isn't vi that text editor with two modes... one that beeps and one
that corrupts your file?
– Dan Jacobson, on comp.os.linux.advocacy
[-- Attachment #2.1: Type: text/html, Size: 4732 bytes --]
[-- Attachment #2.2.1: blackboxrc.png --]
[-- Type: application/applefile, Size: 38113 bytes --]
[-- Attachment #2.2.2: blackboxrc.png --]
[-- Type: image/png, Size: 1386 bytes --]
[-- Attachment #2.3: Type: text/html, Size: 482 bytes --]
[-- Attachment #2.4.1: Deterioration.png --]
[-- Type: application/applefile, Size: 25063 bytes --]
[-- Attachment #2.4.2: Deterioration.png --]
[-- Type: image/png, Size: 10598 bytes --]
[-- Attachment #2.5: Type: text/html, Size: 522 bytes --]
[-- Attachment #2.6.1: wdogdl.png --]
[-- Type: application/applefile, Size: 25013 bytes --]
[-- Attachment #2.6.2: wdogdl.png --]
[-- Type: image/png, Size: 14233 bytes --]
[-- Attachment #2.7: Type: text/html, Size: 3269 bytes --]
reply other threads:[~2008-02-01 21:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B24BD27-1368-4912-9B0C-31240FA5158A@Freenet.DE \
--to=peter_dyballa@freenet.de \
--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).