From: Sergey Organov <sorganov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to enforce unicode font for all charsets?
Date: Fri, 13 Mar 2020 19:38:04 +0300 [thread overview]
Message-ID: <87eetwtdlf.fsf@osv.gnss.ru> (raw)
In-Reply-To: <835zf88d3c.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Mar 2020 17:54:31 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Sergey Organov <sorganov@gmail.com>
>> Cc: help-gnu-emacs@gnu.org
>> Date: Fri, 13 Mar 2020 17:54:51 +0300
>>
>> > Is the snapshot you installed using the HarfBuzz library? (If it
>> > does, you should see it in the output of "C-u C-x =".) If it doesn't,
>> > please try a build that does use HarfBuzz, which is now the default
>> > font backend in Emacs, before you decide that the issue still exists
>> > in the latest codebase.
>>
>> I didn't built it myself and have no idea what HarfBuzz is, here is the
>> output of "C-u C-x =":
>>
>> --- >8 ---
>> position: 24 of 60 (38%), column: 23
>> character: п (displayed as п) (codepoint 1087, #o2077, #x43f)
>> charset: windows-1251 (WINDOWS-1251 (Cyrillic))
>> code point in charset: 0xEF
>> script: cyrillic
>> syntax: w which means: word
>> category: .:Base, L:Left-to-right (strong), Y:2-byte Cyrillic, c:Chinese, h:Korean, j:Japanese, y:Cyrillic
>> to input: type "C-x 8 RET 43f" or "C-x 8 RET CYRILLIC SMALL LETTER PE"
>> buffer code: #xD0 #xBF
>> file code: #xD0 #xBF (encoded by coding system utf-8-unix)
>> display: by this font (glyph code)
>> x:-xos4-terminus-medium-r-normal--16-160-72-72-c-80-microsoft-cp1251 (#xEF)
>
> The output for the other string, the one with the 'unicode' charset,
> is the telltale sign. It shouldn't show "xft" before the font name.
It shows:
ftcrhb:-PfEd-DejaVu Sans Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1 (#x37E)
so it must be HarfBuzz?
> Also, system-configuration-features should include "HARFBUZZ" if Emacs
> was built with HarfBuzz.
system-configuration-features is a variable defined in ‘C source code’.
Its value is
"XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY
INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF
ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS PDUMPER LCMS2
GMP"
Yeah, it is.
-- Sergey
prev parent reply other threads:[~2020-03-13 16:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 11:31 How to enforce unicode font for all charsets? Sergey Organov
2020-03-10 14:48 ` Eli Zaretskii
2020-03-11 5:10 ` Sergey Organov
2020-03-11 8:17 ` Robert Pluim
2020-03-11 12:18 ` Sergey Organov
2020-03-11 16:47 ` Eli Zaretskii
2020-03-12 6:53 ` Sergey Organov
2020-03-12 15:10 ` Eli Zaretskii
2020-03-13 6:48 ` Sergey Organov
2020-03-13 9:06 ` Eli Zaretskii
2020-03-13 11:58 ` Sergey Organov
2020-03-13 14:21 ` Eli Zaretskii
2020-03-13 15:03 ` Sergey Organov
2020-03-13 15:55 ` Eli Zaretskii
2020-03-17 4:34 ` Sergey Organov
2020-03-13 13:58 ` Sergey Organov
2020-03-13 14:36 ` Eli Zaretskii
2020-03-13 14:54 ` Sergey Organov
2020-03-13 15:54 ` Eli Zaretskii
2020-03-13 16:22 ` Robert Pluim
2020-03-13 19:44 ` Eli Zaretskii
2020-03-14 16:07 ` Robert Pluim
2020-03-14 16:55 ` Eli Zaretskii
2020-03-13 16:38 ` Sergey Organov [this message]
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=87eetwtdlf.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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).