From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: % in URL
Date: Tue, 22 Apr 2008 16:48:39 +0200 [thread overview]
Message-ID: <480DFAC7.5040600@wxs.nl> (raw)
In-Reply-To: <50A80C5D-2C78-4B84-9970-E23934349663@princeton.edu>
Alan Bowen wrote:
> Again, many thanks, Wolfgang.
>
> The key is to use \from rather than \goto. As for using just % in the
> links,
>
> \useURL
> [Hoyrup2007bURL]
> [{http://www.akira.ruc.dk/~jensh/Publications/2005%7BR%7D1_Folkerts_vol-1.PDF
> }]
> []
> [{http://www.akira.ruc.dk/\~{}jensh/Publications/2005\%7BR\%7D1
> \_Folkerts\_vol-1.PDF}]
>
> works but looks odd, since TeXShop (my editor) puts everything from
> the the first “%” on in the URL field (the 2nd field) in red
> (indicating that it is commented out). Using “\%” in this field seems
> to work too.
>
> Very best, Alan
>
> On Apr 22, 2008, at 02;14,05 , Wolfgang Schuster wrote:
>
>> On Tue, Apr 22, 2008 at 4:00 AM, Alan Bowen <acbowen@princeton.edu>
>> wrote:
>>> I am trying to typeset a URL that has numerous "%"s in it which I am
>>> replacing with "\%"s. The problem is that while the typeset URL
>>> works,
>>> the printed URL is showing the "\%"s rather than just the "%"s.
>>>
>>> For example,
>>> \useURL
>>> [Hoyrup2007bURL]
>>> [{http://www.akira.ruc.dk/~jensh/Publications/2005\
>>> %7BR{\percent}7D1_Folkerts_vol-1.PDF}]
>>> []
>>> [{http://www.akira.ruc.dk/~jensh/Publications/2005\%7BR\
>>> %7D1_Folkerts_vol-1.PDF}]
>>>
>>> produces a link that works but reads as
>>> http://www.akira.ruc.dk/~jensh/Publications/2005\
>>> %7BR{\percent}7D1_Folkerts_vol-1.PDF
>>>
>>> I notice that "\&" behaves as it should in this context.
>>>
>>> Any suggestions or pointers to a solution will be much appreciated.
>> You could write % just as % in your links.
>>
>> \useURL
>> [Hoyrup2007bURL]
>> [http://www.akira.ruc.dk/~jensh/Publications/2005%7BR%7D1_Folkerts_vol-1..PDF
>> ]
>>
>> \starttext
>> \from[Hoyrup2007bURL]
>> \stoptext
\expanded{\whatever[messycode\letterpercent andmore]}
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-22 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 2:00 Alan Bowen
2008-04-22 6:14 ` Wolfgang Schuster
2008-04-22 11:30 ` Alan Bowen
2008-04-22 14:48 ` Hans Hagen [this message]
2008-04-26 22:17 ` Standalone chart David Arnold
2008-04-26 22:57 ` Peter Rolf
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=480DFAC7.5040600@wxs.nl \
--to=pragma@wxs.nl \
--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).