ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wybo Dekker <wybo@servalys.hobby.nl>
Cc: ntg-context@ntg.nl
Subject: Re: decriptions
Date: Sat, 26 Jun 1999 12:37:30 +0200	[thread overview]
Message-ID: <199906261037.MAA02529@servalys.hobby.nl> (raw)
In-Reply-To: <37736A72.B9FB6AD1@wxs.nl>

Hans Hagen wrote:
> 
> Hi all and Wybo in particular, 
> 
> I suppose this is what you want: 
> 
> \setuplayout[width=100mm]
> 
> \definedescription
>   [description]
>   [location=hanging,        % implemented recently 
>    margin=standard,
>    headstyle=bold]
> 
> \definestartstop
>   [descriptions]
>   [before=\blank\startpacked,
>    after=\stoppacked\blank,
>    commands=\let\item\description]
> 
> \starttext
> 
> \dorecurse{10}{This one is for Wybo. }
> 
> \startdescriptions
> 
> \description {aap:} is a monkey, but much more can be told
> about this animal;s for example they are hairy, mostly
> brown or black and they resemble people a lot.
> 
> \item {noot:} is a vegetable; again there are many kinds
> and you will get very fat if you eat lots of them.
> 
> \startdescription {this is a rather long item:}
> 
> it is not very interesting in itself, but gives me the
> opportunity to tell you something about the description
> environment: it is like an itemize, but with user-supplied
> labels which are printed bold.
> 
> \stopdescription
> 
> \stopdescriptions
> 
> \dorecurse{10}{This one is for Wybo. }
> 
> \stoptext 

That's exactly what I meant. Yet a few remarks: 
1: why allow a mix of `item' and `description'? Just `item' would suffice
2: the only need for the \startdescription/\stopdescription pair I see
   is that it allows for more than 1 paragraph in a description/item. Latex
   allows for that without extra's.  And it always separates
   paragraphs in lists with an empty line and with no parindent. And
   if one doesn't want the empty line: use \\
   I like that behaviour.

> I think it makes sense to add such latex counterparts to a specific
> module m-latex or so. If needed, with some \begin \end alike
> substitutes, like 

[...]

I don't think it's a good idea to emulate latex in context. It just
makes people to stick with latex instead of thinking the context way. 

You should do two things:
1: make context alternatives for things that people like in latex, but
   only if they are right in your view.
2: give people hints about how they can do the things they did in
   latex better in context.

A final question: 
As Hans now generously generates new code for me in English, while I
started my book in Dutch (which was the language used during the
course). I decided to translate the book into english, using my `tran'
perlscript. But that doesn't find translations for:

\startstandaardopmaak
\stopstandaardopmaak
\volledigeinhoudsopgave

Those words are not in mult-co[mn].tex. Howcome?
-- 
Hartelijke groet, Wybo
--
__Servalys Analytical Chemistry Services__
Wybo H. Dekker      wybo@servalys.hobby.nl
Deilsedijk 60       www.hobby.nl/~servalys
4158 CH Deil        tel +31-345-652164    
The Netherlands     fax +31-345-652383    


  parent reply	other threads:[~1999-06-26 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 11:39 decriptions Hans Hagen
1999-06-25 13:48 ` decriptions Taco Hoekwater
1999-06-25 11:53   ` decriptions Hans Hagen
1999-06-26 10:37 ` Wybo Dekker [this message]
1999-06-26 15:54   ` decriptions Hans Hagen
1999-06-26 21:09 ` decriptions Wybo Dekker
1999-06-26 23:03   ` decriptions Hans Hagen

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=199906261037.MAA02529@servalys.hobby.nl \
    --to=wybo@servalys.hobby.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).