From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Sun, 7 Feb 2016 13:04:11 +1100 Message-ID: From: Bruce Ellis To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114a10921ebaae052b2480a8 Subject: [9fans] utf-8 Topicbox-Message-UUID: 836988bc-ead9-11e9-9d60-3106f5b1d025 --001a114a10921ebaae052b2480a8 Content-Type: text/plain; charset=UTF-8 Not to burst a balloon but check out variable length ints in the Midi File Format for utf-8 in the early 80s. brucee --001a114a10921ebaae052b2480a8 Content-Type: text/html; charset=UTF-8
Not to burst a balloon but check out variable length ints in the Midi File Format for utf-8 in the early 80s.

brucee
--001a114a10921ebaae052b2480a8-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Skip Tavakkolian Date: Sun, 7 Feb 2016 05:42:23 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114336b0070a86052b278d53 Subject: Re: [9fans] utf-8 Topicbox-Message-UUID: 836db090-ead9-11e9-9d60-3106f5b1d025 --001a114336b0070a86052b278d53 Content-Type: text/plain; charset=UTF-8 but following that line of reasoning, aren't they all specialized versions of Huffman encoding? On Sat, Feb 6, 2016 at 6:04 PM Bruce Ellis wrote: > Not to burst a balloon but check out variable length ints in the Midi File > Format for utf-8 in the early 80s. > > brucee > --001a114336b0070a86052b278d53 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
but following that line of reasoning, aren't they all = specialized versions of Huffman encoding?


On Sat, Feb 6, 2016 at 6:04 PM Bruce Ell= is <bruce.ellis@gmail.com&g= t; wrote:
Not to b= urst a balloon but check out variable length ints in the Midi File Format f= or utf-8 in the early 80s.

brucee
--001a114336b0070a86052b278d53-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 8 Feb 2016 12:09:58 +1100 Message-ID: From: Bruce Ellis To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7beb9abc09345e052b37dcaf Subject: Re: [9fans] utf-8 Topicbox-Message-UUID: 83a7307c-ead9-11e9-9d60-3106f5b1d025 --047d7beb9abc09345e052b37dcaf Content-Type: text/plain; charset=UTF-8 Yes. But the midi version is utf-8. brucee On 7 February 2016 at 16:42, Skip Tavakkolian wrote: > but following that line of reasoning, aren't they all specialized versions > of Huffman encoding? > > > On Sat, Feb 6, 2016 at 6:04 PM Bruce Ellis wrote: > >> Not to burst a balloon but check out variable length ints in the Midi >> File Format for utf-8 in the early 80s. >> >> brucee >> > --047d7beb9abc09345e052b37dcaf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes. But the midi version is utf-8.

bru= cee

On= 7 February 2016 at 16:42, Skip Tavakkolian <skip.tavakkolian@g= mail.com> wrote:
but following that line of reasoning, aren't they all speciali= zed versions of Huffman encoding?


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

brucee

--047d7beb9abc09345e052b37dcaf-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Sorace Content-Type: multipart/alternative; boundary=Apple-Mail-33FDBFEC-37A9-47ED-9FFD-63EE53169A36 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Message-Id: <101A317B-5084-4623-B211-496404B04D64@9srv.net> Date: Mon, 8 Feb 2016 08:48:08 -0500 References: In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] utf-8 Topicbox-Message-UUID: 83b45e1e-ead9-11e9-9d60-3106f5b1d025 --Apple-Mail-33FDBFEC-37A9-47ED-9FFD-63EE53169A36 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable It isn't. MIDI variable-length quantities don't include an indication of len= gth in a header, and the last byte in any multi-byte sequence is a valid sin= gle-byte value. It is more bit efficient than UTF-8, but I believe it lacks o= ther properties around synchronization, possibly others. I'm less sure here, but I believe the MIDI version is more similar to the th= ing the X/Open folks were considering before UTF-8 supplanted it. > On Feb 7, 2016, at 20:09, Bruce Ellis wrote: >=20 > Yes. But the midi version is utf-8. >=20 > brucee >=20 >> On 7 February 2016 at 16:42, Skip Tavakkolian wrote: >> but following that line of reasoning, aren't they all specialized version= s of Huffman encoding? >>=20 >>=20 >>> On Sat, Feb 6, 2016 at 6:04 PM Bruce Ellis 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--