bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Juanma Barranquero]

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

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Kenichi Handa]

In article <f7ccd24b0903230817n5ee5a30fy96ebe948f632a4ee@mail.gmail.com>, Juanma Barranquero <lekktu@gmail.com> writes:

> 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

I can't reproduce that problem on GNU/Linux system.

> 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)

This is very strange.  243 is the byte code of that raw-byte
character #x3ffff3.  But, usually the log should say that
the character code is #x3ffff3, And, it says that the
character has `charset' text property `iso-8859-1'.  But,
describe-char doesn't show that property.

> 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

Is it a Windows specific problem?

---
Kenichi Handa
handa@m17n.org

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Juanma Barranquero]

On Thu, Apr 2, 2009 at 14:29, Kenichi Handa <handa@m17n.org> wrote:

> This is very strange.  243 is the byte code of that raw-byte
> character #x3ffff3.  But, usually the log should say that
> the character code is #x3ffff3, And, it says that the
> character has `charset' text property `iso-8859-1'.  But,
> describe-char doesn't show that property.

> Is it a Windows specific problem?

I suppose so.

Unfortunately, I've just lost access to the only computer where I was
able to reproduce the problem, so I think we should either close this
bug, or tag it as +moreinfo on the hope that it can be reproduced
(I'll try to duplicate on the laptop the font setup I had at work as
exactly as possible, but it's a long shot).

I still see #2741, though.

    Juanma

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Kenichi Handa]

In article <f7ccd24b0904020546l5eb3ddd8q81fe94123e3f8f25@mail.gmail.com>, Juanma Barranquero <lekktu@gmail.com> writes:

> On Thu, Apr 2, 2009 at 14:29, Kenichi Handa <handa@m17n.org> wrote:
> > This is very strange.  243 is the byte code of that raw-byte
> > character #x3ffff3.  But, usually the log should say that
> > the character code is #x3ffff3, And, it says that the
> > character has `charset' text property `iso-8859-1'.  But,
> > describe-char doesn't show that property.

> > Is it a Windows specific problem?

> I suppose so.

> Unfortunately, I've just lost access to the only computer where I was
> able to reproduce the problem,

Oops, I should have respond in this thread much earlier, sorry.

> so I think we should either close this bug, or tag it as
> +moreinfo on the hope that it can be reproduced

I agree with +moreinfo.  How to do that?

> I still see #2741, though.

I have no knowledge about vc.el.  Isn't it possible to fix
this bug within vc*.el?  Does it require more fundamental
change?

---
Kenichi Handa
handa@m17n.org

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Juanma Barranquero]

On Fri, Apr 3, 2009 at 04:15, Kenichi Handa <handa@m17n.org> wrote:

> Oops, I should have respond in this thread much earlier, sorry.

No problem; it wasn't a serious bug anyway (not to mention being
almost non-reproducible).

> I agree with +moreinfo.  How to do that?

Just Cc: to control@emacsbugs.donarmstrong.com, and start the message with

tags 2755 + moreinfo
quit

> I have no knowledge about vc.el.  Isn't it possible to fix
> this bug within vc*.el?  Does it require more fundamental
> change?

No, I think it's just vc.

    Juanma

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Juanma Barranquero]

On Thu, Apr 2, 2009 at 14:46, Juanma Barranquero<lekktu@gmail.com> wrote:

> Unfortunately, I've just lost access to the only computer where I was
> able to reproduce the problem

FWIW, I can now reproduce #2755, so if you want me to try something, just ask.

    Juanma

bug#2755: describe-char says that DejaVu Sans Mono is being used to display a raw character

[Juanma Barranquero]

On Thu, Sep 10, 2009 at 01:34, Juanma Barranquero <lekktu@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