ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <acbowen@princeton.edu>
Subject: Re: wrapping a long URL without added spaces
Date: Thu, 13 Apr 2006 07:53:28 -0400	[thread overview]
Message-ID: <06BE2A64-6F9F-44CD-A26A-CB4F6B978BC0@princeton.edu> (raw)
In-Reply-To: <443CF666.60209@elvenkind.com>

Taco—

Many thanks for the diagnosis. That is a good start, but I guess that  
for now I will have to find another way get long interactive links  
into my docs.

Best, Alan



On Apr 12, 2006, at 8:45 AM, Taco Hoekwater wrote:

>
>
> Alan Bowen wrote:
>> Hi, Taco!
>>
>> Here is a minimal file that produces the problem. Note that if you
>> comment out \setupinteraction[...], the problem goes away and the URL
>> is wrapped nicely.
>
> Ok, here is the diagnosis:
>
> The \from command calls \dogotospace which in turn calls
> \processisolatedwords, and at that point, \betweenisolatedwords
> contains the actual space that is causing the problems.
>
> I am not sure how to fix this elegantly, though.
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-04-13 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 22:33 Alan Bowen
2006-04-12  8:04 ` Taco Hoekwater
2006-04-12 11:47   ` Alan Bowen
2006-04-12 12:45     ` Taco Hoekwater
2006-04-13 11:53       ` Alan Bowen [this message]
2006-04-13 11:29 ` Hans Hagen
2006-04-13 12:03   ` Alan Bowen
2006-04-13 13:00     ` Hans Hagen
2006-04-13 19:15       ` Alan Bowen
2006-04-14 18:21         ` Johannes Graumann
2006-04-14 18:35           ` Hans Hagen
2006-04-14 18:36             ` Johannes Graumann
2006-04-14 18:55           ` Alan Bowen
2006-04-14 18:58             ` Johannes Graumann

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=06BE2A64-6F9F-44CD-A26A-CB4F6B978BC0@princeton.edu \
    --to=acbowen@princeton.edu \
    --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).