ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: [NTG-context] figure libs
Date: Wed, 16 Oct 2002 17:43:23 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20021016173935.03419640@server-1> (raw)
In-Reply-To: <20021016154448.48d59fe3.morawski@gmx.net>

At 03:44 PM 10/16/2002 +0200, Jens-Uwe Morawski wrote:
>On Wed, 16 Oct 2002 13:30:19 +0200
>Hans Hagen <pragma@wxs.nl> wrote:
>
> > At 11:31 AM 10/16/2002 +0200, Jens-Uwe Morawski wrote:
> >
> > >i have some questions about figure libs:
> > >
> > >1) i can only access figures from a figure-lib if the
> > >    file is in the same directory as the document that
> > >    should embed the figures.
> > >    For documents in different variants (screen, print)
> > >    i would prefer that i can have the figure lib in the
> > >    parent directory.
> >
> > \setupexternalfigures[directory={...,...,...}]
>
>Hmm, since ConTeXt is so good in finding components and
>environments i thought that finding figures should not
>that problem. Setting up a specific directory is not
>a solution if different authors (with different directory
>structure) work on the same document.

hm, actually it's practice here, in order to prevent duplicates, how is 
your directory structure for this doc?

> > >2) is the XML-file that describes the figure-lib really
> > >    required to access the figures in the figure-lib:
> >
> > yes, since it determines the page to pick up; of course you can also 
> direct
> > the page directly using
> >
> > \externalfigure[somefile.pdf][page=3]
> >
> > >/Subtype /Link /Border [0 0 0] /A <</S /GoTo /D (about: fig-one)>>
> >
> > it could be done if pdftex supported access to named pages; parsing the
> > file using tex macros is not doable (well, partially, but a pain for 500
> > meg files)
>
>I thought that the parsing could be done with TeXUtil (Perl). Is there
>no Perl-Module (maybe a wrapper for pdflib by Thomas Merz) that allows
>efficient parsing? But, I see that this way still consumes too much
>time (for a 500M file). Thus, having the xml-file in place sounds
>like the better solution.

next versions of context will also provide you a mechanism for generating 
the library

> > PS. The fig lib mechanism will be replaced (extended) by a more versatile
> > resource library system (working on that now)
>
>Can you give some examples what enhanced functionality is available
>then, please.

- labeling, language or application dependent
- alternatives, like graphics, placeholders, applets, videos, depending on 
the kind of doc instance
- more associated data
- clipping, manipulation, etc
- slide show features

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                        information: http://www.pragma-ade.com/roadmap.pdf
                     documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------

_______________________________________________
ntg-context mailing list
ntg-context@ref.ntg.nl
http://ref.ntg.nl/mailman/listinfo/ntg-context


  reply	other threads:[~2002-10-16 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  9:31 Jens-Uwe Morawski
2002-10-16 11:30 ` Hans Hagen
2002-10-16 13:44   ` Jens-Uwe Morawski
2002-10-16 15:43     ` Hans Hagen [this message]
2002-10-16 19:55       ` Jens-Uwe Morawski
2002-10-16 13:55   ` Bruce D'Arcus

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=5.1.0.14.1.20021016173935.03419640@server-1 \
    --to=pragma@wxs.nl \
    --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).