From: Hans Hagen <pragma@wxs.nl>
Cc: <ntg-context@ntg.nl>
Subject: Re: URL as parameter...
Date: Tue, 13 Jun 2000 22:06:02 +0200 [thread overview]
Message-ID: <3.0.6.32.20000613220602.00adbb20@pop.wxs.nl> (raw)
In-Reply-To: <20000612204633.10077.qmail@crux.private.off-line>
At 10:46 PM 6/12/2000 +0200, Joop Susan wrote:
>> > Can anyone tell me how to pass a URL as a parameter to a
>> > macro if there is
>> > a tilde character present in the string. In the following
>>
>> Perhaps use something that really is a tilde:
>>
>> \def\MyTilde{\tttf ~}
>>
>> \useURL[test][test/\MyTilde test]
>>
>
>\url seems to use a diferent mechnism. I was hoping there is something
>similar for this case. I'm afraid I'm not very good at understanding
>ConTEXt source. ;-)
Indeed a different mechanism: ~ as well as \~ are handled. The \url macro
takes care of sanitizing chars as well as breaking url's. The \useURL is
more robust. Anyhow, it should work ok, even in situations where the url is
passed as argument. I remember that tobias and I spend quite some time
discussing the ways to hyphenate them,so there are even different
strategies available.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2000-06-13 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Mon, 12 Jun 2000 20:16:57 +0200." <00c001bfd49a$659c08c0$0321a8c0@bmach.nederware.nl>
2000-06-12 20:46 ` Joop Susan
2000-06-13 20:06 ` Hans Hagen [this message]
[not found] <20000614100157.11715.qmail@crux.private.off-line>
2000-06-14 13:58 ` Hans Hagen
2000-06-12 14:47 Joop Susan
2000-06-12 18:16 ` Berend de Boer
2000-06-13 20:03 ` 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=3.0.6.32.20000613220602.00adbb20@pop.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).