9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anselm R. Garbe" <garbeam@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: 9base ports to unix (flame of byron's rc)
Date: Sat, 20 Aug 2005 23:45:49 +0200	[thread overview]
Message-ID: <89d1e7b80508201445723c982e@mail.gmail.com> (raw)
In-Reply-To: <W7291019248189101124572993@webmail2>

On 8/20/05, quanstro@speakeasy.net <quanstro@speakeasy.net> wrote:
> well the gentoo folks should have consulted you before deciding
> to name their init script /sbin/rc. see this bug for some humor:
> http://bugs.gentoo.org/show_bug.cgi?id=45183

Fun :)

> you've also got to realize that in 1990 linus and tannenbaum were still
> duking it out. nobody had any idea that plan9 stuff would actually be
> available to the public. byron's rc would not have been written if
> that had been the case.

Sure.

> > Anymore? Which *NIX tool did ever support unicode? I know of none,
> > even today there's no Unix tool which really supports UTF8. Those UTF8
> > locales in Linux are a joke, and these Mozilla workaround are just
> > insane.
> 
> many unix tools do pretty well with utf-8 (thank's rob, ken. excellent design.)
> do-nothing gets you a long way towards utf-8 support.
> 
> obviously, explicitly single-character-based stuff breaks. but i've been using
> utf-8 for years without any serious problems. sam and 9term have managed
> when other tools (e.g. vi, xterm) were confused.
> 
> in fact, gnu's utf-8 "support" has made things quite a bit worse. unless it's
> been fixed in the last month grep on a fixed ascii string in ascii text is about
> 100x slower in a utf-8 locale because wctomb() is called on each character.

I referred more to the GNU stuff and non-plan9ish tools which
introduced locales instead... but well, there haven't been much tools
except the plan9ish ones which supported utf8 in the 90s already. And
as stated what I've seen so far in the Unix world are many different
approaches which never work well - I investigated some time into the
X11 crap to get UTF8 working, but with very emberassing results (even
public available libraries like libcairo are crashing when processing
UTF8 strings for odd reasons)... there might be hope that this will
change. But I personally consider using libutf9 from plan9 and
libregexp instead of hoping... 9term and sam did similiar
(libXg/libtext dependencies which solved UTF8 very early).

> the grammar was publised in duff's original paper. the "similarities"
> were all based on reading the paper. i don't think you understand how
> restrictive AT&T licensing was at the time.

Ok, that explains the comments especially in the yacc file.

Thanks so far,
-- 
  Anselm R. Garbe  ><><  www.ebrag.de  ><><  GPG key: 0D73F361


  reply	other threads:[~2005-08-20 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20 21:23 quanstro
2005-08-20 21:45 ` Anselm R. Garbe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-20 15:25 quanstro
2005-08-20 17:49 ` Anselm R. Garbe
2005-08-20 21:07   ` Axel Belinfante

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=89d1e7b80508201445723c982e@mail.gmail.com \
    --to=garbeam@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).