-
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
Corrupt 'loca' table after convert #11
Comments
Confirmed, this is because the font file doesn't have a We only rebuild the |
I think we actually shouldn't emit loca at all in this case. Can you try with the latest commit in master? |
Thank you for the patch. libeot/eot2ttf font1.fntdata font1.ttf
has table: CFF
has table: DSIH
has table: GDEF
has table: GPOS
has table: GSUB
has table: OS/2
has table: cmap
has table: head
has table: hhea
has table: hmtx
has table: maxp
has table: name
has table: post When I'm trying to install eot2ttf with |
I am able to open the resulting font in fontforge. It will take me a bit longer to investigate why it doesn't work in gnome-font-viewer or libreoffice. I'll leave this issue open in the meantime. The issue with |
ots-sanitize is able to fix the font. It gives a sudo apt-get install opentype-sanitizer
ots-sanitize font1.ttf font1-santized.ttf
WARNING: wrong sfntVersion for glyph data
File sanitized successfully!
|
The eot is otf. this PR fixes the magic number #2 and output a working font. |
Hi @pablopla , can you try with the Also, are you able to share the .eot ? |
It works. Thank you. Can you please tag a new release? It might help distros to update their libeot version. |
I'm trying to convert the attached eot file from a pptx presentation with libeot latest commit.
The ttf font doesn't open in Debain 12 and 'fonttols ttx font1.ttf' gives me a warning:
WARNING: corrupt 'loca' table, or wrong numGlyphs in 'maxp': -1 1151
font1.zip
Is there something wrong with the original font or the conversion?
Is it possible to fix the loca table in the ttf font?
The text was updated successfully, but these errors were encountered: