On Mon, 13 Jan 2020 at 03:41, Doug McKenna wrote:
>
> David Carlisle wrote:
>
> >| Note this list is for the xetex extended tex,
> >| but the issues you raise are unrelated to xetex
> >| but to the latex format initialisation so this
> >| is not really the right list.
>
> I checked all the lists b
On 13/01/2020 03:41, Doug McKenna wrote:
Phil Taylor wrote:
| So because JSBox is required/designed to incorporate all of XeTeX's
| features, it must (by definition) implement/provide \Umathcode.
Just to be clear, JSBox can eventually incorporate all of XeTeX's features
(primitives), but doe
On 13/01/2020 03:41, Doug McKenna wrote:
| load-unicode-data handles some of the reading, but there is additional
| reading (see l3unicode.dtx) that is in expl3.sty (in current xelatex
| fomats) but will be preloaded in future releases and in the current
| xelatex-dev release as noted above.
I
On Mon, 13 Jan 2020 at 03:41, Doug McKenna wrote:
> >| Are there architectural reasons preventing you from having a
> >| format file, or is it simply that you hope to make loading quick
> >| enough that you do not need it?
>
> Yes, and yes. JSBox does not depend on an internal array of integers
