From: "Holger Schöner" <hfsch@cs.tu-berlin.de>
Subject: Re: Re: listings.sty
Date: Mon, 28 Jun 2004 10:39:06 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0406281025410.3597@dunedain.cs.tu-berlin.de> (raw)
In-Reply-To: <40DFD0D9.4030801@wxs.nl>
Hello,
> >>I suggested to the author of the very feature rich LaTeX-Listings package,
> >>Carsten Heinz, to port this package to ConTeXt, and it seems, that he is
> >>interested. But before doing it, there are some questions:
> >>
> >>* What do Hans and other people thing about that?
> >>
> what is listings.sty providing?
listings.sty is one of the very few packages from LaTeX, which I am still
missing in ConTeXt. I yet never extensively used the listings functionality
provided by ConTeXt, but from what I remember from reading the
documentation, the liststings.sty is much more flexible.
It has an easy interface to define new languages (like Opal, a functional
programming language used in courses at my university), allows flexible line
numbering (all, every n lines), it allows customization of all fonts (line
numbers, keywords, comments, ...), indenting, ...
Most importantly for me: It allows easy escaping to TeX. One option is to
interpret all comments as (La)TeX code. This was very useful for typesetting
correctness proofs of programs using the Hoare Calculus, because it makes
such listings much more readable. Then there are other niceties already
provided by ConTeXt, like frames, floats, etc.
Oh, one other nice thing is, that it allows to use proportional fonts (is
that the right translation? I mean non-fixed width fonts), and still can
keep indentations correctly, e.g. with assignments like
alongvariable = 1;
short = 2;
I think the algorithm is described a little in the documentation. As far as
I remember, it assumes a (configurable) average character width of
proportional fonts and typesets every word in a box of the width
corresponding to the number of characters included in the word.
These were at least the features most important to me ...
--
Holger F. Schoener TU Berlin; Dept. IV: EE and Computer Science
hfsch@cs.tu-berlin.de http://www.cs.tu-berlin.de/~hfsch/
Rooms FR2525 Tel: +49-30-314-73115, Fax: -73121
Office FR 2-1 Franklinstr. 28/29, D-10587 Berlin, Germany
next prev parent reply other threads:[~2004-06-28 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 17:23 listings.sty Peter Münster
2004-06-28 7:38 ` listings.sty Patrick Gundlach
2004-06-28 8:03 ` listings.sty Hans Hagen
2004-06-28 8:18 ` Morten Høgholm
2004-06-28 8:39 ` Holger Schöner [this message]
2004-06-28 9:26 ` Peter Münster
2004-06-28 14:39 ` Hans Hagen
2004-06-28 17:46 ` Peter Münster
2004-06-28 21:51 ` Nikolai Weibull
2004-07-10 9:44 ` Peter Münster
2008-07-10 0:27 ` listings.sty Mohamed Bana
2008-07-10 12:29 ` listings.sty Aditya Mahajan
2008-07-10 18:26 ` listings.sty nico
2008-07-10 20:34 ` listings.sty Mohamed Bana
2008-07-10 22:02 ` listings.sty Aditya Mahajan
2008-07-10 21:31 ` listings.sty Hans Hagen
2008-07-11 21:51 ` listings.sty Mohamed Bana
2008-07-11 22:53 ` listings.sty Hans Hagen
2008-07-11 22:54 ` listings.sty Aditya Mahajan
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.58.0406281025410.3597@dunedain.cs.tu-berlin.de \
--to=hfsch@cs.tu-berlin.de \
--cc=ntg-context@ntg.nl \
/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).