-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URGENT: Critical error with GDEF table #2
Comments
The OTF doesn't have a problem, though |
@erinmclaughlin ping |
@erinmclaughlin any luck with this? :) |
Hey! I contacted Nicolas, who said he'd only be available this weekend to take a look. I'm sorry I've been so busy! Now... trying to get the Bengali thing done :)On March 18, 2016 at 1:19 AM Dave Crossland notifications@github.com wrote:@erinmclaughlin any luck with this? :)—You are receiving this because you were mentioned.Reply to this email directly or view it on GitHub |
Okay cool :) We can't launch Hubballi without it, but anytime early next
week is good :)
|
I am on it now, just read what the issue is. I will take a look to it |
I think that the issue is that there is not base glyph class defined in the GDEF |
Fixed in 6e248b2 |
@erinmclaughlin I'm sad to say that the error persists in the latest TTF :(
|
I will take a look to see what is defined in the feature file, what is in fact compiled in the font, and what makeotf is being used. Sent from my iPhone
|
oh my GOSH I must be going insane... I must not have hit save after I changed the GDEF the last time. I am so so so sorry for wasting your time, both of you!! Ok I just uploaded a revised version with new fonts generated |
You are more than welcome Best, Nicolás
|
It is not working:
|
Thanks boss!! :D
|
Very good suggestion, thank you so much Nicolas :) I just cleaned it up. Want to give this a try, Dave? |
I'm sorry to say it is still not working.
Are you able to reproduce this yourself? Here is how to install it:
|
Hey Dave! I just rebuilt the font in RoboFont with a fresh file, and the .ttf wouldn't generate. Which is actually perhaps a good thing, as it can maybe help us figure out what's going on. Here's the error. Can you translate this into English for me? :) hehee
|
On 30 March 2016 at 15:12, Erin McLaughlin notifications@github.com wrote:
You have a string somewhere that is not ASCII, perhaps in the POST table. |
Ok! Must have had an emdash instead of a hyphen or something, no clue, but it's generating now. Can you try the new test fonts in the Generated Test Fonts folder? |
It is still broken :(
|
I've also noticed that at some point along the way, my "lookupflag IgnoreMarks;" virama fix stopped working, too. :( Aghghhh. I'll keep backtracking and try to figure it out :( I totally don't understand why this font doesn't work, but my others do... |
Hey Dave! Ok, so I tried recreating Hubballi in Glyphs, and exported a .ttf from that. I also brought the Glyphs-built .UFO back into Robofont and exported that again. Could you open the generated fonts folder and test all three of the .ttfs? Do any of those work in the validator? The only problem now is that I still am not getting the virama issue to work. It might be because I'm unsure of how to set up the GDEF in Glyphs. I created a custom GlyphData.xml file to assign the non-unicode Kannada glyphs to either "Letter" or "Mark" categories, but that didn't seem to do the trick. Can you point me where to look for this? |
These 2 are broken:
But this one basically works; the max_zones issue can be hotfixed with ttx.
This is not a problem, and ot can 'hotfix' it like this:
|
I'm not so familiar. I think James Puckett or Nicolas would know. |
Yay! A tiny shred of progress! I'll ask them :) |
update: Georg is helping me with this... inching closer :) |
Maybe if you use the flag IgnoreMark in a feature, try to defined a markClass, otherwise the OT compiler won’t have the information to write the MarkAttachClassDef table, that is required when the OT Layout shaping hit a lookup with “ignore Marke” flag. |
The current OTF seems working:
|
@erinmclaughlin Open Terminal, and go to the directory in which the fonts are, something like:
type Then type the following command in order to inject the GDEF of the OTF into the TTF:
That will work. Attached a TTF that pass OTS |
@zar-nicolas20 Hi Nicolas! Thanks so much for keeping an eye on this and continuing to help!! I appreciate it SO much. |
Maybe I just need to find some examples of recently-generated fonts that have unusual marks and "ignoremarks" lookups that actually pass the test, so I can see what I'm doing wrong... |
No anchors, hmm that changes everything. The script that I passed you dumps the GDEF from the OTF and merge it to the TTF. Try to generate a OTF in which the Virama works, then generate a TTF and use the script that I send you, one time writing GDEF and a second time writing GSUB. Best, Nicolás
|
I type wrong the command, tomorrow I will fix it |
First check if your OTF is working as expected, if so, in addition to inject the GDEF from the OTF into the TTF, you can also inject the GDEF and GSUB, the way to do that will be the following;
And press enter. |
Darn! Still didn't work. So maybe this does have to do with the construction of the glyphs, that I didn't use anchors with these marks? Luckily, Georg was able to recreate my file in Glyphs and did some alterations to the GlyphData.xml so that it's now working. I still wish that we could figure out why it's not working in Robofont! Maybe someday we can revisit this when we have more time! Thank you SO SO much for helping me. |
What's the latest status of this? :) |
I saw that the TTF lacks GDEF at all. That is the problem with font parser. Besides that I think Erin is working with something with Virama and an ignore mark flag in a lookup. I post a work around merging the GDEF of the OTF into the TTF using TTX. Best, Nicolás
|
Hi guys! The font export is working from glyphs - I was cleaning up file, re-composing accented glyphs. So sorry for delay, will update this as soon as I can, hopefully tonight On April 14, 2016 at 11:34 PM José Nicolás Silva Schwarzenberg notifications@github.com wrote:I saw that the TTF lacks GDEF at all. That is the problem with font parser. Besides that I think Erin is working with something with Virama and an ignore mark flag in a lookup. I post a work around merging the GDEF of the OTF into the TTF using TTX. Best, Nicolás > On Apr 14, 2016, at 12:45 PM, Dave Crossland notifications@github.com wrote: > > What's the latest status of this? :) > > — > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub > —You are receiving this because you were mentioned.Reply to this email directly or view it on GitHub |
Hi Dave, sorry again for the lateness. One setback (among other life things) is that when Georg re-created my file in Glyphs, sidebearings got all messed up and kerning didn't come along with it. Having to find/replace all of the glyphnames to match what is used in Glyphs. Taking a long time :) I will try to be finished with it tonight. |
thanks erin!! :)
|
To reproduce:
Currently this fails with:
This is fatal and means the font won't work in Chrome and Firefox.
The text was updated successfully, but these errors were encountered: