ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Stefan Wachter <stefan.wachter@gmx.de>
Subject: REALLY STRANGE: (was: Is there a bug during pagination of external figures?)
Date: Mon, 16 Aug 2004 22:29:29 +0200	[thread overview]
Message-ID: <41211929.8050806@gmx.de> (raw)
In-Reply-To: <m2zn4vrtnq.fsf@levana.de>

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

Hi Patrick,

you are right. If I change the header text such that there is no 
underbar in there then the error disappears.

I prunned the example to investigate the situation further. Now I have 
only two pages. If you "texexec" the file then you get the error. If you 
uncomment the \page command at the end then the error disappears.

BUT NOW THE SITUATION REALLY BECOMES STRANGE!

If you delete all *.png files except the one that is included by the 
\externalfigure command then the error also disappears! It seems that 
the behaviour of Context is influenced by the content of the directory!


--Stefan

[-- Attachment #2: extfig_problem.tgz --]
[-- Type: application/x-gtar, Size: 150403 bytes --]

[-- Attachment #3: Type: text/plain, Size: 139 bytes --]

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

  reply	other threads:[~2004-08-16 20:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06  7:38 Is there a bug during pagination of external figures? Stefan Wachter
2004-08-06  7:30 ` Hans Hagen
2004-08-06 13:06   ` Stefan Wachter
2004-08-06 13:12   ` Stefan Wachter
2004-08-06 12:55     ` Hans Hagen
2004-08-09 19:58     ` Hans Hagen
2004-08-13  8:30       ` Stefan Wachter
2004-08-13 14:57         ` Patrick Gundlach
2004-08-16 15:53           ` Stefan Wachter
2004-08-16 15:26             ` Patrick Gundlach
2004-08-16 20:29               ` Stefan Wachter [this message]
2004-08-18  9:50                 ` error with _ in header? Patrick Gundlach
2004-08-18 11:24                   ` Eros Albertazzi
2004-08-18 14:19                     ` Hans Hagen
2004-08-18 12:23                   ` Stefan Wachter
2004-08-18 11:43                     ` Patrick Gundlach
2004-08-18 14:59                   ` Hans Hagen
2004-08-18 18:10                     ` Patrick Gundlach
2004-08-19  8:49                       ` Hans Hagen
2004-08-19 10:51                         ` Patrick Gundlach
2004-08-19 15:08                         ` Stefan Wachter
2004-08-19 14:40                           ` Hans Hagen
2004-08-19 14:40                           ` Hans Hagen
2004-08-16 21:28               ` Re: Is there a bug during pagination of external figures? Hans Hagen
2004-08-19  9:19                 ` Stefan Wachter
2004-08-19  9:07                   ` Hans Hagen
2004-08-19 15:50                     ` Stefan Wachter
2004-08-19 16:33                       ` Hans Hagen
2004-08-16 11:27         ` metafun question Floris van Manen
2004-08-16 13:46           ` Hans Hagen
2004-08-16 11:41         ` metafun question getting XY Floris van Manen
2004-08-16 13:45           ` Hans Hagen

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=41211929.8050806@gmx.de \
    --to=stefan.wachter@gmx.de \
    --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).