From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \hyphenatedurl problem
Date: Mon, 22 Dec 2003 12:36:53 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20031222123401.01dbee90@localhost> (raw)
In-Reply-To: <20031221223503.GA16055@physik.fu-berlin.de>
At 23:35 21/12/2003, you wrote:
>Hi,
>
>I'm sure I miss something obvious but I have no clue what it is.
>I have:
>
>\def\gotoDOI#1{\hyphenatedurl#1}
\def\gotoDOI#1{\hyphenatedurl{#1}}
otherwise the first token in #1 becomes the argument to \hyphenatedurl
> \gotoDOI{10.1016/S0009-2614(01)01361-6}
^
in your def it's now \hyphenatedurl -> #1 == 1 and the
0.... is just text
>\hyphenatedurl{10.1016/S0009-2614(01)01361-6}
>
>and I redefined supp-lan.tex's \scanurl to hyphenate at '(' and ')'.
\else\if#1(%
\flushurl\splitbefore(%
\else\if#1)%
\flushurl\splitafter)%
...\fi\fi...
Hans
next prev parent reply other threads:[~2003-12-22 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 22:35 Tobias Burnus
2003-12-22 11:36 ` Hans Hagen [this message]
2015-04-11 5:20 Rik
2015-04-13 17:19 ` Pablo Rodriguez
2015-04-13 18:45 ` Rik Kabel
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=6.0.1.1.2.20031222123401.01dbee90@localhost \
--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).