Hey folks, I'm not sure where to be looking, as this may well be a feature already implemented in ConTeXt or its lower level dependencies. I couldn't find anything in the mailing archives, nor in the reference manual or wiki. In my PDF viewer Evince, I have a navigation tree in the side bar that allows me quick access to various parts of some PDF documents. When I was using Texinfo, this was generated automatically for each @chapter / @section / @subsection / etc when the PDF was being written out. I noticed this doesn't appear to happen automatically with ConTeXt. How does one go about doing the same in ConTeXt? -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
Hey folks,
I'm not sure where to be looking, as this may well be a feature already implemented in ConTeXt or its lower level dependencies. I couldn't find anything in the mailing archives, nor in the reference manual or wiki.
In my PDF viewer Evince, I have a navigation tree in the side bar that allows me quick access to various parts of some PDF documents. When I was using Texinfo, this was generated automatically for each @chapter / @section / @subsection / etc when the PDF was being written out. I noticed this doesn't appear to happen automatically with ConTeXt.
How does one go about doing the same in ConTeXt?
On Thu, Jun 16, 2011 at 1:51 AM, Kip Warner
luigi scarso
pdfbookmarks ? http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers
Hey Luigi. The sample code in the link you gave me works fine if I compile it. If I put it in my own book, should the adjusted code be in the environment, project, or product file? I have only one project / product. Kip
Am 18.06.2011 um 03:43 schrieb Kip Warner:
luigi scarso
writes: pdfbookmarks ? http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers
Hey Luigi. The sample code in the link you gave me works fine if I compile it. If I put it in my own book, should the adjusted code be in the environment, project, or product file? I have only one project / product.
When you use a environment file put all setups in it. When you have only one product you don’t need a project file because you can load the environment file from the product and component files. Wolfgang
On Sat, 2011-06-18 at 06:18 +0200, Wolfgang Schuster wrote:
When you use a environment file put all setups in it. When you have only one product you dont need a project file because you can load the environment file from the product and component files.
Wolfgang
Thanks Wolfgang. For some reason, and I have absolutely no idea why, the index is showing today and I can't recall what I had changed. Oh well, as Scotty said, if it ain't broke, don't fix it. I'll also merge the project / product files together into one as you suggested. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
Kip Warner wrote:
Hey folks,
I'm not sure where to be looking, as this may well be a feature already implemented in ConTeXt or its lower level dependencies. I couldn't find anything in the mailing archives, nor in the reference manual or wiki.
In my PDF viewer Evince, I have a navigation tree in the side bar that allows me quick access to various parts of some PDF documents. When I was using Texinfo, this was generated automatically for each @chapter / @section / @subsection / etc when the PDF was being written out. I noticed this doesn't appear to happen automatically with ConTeXt.
How does one go about doing the same in ConTeXt?
Try \setupinteraction[state=start].
participants (4)
-
Kip Warner -
luigi scarso -
Wolfgang Schuster -
Yury G. Kudryashov