FiraSans and FiraMono appear blank #10

gyscos · Apr 14, 2015

Similar to:
https://code.google.com/p/googlefontdirectory/issues/detail?id=368 and https://code.google.com/p/googlefontdirectory/issues/detail?id=407

Both the FiraSans and the FiraMono fonts appear buggy, since they only result in blank characters.

https://github.com/mozilla/Fira

FiraSans-Medium.ttf size from google/fonts:
158552 bytes

FiraSans-Medium.ttf size from mozilla/Fira:
401304 bytes

Other files have the same kind of disrepancy. Maybe a copy went wrong?
(Although FiraSans-LightItalic.ttf appears to work, and also has a different file size, so that may not mean much.)

gyscos · Apr 14, 2015

FiraSans-Medium.ttf size from google/fonts:
158552 bytes

FiraSans-Medium.ttf size from mozilla/Fira:
401304 bytes

Other files have the same kind of disrepancy. Maybe a copy went wrong?
(Although FiraSans-LightItalic.ttf appears to work, and also has a different file size, so that may not mean much.)

mozilla/Fira is a newer version of the font with significantly more Unicode coverage and better line spacing. Should probably be updated here regardless.

codeman38 · Apr 14, 2015

mozilla/Fira is a newer version of the font with significantly more Unicode coverage and better line spacing. Should probably be updated here regardless.

Yep 4.1x just came out so I'm due to do this soon!

mozilla/Fira#110

davelab6 · Apr 14, 2015

Yep 4.1x just came out so I'm due to do this soon!

mozilla/Fira#110

any news?

Mte90 · Jun 22, 2015

any news?

Same issue with this website using Fira Sans which is blank on my machine : http://firefox-dev.tools

Delapouite · Jun 28, 2015

Same issue with this website using Fira Sans which is blank on my machine : http://firefox-dev.tools

Same issue only in IE9, in Windows Vista and 7 for me. Fira Sans displays blank.

jkbyln · Jul 24, 2015

Same issue only in IE9, in Windows Vista and 7 for me. Fira Sans displays blank.

any news about this?

Mte90 · Sep 14, 2015

any news about this?

The version hosted by Mozilla doesn't have the rendering bug:
https://github.com/mozilla/Fira

jkbyln · Sep 14, 2015

The version hosted by Mozilla doesn't have the rendering bug:
https://github.com/mozilla/Fira

Appears to be still buggy...

Schweinepriester · Oct 9, 2015

Appears to be still buggy...

any news??

Mte90 · Nov 2, 2015

any news??

If updating the font is not possible, maybe it could at least be removed from the repository so it doesn't conflict with the individual, valid font?

gyscos · Nov 2, 2015

If updating the font is not possible, maybe it could at least be removed from the repository so it doesn't conflict with the individual, valid font?

I will update this; its tricky because I need to be careful about regressions. Also now Fira has so many styles, and I don't think I reached an agreement with the GF team on how to onboard them. Thanks for your patience.

davelab6 · Nov 3, 2015

I will update this; its tricky because I need to be careful about regressions. Also now Fira has so many styles, and I don't think I reached an agreement with the GF team on how to onboard them. Thanks for your patience.

Font still displayed as blank (whitespace) in the latest Firefox 43.0.4.

nekromoff · Jan 9, 2016

Font still displayed as blank (whitespace) in the latest Firefox 43.0.4.

Failing with iceweasel 43.

damiadev · Jan 14, 2016

Failing with iceweasel 43.

any news?

Mte90 · Jan 18, 2016

any news?

Is there an update on this? This hasn't font hasn't been working for me for at least a year...(Fedora 22, Fedora 23, OpenSuse 13.2)

My two cents: either remove Fira from this repo, or use the version from https://github.com/mozilla/fira. Is there any chance of an update on this situation?

krrg · Feb 3, 2016

Is there an update on this? This hasn't font hasn't been working for me for at least a year...(Fedora 22, Fedora 23, OpenSuse 13.2)

My two cents: either remove Fira from this repo, or use the version from https://github.com/mozilla/fira. Is there any chance of an update on this situation?

I've put https://github.com/google/fonts/compare/master...davelab6:ofl/firasans-v4.106g?expand=1 up and will check with Mozilla that its good to go

