From: "rob pike, esq." <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: [9fans] faces
Date: Tue, 2 Sep 2003 10:20:22 -0700 [thread overview]
Message-ID: <c93f7b7a1c3262fa2d86e62c64376435@mightycheese.com> (raw)
the need for multiple resolutions of faces disappeared with the last
gnot. the facebase should be collapsed into a single
resolution-independent hierarchy. the faces program can handle any
resolution; just put all the resolutions in one directory and use
.dict to choose which one to show.
as for personal versions, i see two solutions. one is to use binding,
which would be easier if the hierarchy were collapsed. the other is
to use a pair of .dict files and search the personal one first. in
the collapsed scheme, there is only one .dict file. faces could
easily be modified to take an argument specifying a .dict file to use
first, and fall to the official one if no match is found. finally,
all the names in .dict are relative. easy change: make it understand
absolute names, which would make personal .dict files easier to write.
-rob
next reply other threads:[~2003-09-02 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 17:20 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-06 22:08 Steve Simon
2010-01-07 0:40 ` blstuart
2010-01-07 2:33 ` Akshat Kumar
2010-01-07 3:03 ` blstuart
2010-01-07 13:33 ` matt
2010-01-08 3:59 ` blstuart
2010-01-08 5:39 ` Jeff Sickel
2010-01-08 14:54 ` Patrick Kelly
2010-01-06 19:42 Steve Simon
2003-08-28 3:45 bm
2003-08-28 3:49 ` bm
2003-08-21 4:38 zer0dB
2003-08-21 4:44 ` zer0dB
2003-08-21 13:03 ` boyd, rounin
2003-07-23 2:19 [9fans] Faces Kris Van Hees
2003-07-23 3:03 ` andrey mirtchovski
2001-07-13 9:15 [9fans] faces nemo
2001-07-13 9:56 ` Boyd Roberts
2001-07-11 15:31 nemo
2001-07-11 15:10 bwc
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=c93f7b7a1c3262fa2d86e62c64376435@mightycheese.com \
--to=rob@mightycheese.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).