ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: weird interaction in linenotes command (again)
Date: Wed, 17 Jul 2013 21:05:05 +0200	[thread overview]
Message-ID: <4F9901D8-3C1E-4650-88FF-95464B59B7C6@gmail.com> (raw)
In-Reply-To: <51E6D88A.8040403@web.de>


Am 17.07.2013 um 19:46 schrieb Pablo Rodríguez <oinos@web.de>:

> Dear list,
> 
> sorry for posting this again, but I don’t know how to solve this issue
> and I really need your help.
> 
> I have the following sample:
> 
>    \setuppapersize[A6]
>    \newcounter\LineNote
> 
>    \setupnote[linenote][paragraph=yes]
>    \setupnotation[linenote][alternative=serried]
> 
>    \define[2]\Variant
>      {\increment\LineNote
>       \startlinenote[LineNote:\LineNote]{#2}#1%
>       \stoplinenote[LineNote:\LineNote]}
> 
>    \starttext
> 
>    \startlinenumbering
>    \dorecurse{10}{\Variant{\showhyphens{legislation}not
>    original}{variant} \Variant{\showhyphens{legibility}origin}
>    {variants} }
>    \stoplinenumbering
>    \stoptext
> 
> The problem here is that \Variant gets always #1 not hyphenated,
> although \showhyphens works fine in that argument.
> 
> The cause of this is the \increment command within \Variant. I don’t
> know why this happens, but the increment is required by \Variant to make
> sense at all.
> 
> I guess this might be a bug. Is there no possible workaround for this?


I have no solution but a better example because it’s a bug in the reference mechanism
(also used by line notes) as shown below.

\setuppapersize[A6]

\starttext

\dorecurse{10}{not original }

\dorecurse{10}{not \pagereference[test:#1]original }

\stoptext


The problem is the following code in the reference macros (str-ref.mkvi),
when the box code is commented the hyphenation works.

\unexpanded\def\strc_references_set_named_reference_indeed#kind#labels#userdata#text% labels userdata text -> todo: userdata
  {...
   % will become an option:
   \ifnum\lastdestinationattribute>\zerocount
     \dontleavehmode\hbox attr \destinationattribute\lastdestinationattribute\bgroup
       \strc_references_flush_destination_nodes
     \egroup
   \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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2013-07-17 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 17:46 Pablo Rodríguez
2013-07-17 19:05 ` Wolfgang Schuster [this message]
2013-07-18 10:21   ` Hans Hagen
2013-07-18 15:38     ` Pablo Rodríguez
2013-07-18 19:31       ` Wolfgang Schuster
2013-07-18 20:41         ` Pablo Rodríguez

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=4F9901D8-3C1E-4650-88FF-95464B59B7C6@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).