petaluma
petaluma copied to clipboard
steinbergmedia
Petaluma music font, licensed under the SIL Open Font License
Multi-line text displays differently on Windows and Mac, and not just in Dorico, but in other programs like in Microsoft Word, causing line spacing inconsistencies depending on which OS was...
In the Petaluma.json file ("fontVersion": 1.12), there are codepoints referenced, for example, in the "optionalGlyphs" section (and "ligatures"), that do not exist in the Petaluma.otf font (I checked Version 1.064...
In SMuFL 1.4, the [Extended Helmholtz-Ellis Just Intonation](https://w3c.github.io/smufl/releases/1.4/tables/extended-helmholtz-ellis-accidentals-just-intonation.html) range was updated: see [SMuFL #126](https://github.com/w3c/smufl/issues/126). We need to make the corresponding changes to Petaluma to bring it in line with the...
The combinations of "Fö" änd "Fä" don't work out well with the current kerning values. "Fö" are too tight, causing the left "ö" dot collide with "F" roof line. "Fä",...
In processing json metadata and reading the glyphBBoxes data, one step that needs to happen is to get a codepoint for the named glyph, and that can either come from...
The spacing of the lines in the sharp symbol ought to be spread out more. I had someone misunderstand it as a half-sharp. Here's Petaluma's sharp at a modest size...
I implement a score rendering and for testing I switch between Bravura and Petaluma. So here I noticed, that ledgerLine returns the glyph for accidentalDoubleFlat, ledgerLineWide seems off as well....
The metadata for Petaluma does not contain any sets. This is potentially problematic: If I would like to use the small flag for eight notes, there is currently no reliable...
When using the font with the metadata.json I got an error with glyph E262 (accidentalSharp) saying that one of the cutOut point is outside the bounding box of the glyph...
Metadata
Owner
Metadata
Petaluma music font, licensed under the SIL Open Font License