- From: Douglas Blumeyer <douglas.blumeyer@gmail.com>
- Date: Wed, 29 Apr 2020 16:43:29 -0700
- To: Daniel Spreadbury <D.Spreadbury@steinberg.de>
- Cc: "public-music-notation-contrib@w3.org" <public-music-notation-contrib@w3.org>
- Message-ID: <CAEEs2ALBYieX5pM36xTqtpuu6Fj=CvDVenLxnzeYtJdR+djApw@mail.gmail.com>
Thank you for the speedy reply, Daniel. Issue #25 on Bravura's GitHub repo was opened by yours truly :) I will open another issue there soon when the Sagittal updates are ready. On Wed, Apr 29, 2020 at 8:41 AM Daniel Spreadbury <D.Spreadbury@steinberg.de> wrote: > Thanks for getting in touch, Douglas. > > > > The issue with WOFF2 fonts not having the correct font tables to make the > combining positions work properly is an open issue in Bravura’s GitHub > repository, issue #25. I’ve not yet had a chance to look into this, but my > suspicion is that it’s a tooling issue: I use a tool called FontPlop to > convert the OTF produced by FontLab into EOT, WOFF and WOFF2. > > > > If any community group members who are expert in converting fonts into > web-friendly formats have any suggestions for alternative tools that would > produce better results, I’d love to hear them. > > > > But to answer the perhaps most pressing issue: if you would like to > contribute updated versions of the Sagittal accidentals to Bravura, that’s > great, and I’d certainly be interested to take a look at them. Since this > is really a Bravura issue rather than strictly speaking a SMuFL one, I > suggest you open an issue in the Bravura repository and we can take it from > there: > > > > https://www.github.com/steinbergmedia/bravura > > > > All the best, > > > > Daniel > > > > *From: *Douglas Blumeyer <douglas.blumeyer@gmail.com> > *Date: *Tuesday, 28 April 2020 at 22:23 > *To: *"public-music-notation-contrib@w3.org" < > public-music-notation-contrib@w3.org> > *Subject: *Trouble generating Bravura Text / submitting to Bravura > *Resent from: *<public-music-notation-contrib@w3.org> > *Resent date: *Tuesday, 28 April 2020 at 22:22 > > > > Hello, > > > > I am a new member here. Thank you all in advance for being patient with me > as I ramp up. > > > > I have searched the archives already (including the older archives on > Nabble) but haven't found what I'm looking for yet. > > > > This is my situation: I am a volunteer contributor to the Sagittal > microtonal music notation system (http://sagittal.org/). I am working on > submitting both new and updated Sagittal glyphs to Steinberg via an updated > Bravura font. Before I finalize my submission, however, I want to ensure > that the vertical positioning of my glyphs is just right with respect to > staff lines. I am familiar with Bravura Text's ligatures using > combining staff position characters ( > https://www.w3.org/2019/03/smufl13/tables/combining-staff-positions.html). > However I am unable to generate new versions of Bravura Text using leading > font editing software such as FontForge and FontLab; even without making > any changes to Bravura Text, exporting or generating the font leads to > invalid files (unable to be installed) which have much larger file sizes > than they should. I am able to export/generate new versions of Bravura just > fine; it is only Bravura Text which I cannot create new versions of. > Bravura does not give the ability to test the combining staff position > ligatures to be able to test my new and updated glyph's vertical > positioning, which is why I need to be able to copy my new and updated > glyphs over from Bravura into Bravura Text. > > > > So questions related to this situation are: > > 1) Is there a better way (than creating a new version of Bravura Text) to > confirm whether my new and updated glyphs will have the correct vertical > positioning relative to the staff lines? Am I missing something fundamental > about how to contribute to Bravura? > > 2) If not, has anyone else had this kind of technical trouble generating > new versions of Bravura Text? > > > > On a related note, the ligatures for Bravura Text do not work for me with > the web font versions. The .woff file included in the GitHub > release includes the ligature glyphs, however the lookup tables mapping the > pairs of code points to these ligature glyphs are missing. I thought it > might be as easy as restoring the ligature lookup tables, but my attempts > were inconclusive -- again, because I cannot generate new versions of the > Bravura Text font using the font editing software applications I have > tried, whether through their UI's or their scripting tools. I suspect, > given how elaborate the installation process for Bravura and Bravura Text > is, that something more complex is happening in these fonts that I don't > know enough about yet to account for. > > > > Thank you again for your patience and for any guidance you can provide me. > > > > Best, > > Douglas Blumeyer > > Product Marketing Manager > Phone: +44 20 3696 1811 > > *Steinberg Media Technologies GmbH* > Beim Strohhause 31, 20097 Hamburg, Germany > > President: Andreas Stelling | Managing Directors: Masahiro Ikeda, Jun > Nishimura > Registration Court: Hamburg HR B 86 534 | VAT ID: DE118677139 > > Visit the Steinberg website <http://www.steinberg.net> or connect with us > on Facebook <http://www.facebook.com/Steinberg>, Twitter > <http://twitter.com/steinbergmedia>, Instagram > <http://www.instagram.com/steinbergmedia> and SoundCloud > <http://www.soundcloud.com/steinbergmedia>. > Watch our Cubase <https://www.youtube.com/cubase>, Dorico > <https://www.youtube.com/dorico>, Mobile Apps > <https://www.youtube.com/mobile_apps_steinberg>, Nuendo > <https://www.youtube.com/nuendo>, Steinberg > <https://www.youtube.com/user/SteinbergSoftware>, Audio Interfaces > <https://www.youtube.com/audiointerfaces>, VST Instruments & Plug-Ins > <https://www.youtube.com/VSTinstrumentsplugins> and WaveLab > <https://www.youtube.com/WaveLab> videos on YouTube. >
Received on Wednesday, 29 April 2020 23:43:55 UTC