From: Andreas Schneider <aksdb@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Validate (cross)references
Date: Fri, 27 May 2011 17:19:30 +0200 [thread overview]
Message-ID: <1213928373.20110527171930@gmx.de> (raw)
In-Reply-To: <9969F0B4-6FAD-43E7-B58F-6923425027B6@googlemail.com>
On Friday, May 27, 2011 17:09 Wolfgang Schuster wrote:
> Am 27.05.2011 um 17:04 schrieb Andreas Schneider:
>> Hello,
>>
>> if I use \in, \about, \at or anything else that generates a
>> cross-reference, and that reference happens to be invalid (typo or
>> whatever), it just prints out "nothing". Is there a way to have
>> context throw an error if a reference is invalid? (That probably would
>> only make sense in the second pass of context, since the first pass
>> has to collect the references first.)
> Unknown references are shown as “??” in your text.
> Wolfgang
True, I was mostly thinking about "\about", which just prints two
quotation marks and nothing in between. But my "problem" (if I can
even call it that, since grep is already a solution, just maybe not
the best one :D) is, that I could easily miss such small changes. I'm
working on technical documentation that even has parts that are
automatically generated (from XML files). I just update whatever is
necessary (the document itself, or just the input files), commit them
to SVN and our CI server grabs them, and runs ConTeXt. If ConTeXt
returns with a return code > 0, the build is marked as "failed" and
all necessary admins (me and my colleague) are informed via eMail
and/or RSS feed. If the build succeeds, the generated PDF is
automatically distributed to the users. I consider wrong references an
error, so I would like the build to fail (imho referencing something
that doesn't exist is like using a macro that doesn't exist, which
fails too).
But as I said: if context can't treat that as error, I'm fine with it
too and will continue to grep the logfile. It's just curiosity if
there may already be a setting/parameter/whatever to get context to be
more "restrictive".
--
Best Regards,
Andreas
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-27 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 15:04 Andreas Schneider
2011-05-27 15:09 ` Wolfgang Schuster
2011-05-27 15:19 ` Andreas Schneider [this message]
2011-05-27 16:58 ` Jesse Alama
2011-05-27 17:50 ` Aditya Mahajan
2011-05-27 18:03 ` Taco Hoekwater
2011-05-27 21:00 ` 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=1213928373.20110527171930@gmx.de \
--to=aksdb@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).