From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: utf-8 thai character display issue?
Date: Sat, 06 Jun 2020 21:29:43 +0300 [thread overview]
Message-ID: <83a71g82ug.fsf@gnu.org> (raw)
In-Reply-To: <87ftb8duxi.fsf@dstar.dstar.net> (message from scole_mail on Sat, 06 Jun 2020 09:24:09 -0700)
> From: scole_mail <scole_mail@gmx.com>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Sat, 06 Jun 2020 09:24:09 -0700
>
> > This sounds like a problem with the text shaping engine your build is
> > using on NetBSD. (you didn't give the details of the build, so I
> > cannot know which shape engine is being used, but I'm guessing its
> > libflt.) Try upgrading to Emacs 27, and make sure it is built with
> > HarfBuzz support (the latest pretest can be downloaded from
> > alpha.gnu.org).
>
> Just for posterity, I was using the pkgsrc/editors/emacs26 from
> http://pkgsrc.org/, which I think is actually emacs26.3. As best as I
> could tell, it was not using harfbuzz?
No, HarfBuzz was not supported before Emacs 27.
> Luckily, there already existed a package in
> pkgsrc/editors/emacs-snapshot that is emacs28.0.50. It had almost the
> same dependencies plus
> harfbuzz>=2.6.4nb2
> and a few others. It seems to be working now for what I need.
Thanks, so I think my guess was correct, and the problem was with the
shaping engine.
prev parent reply other threads:[~2020-06-06 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 18:05 utf-8 thai character display issue? scole_mail
2020-06-05 20:34 ` Eli Zaretskii
2020-06-06 16:24 ` scole_mail
2020-06-06 18:29 ` Eli Zaretskii [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=83a71g82ug.fsf@gnu.org \
--to=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).