davelab6 · Feb 3, 2016

I've put https://github.com/google/fonts/compare/master...davelab6:ofl/firasans-v4.106g?expand=1 up and will check with Mozilla that its good to go

Fixed in 79d9ee2

davelab6 · Feb 6, 2016

Fixed in 79d9ee2

@davelab6 When will the fix be released?

enoch85 · Feb 6, 2016

@davelab6 When will the fix be released?

I have a minor update to make and that going well it may go live on Wedneday

davelab6 · Feb 6, 2016

I have a minor update to make and that going well it may go live on Wedneday

I found that the vertical metrics shift in some browsers so I'll make another update this week, to go live next week.

davelab6 · Feb 10, 2016

I found that the vertical metrics shift in some browsers so I'll make another update this week, to go live next week.

@davelab6 Any update here? Just updated to latest stable on Debian, still same issue. Currently using Opera to browse my own website, but want to use Chrome ofc...

enoch85 · Feb 26, 2016

@davelab6 Any update here? Just updated to latest stable on Debian, still same issue. Currently using Opera to browse my own website, but want to use Chrome ofc...

@davelab6 Thanks for your efforts on this, but it's been a month now since the last update here. What's going on?

enoch85 · Mar 15, 2016

@davelab6 Thanks for your efforts on this, but it's been a month now since the last update here. What's going on?

I've postponed working on this until I've finished working on new upcoming projects.

davelab6 · Mar 15, 2016

I've postponed working on this until I've finished working on new upcoming projects.

@davelab6 Ok, thanks for the update. Do you have any ETA?

enoch85 · Mar 15, 2016

@davelab6 Ok, thanks for the update. Do you have any ETA?

Found out about this issue today; using Windows 7, fonts do not appear at all in Chrome and some characters are missing in Internet Explorer 9.

bhulsman · Mar 22, 2016

Found out about this issue today; using Windows 7, fonts do not appear at all in Chrome and some characters are missing in Internet Explorer 9.

I've switched to using Fira Sans from Mozilla CDN until this is resolved. It's not anywhere as optimised at the Google Fonts version, but at least no rendering issues.

jace · Mar 24, 2016

I've switched to using Fira Sans from Mozilla CDN until this is resolved. It's not anywhere as optimised at the Google Fonts version, but at least no rendering issues.

Seriously, people? How come it's been 1.5 years since report and still no fix?

gonzalocasas · Nov 23, 2016

Seriously, people? How come it's been 1.5 years since report and still no fix?

@davelab6 Hey, I'll be tackling Fira this week.

We have a tonne of variants and weights here. I propose we do the following so the fonts are GF api friendly:

Get rid of the two, four and eight family variants. These family variants are for the Hairline weights only. They're like optical weights in printing. They add extra weight, depending on what size they're used. Imo, this is fiddly. A more elegant solution is to use variable fonts. If people object, I can include them.
Remapping
We have the following weights:

'FiraSans-Hair.ttf'
'FiraSans-Thin.ttf'
'FiraSans-UltraLight.ttf'
'FiraSans-ExtraLight.ttf'
'FiraSans-Light.ttf'
'FiraSans-Book.ttf'
'FiraSans-Regular.ttf'
'FiraSans-Medium.ttf'
'FiraSans-SemiBold.ttf'
'FiraSans-Bold.ttf'
'FiraSans-ExtraBold.ttf'
'FiraSans-Heavy.ttf'
'FiraSans-Ultra.ttf'

We should do this:

'FiraSans-Hair.ttf' -> 'FiraSansHairline-Regular.ttf'
'FiraSans-Thin.ttf' -> 'FiraSans-Thin.ttf'
'FiraSans-ExtraLight.ttf' -> 'FiraSans-ExtraLight.ttf'
'FiraSans-Light.ttf' -> 'FiraSans-Light.ttf'
'FiraSans-Regular.ttf' -> 'FiraSans-Regular.ttf'
'FiraSans-Medium.ttf' -> 'FiraSans-Medium.ttf'
'FiraSans-SemiBold.ttf' -> 'FiraSans-SemiBold.ttf'
'FiraSans-Bold.ttf' -> 'FiraSans-Bold.ttf'
'FiraSans-ExtraBold.ttf' -> 'FiraSans-ExtraBold.ttf'
'FiraSans-Heavy.ttf' -> 'FiraSans-Black.ttf'
'FiraSans-Ultra.ttf' -> 'FiraSansUltra-Regular.ttf'


