From: Zachary Kline <kline.zachary@gmail.com>
To: speakup@braille.uwo.ca
Subject: jzip: an alternative to frotz
Date: Thu, 19 Nov 2009 20:16:57 -0800 [thread overview]
Message-ID: <20091120041657.GA18181@blackbird> (raw)
Hi,
In my attempts to find an interactive fiction interpreter which works
well with Speakup, I stumbled upon jzip. This is a bit older than frotz
and isn't maintained, but it supports all the modern interactive
fiction standards with the exception of blorb. I thought of cutting my
teeth in C by trying to integrate Andrew Plotkin's Blorblib with it.
The termcap-based interface is compilable if you link with the ncurses
library. It works quite nicely, and doesn't suffer from the frotz
habbit of repeating old text when the screen fills.
It can be found at the IF archive, in /interpreters-infocom-zcode/zip.
The version I have is from 2000, and unfortunately doesn't respect the
unix convention and extract into its own directory.
I'm not sure how many interactive fiction players are on this list, but
I thought I'd pass this along.
Best and enjoy,
Zack.
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline [this message]
` Jason White
` Tony Baechler
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=20091120041657.GA18181@blackbird \
--to=kline.zachary@gmail.com \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).