From: handa <handa@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Display of Lao script
Date: Sun, 22 Oct 2017 12:37:14 +0900 [thread overview]
Message-ID: <877evndf9x.fsf@gnu.org> (raw)
In-Reply-To: <87po9irqej.fsf@gmx.net> (message from Stephen Berman on Fri, 20 Oct 2017 13:48:36 +0200)
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
In article <87po9irqej.fsf@gmx.net>, Stephen Berman <stephen.berman@gmx.net> writes:
> I haven't yet tried a font specialized for Lao, but I did try Symbola,
> and with that the Lao HELLO example appears as it does in Emacs without
> m17n-lib and libotf (with one exeption, see below) -- though the font
> used to display the Lao is not Symbola but DejaVu Sans. Then I realized
> what the difference is: Symbola is a variable pitch font, while my
> default font is DejaVu Sans Mono (also the default with -Q). And
> indeed, using DejaVu Sans (not Mono) as the default font displays the
> Lao as in Emacs without m17n-lib and libotf (but in the latter Emacs
> it's the same display also with DejaVu Sans Mono) -- with the exception
> of the character LAO LETTER HO SUNG, which is composed with LAO TONE MAI
> THO, but in the display, the latter appears over the following
> character, while in the Emacs without m17n-lib and libotf it appears
> over the character it is composed with (which I assume is correct). The
> other three character compositions in the Lao example appear the same in
> Emacs both without and with m17n-lib and libotf -- but again, in the
> latter only with variable pitch DejaVu Sans. So this does seem to be a
> problem in the m17n-lib and/or libotf code.
In my environment, Lao can be rendered correctly by Dejavu Sans Mono
(see the attached image). Please run Emacs as this, and show me the
printed log:
% MDEBUG_DATABASE=1 MDEBUG_FLT=1 emacs
---
K. Handa
handa@gnu.org
[-- Attachment #2: temp.png --]
[-- Type: image/png, Size: 24803 bytes --]
next prev parent reply other threads:[~2017-10-22 3:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:14 Display of Lao script Stephen Berman
2017-10-17 16:40 ` Eli Zaretskii
2017-10-20 11:48 ` Stephen Berman
2017-10-22 3:37 ` handa [this message]
2017-10-22 11:13 ` Stephen Berman
2017-10-24 9:14 ` handa
2017-10-24 10:01 ` Stephen Berman
2017-10-24 12:04 ` handa
2017-10-24 12:29 ` Stephen Berman
2017-10-24 22:48 ` handa
2017-11-05 5:26 ` handa
2017-11-05 12:28 ` Stephen Berman
2017-11-06 15:26 ` handa
2017-11-06 16:11 ` Eli Zaretskii
2017-11-07 11:56 ` handa
2017-10-20 13:11 ` Kaushal Modi
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=877evndf9x.fsf@gnu.org \
--to=handa@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).