Skip to content
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.

Sign up for GitHub

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

Jump to bottom

maxp: Bad maxZones: 0 warning is reported by firefox looks good in chrome and edge #83

Open
gatlesan opened this issue Dec 4, 2020 · 1 comment
Open

maxp: Bad maxZones: 0 warning is reported by firefox looks good in chrome and edge #83

gatlesan opened this issue Dec 4, 2020 · 1 comment

Comments

@gatlesan
Copy link

gatlesan commented Dec 4, 2020

We are using a script using fontmin: 0.9.8 to convert ttf files to woff/woff2 when we use the converted version rendering works fine but it looks like firefox throws,

downloadable font: maxp: Bad maxZones: 0 (font-family: "myFirstFont" style:normal weight:400 stretch:100 src index:0) source: converted-from-ttf.woff warning
@edent
Copy link

edent commented Jun 1, 2022

As per mclemente/fvtt-module-polyglot#64 this is caused by having a space between the property name and value.

Change:
(font-family: "myFirstFont"

To:
(font-family:"myFirstFont"

That is, remove the space character after the :

ericfortmeyer pushed a commit to ericfortmeyer/ericfortmeyer.dev that referenced this issue Apr 23, 2023
remove space between property name and value
2ba2102 
See ecomfe/fontmin#83.

Fixes `downloadable font: maxp: Bad maxZones: 0...`
@ericfortmeyer ericfortmeyer mentioned this issue Apr 23, 2023
Merged
@kkdaisuki kkdaisuki mentioned this issue Jul 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@edent @gatlesan