From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] bib tool for troff and html conversion revisited
Date: Mon, 17 Dec 2001 09:27:12 +0100 [thread overview]
Message-ID: <20011217082715.6D79B199E8@mail.cse.psu.edu> (raw)
I found a tool that does all the bib stuff for me, including
formatting. Besides I made a silly html converter (see below).
I just got the source code of a bibliography tool
for troff called bib and used ape to get it working.
It can be found at http://plan9.escet.urjc.es/export/troffbib.tgz
The format of the bib files is quite straightforward (not like bibtex)
and the syntax for citations is easy to remember (and you don't have
to remember identifiers to make a citation).
I also wanted to get the paper converted to html without human
intervention, so I tried both ms2html and troff2html. The
troff2html output
did not convince me (problems w/ .IP, etc.),
and ms2html couldn't handle bib entries (which are not ms macros)
Thus I did the following as an experiment:
- changed ms2html to accept pseudo device control strings to be
passed as-is to the output.
- used sam to make silly scripts bib2html tbl2html etc. that
replace the involved portions of input with html.
I think the output is reasonable given the kludges I made in
these *2html scripts.
As an example, this is the mkfile rule I use:
box.html: box.ms
bib box.ms | fig | bib2html | pic2html | tbl2html |
ms2html > box.html
IMHO the experient result says that this can work
nicely; i.e. same nice output of ms2html but still able to
format non-ms troff packages. What about going in this direction
instead of improving troff2html to handle it all on its own?
I mean, such intermediate blah2html filters can translate macros or
whatever weird troff construction be used in the source,
when the input model can still be matched to the html one.
Although my set of scripts would probably fail if the document does
not follow the conventions I follow, I placed them at
http://plan9.escet.urjc.es/export/troffutil.tgz, just
to illustrate what I mean.
next reply other threads:[~2001-12-17 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 8:27 Fco.J.Ballesteros [this message]
2001-12-17 12:27 ` Ralph Corderoy
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=20011217082715.6D79B199E8@mail.cse.psu.edu \
--to=nemo@plan9.escet.urjc.es \
--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).