From: David Kastrup <dak@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Eli Zaretskii <eliz@gnu.org>, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Creating a coding system
Date: Sat, 20 Dec 2014 19:40:27 +0100 [thread overview]
Message-ID: <87mw6igo6c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877fxmcgwi.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 21 Dec 2014 03:31:09 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> David Kastrup writes:
>
> > Maybe a coding system is not even the right way to do this, but at
> > least it seems like a builtin mechanism and consequently fast.
>
> I think a coding system is the right way to do it, but you probably
> need to construct the coding system a different way. You might need
> to write a little CCL (Aidan Kehoe can probably help if Handa-san is
> unavailable). There's some CCL documentation in the XEmacs manuals,
> but it's probably not much more than a Texinfoization of the comments
> in the files defining CCL.
Oh wow. I thought CCL was Emacs-only, and it seemed like it was
deprecated anyway. But CCL seems better suited for converting Midi in a
more complete manner, particularly where numeric parameters are
concerned.
--
David Kastrup
next prev parent reply other threads:[~2014-12-20 18:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 9:05 Creating a coding system David Kastrup
2014-12-20 10:20 ` Thien-Thi Nguyen
2014-12-20 10:42 ` David Kastrup
2014-12-20 13:51 ` Andreas Schwab
2014-12-20 14:19 ` David Kastrup
2014-12-20 14:50 ` Eli Zaretskii
2014-12-20 15:56 ` Thien-Thi Nguyen
2014-12-20 16:11 ` Andreas Schwab
2014-12-20 16:14 ` Andreas Schwab
2014-12-20 16:43 ` David Kastrup
2014-12-20 16:53 ` Eli Zaretskii
2014-12-20 17:38 ` David Kastrup
2014-12-20 18:31 ` Stephen J. Turnbull
2014-12-20 18:40 ` David Kastrup [this message]
2014-12-20 18:35 ` Eli Zaretskii
2014-12-20 19:06 ` David Kastrup
2014-12-20 20:02 ` Eli Zaretskii
2014-12-20 20:11 ` David Kastrup
2014-12-20 20:45 ` Eli Zaretskii
2014-12-20 21:15 ` David Kastrup
2014-12-21 19:46 ` David Kastrup
2014-12-21 21:25 ` David Kastrup
2014-12-21 5:54 ` Stephen J. Turnbull
2014-12-20 16:21 ` Stephen J. Turnbull
2014-12-20 16:52 ` David Kastrup
2014-12-20 18:34 ` Eli Zaretskii
2014-12-20 18:42 ` David Kastrup
2014-12-23 8:59 ` K. Handa
2014-12-23 9:25 ` David Kastrup
2014-12-24 15:06 ` K. Handa
2014-12-25 6:39 ` David Kastrup
2014-12-29 14:11 ` K. Handa
2014-12-29 14:25 ` David Kastrup
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=87mw6igo6c.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stephen@xemacs.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.
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).