Weights removed: Book, Ultra Light,
Weights renamed: Hair, Heavy, Ultra

@davelab6 @patrykdesign What are your thoughts on this?

I was very happy with the Mono fonts. Also, the otf folder includes condensed fonts. They're not present in the ttf folder.

m4rc1e · Nov 28, 2016

@davelab6 Hey, I'll be tackling Fira this week.

We have a tonne of variants and weights here. I propose we do the following so the fonts are GF api friendly:

Get rid of the two, four and eight family variants. These family variants are for the Hairline weights only. They're like optical weights in printing. They add extra weight, depending on what size they're used. Imo, this is fiddly. A more elegant solution is to use variable fonts. If people object, I can include them.
Remapping
We have the following weights:

'FiraSans-Hair.ttf'
'FiraSans-Thin.ttf'
'FiraSans-UltraLight.ttf'
'FiraSans-ExtraLight.ttf'
'FiraSans-Light.ttf'
'FiraSans-Book.ttf'
'FiraSans-Regular.ttf'
'FiraSans-Medium.ttf'
'FiraSans-SemiBold.ttf'
'FiraSans-Bold.ttf'
'FiraSans-ExtraBold.ttf'
'FiraSans-Heavy.ttf'
'FiraSans-Ultra.ttf'

We should do this:

'FiraSans-Hair.ttf' -> 'FiraSansHairline-Regular.ttf'
'FiraSans-Thin.ttf' -> 'FiraSans-Thin.ttf'
'FiraSans-ExtraLight.ttf' -> 'FiraSans-ExtraLight.ttf'
'FiraSans-Light.ttf' -> 'FiraSans-Light.ttf'
'FiraSans-Regular.ttf' -> 'FiraSans-Regular.ttf'
'FiraSans-Medium.ttf' -> 'FiraSans-Medium.ttf'
'FiraSans-SemiBold.ttf' -> 'FiraSans-SemiBold.ttf'
'FiraSans-Bold.ttf' -> 'FiraSans-Bold.ttf'
'FiraSans-ExtraBold.ttf' -> 'FiraSans-ExtraBold.ttf'
'FiraSans-Heavy.ttf' -> 'FiraSans-Black.ttf'
'FiraSans-Ultra.ttf' -> 'FiraSansUltra-Regular.ttf'


Weights removed: Book, Ultra Light,
Weights renamed: Hair, Heavy, Ultra

@davelab6 @patrykdesign What are your thoughts on this?

I was very happy with the Mono fonts. Also, the otf folder includes condensed fonts. They're not present in the ttf folder.

@m4rc1e Hey, yes some of the weights are experimental. So the mapping should go as follows for CSS weighting...

Thin (22em / CSS 100)
UltraLight (34em / CSS 200)
Light (58em / CSS 300)
Regular (92em / CSS 400)
Medium (128em / CSS 500)
SemiBold (142em / CSS 600)
Bold (158em / CSS 700)
ExtraBold (178em / CSS 800)
Heavy (198em / CSS 900)

Also please make sure you're using the latest version, 4.2 was recently released: https://github.com/carrois/Fira/tree/master/Fira_Sans_4_2/Fonts/FiraSans_OTF_4203

And I believe we moved off TTF since OFT supports advanced type features present in Fira. So hopefully you can use the OFTs instead. Thanks for your hard work.

patrykdesign · Nov 28, 2016

@m4rc1e Hey, yes some of the weights are experimental. So the mapping should go as follows for CSS weighting...

Thin (22em / CSS 100)
UltraLight (34em / CSS 200)
Light (58em / CSS 300)
Regular (92em / CSS 400)
Medium (128em / CSS 500)
SemiBold (142em / CSS 600)
Bold (158em / CSS 700)
ExtraBold (178em / CSS 800)
Heavy (198em / CSS 900)

Also please make sure you're using the latest version, 4.2 was recently released: https://github.com/carrois/Fira/tree/master/Fira_Sans_4_2/Fonts/FiraSans_OTF_4203

And I believe we moved off TTF since OFT supports advanced type features present in Fira. So hopefully you can use the OFTs instead. Thanks for your hard work.

