From: Mark Smith <mark@bbprojects.net>
Subject: Re: xecontext/bibtex issue ?
Date: Fri, 11 Mar 2005 15:53:05 +0100 [thread overview]
Message-ID: <r02010500-1038-46C33CB0923D11D9A2B2001124759EE4@[10.0.1.4]> (raw)
In-Reply-To: <20050311141053.23203@mail.comp.lancs.ac.uk>
Adam Lindsay wrote:
>Mark Smith said this at Fri, 11 Mar 2005 14:56:06 +0100:
>
>>The problem is that bibtex "can't read" the .aux file that is generated
>>by xextex.
>
>Okay, can we see a copy (or reduction) of that file, then?
Hmm... Interesting. In preparing a short and highly sanitized file *with* citations, I find that the problem no longer exists. Jumped the gun with the assumption about bibtex.
I have three files. They all started out as LaTeX articles. Each could be processed w/o problems:
latex
bibtex
latex
latex
I then made the necessary modifications to generate a ConTeXt version of each file and:
context
bibtex
context
also ran w/o problems.
However, with the minimum necessary modifications to the preamble:
"xecontext"
...would stop after generating the xdv and bibtex would not read the .aux.
I found that removing all of the paragraphs and elements containing citations enabled all three files to be processed to pdf via xetex.
Now, having made a sanitized and very short version of one of the three files, but leaving a small number of citations in place, I find that:
xecontext
bibtex
xecontext
...runs fine as expected.
I've got my work cut out to find the problem. Any tips about what I might look for ?
Could it be associated with particular environments or characters ?
wt[and apologies]ia,
mark.
next prev parent reply other threads:[~2005-03-11 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 13:56 Mark Smith
2005-03-11 14:10 ` Adam Lindsay
2005-03-11 14:53 ` Mark Smith [this message]
2005-03-11 15:43 ` Mark Smith
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='r02010500-1038-46C33CB0923D11D9A2B2001124759EE4@[10.0.1.4]' \
--to=mark@bbprojects.net \
--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).