User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0)
            Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
References: <55676BAC.7010604@free.fr> <55678C62.1090601@morningstar2.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Message-ID:  <556A194A.9070501@morningstar2.co.uk>
Date:         Sat, 30 May 2015 21:10:50 +0100
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: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: l3galley, margins/parshapes and cutouts
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <55678C62.1090601@morningstar2.co.uk>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 28/05/2015 22:45, Joseph Wright wrote:
> On 28/05/2015 20:25, Julien RIVAUD (_FrnchFrgg_) wrote:
>> From my tests, \galley_cutout_*:nn calls don't interact well with
>> \galley_margins_set_*:nn or \galley_parshape_set_*:nnnN
>>
>> Indeed, cutouts seem to completely ignore any margin or parshape and
>> compute the cutout from the full galley width. Is that expected ? (I
>> cannot find any mention of that fact in the l3galley documentation)
>> Of course I understand that l3galley is an experimental work in progress.
>>
>> I might try to write a patch if the current behaviour is to be changed,
>> but I am currently buried under heaps of exams to grade so don't expect
>> anything soon.
>>
>> Cheers,
>>
>> Julien "_FrnchFrgg_" Rivaud
> 
> I noticed the exactly same thing yesterday :-) I've already made a few
> check-ins to fix this and will be revising the appropriate code more
> fully over the coming days.  As this has come up on the list, not just
> in my own tests, once it looks OK I'll update CTAN. (Probably over the
> weekend.)

Further to this, I believe I have sorted the issues. I am happy to
update CTAN tomorrow with the new code: would that be helpful?
--
Joseph Wright