Hey,

Thank you for your in depth response. I will make sure we use the latest release.
We need to use the following mapping for our api to work correctly:

"Thin": 250,
"ExtraLight": 275,
"Light": 300,
"Regular": 400,
"Medium": 500,
"SemiBold": 600,
"Bold": 700,
"ExtraBold": 800,
"Black": 900

At the moment, we only support ttfs I'm afraid. I'm guessing you folks used the otf format because you can use floating point units. This is especially useful in the hairline weight. ttfs uses integers only.

I hope you understand and don't mind us using ttfs instead?

Cheers,
Marc

m4rc1e · Nov 28, 2016

Hey,

Thank you for your in depth response. I will make sure we use the latest release.
We need to use the following mapping for our api to work correctly:

"Thin": 250,
"ExtraLight": 275,
"Light": 300,
"Regular": 400,
"Medium": 500,
"SemiBold": 600,
"Bold": 700,
"ExtraBold": 800,
"Black": 900

At the moment, we only support ttfs I'm afraid. I'm guessing you folks used the otf format because you can use floating point units. This is especially useful in the hairline weight. ttfs uses integers only.

I hope you understand and don't mind us using ttfs instead?

Cheers,
Marc

@carrois should be able to provide the TTF exports, hopefully he'll have some cycles to do so soonish.

patrykdesign · Nov 28, 2016

@carrois should be able to provide the TTF exports, hopefully he'll have some cycles to do so soonish.

@m4rc1e hey as far as the mapping goes, I think for maximum I'll remap THIN from CSS 100 to 250 and Ultralight from CSS200 to 275 while keeping the other weights the same as their CSS mapping spec:

Light (58em / CSS 300)
Regular (92em / CSS 400)
Medium (128em / CSS 500)
SemiBold (142em / CSS 600)
Bold (158em / CSS 700)
ExtraBold (178em / CSS 800)
Heavy (198em / CSS 900)

patrykdesign · Nov 28, 2016

@m4rc1e hey as far as the mapping goes, I think for maximum I'll remap THIN from CSS 100 to 250 and Ultralight from CSS200 to 275 while keeping the other weights the same as their CSS mapping spec:

Light (58em / CSS 300)
Regular (92em / CSS 400)
Medium (128em / CSS 500)
SemiBold (142em / CSS 600)
Bold (158em / CSS 700)
ExtraBold (178em / CSS 800)
Heavy (198em / CSS 900)

@patrykdesign please don't worry about any of this :-). I have it all automated. Please do not deviate from your sources to please us. You don't want to upset your existing users. We can modify our own version of the fonts for our spec. I've been doing this for Lato

We have fontbakery which helps us to hot fix fonts to work with our spec in mind.

m4rc1e · Nov 28, 2016

@patrykdesign please don't worry about any of this :-). I have it all automated. Please do not deviate from your sources to please us. You don't want to upset your existing users. We can modify our own version of the fonts for our spec. I've been doing this for Lato

We have fontbakery which helps us to hot fix fonts to work with our spec in mind.

@m4rc1e I mistyped... By "I'll remap" I meant hope you guys can remap. We'll keep our mappings as is. Also do you still need a TTF source or can you convert the OFT fonts to TTF. We also have the .glyphs source files you can use.

patrykdesign · Nov 28, 2016

@m4rc1e I mistyped... By "I'll remap" I meant hope you guys can remap. We'll keep our mappings as is. Also do you still need a TTF source or can you convert the OFT fonts to TTF. We also have the .glyphs source files you can use.

Thank you for the confirmation.

I'll look into the conversion. It is possible.

Cheers,
Marc

m4rc1e · Nov 28, 2016

Thank you for the confirmation.

I'll look into the conversion. It is possible.

Cheers,
Marc

Almost finished mastering the v4.2 fonts so they'll work on GF.

Issue has been solved.

m4rc1e · Nov 29, 2016

Almost finished mastering the v4.2 fonts so they'll work on GF.

Issue has been solved.

@m4rc1e thanks so much for fixing this. It came up this week with a client website and brought me here.

I've asked them to hold until the fix is out rather than change their site font. Do you have an ETA for when v4.2 might land?

ben-rabid · Nov 29, 2016

