LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Mon, 18 Oct 2021 16:06:33 +0200
Content-Disposition: inline
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=iso-8859-1
From: LARONDE Thierry <[log in to unmask]>
Parts/Attachments: text/plain (36 lines)
Hello Joseph,

Le Mon, Oct 18, 2021 at 02:04:20PM +0100, Joseph Wright a écrit :
> Hello Thierry
> >  From an engineering point of view, couldn't the code set everything with
> > some:
> > 
> > \ifx\engineversion\undefined
> > \else
> >    \input engine.tex
> > \fi
> > 
> > ? So that it's easier to see what depends on the engine and in order
> > for modifications to the engine to be severed from the rest of the code?
> Very little of the code is engine-specific, and the parts that are are
> largely in separate files as you suggest. Broadly
> - l3names needs to save primitives in a predictable way, so checks for
>   example for pdfTeX and LuaTeX names for the same concepts
> - l3sys sets up engine-specific paths
> - l3backend is split by backend: you likely are using dvips so
>   l3backend-dvips.def needs to be loaded

OK, I will restrict my interventions to these .dtx.

        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C