wrote= : >>> Not to burst a balloon but check out variable length ints in the Midi Fi= le Format for utf-8 in the early 80s. >>>=20 >>> brucee >=20 --Apple-Mail-33FDBFEC-37A9-47ED-9FFD-63EE53169A36 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

It isn't. MIDI variable-len= gth quantities don't include an indication of length in a header, and the la= st byte in any multi-byte sequence is a valid single-byte value. It is more b= it efficient than UTF-8, but I believe it lacks other properties around sync= hronization, possibly others.

I'm less sure here, b= ut I believe the MIDI version is more similar to the thing the X/Open folks w= ere considering before UTF-8 supplanted it.

On Feb 7, 2016, at= 20:09, Bruce Ellis <bruce.ellis= @gmail.com> wrote:

Yes. But the midi version is utf-8.

brucee

On 7 Febru= ary 2016 at 16:42, Skip Tavakkolian <skip.tavakkolian@gmail.com= > wrote:
but foll= owing that line of reasoning, aren't they all specialized versions of Huffma= n encoding?

=
On Sat, Feb 6, 2016 at 6:04 PM B= ruce Ellis <br= uce.ellis@gmail.com> wrote:
Not to burst a balloon but check out variable length ints in t= he Midi File Format for utf-8 in the early 80s.

brucee

= --Apple-Mail-33FDBFEC-37A9-47ED-9FFD-63EE53169A36--