The baseline on the 7-limit sharp alteration should actually be where the blue arrow is on the attached file. Learning the Lua script is next on the list, once this piece is done.Įdit: This doesn’t actually solve everything, in part because the baselines with Bravura’s Helmholtz-Ellis notation aren’t all correct. Thanks a lot! Just switched from Lilypond after ~9 years of developing all sorts of extensions and custom Scheme scripts, and so far I dig it. You can move the glyphs so that their base point is on the baseline, ie, their point has a y value of 0. If you look at the emsize, its likely 1,000, and typically there are 200 units below the baseline and 800 units above. Attaching a screenshot of the Tonality Editor window as well, so you can clearly see that the undecimal 1/4-tone sharp is the “primary” accidental. The baseline is where y '0' in the cartesian grid system of the 'em square'. The center of the grace note is aligned with the center of the accidental, and you can see that the Y-offset from the middle-right of the main accidental (the quarter-tone sharp) positions the flat in the same place both times. Attachment settings are “from Middle Right,” “to Bottom Left,” and Y-offset is 7.0. Not all applications support extension lookups. This means FontForge must use an extension lookup to output it. Lookup mark Mark Positioning lookup 7 has an offset bigger than 65535 bytes. The original bug was about X-spacing, so making sure the Attachment Settings let you enter a very small X-offset would naturally fix the spacing-scaling error.Īs a more dramatic example, I’ve attached an example where I created the accidentals left-to-right. In the FontForge coordinate system, the baseline is at their 0 point on their vertical access. pdf2htmlex snapshot 20140323 fontforge 0101 https. My guess is that the reason that the fix (re-creating the accidentals in a different order) works is because the default attachment settings assume left-to-right entry, so your X-offset is 0.0 or at most 1.0 for minimal spacing.
What did fix my problem was making sure that the attachment settings were “baseline” rather than “center.” But I think that only fixed it because then the Y-offset could be 0.0, so there was no scaling problem to be had. I did find a workaround that makes the problem less severe, but I’m pretty sure there’s still a bug. This didn’t actually straight-out fix my problem (though it did give me hope). When you hit the OK button, you get a big window with some parameters on top, two lists of classes, and a matrix below. I couldn’t find that one searching for some reason.
0 kommentar(er)