@m4rc1e thanks so much for fixing this. It came up this week with a client website and brought me here.

I've asked them to hold until the fix is out rather than change their site font. Do you have an ETA for when v4.2 might land?

@davelab6 shall I submit a pr for this?

Our hotfix repo is here. If you urgently need these fonts, self host the fonts in the /fonts directory.

m4rc1e · Dec 1, 2016

@davelab6 shall I submit a pr for this?

Our hotfix repo is here. If you urgently need these fonts, self host the fonts in the /fonts directory.

@carrois should be able to provide the TTF exports, hopefully he'll have some cycles to do so soonish.

@patrykdesign not sure what you mean. 4203 TTF files are all there?!

carrois · Dec 1, 2016

@carrois should be able to provide the TTF exports, hopefully he'll have some cycles to do so soonish.

@patrykdesign not sure what you mean. 4203 TTF files are all there?!

@carrois When I look at the official repo's ttf folder, there are no Condensed weights. @patrykdesign's link includes both Condensed and Compressed variants. My hotfix repo includes those Condensed and Compressed variants. Is the link @patrykdesign valid? or should I just hotfix the official repo sources only?

Cheers,
Marc

m4rc1e · Dec 1, 2016

@carrois When I look at the official repo's ttf folder, there are no Condensed weights. @patrykdesign's link includes both Condensed and Compressed variants. My hotfix repo includes those Condensed and Compressed variants. Is the link @patrykdesign valid? or should I just hotfix the official repo sources only?

Cheers,
Marc

Yes the link is valid and in case of doubts the most recent. We only have control over this repository, not over Mozilla's.

…

Am 01.12.2016 um 16:55 schrieb Marc Foley ***@***.***>: @carrois When I look at the official repo's ttf folder, there are no Condensed weights. @patrykdesign's link includes both Condensed and Compressed variants. My hotfix repo includes those Condensed and Compressed variants. Is the link @patrykdesign valid? or should I just hotfix the official repo sources only? Cheers, Marc — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

carrois · Dec 1, 2016

Yes the link is valid and in case of doubts the most recent. We only have control over this repository, not over Mozilla's.

…

Am 01.12.2016 um 16:55 schrieb Marc Foley ***@***.***>: @carrois When I look at the official repo's ttf folder, there are no Condensed weights. @patrykdesign's link includes both Condensed and Compressed variants. My hotfix repo includes those Condensed and Compressed variants. Is the link @patrykdesign valid? or should I just hotfix the official repo sources only? Cheers, Marc — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

@carrois my bad didn't see that the TTFs were in the web version url

@m4rc1e please use the carrois repo ^^^, I am in talks with people at Mozilla, trying to figure out what they intend to do with the Fira project since I left the company and Firefox OS was cancelled.

patrykdesign · Dec 1, 2016

@carrois my bad didn't see that the TTFs were in the web version url

@m4rc1e please use the carrois repo ^^^, I am in talks with people at Mozilla, trying to figure out what they intend to do with the Fira project since I left the company and Firefox OS was cancelled.

Ok, then everything seems to be clarified. @patrykdesign We're curious ;-)

…

Am 01.12.2016 um 17:13 schrieb Patryk Adamczyk ***@***.***>: @carrois my bad didn't see that the TTFs were in the web version https://github.com/carrois/Fira/tree/master/Fira_Sans_4_2/Fonts/FiraSans_WEB_4203 @m4rc1e please use the carrois repo ^^^, we're still trying to figure out what Mozilla intends to do with the project since I left and Firefox OS was cancelled. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

carrois · Dec 1, 2016

Ok, then everything seems to be clarified. @patrykdesign We're curious ;-)

…

Am 01.12.2016 um 17:13 schrieb Patryk Adamczyk ***@***.***>: @carrois my bad didn't see that the TTFs were in the web version https://github.com/carrois/Fira/tree/master/Fira_Sans_4_2/Fonts/FiraSans_WEB_4203 @m4rc1e please use the carrois repo ^^^, we're still trying to figure out what Mozilla intends to do with the project since I left and Firefox OS was cancelled. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Sorry to hear that. Google Fonts can adopt the project if Mozilla would like

davelab6 · Dec 1, 2016

Sorry to hear that. Google Fonts can adopt the project if Mozilla would like

