Question about internal links

Leo

unread,

Jan 4, 2010, 11:03:41 AM1/4/10

to

Hello,

In pgfmanual.pdf
(http://media.texample.net/pgf/builds/pgfmanualCVS2010-01-03.pdf),
there are a myraid of links to tikz options and commands. I wonder if
those links are done automatically.

I am thinking whether it is possible to produce a list of acronyms
automatically, i.e., instead of writing \gls{GNU}, just GNU.

Thanks.

Leo

Philipp Stephani

unread,

Jan 4, 2010, 1:46:08 PM1/4/10

to

Leo <sdl...@gmail.com> writes:

> I am thinking whether it is possible to produce a list of acronyms
> automatically, i.e., instead of writing \gls{GNU}, just GNU.

XeTeX makes it possible to do things like this, see the xesearch
package.

--
Change “LookInSig” to “tcalveu” to answer by mail.

Robin Fairbairns

unread,

Jan 4, 2010, 3:11:24 PM1/4/10

to

the xesearch package (for xetex, any macro format) does that. i
don't know how. there's also a package xeindex, which uses that
mechanism for producing an index -- not a million miles from what you
want.
--
Robin Fairbairns, Cambridge

Leo

unread,

Jan 5, 2010, 7:46:18 AM1/5/10

to

rf...@cl.cam.ac.uk (Robin Fairbairns) writes:
> the xesearch package (for xetex, any macro format) does that. i
> don't know how. there's also a package xeindex, which uses that
> mechanism for producing an index -- not a million miles from what you
> want.

Philipp Stephani <Look...@arcor.de> writes:

> XeTeX makes it possible to do things like this, see the xesearch
> package.

Thanks. I am aware of those two packages. I have been using pdflatex
throughout the current project so I will look at it again in future
projects.

Any idea how pgf/pgfplots manuals do that? They don't require xetex at
all.

Best,
Leo

Philipp Stephani

unread,

Jan 5, 2010, 8:27:33 AM1/5/10

to

Leo <sdl...@gmail.com> writes:

See the file
http://pgf.cvs.sourceforge.net/viewvc/pgf/pgf/doc/generic/pgf/macros/pgfmanual-en-macros.tex?hideattic=0&view=log
where this is implemented. However, I doubt that it can be generalized
to non-PGF applications, or that it could be made to work the way you
requested. Basically that seems to scan certain environments and the
contents of "short verbatims" (|...|), but not the whole text. If you
want to write |GNU| instead of \gls{GNU}, you can try to use the
shortvrb package or something like the following:

\catcode `\|=\active
\def|#1|{\gls{#1}}

Leo

unread,

Jan 5, 2010, 8:59:26 AM1/5/10

to

Philipp Stephani <Look...@arcor.de> writes:

> See the file
> http://pgf.cvs.sourceforge.net/viewvc/pgf/pgf/doc/generic/pgf/macros/pgfmanual-en-macros.tex?hideattic=0&view=log
> where this is implemented. However, I doubt that it can be generalized
> to non-PGF applications, or that it could be made to work the way you
> requested. Basically that seems to scan certain environments and the
> contents of "short verbatims" (|...|), but not the whole text. If you
> want to write |GNU| instead of \gls{GNU}, you can try to use the
> shortvrb package or something like the following:
>
> \catcode `\|=\active
> \def|#1|{\gls{#1}}

Thanks for this. What they have done in pgfmanual is abolutely
important. Imagine reading the code and seeing an option x=(45:1cm),
you can click x to find out what it is about.

Leo