ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rob Ermers <r.ermers@hccnet.nl>
Subject: Re: Re: blocks in itemize
Date: Mon, 22 Aug 2005 22:39:11 +0200	[thread overview]
Message-ID: <430A37EF.5090908@hccnet.nl> (raw)
In-Reply-To: <430A329B.4030309@hccnet.nl>

Hi,

If I make sure there is enough space, i.e. more than one space, between 
the \begin... and the text, it works! However in the pdf the item drops 
a line down, like this:


*
     Ik vraag me af ...

Does anyone have a workaround?

Kind regards,

Robert


\defineblock[Nederlandsblok, Engelsblok]

\starttext
\startitemize
\item    \beginNederlandsblok         Ik vraag me af of ze ook appels 
verkopen
         \endNederlandsblok
         \beginEngelsblok         I really wonder if they do sell apples
         \endEngelsblok
\item         \beginNederlandsblok         Ik vraag me af of ze ook 
appels verkopen
         \endNederlandsblok
         \beginEngelsblok         I really wonder if they do sell apples
         \endEngelsblok
\stopitemize
\stoptext


Rob Ermers wrote:
> Thanks Brooks and Olivier,
> I'm afraid the problem has not entirely been solved.
> 
> Brooks' solution works in the sense that I can hide BlockA or B 
> (\hideblocks[BlockA]), but the \items remain, and empty items are 
> generated.
> 
> Olivier's suggestion is processed, the result is only one language. Now 
> now I wonder how to hide either one of the languages. The document I 
> want to produce is monolingual, either Dutch or English.
> 
> Thanks again!
> 
> Kind regards,
> 
> Robert
> 
> 
> 
> Brooks Moses wrote:
> 
>> At 04:58 AM 8/22/2005, you wrote:
>>
>>> 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.
>>
>>
>>
>> I don't know anything about how blocks work, so this may be completely 
>> off-base, but if they do any sort of grouping, that would be quite 
>> sufficient to cause problems in a situation like that.  Does this work?
>>
>> \startitemize
>>   \item \beginblockA
>>     Apple
>>   \endblockA
>>   \item \beginblockB
>>     Pomme
>>   \endBlockB
>>   \item \beginblockA
>>     Pear
>>   \endblockA
>>   \item \beginblockB
>>     Poire
>>   \endBlockB
>> \stopitemize
>>
>> - Brooks
>>
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>>
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
> 
> 

  reply	other threads:[~2005-08-22 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050822114120.GA19715@blackowl.org>
2005-08-22 11:58 ` r.ermers
2005-08-22 18:31   ` Brooks Moses
2005-08-22 20:16     ` Rob Ermers
2005-08-22 20:39       ` Rob Ermers [this message]
2005-08-23 19:32         ` Mojca Miklavec
2005-08-23 21:36           ` Rob Ermers
2005-08-24  6:15           ` Hans Hagen Outside

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=430A37EF.5090908@hccnet.nl \
    --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).