Newsgroups: rec.games.int-fiction,rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!newshub2.home.com!news.home.com!howland.erols.net!portc.blue.aol.com.MISMATCH!portc03.blue.aol.com!newsfeed.skycache.com.MISMATCH!newsfeed1.cidera.com!Cidera!news-reader.ntrnet.net!uunet!ash.uu.net!world!buzzard
From: buzzard@world.std.com (Sean T Barrett)
Subject: Re: WinFrotz color bugs
Message-ID: <GI63C5.BA0@world.std.com>
Date: Thu, 16 Aug 2001 15:36:04 GMT
References: <9k2i61$48d$1@cascadia.drizzle.com> <9ldghm$lfu$2@news.lth.se> <GI495D.D56@world.std.com> <9lgbui$dhi$1@news.lth.se>
Organization: The World Public Access UNIX, Brookline, MA
Lines: 14
Xref: news.duke.edu rec.games.int-fiction:64951 rec.arts.int-fiction:91211

In article <9lgbui$dhi$1@news.lth.se>, Magnus Olsson <mol@df.lth.se> wrote:
>Sean T Barrett <buzzard@world.std.com> wrote:
>>I had configured my WinFrotz to use Courier, and had the same problem
>
>OK - this seems to be a problem with Windows rather than with
>WinFrotz.

In some sense, it's a problem not with Windows but with configurability
on the user's side: the user is free to configure things differently
from how the author expected, which means it's easy for the user to
not merely get a different experience than intended, but an objectively
inferior experience than intended. See the Glk stylehints debate...

SeanB
