From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Font behaviour
Date: Thu, 7 Feb 2002 09:56:07 +0000 [thread overview]
Message-ID: <3C61DB56.5BF1FFD7@null.net> (raw)
In-Reply-To: <3C6129B5.E0FBCEFA@strakt.com>
Boyd Roberts wrote:
> rob pike wrote:
> > Platitudes are fine in their place ...
I was just trying to raise the level of awareness about the
meta-issue: any in-band value that might have a valid normal
meaning should not be usurped for any special purpose. This
is not just about one font package, but applies to a large
number of legacy interfaces. With hindsight gained from
experience, we should strive not to do this in new designs.
Then the future will be somewhat more pleasant.
> I think the pjw solution is actually quite elegant.
It addresses one issue, namely missing code points, but not
the other, namely genuine 0-width characters (which for some
strange reason all look alike).
next prev parent reply other threads:[~2002-02-07 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 12:53 rob pike
2002-02-06 13:03 ` Boyd Roberts
2002-02-07 9:56 ` Douglas A. Gwyn [this message]
2002-02-07 10:43 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-02-08 1:06 okamoto
2002-02-08 9:58 ` Douglas A. Gwyn
2002-02-06 12:16 rob pike
2002-02-05 17:22 rob pike
2002-02-06 9:33 ` Douglas A. Gwyn
2002-02-06 10:52 ` Boyd Roberts
2002-02-05 16:39 Graham Gallagher
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=3C61DB56.5BF1FFD7@null.net \
--to=dagwyn@null.net \
--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).