Re: Creating a coding system

[David Kastrup]

Eli Zaretskii <address@hidden> writes:

>> From: David Kastrup <address@hidden>
>> Cc: address@hidden,  address@hidden
>> Date: Sat, 20 Dec 2014 20:06:45 +0100
>> 
>> Now the first iteration would be just using the pitches from a Midi
>> keyboard.  The second iteration would then try working with durations.
>> Either by putting time stamps on the events as they trundle in, or by
>> reading from a "cooked" Midi stream already containing encoded time time
>> stamps.
>> 
>> Conversion of time stamps to musical durations, particularly when the
>> time stamps have not been generated by a notation program but by a human
>> player, is non-trivial and would hopefully end up as an incremental
>> process where a human corrects durations and Emacs improves its overall
>> guesswork.
>> 
>> But time stamps are for another time.  Right now I'd be glad just to
>> convert the pitches from they keyboard into LilyPond's pitch notation in
>> order to make key entry faster.
>
> I might be mistaken, but this doesn't look to me like a job for a
> coding-system.  You are talking about parsing input into some abstract
> notation,

"parsing input" is sort of bombastic for interpreting a binary
representation consisting of isolated minimal words.

> then generating a representation of that input in a different
> language.  This is sufficiently different from converting characters
> from one encoding to another that you should perhaps look at
> cedet/semantic/ stuff instead.

Uh, there is no grammar involved here, no context, most certainly not a
push-down stack or something.  There is nothing that would warrant using
a parser.  And we are talking about real-time processing needs,
basically an input method using a different device than the keyboard.

cedet/semantic seem like much more of a mismatch, both in functionality
and response time, than using a process encoding here.

-- 
David Kastrup