@davelab6 @carrois great to hear, I'll let them know. They just need to elect a new champion at the company to drive some sort of roadmap, so they are deciding on that now.

patrykdesign · Dec 1, 2016

@davelab6 @carrois great to hear, I'll let them know. They just need to elect a new champion at the company to drive some sort of roadmap, so they are deciding on that now.

@carrois @patrykdesign alas I am going to need to change the names of the widths in the family names to meet the GF requirements. I'll follow up shortly with this

davelab6 · Dec 6, 2016

@carrois @patrykdesign alas I am going to need to change the names of the widths in the family names to meet the GF requirements. I'll follow up shortly with this

Is this patched yet? Still not working on Debian.

enoch85 · Jan 9, 2017

Is this patched yet? Still not working on Debian.

@enoch85 version served on fonts.google.com is v3.107. Our update is 3.206. I guess we didn't upload because we need sort out the widths naming first.

m4rc1e · Jan 9, 2017

@enoch85 version served on fonts.google.com is v3.107. Our update is 3.206. I guess we didn't upload because we need sort out the widths naming first.

@m4rc1e Thanks for the clarification. Any ETA?

enoch85 · Jan 9, 2017

@m4rc1e Thanks for the clarification. Any ETA?

Just doing a little research as this font is rendering fine for me EXCEPT when I have an 'f' and 'i' next to eachother. What gives? Been using the Google Font version, should I download from here or Mozilla to fix or will this be fixed shortly?

Sprinkles22 · Feb 24, 2017

Just doing a little research as this font is rendering fine for me EXCEPT when I have an 'f' and 'i' next to eachother. What gives? Been using the Google Font version, should I download from here or Mozilla to fix or will this be fixed shortly?

@Sprinkles22 start a new issue, add a screenshot and mention which OS and platform.

Thanks,

m4rc1e · Feb 27, 2017

@Sprinkles22 start a new issue, add a screenshot and mention which OS and platform.

Thanks,

This issue is finally fixed for me on Chromium! Thanks guys!

Version 55.0.2883.75 built on Debian stretch/sid, running on Debian 8.0 (64-bit)

enoch85 · Apr 8, 2017

This issue is finally fixed for me on Chromium! Thanks guys!

Version 55.0.2883.75 built on Debian stretch/sid, running on Debian 8.0 (64-bit)

Just checked this out again and using Fira Sans from Google Fonts no longer has the problems I showed earlier. It displays fine in IE9 as well as Chrome/Firefox.

svivian · Oct 12, 2017

Just checked this out again and using Fira Sans from Google Fonts no longer has the problems I showed earlier. It displays fine in IE9 as well as Chrome/Firefox.

Looks fixed! And it only took 2 years :)

gyscos · Oct 12, 2017

Looks fixed! And it only took 2 years :)

Thank you for your patience :)

davelab6 · Oct 12, 2017

Thank you for your patience :)

👏 thank you!

ben-rabid · Oct 12, 2017

👏 thank you!

thank you, folks!

gonzalocasas · Oct 13, 2017

thank you, folks!

davelab6 self-assigned this Apr 14, 2015

davelab6 added the new family label Aug 25, 2015

Mte90 referenced this issue Sep 11, 2015
Open
rendering problem #2

This was referenced Sep 12, 2015

Closed

[Documentation] Source example not visible in all my browsers facebook/immutable-js#468

Closed

Problematic font families keithamus/npm-scripts-example#28

mmhyamin referenced this issue Sep 15, 2015
Closed
font in the footer menu making confusion with the letter 'C' and 'E' #42

rpominov referenced this issue Sep 23, 2015
Closed
Documentation is invisible #153

yixuan referenced this issue Oct 26, 2015
Closed
Fira Sans returns freetype: error code 139 #5

oskarkrawczyk referenced this issue Dec 17, 2015
Closed
Code boxes are gray #686

google-admin unassigned davelab6 Jan 18, 2016

lepaperwan referenced this issue Jan 30, 2016
Closed
ttf-google-fonts: Remove broken Fira fonts #75

davelab6 referenced this issue Jan 31, 2016
Closed
Fira Sans is not working #206

m4rc1e referenced this issue Nov 25, 2016
Open
Add Lato v2.0 #6

