User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20131118
            Thunderbird/17.0.11
MIME-Version: 1.0
References: <577FE39F.4030402@tex-tipografia.com>
            <a27b551d-3d55-22dc-18a4-98eabd6ada8c@nag.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:  <577FFC14.3020106@tex-tipografia.com>
Date:         Fri, 8 Jul 2016 21:16:36 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Javier Bezos <listas@TEX-TIPOGRAFIA.COM>
Subject: Re: \parshape and bidi
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <a27b551d-3d55-22dc-18a4-98eabd6ada8c@nag.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

David,

> For context, that was dev-luatex list not the main luatex list at tug
>
> https://mailman.ntg.nl/pipermail/dev-luatex/2016-July/005769.html

Yes, sorry.

> I'd have thought that your example isn't convincing, and that parshape
> should always follow the writing direction. Even if the shape is a map
> of the Netherlands if writing left to right or right to left, specifying
> a sequence of starting points and line lengths would seem reasonable,
> although of course the actual numbers would be different depending on
> whether you are specifying offsets from the left or right.

Nothing prevents us from having two versions, of course, but
I was describing how \parshape is being used, and the fact
very likely both uses are going to coexist in the future. I
still think the default behavior should depend on the current
direction, but we must not forgot this fact.

> even if luatex's primitive \parshape doesn't get a flag, you could
> define it in lua,

I've even managed to write a "converter" (just a "promising" draft) for
the case n = 1 in pure TeX (with a few \afterassignment's). And the
new tokenizer is of course another solution (thank you for the code).

But for backwards compatibility the issue of the two functions
still remain, and I'm not sure how to handle the possible conflicts.

Javier