when I create anchor-based composites, e.g. with the i base, they automatically get LSB: lsb(idotless), RSB: rsb(idotless).
When I then create an anchor-based composite imacronbreve (imacron+brevecomb), breve is shifted to the left:
When I create an anchor-based composite imacronbreve (idotless+macroncomb+brevecomb), all looks OK.
It seems that it might have sth to do with LSB: lsb(idotless)? Then, when I select several i-based composites to change LSB: lsb(idotless), RSB: rsb(idotless) to base(), I cannot change both: when I input base() for LSB, RSB changes to a number, and vice versa. (But the position of breve is correct in imacronbreve=imacron+brevecomb.)
If those are all composites, then they will all use the values according to their individual base glyph. If it all works as expected, it will eventually replace the current lsb(…) and rsb(…) expressions.
PART I works OK now. Thank you for fixing that
PART II still doesn’t though.
What happens when you paste base() to LSB and RSB of several glyphs selected at the same time?
That was actually my question for Bhikkhu Pesala about the issue from an earlier post:
when I select several i-based composites to change LSB: lsb(idotless), RSB: rsb(idotless) to base(), I cannot change both: when I input base() for LSB, RSB changes to a number, and vice versa
Also, I think this update introduced some changes to preferred anchor names:
We will make some changes, so the next update of FontCreator will prefer common anchor names, thus ones that contain top, bottom, ogonek, etc over unknown names.
Because suddenly ogonekcomb, which was using ogonek anchor, now appears to use something else:
That is true, as that fix is included in 4041. Now top is top priority, then bottom, etc. Since your ogonekcomb contains both bottom and ogonek anchors, it uses bottom. Why does it contain bottom anchors?
Sorry - I see what you mean. Ye, there’s a better way!