lmtx: new text & math font stuff
Hi, As you know, lmtx is also a place for experiments. Currently I'm playing a bit with fonts. Recently (as mentioned a whil eback) I added glyph scaling which permits interesting trickery, although one needs to be aware of how it combines with other features. Here's an example: \def\UnKernedTeX {T% {\glyph xoffset -.2ex yoffset -.4ex `E}% {\glyph xoffset -.4ex options "C0 `X}} \dorecurse{100}{ x \UnKernedTeX} There are alse \glyphxscale cum suis but again, beware that it might influence things when not used grouped. At some point this will be an option in scaled fonts (think of \tfc and such). It saves instances. You can get an idea with: \enableexperiments[text.fonts.compact] The 'text' in this command suggests that we can also do that with math and indeed we have \enableexperiments[math.fonts.compact] These directives have to come *before* loading fonts in order to be effective. Especially the math can bring down the number of font instances: text, script and scriptscript all use the same instance, which is good news. The bad news is that it's up to users to check how this plays out. There are some differences due to the fact that scaling happens elsewhere and otherwise which results in tiny differences (4/5th decimal). As said, these are experiments so ity might progress. I post intermediate versions because that way I can control it better. There is another variant in the planning. Yet another expriment (undecided if that will stay, i played with if before and then rejected it): \enabledirectives[fonts.injections.method=advance] If it stays I probbably have to patch some other code to better suit it. Overall, although in math it add to the overhead, due to the fact that math is hardly demanding (makes only a fraction of the rendering) the memory footprint can be quite a bit lower and performance a bit better (not that much). The measures used in rendering are kind of floating (recalculated often) when these mechanisms are enabled but my impression is that todays compilers make that hardly noticeable. As usual, it opens up possibilities, but of course at the price of testing. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
On 12/30/20 4:53 PM, Hans Hagen wrote:
As usual, it opens up possibilities, but of course at the price of testing.
Hans, I had seen the alignment bug as well; this has been fixed in today's upload. I'm in a book project (from xml), so I don't have small examples right now, but I want to point out that there are two more areas where current lmtx has serious problems that luatex doesn't have: 1. I have a bibliography that is structured in sections. lmtx does not respect the scope of these sections, but prints the entire bibliographical list at the first occurrence of \placelistofpublications. I wasn't sure if I had the right keywords and experimented an entire afternoon before I realized this was a bug in lmtx... 2. For some reason, lmtx introduces lots of empty pages into my document. When I compile my book with luatex, I get 176 pages at the moment, in lmtx, I have 208. Must be something about chapter breaks and so on. I will try in the next days to come up with examples, but right now, I'm working on a chapter and don't want to interrupt the flow... As always, thanks for your work on context, and best wishes for 2021 - may it suck less that 2020! Thomas
On 12/30/2020 7:27 PM, Thomas A. Schmitz wrote:
On 12/30/20 4:53 PM, Hans Hagen wrote:
As usual, it opens up possibilities, but of course at the price of testing.
Hans,
I had seen the alignment bug as well; this has been fixed in today's upload. I'm in a book project (from xml), so I don't have small examples right now, but I want to point out that there are two more areas where current lmtx has serious problems that luatex doesn't have:
Must have been some side effect of some of the font stuff as iI didn't really touch the alignment code.
1. I have a bibliography that is structured in sections. lmtx does not respect the scope of these sections, but prints the entire bibliographical list at the first occurrence of \placelistofpublications. I wasn't sure if I had the right keywords and experimented an entire afternoon before I realized this was a bug in lmtx...
hm, should not be too hard to solve (with an example) ... keep in mind that there is no functionality difference between mkiv and lmtx (although lmtx will evolve), so maybe some oversight in upgrading the low level interfacing macros (removing indirectness)
2. For some reason, lmtx introduces lots of empty pages into my document. When I compile my book with luatex, I get 176 pages at the moment, in lmtx, I have 208. Must be something about chapter breaks and so on.
here we definitely need an example
I will try in the next days to come up with examples, but right now, I'm working on a chapter and don't want to interrupt the flow...
sure (sometimes) comparing the tuc files gives a clue
As always, thanks for your work on context, and best wishes for 2021 - may it suck less that 2020! Thanks,
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Hans Hagen
-
Thomas A. Schmitz