ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christian Prim <christian.prim@gmx.ch>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Cloze Text (text with gaps)
Date: Thu, 27 Jun 2013 09:16:02 +0200	[thread overview]
Message-ID: <CA+9XOxrHC2i0RsK1YferpvZweCa_TKaBN_tutd9KNHYjsM3S9g@mail.gmail.com> (raw)
In-Reply-To: <864ncktbrj.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1647 bytes --]

Thanks David

I think the first one is a very good idea. But I failed to give the
\underbar a color different to the one of the text. Can you help me please?

Thanks
Christian


2013/6/27 David Rogers <davidandrewrogers@gmail.com>

> Christian Prim <christian.prim@gmx.ch> writes:
>
> > I wonder if I can typeset a cloze text using context. The gaps
> (__________)
> > must have a given length (say in cm or the length of a given word, given
> > sentence) and must break at the end of a line.
> >
> > \hl[4] is nice but won't do the trick since it won't break. \fillinline
> and
> > others fill the hole line, but I only want to fill a given size.
> >
> > Are there some ideas how to deal with it?
> >
> > Example:
> >
> > The name of the _____________ is _____
> > ________. And now it's time to go to bed.
> > Some more text.....
>
>
> I haven't tested these ideas...
>
> One possibility: type the answer in white, but give it a coloured
> \underbar. (You might need to type longer answers, or in a larger font
> size, to leave enough room for hand writing.)
>
> Another: use a \fillinline - you can define the length.
>
> --
> David
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2657 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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-06-27  7:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 14:36 Christian Prim
2013-06-27  4:31 ` David Rogers
2013-06-27  7:16   ` Christian Prim [this message]
2013-06-27 18:23 ` Wolfgang Schuster
2013-06-27 18:53   ` Jaroslav Hajtmar
2013-06-27 19:02     ` Wolfgang Schuster
2013-06-28  7:06       ` Christian Prim
2013-06-28  7:36         ` Jaroslav Hajtmar
2013-06-28 12:35           ` Wolfgang Schuster

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=CA+9XOxrHC2i0RsK1YferpvZweCa_TKaBN_tutd9KNHYjsM3S9g@mail.gmail.com \
    --to=christian.prim@gmx.ch \
    --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).