From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Go (again) on plan9/arm
Date: Wed, 10 Apr 2013 15:53:46 -0400 [thread overview]
Message-ID: <b5e468dacc2ac9de4ddb8a880051bb9c@ladd.quanstro.net> (raw)
In-Reply-To: <9f71f8d13bf0b8e1fba7e22626b8dbc8@proxima.alt.za>
> We are expecting a release from Bell Labs of Plan 9 with 21-bit runes
> replacing the current 16-bit version. This is big and difficult and
> almost certainly extremely painful, so I doubt it will be completed
> quickly (feel free to surprise me, guys!). I noticed some changes
> being applied today, I think Geoff and Co. are approaching the problem
> circumspectly and, this is my guess, by making adjustments that can be
> kept self-contained. I do wish them speedy success.
i transitioned to 20 bit runes a few years ago, and the process was
really pain-free. Runemax is handy to have instead of just hard-coding
0xffff, and character arrays on the stack are a bit suspicious, since they
often mean UTFmax or UTFmax+1. but most programs are good-to-go
for large runes. notible exceptions that i can think of off the top of my head
are in no order:
- wc
- ed, sed, sort
- rc
- grep (for bursting rune ranges)
these are fixed in 9atom, and not a problem unless you actually use them.
there are a few problems in the libraries, also fixed. mostly in the font code.
there are also tools in 9atom to create new tables for libc in /sys/src/cmd/rune,
including a unicode 6.1 /lib/unicode.
because who doesn't want to grin
; grep grin /lib/unicode
01f600 grinning face
01f601 grinning face with smiling eyes
01f638 grinning cat face with smiling eyes
; ; unicode 01f600 01f601 01f638
😀
😁
😸
- erik
next prev parent reply other threads:[~2013-04-10 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 19:21 lucio
2013-04-10 19:53 ` erik quanstrom [this message]
2013-04-11 5:48 ` lucio
2013-04-10 20:20 ` Bakul Shah
2013-04-10 22:56 ` Skip Tavakkolian
2013-04-11 5:40 ` lucio
2013-04-10 21:31 ` Skip Tavakkolian
2013-04-10 23:53 ` Christopher Nielsen
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=b5e468dacc2ac9de4ddb8a880051bb9c@ladd.quanstro.net \
--to=quanstro@quanstro.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).