From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Descriptions ... I wish I understood them
Date: Thu, 25 Sep 2008 15:53:24 +0200 [thread overview]
Message-ID: <09B28A9E-453A-4144-A6B8-045FCBE67D68@gmail.com> (raw)
In-Reply-To: <6faad9f00809241145x27453f17uc2d87461c3ae2c4b@mail.gmail.com>
On 24 sept. 08, at 20:45, Mojca Miklavec wrote:
> Hello,
>
> I have some weird problems with descriptions, but let's start at the
> beginning. (I have more problems with understanding how they work, but
> more about the rest later.)
>
> 1.) How do I get some space between "title" and "abc"? (I currently
> put the space there manually.) If I set distance=1em, weird things
> start happening.
Hi Mojca,
I wish too…
At some point some years ago, I used descriptions such as yours and
the only way
I could solve the problem of your "abc" too clsoe to "title" was to
put an empty {}:
\definedescription
[ma]
[headstyle=bold,
style=italic,
align=left,
location=left,
width=fit,
distance=0pt,
margin=0pt,
hang=2,
indenting=never]
\starttext
\input tufte
\startma[Thm]{Conjecture 1}{} abc. \input knuth
\stopma
\input tufte
\blank
As mentioned in \in {}[Thm], we can show that\dots
\stoptext
>
> 2.) What exactly does "hang=1" do? I have no idea what it does there,
> but that was the only way to get the desired result, else everything
> gets indented. width=fit makes problems. With width=5cm everything is
> OK.
>
the "hang" parameter is the number of lines which are hang-indenting
after the beginning of the description;
however "hang=0" means that all the description is hang-indenting.
Best regards: OK
> \definedescription
> [ma]
> [headstyle=bold,
> style=italic,
> align=left,
> location=left,
> width=fit,
> distance=0pt,
> margin=0pt,
> hang=1,
> indenting=never,
> ]
> \starttext
>
> \input tufte
>
> \startma{title} abc. \input tufte
> \stopma
>
> \input tufte
>
> \stoptext
>
> Thanks a lot,
> Mojca
> ___________________________________________________________________________________
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-09-25 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 18:45 Mojca Miklavec
2008-09-25 13:53 ` Otared Kavian [this message]
2008-09-25 19:37 ` 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=09B28A9E-453A-4144-A6B8-045FCBE67D68@gmail.com \
--to=otared@gmail.com \
--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).