ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Nonbreaking, non-vanishing horizontal spaces above underbar
Date: Wed, 14 Sep 2016 16:57:56 +0200	[thread overview]
Message-ID: <7da9b510-baf3-f24c-3aa2-4037f61b9e79@wxs.nl> (raw)
In-Reply-To: <2ace42b8-2729-8259-518a-fa6ba811afc0@wxs.nl>

On 9/14/2016 4:57 PM, Hans Hagen wrote:
> On 9/14/2016 2:33 PM, Florian Leupold wrote:
>> Dear all,
>>
>> I would like to create cloze texts with solutions, but I have problems
>> with horizontal spaces above the underbar, namely:
>> 1) After a linebreak, horizontal space is cut off despite the \zwj.
>> 2) I cannot find a way of scaling the leading and trailing space to
>> equal 0.2 times the width of the text above the underbar.
>>
>> MNWE:
>>
>> \definebar[ClozedBar][underbar][continue=yes, color=black, offset=-0.5]
>> \unexpanded\def\Clozed#1{\startbar[ClozedBar]
>>     \zwj\hskip\widthofstring{#1}#1\hskip\widthofstring{#1}\zwj\stopbar}
>> \starttext
>> \Clozed{\color[red]{CLOZE 1}} text text text text text
>> \Clozed{\color[red]{CLOZE 2}} <- This one is cut at the beginning.
>> \stoptext
>>
>> Could someone help me? Thanks a lot in advance!
>>

and please wikify this so that others can benefit from it

> \definebar
>   [ClozedBar]
>   [underbar]
>   [continue=yes,
>    color=black,
>    offset=-0.5]
>
> \starttexdefinition unexpanded Clozed #1
>     \startbar[ClozedBar]%
>     \scratchdimen\widthofstring{#1}\relax
>     \zwj
>     \kern.2\scratchdimen
>     #1
>     \kern.2\scratchdimen
>     \zwj
>     \stopbar
> \stoptexdefinition
>
>
> \starttext
>     \Clozed{\color[red]{CLOZE 1}} text text text text text
>     \Clozed{\color[red]{CLOZE 2}} <- This one is cut at the beginning.
> \stoptext
>
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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
___________________________________________________________________________________

  reply	other threads:[~2016-09-14 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 12:33 Florian Leupold
2016-09-14 14:57 ` Hans Hagen
2016-09-14 14:57   ` Hans Hagen [this message]
2016-09-15 11:28     ` Florian Leupold

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=7da9b510-baf3-f24c-3aa2-4037f61b9e79@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).