ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Damien Thiriet via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
	Damien Thiriet <damien@thiriet.web4me.fr>
Subject: Re: right item marks for associative questions?
Date: Tue, 12 Apr 2022 21:58:45 +0200	[thread overview]
Message-ID: <a352332e-9ed3-ecc7-4886-8fc0f49c4823@gmail.com> (raw)
In-Reply-To: <YlXI/8XqgvEyGIgd@valencay.home>

Damien Thiriet via ntg-context schrieb am 12.04.2022 um 20:46:
> Thank you for all your answers.
> I will have a deeper look at them.
> My first comments:
>
>> If you are certain that the there will be no
>> multi-line item
> Unfortunately there are often some. History
> teachers are not known for loving short texts,
> at least in France.
>
>> Using the “columns" feature is one way to go
> Might be, but I do not always give the same
> number of answers on both columns
>
> Something I forgot to put in my MWE is that I
> randomize both lists. Messing the answers is a
> good way to prevent pupils from cheating,
> especially with long answers..
> That makes a four columns table more cumbersome,
> so I believe.

You can use different alignment settings to move the bullet points to 
the right side of your lists.

\starttext

\bTABLE[frame=off,width=.4\textwidth,columndistance=.2\textwidth,align={normal,lohi}]
   \bTR
     \bTD
       \startitemize[circle,random][align=righttoleft]
       \startitem {\lefttoright One} \stopitem
       \startitem {\lefttoright Two} \stopitem
       \startitem {\lefttoright Three} \stopitem
       \stopitemize
     \eTD
     \bTD
       \startitemize[circle,random]
       \startitem First \stopitem
       \startitem Second \stopitem
       \startitem Third \stopitem
       \startitem Foruth \stopitem
       \stopitemize
     \eTD
   \eTR
\eTABLE

\stoptext

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:[~2022-04-12 19:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 18:46 Damien Thiriet via ntg-context
2022-04-12 19:58 ` Wolfgang Schuster via ntg-context [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-15  8:54 Damien Thiriet via ntg-context
2022-04-15 12:52 ` śrīrāma via ntg-context
2022-04-11 18:46 Damien Thiriet via ntg-context
2022-04-11 20:18 ` Pablo Rodriguez via ntg-context
2022-04-11 22:04 ` Jeong Dal via ntg-context
2022-04-12  5:48 ` śrīrāma via ntg-context

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=a352332e-9ed3-ecc7-4886-8fc0f49c4823@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=damien@thiriet.web4me.fr \
    --cc=wolfgang.schuster.lists@gmail.com \
    /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).