all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: stephen@xemacs.org, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: Creating a coding system
Date: Sat, 20 Dec 2014 20:34:33 +0200	[thread overview]
Message-ID: <83oaqyqifa.fsf@gnu.org> (raw)
In-Reply-To: <87vbl6gt6a.fsf@fencepost.gnu.org>

> From: David Kastrup <dak@gnu.org>
> Date: Sat, 20 Dec 2014 17:52:29 +0100
> Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
> 
> >  > I am missing the big picture here in some manner.  Does decoding not
> >  > start from a byte stream but rather from an emacs-utf-8 encoded version
> >  > of a byte stream?
> >
> > Either (see Eli's reply).  But the translation table is an add-on, not
> > part of the bytes-to-character coding system itself.
> 
> Huh.  Then maybe I am not doing this right.  I want to use a "process
> coding system" to efficiently sift through Midi data and leaves some
> useful form (a more versatile form would likely be the Lisp reader
> equivalent of MidiXML).

May I suggest to describe your problem in more detail?  I couldn't
glean that from the snippet that started this thread.  (I know nothing
about Midi.)  Maybe if we knew what is it that you are trying to
accomplish with your coding-system, we could be of more assistance.

> It would seem that Handa-san is currently the only documentation for the
> coding system details Emacs has.  Some more redundancy might be a good
> idea.

We already have that:


  32.10 Coding Systems
  ====================

  When Emacs reads or writes a file, and when Emacs sends text to a
  subprocess or receives text from a subprocess, it normally performs
  character code conversion and end-of-line conversion as specified by a
  particular "coding system".

     How to define a coding system is an arcane matter, and is not
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  documented here.
  ^^^^^^^^^^^^^^^^



  reply	other threads:[~2014-12-20 18:34 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83oaqyqifa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dak@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 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.