From: Michael Wiedmann <mw@miwie.in-berlin.de>
Cc: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: URL hyperlinks
Date: Mon, 11 Mar 2002 20:04:02 +0100 [thread overview]
Message-ID: <20020311190402.GA2554@miwie.in-berlin.de> (raw)
In-Reply-To: <877kojvb4q.fsf@dellius.nederware.nl>
* Berend de Boer <berend@pobox.com> [020311 08:04]:
> I suppose \goto can take a url directoryl, so you don't have to use
> \useURL. Have you tried this?
It does not work, I have to use \useURL.
Multiple instances of the same label for \useURL seem to work, at least
I did not get any errors in processing a document containing many <ulink>s.
> > - only the first character of the XML element text ("s") is taken as the
> > hyperlink text
The probem was
\defineXMLcommand[ulink] \makeulink
it has to be
\defineXMLargument[ulink] \makeulink
Thanks
Michael
--
mw@miwie.in-berlin.de http://www.miwie.org
mw@miwie.org
next prev parent reply other threads:[~2002-03-11 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 13:27 Michael Wiedmann
2002-03-09 15:40 ` Berend de Boer
2002-03-10 16:17 ` Michael Wiedmann
2002-03-11 7:04 ` Berend de Boer
2002-03-11 19:04 ` Michael Wiedmann [this message]
2002-03-11 21:33 ` 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=20020311190402.GA2554@miwie.in-berlin.de \
--to=mw@miwie.in-berlin.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).