From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Bug/change in fillinrules
Date: Thu, 31 Mar 2016 08:51:36 +0200 [thread overview]
Message-ID: <56FCC8F8.3090207@wxs.nl> (raw)
In-Reply-To: <CAGbDsP2+frT82HD=JnDmyZ6zjLNKyUh1sfHUWVoFCitdu9v4ew@mail.gmail.com>
On 3/31/2016 8:19 AM, Mari Voipio wrote:
> Darn, a bug. Thank you, Wolfgang. I figured out a workaround that's ok
> for now, but of course I hope that in the long run this gets fixed.
>
>
> Mari
>
> On Tue, Mar 29, 2016 at 7:09 PM, Wolfgang Schuster
> <schuster.wolfgang@gmail.com> wrote:
>> Mari Voipio
>> 29. März 2016 um 14:13
>> Hello,
>>
>> after I updated to about newest ConTeXt, I found out that \fillinrules
>> doesn't work any more as expected, i.e. instead of filling the rest of
>> the first line, the rule now starts on the second line, below the text
>> that precedes \fillinrules. This doesn't match the behaviour indicated
>> in http://wiki.contextgarden.net/Command/fillinrules . Is this a bug
>> or should I change something in my code? Now I have
>>
>>
>> \setupfillinrules
>> [n=1, %one rule per command \fillinrules
>> width=broad] %leaves some space between the text and the line
>>
>> \starttext
>>
>> \fillinrules{Refractometer serial no:}
>> \fillinrules{Customer:}
>> \fillinrules{Address:}
>> \fillinrules{Fax:}
>> \fillinrules{Email:}
>> \fillinrules{Sample description:}
>> \fillinrules{Solvent (water/other):}
>> \fillinrules{Laboratory method:}
>> \fillinrules{Date:}
>> \fillinrules{Data collected by:}
>>
>> \stoptext
>>
>> It’s a \thinrules bug which inserts a line break when you have only a single
>> line.
>>
>> \starttext
>>
>> Left \thinrules[n=1] Right
>>
>> \blank
>>
>> Left \thinrules[n=2] Right
>>
>> \blank
>>
>> Left \thinrules[n=3] Right
>>
>> \stoptext
fixed in next beta
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-03-31 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 12:13 Mari Voipio
2016-03-29 16:09 ` Wolfgang Schuster
2016-03-31 6:19 ` Mari Voipio
2016-03-31 6:51 ` Hans Hagen [this message]
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=56FCC8F8.3090207@wxs.nl \
--to=pragma@wxs.nl \
--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).