ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Patzer <homerow@lavabit.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Error markers for invalid section references
Date: Mon, 7 Jan 2013 13:02:35 +0100	[thread overview]
Message-ID: <20130107120235.GR11551@homerow> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1096 bytes --]

Hi,

in the final stage of a document I always run a grep for ?? and
xxxx on the document to find invalid references and missing
bibliography entries.

However, in documents that do not have a section number the
references to the number are also wrong, they need to be references
to the name instead of the number. In this case no error marker is
printed and AFAIK not even a hint in the log file. The correct way
is to use \about instead of \in. Here's an example:

\setuphead [section] [number=no]
\starttext

\startsectionlevel [title=Alpha]
  See section \in[invalid]. \par %% prints ??
  See section \in[sec:bar]. \par %% prints nothing
  See section \about[sec:bar].   %% correct reference
  
  \startsectionlevel [title=Foo]
  \stopsectionlevel
  \startsectionlevel [title=Bar, reference=sec:bar]
  \stopsectionlevel
\stopsectionlevel

\stoptext

The wrong \in[invalid] reference receives an easy to find error
marker and an entry in the log file. The wrong entry \in[sec:bar] is
hard to find.

Is there a way to add ?? for those cases as well?


Marco

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2013-01-07 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 12:02 Marco Patzer [this message]
2013-01-07 21:56 ` Hans Hagen
2013-01-07 22:06   ` Marco Patzer

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=20130107120235.GR11551@homerow \
    --to=homerow@lavabit.com \
    --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).