GNU bug report logs -
#2755
describe-char says that DejaVu Sans Mono is being used to display a raw character
Previous Next
Reported by: Juanma Barranquero <lekktu <at> gmail.com>
Date: Mon, 23 Mar 2009 15:25:04 UTC
Severity: normal
Tags: moreinfo
Done: Juanma Barranquero <lekktu <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Thu, 7 Jul 2011 01:48:58 +0200
with message-id <CAAeL0SRPPvEe4zJ=3j1gc3bXqzObBb5y9ys5mAceRdY6NmAv3w <at> mail.gmail.com>
and subject line Re: bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character
has caused the GNU bug report #2755,
regarding describe-char says that DejaVu Sans Mono is being used to display a raw character
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
2755: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2755
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
As a consequence of bug#2741, after vc-annotate I get a buffer that is
nominally utf-8-dos but contains raw bytes, for example:
ca005e53 test.txt (Juanma Barranquero 2008-01-29 08:56:38 +0000 32)
;;; Preparaci\363n
If I `describe-char' the \363 character, I get:
character: (4194291, #o17777763, #x3ffff3)
preferred charset: eight-bit (Raw bytes 128-255)
code point: 0xF3
syntax: w which means: word
buffer code: #xF3
file code: not encodable by coding system utf-8-dos
display: by this font (glyph code)
uniscribe:-outline-DejaVu Sans
Mono-normal-normal-normal-mono-13-*-*-*-c-*-iso8859-1 (#x03)
Character code properties: customize what to show
There are text properties here:
face vc-annotate-face-FF3F3F
fontified t
which seems wrong. In fact, I can only reproduce this at work; on my
laptop, with a very similar font setup (both have nearly identical
fonts, including the very same version of DejaVu Sans Mono)
`describe-char' says that it has no font available for that character.
The relevant part of the font log:
font for: (243 . iso-8859-1)
list: -outline-DejaVu Sans Mono-*-mono-*-iso8859-1
-outline-DejaVu Sans Mono-normal-italic-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-bold-italic-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-bold-normal-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-normal-normal-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-normal-italic-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-bold-italic-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-bold-normal-normal-mono-*-c-*-iso8859-1
-outline-DejaVu Sans Mono-normal-normal-normal-mono-*-c-*-iso8859-1
sort-by: -*-normal-normal-normal-*-13-*
uniscribe:-outline-DejaVu Sans Mono-normal-normal-normal-mono-*-c-*-iso8859-1
Juanma
[Message part 3 (message/rfc822, inline)]
On Thu, Sep 10, 2009 at 01:34, Juanma Barranquero <lekktu <at> gmail.com> wrote:
> FWIW, I can now reproduce #2755, so if you want me to try something, just ask.
I cannot reproduce it anymore, so I'm closing this one.
Juanma
This bug report was last modified 13 years and 326 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.