Embed Error

[loganheffernan2]

Hey @brycewilner,

Running into an odd error w/ Standard — when the type is embedded in PowerPoint and saved for editing (settings shown in the first attached image), the program spits back a "General Failure" (see attached) error when opening the file on a system that does not have Standard installed locally.

We tried to correct this in a handful of ways: converting the typeface with software designed to remove use restrictions, re-exporting the font from FontForge with the "Embeddable" option set to "Editable," and even copy-pasting all of the glyphs/kerning/etc. into a new Glyphs and subsequent TTF and OTF.

This leads us to think that it must be an encoding error of sorts — wondering if you have any input or possible fixes.

Thanks!

[brycewilner]

Hi, Logan Thanks for your message and your interest in the typeface. This error is a new one for me. I don’t have much PowerPoint experience. I design type in RoboFont, a program that has, by default, its OpenType permissions set to “No embedding restrictions.” This setting works well with most word processing/design apps, but occasionally snags with apps I don’t use often. I just pushed a version of Standard to my Github repository <https://github.com/brycewilner/Standard> that has the settings switched to “Editable embedding allowed”. Could you download/install the updated version and give that a shot? If not that, maybe an unsatisfactory solution would be installing Standard on the machine to which you’re sending the PP file.

…

On Tue, Jun 30, 2020 at 2:29 PM loganheffernan2 ***@***.***> wrote: Hey @brycewilner <https://github.com/brycewilner>, Running into an odd error w/ Standard — when the type is embedded in PowerPoint and saved for editing (settings shown in the first attached image), the program spits back a "General Failure" (see attached) error when opening the file on a system that does not have Standard installed locally. We tried to correct this in a handful of ways: converting the typeface with software designed to remove use restrictions, re-exporting the font from FontForge with the "Embeddable" option set to "Editable," and even copy-pasting all of the glyphs/kerning/etc. into a new Glyphs and subsequent TTF and OTF. This leads us to think that it must be an encoding error of sorts — wondering if you have any input or possible fixes. Thanks! [image: Screen Shot 2020-06-30 at 2 15 56 PM] <https://user-images.githubusercontent.com/62774086/86163235-f50c8a80-badd-11ea-863b-2339f6101704.png> [image: Screen Shot 2020-06-30 at 2 15 43 PM] <https://user-images.githubusercontent.com/62774086/86163248-f9d13e80-badd-11ea-8e60-7f8789a3d3fc.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4H6E4VTXVB5T6OPGC7AHTRZIVH5ANCNFSM4OMRB22A> .

-- Bryce Wilner

[bghryct]

Heya @brycewilner if you upload source ufo's I'd be happy to take a second look at permissions, as well as doing the work I proposed in the linked issue. #2

[loganheffernan2]

@brycewilner Thank you — the new files embed with no problem. Peace!

[brycewilner]

+++