[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Parallel text on two pages

From: Valeriy E. Ushakov
Subject: Re: Parallel text on two pages
Date: Tue, 21 Aug 2001 17:06:25 +0400
User-agent: Mutt/1.3.3i

Well, I just thought it's a good example to show @NotRevealed in
action because of the regular and straightforward pattern this example

On Tue, Aug 21, 2001 at 06:36:52 +0400, Valeriy E. Ushakov wrote:

>     def @Bilingual
>     {
>       3i @Wide @EnPlace ||1i 3i @Wide @DePlace @NotRevealed
>       // @Bilingual
>     }

Let's consider this definition but with @NotRevealed omitted.
What happens when Lout encounters:

    // @En { ... }
    // @De { ... }

When Lout encounters @Bilingual it just lazily leaves it unexpanded.
Then when it hits @En it starts a search for @EnPlace and it expands
@Bilingual one time to get (omitting gaps etc):

       @EnPlace || @DePlace
    // @Bilingual  # <- @DePlace is visible

Now when Lout hits @De it will search for @DePlace and it will find it
in the yet unexpanded @Bilingual!  So the result will look like

        en en en en en en
        en en en en en en 
                            de de de de de de
                            de de de de de de

That's where @NotRevealed comes to rescue.  With @NotRevealed in place

       @EnPlace || @DePlace
    // @Bilingual  # <- @DePlace is not wisible

the @DePlace in the unexpanded @Bilingual is, well, not revealed - so
when Lout searches for a preceding @DePlace for @De it won't consider
the unexpanded @Bilingual and @De will be sent to the first @DePlace
producing the desired result.

SY, Uwe
address@hidden                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]