Music Fonts - Editing and Saving

[as_above01]

Dear Forum,

     I'm using fontlab to design a new font that I can use in music engraving with the program Sibelius.  I'm opening one of the Sibelius fonts (inkpen2.dfont) to use as a template - in this way I figure I can integrate the newly designed font in the notation software in a way that works with it.
     Well, I've been having a hell of a time.  After experimenting with it quite a bit, and searching a lot, I've come up empty handed.  What it generally boils down to is this: when I open the font the unicode information does not appear to come with it.  It opens the file in the coded-pages mode-of-view for the font, which has a bunch of F043...etc.  If I go to the unicode view mode, all of the characters are after the "---" at the end, and are not assigned any unicode values.  I've tried what seems like almost every option to open the file with that information or generate the information after it's been opened, but nothing has worked. 
     If I open the font in FontForge it opens with the unicode information, it seems.  If I open inkpen2 in Fontlab, save it as inkpen3 right away, and open inkpen3 in FontForge, the unicode information is gone (which is why I suspect it is not working with the software)
     The font comes for free with sibelius scorch or you can download it here to check it out:

http://www.4shared.com/file/64781375/cb7e6fec/Inkpen2.html

     I'd be grateful for any help, I'm at my wits end.

-james

[Alex Petrov (FontLab)]

James,
I've downloaded the font which appears to have glyphs encoded with MS Windows Symbol codepage. It opens normally in Fontlab Studio. What do you call "the unicode information"?

[as_above01]

Hi,

     Thanks for the response.  When I open the font in FontForge the glyphs are associated with keys.  When I open it in FontLab, indeed the glyphs are present, but when I save the file under a different name and open the new file in FontForge all of the glyphs are at the bottom under question marks instead of associated with keys, and this makes it impossible for the music program to read the font. 
     Perhaps I'm re-saving in FontLab in an incorrect format, but if memory serves me I've tried them all.  Either it's opening it without the information associating the glyphs with characters/keystrokes, or when I save it it does not save that information with it.  I've been unable to hunt down where the error is occurring, despite hours and hours of trial and error.

 

-j

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics