ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: Sanjoy Mahajan <sanjoy@olin.edu>, ntg-context@ntg.nl
Subject: Re: [DKIM Failure] Re: reference containing parentheses causes trouble
Date: Wed, 10 Jul 2019 14:28:38 +0200	[thread overview]
Message-ID: <cf39053a-9619-3a5a-aba4-0eff2af82c85@gmx.net> (raw)
In-Reply-To: <87imsap1do.fsf@olin.edu>

Am 10.07.2019 um 13:36 schrieb Sanjoy Mahajan:
> On 2019-07-10 13:04, Peter Rolf <indiego@gmx.net> wrote:
>
>> Hi Sanjoy,
>>
>> I think it's just the 'normal' limitations you have when setting a
>> variable/id name. Special characters, like parenthesis, are not allowed
>> here.
>
> Peter,
>
> I think that's right, but there are small differences.  For example,
> variables in most languages don't allow hyphens, because they are
> interpreted as minus signs.  But ConTeXt references do allow them (and I
> use them all the time).  That may be why I expected free reign to use
> any characters in the reference (except, as you say, for whitespace!)
> and wrote my script accordingly to turn problem titles into references
> (by replacing whitespace with a hyphen).
>

I agree (I always use the underscore instead of space). In general it's
best to avoid problems if you can.
If you use messy third party data as reference things are totally
different. In my current project I have one dead link out of 1275 (also
caused by parenthesis). Not enough to make me write some extra code to
deal with it.

Peter
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-07-10 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  2:15 Sanjoy Mahajan
2019-07-10 11:04 ` Peter Rolf
2019-07-10 11:36   ` [DKIM Failure] " Sanjoy Mahajan
2019-07-10 12:28     ` Peter Rolf [this message]
2019-07-10 11:39   ` Hans Hagen
2019-07-10 19:29 ` Wolfgang Schuster
2019-07-11  9:03   ` Peter Rolf
2019-07-11 12:56     ` Otared Kavian
2019-07-11 15:27       ` Alan Braslau
2019-07-12 11:31         ` 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=cf39053a-9619-3a5a-aba4-0eff2af82c85@gmx.net \
    --to=indiego@gmx.net \
    --cc=ntg-context@ntg.nl \
    --cc=sanjoy@olin.edu \
    /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).