From: r.ermers@hccnet.nl
Subject: Re: blocks in itemize
Date: Mon, 22 Aug 2005 13:58:08 +0200 (MEST) [thread overview]
Message-ID: <43458.62.251.0.62.1124711888.squirrel@62.251.0.62> (raw)
In-Reply-To: <20050822114120.GA19715@blackowl.org>
Hi Olivier,
Thanks for your reaction. My original proposal was:
\startitemize
\beginblockA
\item Apple
\endblockA
\beginblockB
\item Pomme
\endBlockB
\beginblockA
\item Pear
\endblockA
\beginblockB
\item Poire
\endBlockB
\stopitemize
This does not work.
The advantage of this setup is that in a bilingual document, printed separatedly, I have both languages underneath and thus more control than when I use separate itemize environments, such as proposed by Taco, and what I had thought of earlier:
\beginblockA
\startitemize
....
\stopitemize
\endblockA
\beginblockB
\startitemize
....
\stopitemize
\endblockB
Nevertheless, if my proposal does not work, I guess I'll have to try it this way.
Kind regards,
Rob
> Hi,
>
>
> I might be wrong, but I think blocks are intended as buffered text.
> This way it is not good to use
> \item {block A}{bloc B}
> and it is not good as well to use {\item block A}
> {\item block B}
>
>
> I think the only good way to use block is
> {\startitemize
> \item block A
> \stoptitemize}
> {\startitemize
> \item block B
> \stoptitemize}
> were good means a natural utilisation of blocks.
>
> However, I certainly understand that the third solution is not practical
> for your intended usage.
>
> Maybe a newif is more appropriate to your situation:
> \newif\ifenlang and \ifenlang \else \fi switches,
> or maybe even cases if you have more than one language.
>
> Just some thought hoping it helps,
> Olivier
>
>
>
next parent reply other threads:[~2005-08-22 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050822114120.GA19715@blackowl.org>
2005-08-22 11:58 ` r.ermers [this message]
2005-08-22 18:31 ` Brooks Moses
2005-08-22 20:16 ` Rob Ermers
2005-08-22 20:39 ` Rob Ermers
2005-08-23 19:32 ` Mojca Miklavec
2005-08-23 21:36 ` Rob Ermers
2005-08-24 6:15 ` Hans Hagen Outside
2005-08-21 20:22 Rob Ermers
2005-08-22 7:00 ` Taco Hoekwater
2005-08-22 7:15 ` r.ermers
2005-08-22 7:43 ` Taco Hoekwater
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=43458.62.251.0.62.1124711888.squirrel@62.251.0.62 \
--to=r.ermers@hccnet.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).