9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] utf-8
Date: Mon,  8 Feb 2016 08:48:08 -0500	[thread overview]
Message-ID: <101A317B-5084-4623-B211-496404B04D64@9srv.net> (raw)
In-Reply-To: <CAJQxxwmoe3GethfWs=OZe8B65i-NqPaPQSM6NOOnhWpJ9uVp6g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

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

I'm less sure here, but I believe the MIDI version is more similar to the thing the X/Open folks were 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 February 2016 at 16:42, Skip Tavakkolian <skip.tavakkolian@gmail.com> 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 <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
> 

[-- Attachment #2: Type: text/html, Size: 1890 bytes --]

      reply	other threads:[~2016-02-08 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07  2:04 Bruce Ellis
2016-02-07  5:42 ` Skip Tavakkolian
2016-02-08  1:09   ` Bruce Ellis
2016-02-08 13:48     ` Anthony Sorace [this message]

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=101A317B-5084-4623-B211-496404B04D64@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    /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.
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 NNTP newsgroup(s).