From: Brian Hurt <bhurt@spnz.org>
To: Matt Gushee <matt@gushee.net>
Cc: <caml-list@pauillac.inria.fr>
Subject: Re: [Caml-list] Multi-keyed lookup table?
Date: Fri, 8 Aug 2003 17:13:18 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0308081708240.2616-100000@eagle.ancor.com> (raw)
In-Reply-To: <20030808213037.GA21525@swordfish>
On Fri, 8 Aug 2003, Matt Gushee wrote:
> On Thu, Aug 07, 2003 at 03:16:49PM -0500, Brian Hurt wrote:
> >
> > In the general case, this is hard. In this specific case, you might
> > consider just hard coding your levels. So you'd end up with a data
> > structure like:
> >
> > All font
> > / | \
> > / | \
> > medium bold light <-- pick the weight
> > / | \
> > [ ..... ]
>
> Interesting idea, and not one that I had considered at all. It seems
> quite efficient, too. On the other hand, it looks like the fixed search
> path would make it rather hard to implement fallback rules in case an
> exact match isn't found. It seems to me that that's fairly important for
> fonts: there are many situations where it is preferable to produce some
> output with some fonts not quite right rather than producing nothing.
You certainly can handle * rules by just concatenating results from the
different children. You could also do something like:
match weight with
"medium" ->
let t = get_style tree.medium ... in
match t with
_ :: _ -> (* we have at least one font *) t
| [] ->
(* try getting something in bold *)
let t = get_style tree.bold in
...
Brian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-08-08 22:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 19:41 Matt Gushee
2003-08-07 20:16 ` Brian Hurt
2003-08-07 21:49 ` Yaron Minsky
2003-08-07 22:26 ` John Max Skaller
[not found] ` <D4DBD8568F05D511A1C20002A55C008C11AC05E6@uswaumsx03medge.med.ge.com>
2003-08-08 21:30 ` Matt Gushee
2003-08-08 22:13 ` Brian Hurt [this message]
[not found] ` <005d01c35e51$7c927200$6628f9c1@zofo>
2003-08-09 16:57 ` [Caml-list] Array.filter (was Multi-keyed lookup table?) Matt Gushee
2003-08-09 18:48 ` ijtrotts
2003-08-10 19:53 ` Michal Moskal
2003-08-10 2:34 ` ijtrotts
2003-08-11 5:48 ` David Brown
2003-08-10 18:53 ` ijtrotts
2003-08-10 20:23 ` Marcin 'Qrczak' Kowalczyk
2003-08-10 2:37 ` ijtrotts
[not found] ` <200308102222.16369.qrczak@knm.org.pl>
2003-08-10 20:43 ` Michal Moskal
2003-08-10 21:59 ` Ville-Pertti Keinonen
2003-08-10 20:55 ` [Caml-list] Array.filter Jean-Baptiste Rouquier
2003-08-11 9:46 ` Michal Moskal
2003-08-10 22:29 ` [Caml-list] Array.filter (was Multi-keyed lookup table?) Shawn Wagner
2003-08-11 11:51 ` [Caml-list] Multi-keyed lookup table? Remi Vanicat
2003-08-07 22:19 ` John Max Skaller
2003-08-12 6:34 ` Florian Hars
2003-08-12 9:58 ` Michael Wohlwend
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=Pine.LNX.4.33.0308081708240.2616-100000@eagle.ancor.com \
--to=bhurt@spnz.org \
--cc=caml-list@pauillac.inria.fr \
--cc=matt@gushee.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