ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: relative references
Date: Fri, 12 Aug 2011 18:50:10 +0200	[thread overview]
Message-ID: <4E4559C2.7030309@wxs.nl> (raw)
In-Reply-To: <4C7BAA2B-06B6-416D-B692-D39B6CC519CD@gmail.com>

On 12-8-2011 12:45, Ian Lawrence wrote:
> That was very kind of you, and I'd like to buy you a beer, even though your example seemed to be much more complex than mine.
>
> I assume your example ought to run 'out of the box' by just issuing the commend 'context relabs'.
>
> So I did, and what I got for my trouble was the following pdf (OK, so there was more white space, but this was all the content).
>
>
>
>
>
>
>
> There's not much to guide me in the log file ( the only not found was : files>  readfile>  asked name: 'loc', not found), but context (ConTeXt  ver: 2011.08.04 00:42 MKIV  fmt: 2011.8.12  int: english/english) seems not to have found the component text, or the graphic….
>
> So far I have lost days to this…and I'm afraid I'm none the wiser now.
>
> But I do appreciate the effort. Thanks.

maybe running with

\enabletrackers[graphics.locating]

at the top of the file gives some info

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-08-12 16:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 15:55 Ian Lawrence
2011-08-11 16:05 ` Wolfgang Schuster
2011-08-11 17:46   ` Alan Braslau
2011-08-12  5:52     ` Ian Lawrence
2011-08-12  7:25       ` Wolfgang Schuster
2011-08-12 10:45         ` Ian Lawrence
2011-08-12 16:50           ` Hans Hagen [this message]
2011-08-12 18:02           ` Wolfgang Schuster
2011-08-13 21:16             ` Email Lists
2011-08-23 13:37           ` relative references in OSX Lion Ian Lawrence
2011-08-23 14:49             ` Hans Hagen
2011-08-26 12:02               ` Ian Lawrence
2011-08-26 12:14                 ` Hans Hagen
2011-08-26 13:02                 ` Taco Hoekwater
2011-08-26 14:32                   ` Ian Lawrence
2011-08-23 14:55             ` Wolfgang Schuster
2011-09-15  5:54               ` Ian Lawrence
2011-08-12 14:44   ` relative references Hans Hagen
2011-08-11 16:11 ` Mari Voipio

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=4E4559C2.7030309@wxs.nl \
    --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).