From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Subject: Referencing
Date: Wed, 6 Feb 2002 15:38:59 +0100 [thread overview]
Message-ID: <407346723.20020206153859@bigfoot.com> (raw)
Hello,
I start with a small documentation bug:
in core-ref.tex there is a figure whose handle is [three calls]
which is later referenced by [fig:three calls]. This of course
means that the references remains unknown.
While this is (currently) a bug, it gives ground to an interesting
idea, connected to reference prefix: it should be possible to
allow different kind of stuff to have different automatic
prefixes, in such a way that [three calls] would be automatically
prefixed by fig: for a picture, tab: for a table and so on and so
forth (of course, customizable autoprefixes).
Of course, if such a feature is implemented (or even if it is not
implemented, actually) \definereferenceformat should include an
option to automatically add a particular prefix; so, if tab is
the prefix for tables, I could do the following:
=====================================================================
\setupfloat[table][interactionprefix=tab]
\placetable[here][handle]
{Caption}
\starttable
...
\stoptable
As seen in~\in Table[tab:handle], we have such and so.
\definereferenceformat[intable][text=Table,prefix=tab]
As seen in~\intable[handle], we have such and so.
=====================================================================
(hope this is clear).
While we're at it, I'd ask one more thing: how do I extract the
part/chapter/section/subsection/etc number of a reference?
--
Giuseppe "Oblomov" Bilotta
next reply other threads:[~2002-02-06 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 14:38 Giuseppe Bilotta [this message]
2010-01-05 13:46 Referencing Willi Egger
2010-01-05 15:59 ` Referencing Hans Hagen
2011-11-20 17:46 referencing Hans van der Meer
2011-11-20 18:42 ` referencing Wolfgang Schuster
2011-11-20 20:26 ` referencing Meer, H. van der
2011-11-20 20:37 ` referencing Wolfgang Schuster
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=407346723.20020206153859@bigfoot.com \
--to=bourbaki@bigfoot.com \
/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).