[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Display of undisplayable characters: \U01F3A8 instead of diamond

From: Alan Mackenzie
Subject: Re: Display of undisplayable characters: \U01F3A8 instead of diamond
Date: Fri, 2 Sep 2022 15:38:32 +0000

Hello, Gregory.

On Fri, Sep 02, 2022 at 13:41:14 +0000, Gregory Heytings wrote:

> > In my experience, they work less well than the fonts for the Linux 
> > console.

> Your experience is rather short, isn't it?  You objected to that solution 
> as soon as it was suggested.  Please try again with a better font.

Suggest one to me, please.  I'm not an expert on X-Windows fonts.

> What you see under fbterm is exactly (with respect to fonts) what you
> would see in a terminal emulator under X, including anti-aliasing.

I detest anti-aliasing.  It makes everything go blurred for me.  Maybe
that's a reason why I don't like these fonts.

> > That was the first one I tried this morning.  I didn't like it.  It's a 
> > "spidery" font like all the other ones I have available.

> Can you provide a screenshot of Emacs under fbterm with that font and one 
> of Emacs in the raw Linux console?  I'm not sure I understand what you 
> mean by "spidery".

No, I don't know how to take a screen shot of a console.  But the utility
psf2txt displays the bitmaps of all characters in a console font.  The
image for C in lat1-16.psfu looks like:

// Character 67
Bitmap: -------- \
        -------- \
        --####-- \
        -##--##- \
        ##----#- \
        ##------ \
        ##------ \
        ##------ \
        ##------ \
        ##----#- \
        -##--##- \
        --####-- \
        -------- \
        -------- \
        -------- \
Unicode: [00000043];

Note that the main body of the character is two pixels thick.  This
doesn't appear to be the case for any of the fonts I've tried in fbterm,
which appear to be just one pixel thick; or to use anti-aliasing or other
tricks.  That one pixel thickness is what I mean by "spidery", in the
sense of "as thin as a spider's web".

> > I just came across another problem.  The GPM mouse utility won't 
> > transfer text between an fbterm console and another console, not even a 
> > second fbterm.

> I don't know.  In any case, that seems to be a very minor problem.

It's not minor to me.  Without GPM, I'd have to alter my workflow

> > I think you were being too positive about the topic, and felt I should 
> > express the other side of the argument.

> I don't think you are expressing the other side of the argument.  You are 
> listing very minor problems (and non-problems, such as when you said that 
> "you have to configure faces").

I think you said earlier on in the thread that there were "no known
inconveniences" with fbterm.  I have listed some inconveniences, even if
I've called them problems.  I think you were mistaken on this point.

> By the way, if you don't want 256 colors and want to use only 8 colors as 
> you did before, just don't set TERM=fbterm, or set TERM=linux.

Well, it's not just as before - as I said earlier, hi-green comes out as
brown.  That's the sort of thing I meant when I said that you had to
configure faces.

Alan Mackenzie (Nuremberg, Germany).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]