From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re: pending issues
Date: Thu, 4 Oct 2001 18:05:40 +0200 [thread overview]
Message-ID: <68122971.20011004180540@bigfoot.com> (raw)
In-Reply-To: <5.1.0.14.1.20011001181218.02337210@pop.planet.nl>
[-- Attachment #1: Type: text/plain, Size: 2751 bytes --]
Monday, October 01, 2001 Hans Hagen wrote:
HH> Hi,
HH> I want to make a list of pending issues, if you have the feeling that
HH> something got lost in my mailbox, let me know,
My personal list, not necessarily in priority order:
TEX
((1)) "small" database support in TeXUtil: ability to sort with
multiple keys, in ascending and descending order. And to
sort the same data multiple times, having the results of all
the sortings available (so that you can have e.g. a list of
the data sorted by, say, name, and a list of the same data
sorted, say, by content). I noticed there is already a
database support in TeX provided by the module core-dat. Am
I wasting my time with the xdesc module? Or will xdesc make
core-dat obsolete?
((2)) \defineitemize
((3)) Nine levels for itemizations (I need this for WordPerfect
compatibility
((4)) Inline itemization: (a) like (b) this (c) more or less (I
know it's there in the core ...
((5)) A way to get the (internal) number of a reference, so that i
can be used by TeX (without it being typeset).
((6)) Pseudo-floats: things that are of the same class as real
floats, have captions, are numbered along with the real
floats, but *do* *no* *move* and can (possibly) be split
(e.g. tables etc).
((7)) Subfloats: this was partly done by a recent patch, but it
needs some additions, mostly the possibility to reference each
subfloat separately.
((8)) The footnote bug: footnote ending on the wrong page when
footnote reference is at bottom of the page. (See attached
footbug2.tex; note that the bug appears both when there is a
footnote in the columns (pages 1--2) and when there is no
other footnote (pages 3--4))
IIRC you mentioned at EuroTeX that you already have a fix
for this, but that such fix would break something else in
certain cases. Is it possible to let this fix be "triggable"?
(You choose when to apply it and when not to)
((9)) Threaded documents: I missed that at EuroTeX, so at least
the explanation of the ConTeXt interface to PDF threads
would be greatly welcome :-)
((10)) Abbreviation: some abbreviations are better in small caps,
some are better in normal style. A way to selectively set
this?
META
((1)) MetaFun/ConTeXt interface to MetaObject
((2)) Finer grid in charts.
((3)) Interface limit:
connection_smooth_size := \@@FLOLstraal ;
connection_arrow_size := \@@FLOLstraal ;
connection_dash_size := \@@FLOLstraal ;
(in \dodogetFLOWchart) don't allow for fine-tuning
of the settings. (Should have different options for different
sizes.)
--
Giuseppe "Oblomov" Bilotta
[-- Attachment #2: footbug2.tex --]
[-- Type: application/octet-stream, Size: 678 bytes --]
\setupindenting[medium]
\starttext
\input knuth
\blank
\input zapf
\blank
\startcolumns
\input tufte\footnote{This was a text from Tufte. Let's now get
this footnote a little longer, so as to trigger the second bug. We
need at least two lines, maybe three of four\dots}
\stopcolumns
\blank
\input tufte\footnote{\input zapf }
\blank
\input knuth
\page[yes]
\input knuth
\blank
\input zapf
\blank
\startcolumns
\input tufte
\stopcolumns
\blank
You don't need another footnote to trigger the bug: just
enough text to push the last line of the problematic
paragraph to the end of the page.
\input tufte\footnote{\input zapf }
\blank
\input knuth
\stoptext
next prev parent reply other threads:[~2001-10-04 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 16:13 Hans Hagen
2001-10-04 16:05 ` Giuseppe Bilotta [this message]
2001-10-05 8:27 ` Wishlist (Re: pending issues) Taco Hoekwater
2001-10-04 19:41 ` pending issues Willi Egger
2001-10-04 20:31 ` Frans Goddijn
2001-10-05 6:35 ` Berend de Boer
2001-10-05 7:40 ` Taco Hoekwater
2001-10-05 9:27 ` Dan Seracu
2001-10-02 12:30 Patrick Gundlach
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=68122971.20011004180540@bigfoot.com \
--to=bourbaki@bigfoot.com \
--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).