Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-13 Thread David Carlisle
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

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-13 Thread Joseph Wright
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.

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-13 Thread David Carlisle
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

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-12 Thread Doug McKenna
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 before posting, at and

Re: [XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-12 Thread David Carlisle
On Sat, 11 Jan 2020 at 00:33, Doug McKenna wrote: > > What is the possibility of making a slight enhancement to how the Unicode > LaTeX format is created with respect to "Unicode-aware" engines (an > unfortunately somewhat ill-defined term)? Here's the situation: Note this list is for the

[XeTeX] A LaTeX Unicode initialization desire/question/suggestion

2020-01-10 Thread Doug McKenna
What is the possibility of making a slight enhancement to how the Unicode LaTeX format is created with respect to "Unicode-aware" engines (an unfortunately somewhat ill-defined term)? Here's the situation: My TeX/e-TeX language interpreter, currently called JSBox, is implemented as a simple C