ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Bad interaction between \setupinteraction and \defineenumeration
Date: Mon, 6 Jul 2020 20:48:26 +0200	[thread overview]
Message-ID: <0ba68dbf-ff5b-986f-392f-63b60394ae3c@gmail.com> (raw)
In-Reply-To: <60675c79-acc1-036a-4951-fc31ffa5a701@gmx.es>

Pablo Rodriguez schrieb am 06.07.2020 um 20:04:
> On 7/6/20 3:58 PM, Jairo A. del Rio wrote:
>> So, cannot I use focus=standard and cross-references together? Hmm. I
>> think it should be fixed... But maybe it's an intended feature. Thanks,
>> Otared.
> 
> Hi Jairo,
> 
> "focus=standard" works fine with footnotes.
> 
>      \setupinteraction[state=start,focus=standard,color=,contrastcolor=]
>      \defineenumeration[proposition][referenceprefix=prop]
>      \starttext
>      \startproposition[1]
>      \input ward\footnote{Only a footnote}
>      \stopproposition
>      \in[prop:1]
>      \stoptext
> 
> Your sample doesn’t work, because of the reference prefix. Right now,
> the /Names reads in the PDF code:
> 
>      /Names [ (1) 5 0 R ]
> 
> It seems that "referenceprefix" is forgotten there, which should read
> with the sample code from above:
> 
>      /Names [ (prop:1) 5 0 R ]
> 
> Hans, could you check this? (I’m afraid it doesn’t work with current
> latest [2020.07.06 19:30])?


I'm not Hans but this fixed the problem for me (strc-con.mkiv):

\def\strc_constructions_register_yes[#1][#2]% #1=optional user data 
#2=interfaced-settings
   {\begingroup                              % similar to structure so 
we might generalize this
      ...
      \clf_setinternalreference
-      prefix    {\referenceprefix}%
+      prefix    {\currentconstructionreferenceprefix}%
        reference {\currentconstructionreference}%
        internal  \locationcount
        view      {\interactionparameter\c!focus}%
      \relax
      ...
    \fi}

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2020-07-06 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 23:15 Jairo A. del Rio
2020-07-06  9:31 ` Otared Kavian
2020-07-06 13:58   ` Jairo A. del Rio
2020-07-06 18:04     ` Pablo Rodriguez
2020-07-06 18:48       ` Wolfgang Schuster [this message]
2020-07-06 18:57         ` Hans Hagen
2020-07-06 19:03         ` Pablo Rodriguez
2020-07-07  2:10         ` Jairo A. del Rio
2020-07-07 20:52         ` Otared Kavian

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=0ba68dbf-ff5b-986f-392f-63b60394ae3c@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --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).