m4rc1e referenced this issue Dec 2, 2016
Merged
src | fonts | build: src fonts updated to ttf sources, #2

rkfg referenced this issue Dec 9, 2016
Closed
Fira sans is broken in Chrome and Firefox on Linux #39

This was referenced Jan 2, 2017

Closed

extremely light font rendering in chrome Version 55.0.2883.95 (64-bit) rust-lang/rust-www#658

Closed

fix(css): ensure font-weight is readable rust-lang/rust-www#664

davelab6 removed the Requires Upstream Resolution label Sep 22, 2017

gyscos closed this Oct 12, 2017

jace added a commit to hasgeek/hasjob that referenced this issue Nov 20, 2017

Revert to Google Fonts for Fira Sans since google/fonts#10 is fixed

5e3e4a8

google/fonts

Join GitHub today

FiraSans and FiraMono appear blank #10

Comments

gyscos commented Apr 14, 2015

This comment has been minimized.

gyscos commented Apr 14, 2015

davelab6 self-assigned this Apr 14, 2015

This comment has been minimized.

codeman38 commented Apr 14, 2015

This comment has been minimized.

davelab6 commented Apr 14, 2015

This comment has been minimized.

Mte90 commented Jun 22, 2015

This comment has been minimized.

Delapouite commented Jun 28, 2015

This comment has been minimized.

jkbyln commented Jul 24, 2015

matachi added a commit to matachi/hesitant that referenced this issue Jul 29, 2015

davelab6 added the new family label Aug 25, 2015

Mte90 referenced this issue Sep 11, 2015

This was referenced Sep 12, 2015

This comment has been minimized.

Mte90 commented Sep 14, 2015

This comment has been minimized.

jkbyln commented Sep 14, 2015

mmhyamin referenced this issue Sep 15, 2015

rpominov referenced this issue Sep 23, 2015

This comment has been minimized.

Schweinepriester commented Oct 9, 2015

yixuan referenced this issue Oct 26, 2015

This comment has been minimized.

Mte90 commented Nov 2, 2015

This comment has been minimized.

gyscos commented Nov 2, 2015

This comment has been minimized.

davelab6 commented Nov 3, 2015

oskarkrawczyk referenced this issue Dec 17, 2015

This comment has been minimized.

nekromoff commented Jan 9, 2016

This comment has been minimized.

damiadev commented Jan 14, 2016

google-admin unassigned davelab6 Jan 18, 2016

This comment has been minimized.

Mte90 commented Jan 18, 2016

lepaperwan referenced this issue Jan 30, 2016

davelab6 referenced this issue Jan 31, 2016

This comment has been minimized.

krrg commented Feb 3, 2016

This comment has been minimized.

davelab6 commented Feb 3, 2016

This comment has been minimized.

davelab6 commented Feb 6, 2016

This comment has been minimized.

enoch85 commented Feb 6, 2016

This comment has been minimized.

davelab6 commented Feb 6, 2016

This comment has been minimized.

davelab6 commented Feb 10, 2016

This comment has been minimized.

enoch85 commented Feb 26, 2016

This comment has been minimized.

enoch85 commented Mar 15, 2016

This comment has been minimized.

davelab6 commented Mar 15, 2016

This comment has been minimized.

enoch85 commented Mar 15, 2016

This comment has been minimized.

bhulsman commented Mar 22, 2016

This comment has been minimized.

jace commented Mar 24, 2016

This comment has been minimized.

gonzalocasas commented Nov 23, 2016

m4rc1e referenced this issue Nov 25, 2016

This comment has been minimized.

m4rc1e commented Nov 28, 2016

This comment has been minimized.

patrykdesign commented Nov 28, 2016 • edited Edited 1 time patrykdesign edited Nov 28, 2016 (most recent)

This comment has been minimized.

m4rc1e commented Nov 28, 2016

patrykdesign commented Nov 28, 2016 •

edited

Edited 1 time

patrykdesign edited Nov 28, 2016 (most recent)

patrykdesign commented Nov 28, 2016 •

edited

Edited 1 time

patrykdesign edited Nov 28, 2016 (most recent)

m4rc1e commented Nov 28, 2016 •

edited

Edited 1 time

m4rc1e edited Nov 28, 2016 (most recent)