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: Wed, 25 Oct 2017 07:48:34 +0900 [thread overview]
Message-ID: <87y3o0b1rx.fsf@gnu.org> (raw)
In-Reply-To: <87fua8685t.fsf@gmx.net> (message from Stephen Berman on Tue, 24 Oct 2017 14:29:34 +0200)
In article <87fua8685t.fsf@gmx.net>, Stephen Berman <stephen.berman@gmx.net> writes:
> > Could you please put the attached version of LAOO-OTF.flt under
> > /usr/share/m17n (without any other LAOO-*.flt), and try again?
> With this version the Lao composed characters display correctly; FYI the
> debugging output is appended below. (With this version the variable
> pitch DejaVu Sans also correctly displays the character compositions,
> including the one that was previously incorrectly displayed with this
> font.)
Thank you for checking. So, the layout engine itself is working well,
and the problem is...
> However, when I move the LAOO-{ALICE,GENERIC,MULE}.flt files
> back to /usr/share/m17n, leaving the new LAOO-OTF.flt there, the display
> is again incorrect and the debugging output shows laoo-generic being
> used.
LAOO-OTF.flt is not preferred over the other Lao layouting tables. I'll
check the source code of m17n-lib.
---
K. Handa
handa@gnu.org
next prev parent reply other threads:[~2017-10-24 22:48 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3o0b1rx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.