From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug with hyphenatedurl
Date: Wed, 21 May 2008 19:17:14 +0200 [thread overview]
Message-ID: <4834591A.3000801@elvenkind.com> (raw)
In-Reply-To: <CAD14A16-0470-4FBC-963D-E3BB61A84A11@st.estfiles.de>
Steffen Wolfrum wrote:
> Hi,
>
> please have a look at the following minimal example (ran with mkii):
>
> ->
>
> \usetypescript[postscript][\defaultencoding]
> \setupencoding[default=texnansi]
> \enableregime[utf]
>
> Test text\footnote{{Z4300, Stand: 1.{|DuennRaum|}Januar\;2002,
> einsehbar unter \hyphenatedurl{http://www.thw.de/thw‑inland/
> grundlagen/rechtsgrundlagen/abr\_rili.htm}}}
>
> \stoptext
>
> <-
>
> Just shortly before handing the PDF to the printer I saw that the part
> "thw‑inland" surprisingly became "thw\dochar␣{45}inland" (at least
> on my machine)!
>
> Is there a fix?
Using U+002D instead of U+2011 in the url will remove the symptom
(of course). There is a problem with active characters inside
\hyphenatedurl but frankly I find that hardly surprising.
Hans or Wolfgang will without doubt come up with a nice solution,
but as usual, here is a bizarre (yet working) hack from me:
\enableregime[utf]
\everyhyphenatedurl{\def\softhyphen{-}}
Best wishes,
Taco
___________________________________________________________________________________
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-05-21 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 15:58 Steffen Wolfrum
2008-05-21 17:17 ` Taco Hoekwater [this message]
2008-05-21 19:48 ` 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=4834591A.3000801@elvenkind.com \
--to=taco@elvenkind.com \
--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).