mathsize font feature doesn't work

[olsak]

The functionality of mathsize font feature is lost In the recent version of luaotfload. Suppose the example here: olsak/OpTeX#67 (comment)
The example-image (its second part at the right side) shows that the script size and scriptscript size are smaller. The optional sizes are read from the font data. But this is not true in the new version of luaotfload: all three sizes are equal.

This is critical bug because OpTeX Unicode math macros are based on the mathsize font feature.

[zauguin]

Fixed in dev, but we might want to consider additionally rewriting the font name if this is used to make these fonts more usable. Currently they are rather odd.

[olsak]

The OpTeX is broken now, when new luaotfload version was released, which is very bad. We can ask if you are doing some tests with OpTeX before new release. I don't see when you are preparing a new version. So, I am unable to do these tests in the right time.

The correction in dev branch is the first step, but we need to release a critical bug correction as soon as it is possible.

[u-fischer]

I don't see when you are preparing a new version

You can watch the repo and run your tests when they are commits in the dev branch. luaotfload can be easily installed with l3build.

[olsak]

I have no time for continuously "watch the repo". This is full time job. More friendly seems to add some OpTeX tests to your tests which you run before release.

[josephwright]

@olsak Writing tests is usually the barrier, not running then: some suggestions would be useful - as non of the team looking after luaotfload are familiar with specifics for OpTeX. (I might have to check on l3build and OpTeX: that should I think work but is not currently checked.)

[u-fischer]

@olsak

I have no time for continuously "watch the repo".

You can setup some github action to automate the watching.

This is full time job. More friendly seems to add some OpTeX tests to your tests which you run before release.

I don't have the time nor the skill to write OpTeX tests, and I have neither the time nor the skill to debug them if they fail as I don't know anything about OpTeX.

[zauguin]

Do you have some repository where we can trigger a pipeline whenever we push something? Then you can manage some relevant tests there and they automatically run whenever something changes.

[olsak]

I have repositories at github, of course. But I don't know what does mean "we can trigger a pipeline".

Sorry, my OpTeX tests are only imperfectly. My script runs OpTeX over a set of normal documents and I must to see if there is a suspicious change in log files. In this case, some math text causes Overful/Underful boxes while not before.

In this case, I get the bug report from many OpTeX users first, when I returned from my vacation. :(

The question is: how long we must to wait to the new release of luaotfload package where this critical bug will be corrected.

Now, I added a red text to main web page http://petr.olsak.net/optex/ and additional information about it. Unfortunately, I can't do more.

[olsak]

trigger a pipeline

Maybe, it would be enough to contact me if you decides a core design change. I suppose that somebody from you decided that "mathsize" font feature will be cancelled from luaotfload. If I knew about such decision sufficiently in advance, I can say: no, OpTeX is based on this feature.

[u-fischer]

Maybe, it would be enough to contact me if you decides a core design change. I suppose that somebody from you decided that "mathsize" font feature will be cancelled from luaotfload.

No, we didn't decide a core design change. We imported a new fontloader version from context and that has this part commented (in fontloader-font-otl.lua) and we didn't overwrite it.

If I knew about such decision sufficiently in advance, I can say: no, OpTeX is based on this feature.

As I already wrote: I have neither the time nor the skill to decide if such a change affects OpTeX or not. So if you want warnings, implement suitable tests and watch the repository. Or use your own independent fontloader.

[olsak]

We imported a new fontloader version from context and that has this part commented (in fontloader-font-otl.lua) and we didn't overwrite it.

OK. I understand that this was work of Hans Hagen. But where is the time for testing luaotfload? I see that the commit of the file fontloader-font-otl.lua was done two weeks ago at dev branch and the luaotfload was released two weeks ago too. Coincidentally I was at my vacation (off-line, of course) at this time...

[zauguin]

how long we must to wait to the new release of luaotfload package where this critical bug will be corrected.

I will upload a new release today, so it will probably be in TeX Live roughly tomorrow evening.

But where is the time for testing luaotfload?

Generally we rely on automated testing. Especially fontloader updates (for which we don't have any changelog beside seeing the code diff) are mostly tested though l3build.

If you write some stable, well-behaving tests which integrate into our setup I don't see any issue with adding some optex tests there.