From: Richard Wordingham <richard.wordingham@ntlworld.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Adding Tai Tham Script to GNU/Linux Distribution's Version of Emacs
Date: Tue, 17 Mar 2015 00:23:03 +0000 [thread overview]
Message-ID: <20150317002303.66d7ac33@JRWUBU2> (raw)
In-Reply-To: <83zj7czytg.fsf@gnu.org>
On Mon, 16 Mar 2015 18:34:03 +0200
Eli Zaretskii <eliz@gnu.org> wrote:
> The default composition rules are defined in lisp/composite.el
> (towards the second half of the file), and files in lisp/language/ add
> rules for specific languages. (Those rules sometimes use character
> categories, and sometimes even invent new categories; see thai-util.el
> as an example.) I believe you will see there the data that allows
> Emacs to perform CTL for Thai and Tibetan.
>
> My guess is that you will have to write a tai-tham.el file with
> similar data for Tai Tham, and then load it into Emacs. All the rest
> should "just work".
I've done as you suggested and am getting what seem to be evidence of
communication, Emacs to m17n, for Tai Tham text. Everything was broken
at the first attempt - infinite loop in Emacs, and I think m17n is
giving up on my instructions. I'll just have to approach the full
design bit by bit. I aped burmese.el for tai-tham.el.
Having been forced to recompile emacs for myself, it will be less
awkward to put monitoring in. I nearly missed the need to obtain the
m17n and libotf developer packages - it was only the display of
configuration options selected by configure that alerted me.
Richard.
next prev parent reply other threads:[~2015-03-17 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.28836.1426477412.31050.help-gnu-emacs@gnu.org>
2015-03-16 7:47 ` Adding Tai Tham Script to GNU/Linux Distribution's Version of Emacs Richard Wordingham
2015-03-16 16:34 ` Eli Zaretskii
2015-03-17 0:23 ` Richard Wordingham [this message]
2015-03-17 7:30 ` Eli Zaretskii
2015-03-18 8:27 ` Richard Wordingham
2015-03-18 21:33 ` Richard Wordingham
2015-03-19 3:41 ` Eli Zaretskii
2015-03-19 7:37 ` Richard Wordingham
2015-03-20 1:18 ` Richard Wordingham
2015-03-15 23:15 Richard Wordingham
2015-03-16 3:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2015-03-15 12:32 Richard Wordingham
2015-03-15 16:56 ` Eli Zaretskii
2015-03-15 17:01 ` Eli Zaretskii
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=20150317002303.66d7ac33@JRWUBU2 \
--to=richard.wordingham@ntlworld.com \
--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).