MIME-Version: 1.0
In-Reply-To: <5595540F.9080605@telecom-bretagne.eu>
References: <559534D0.2060001@morningstar2.co.uk>
 <5595540F.9080605@telecom-bretagne.eu>
Date: Thu, 2 Jul 2015 16:32:28 +0100
Message-ID: <CAEW6iOgEZmRptF1K_8ecZ2=kM8O2tRC4VOnYuHqWJsmU5DbKog@mail.gmail.com>
Subject: Re: LuaTeX support in the LaTeX kernel
From: David Carlisle <d.p.carlisle@gmail.com>
To: =?UTF-8?Q?=C3=89lie_Roux?= <elie.roux@telecom-bretagne.eu>
Cc: Heiko Oberdiek <heiko.oberdiek@googlemail.com>,
        Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>,
        "latex-team@latex-project.org" <latex-team@latex-project.org>,
        Philipp Maximilian Stephani <p.stephani2@gmail.com>, mpg@elzevir.fr,
        Lars Madsen <daleif@imf.au.dk>
Precedence: list
Content-Type: text/plain; charset="utf-8"
Errors-To: latex-team-bounces@latex-project.org
Sender: "Latex-team" <latex-team-bounces@latex-project.org>
Content-Transfer-Encoding: 8bit
Status: R

On 2 July 2015 at 16:09, Élie Roux <elie.roux@telecom-bretagne.eu> wrote:


>> *Catcode allocation*

> This would be helpful indeed, or most package using catcodetables will
> define their document, string and makeatother tables...

Yes probably, although one concern that I had with the existing ones
is that they
only differ in the ascii range whereas (perhaps) they ought to reflect
the catcode settings as specified in unicode-letters.def ie 11 or 12
depending on unicode class.


>
>> *Callbacks*
>>
>> We have significantly minimised the callback allocator from
>> luatexbase to cover just the idea of registering multiple callbacks
>> but not resetting/removing/...
>
> I think removing a callback is quite useful: for instance in Gregorio
> (https://github.com/gregorio-project/gregorio, soon to be integrated
> into TeXLive) I make quite convoluted treatment in postlinebreak_filter,
> but only in the context of a score, so I register the callback at the
> beginning of a score and remove it at the end.. Well, I could find other
> means to check if I need to run the callback or not, but I admit I liked
> this way of using callbacks.

use cases are good here, nothing fixed yet....


> That seems like a terrible idea: some packages would register callbacks
> in the LaTeX core interface, and if another registers a callback in the
> more sophisticated interface, the first callback will be overwritten...
> Maybe a solution to this and the removal could be to make the callback
> function lists public?

Clearly we should look at this...


>
> Why not include the code adding kpse to package.searchers ? Or would it
> be better to add it when building the format (so that LaTeX doesn't
> depend on kpse

clearly something we should look at....

>
> Why not include a whatsit allocator (like the one in
> https://github.com/lualatex/luatexbase/blob/master/luatexbase-attr.dtx#L484)?
> This was a request from users and could have its place alongside the
> other allocators.
>

I think it just got missed, partly I suppose as it's almost all on the lua side
although as you say, the  allocator could be done in tex to match the others.
Again: more testing required..

Thanks for your comments!

David

_______________________________________________
Latex-team mailing list
Latex-team@latex-project.org
https://lists.dante.de/mailman/listinfo/latex-team