From: 9trouble@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] recent changes on sources
Date: Sat, 14 May 2005 15:05:14 -0400 [thread overview]
Message-ID: <ca281ff8355333aeff18b6a1ac672c76@plan9.bell-labs.com> (raw)
1. <u.h> now includes a definition for uintptr, which we define
to be an integer of the same width as a pointer. Pointers and
uintptrs should be printed using %p.
I believe that the C standard requires that uintptr_t is at least
as wide, but may be wider, than a pointer. We've chosen to be
a little more restrictive in the definition in order to let code be
a little more lax - it can assume that pointers and uintptrs are
pushed on the stack the same, va_arg the same, and so on.
2. <libc.h> now defines Runeerror as 0xFFFD, the new official
Unicode error value. We used to use 0x80, but the rest of the
world standardized on 0xFFFD.
3. All fonts that have a glyph for 0x80 (a question mark in a box)
now use the same glyph for 0xFFFD. For those of you who read
raw UTF8 bytes, get used to seeing "ef bf bd" as Runerror now
instead "c2 80".
4. We have a larger variety of sizes of Japanese bitmap subfonts,
prepared and contributed by the TIP9UG Japanese fonts project.
The subfonts have been added to the standard Unicode fonts as
appropriate. TIP9UG started with BDFs from the efont project.
Thanks to both groups.
- 9trouble
next reply other threads:[~2005-05-14 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 19:05 9trouble [this message]
2005-05-15 3:11 ` boyd, rounin
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=ca281ff8355333aeff18b6a1ac672c76@plan9.bell-labs.com \
--to=9trouble@plan9.bell-labs.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).