From: Alan Braslau <braslau.list@comcast.net>
To: Pablo Rodriguez <oinos@gmx.es>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: BUG: Colour spilling in btxrendering
Date: Wed, 9 Aug 2017 11:08:15 -0600 [thread overview]
Message-ID: <20170809110815.71bb8806@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <41c904f6-cad3-46b0-8cbe-05dbb2d71e75@gmx.es>
Hans has made changes to interaction in the latest beta, that I am only
now starting to test. Indeed, using the APS specification in
bibliographies, interaction was not limited to specific fields such as
titles or urls as is intended. This will be fixed.
Alan
On Tue, 8 Aug 2017 23:33:19 +0200
Pablo Rodriguez <oinos@gmx.es> wrote:
> On 08/08/2017 11:02 PM, Henri wrote:
> > On Tue, 2017-08-08 at 17:31 +0200, Pablo Rodriguez wrote:
> >> [...]
> >> This fixes in my computer what I guess is your problem.
> >
> > I would call this a workaround. What I want are coloured links.
> > Usually only the clickable area is coloured but in the bibliography
> > it somehow "spills" over to the surrounding text as well.
>
> You are right, Henri. My guess was wrong.
>
> Link is in both cases the same field (doi). But the color is spilled
> over the whole reference.
>
> Pablo
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-08-09 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 21:43 Henri Menke
2017-08-08 6:04 ` Henri
2017-08-08 15:31 ` Pablo Rodriguez
2017-08-08 21:02 ` Henri
2017-08-08 21:33 ` Pablo Rodriguez
2017-08-09 17:08 ` Alan Braslau [this message]
2017-08-09 17:21 ` 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=20170809110815.71bb8806@zoo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).