From: Renaud AUBIN <aubin@nibua-r.org>
Subject: Re: setupitemize confusion
Date: Thu, 27 Jul 2006 09:11:09 +0200 [thread overview]
Message-ID: <44C8670D.4040901@nibua-r.org> (raw)
In-Reply-To: <CEF5C53C-E61A-4270-8389-22A586BE8917@st.estfiles.de>
[-- Attachment #1.1: Type: text/plain, Size: 2304 bytes --]
Hi Steffen,
Can you provide some working sample code (two or three typical entries +
wrap with \start/stopitemize) ?
Is your bibliography big ? I assume your this work is urgent and you
can't make a .bib, right ?
Renaud
Steffen Wolfrum a écrit :
>Am 27.07.2006 um 08:05 schrieb Aditya Mahajan:
>
>
>
>>On Thu, 27 Jul 2006, Steffen Wolfrum wrote:
>>
>>
>>
>>>Am 27.07.2006 um 07:32 schrieb Aditya Mahajan:
>>>
>>>
>>>
>>>>On Wed, 26 Jul 2006, Steffen Wolfrum wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>both paragraph should be indented 12 pt. But there are different:
>>>>>
>>>>>\starttext
>>>>>
>>>>>\startitemize[width=12pt]
>>>>>\sym{\endash}\input tufte
>>>>>\stopitemize
>>>>>
>>>>>\setupitemize[width=12pt]
>>>>>\sym{\endash}\input tufte
>>>>>
>>>>>\stoptext
>>>>>
>>>>>
>>>>>How do I make the second the same as the first?
>>>>>
>>>>>
>>>>Shouldn't you wrap the second one with \startstop itemize?
>>>>
>>>>\setupitemize[width=12pt]
>>>>\startitemize
>>>>\sym{\endash}\input tufte
>>>>\stopitemize
>>>>
>>>>Aditya
>>>>
>>>>
>>>
>>>Well, I hope not!
>>>
>>>As far as I understood the manual (cont-eni) one can use \item and
>>>\sym also without the start-stop environment: in cases where it is
>>>just needed as one entry (not a list).
>>>This works, somehow. But is there no setup possible?
>>>
>>>I need it in a bibliography: the normal entries "author, title etc.
>>>maybe two lines" are hangindented with \hangafter=1\hangindent=12pt.
>>>But when a author has two or more titles it is written "- title etc.
>>>maybe two lines". And here the "- " must be the same space as the
>>>hangindent (12pt), as one can imagine easily.
>>>That's why I used a \item res. \sym for this. And a start/stop each
>>>would make the code quite chaotic.
>>>
>>>But maybe there is even another solution for this construction, even
>>>better?
>>>
>>>
>>Ask Taco to implement this in the bib module :-)
>>
>>
>
>
>The bib module won't help (I assume): the bibliography is already
>typed, not generated.
>
>Steffen
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2913 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-07-27 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 21:58 Steffen Wolfrum
2006-07-27 5:32 ` Aditya Mahajan
2006-07-27 5:54 ` Steffen Wolfrum
2006-07-27 6:05 ` Aditya Mahajan
2006-07-27 6:17 ` Steffen Wolfrum
2006-07-27 6:57 ` Renaud AUBIN
2006-07-27 7:43 ` Taco Hoekwater
2006-07-27 7:50 ` Renaud AUBIN
2006-07-27 7:11 ` Renaud AUBIN [this message]
2006-07-27 7:50 ` Steffen Wolfrum
2006-07-27 8:36 ` Taco Hoekwater
2006-07-27 8:58 ` Steffen Wolfrum
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=44C8670D.4040901@nibua-r.org \
--to=aubin@nibua-r.org \
--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).