Closed GoogleCodeExporter closed 8 years ago
Yes, we have the same problem here on our website, using the news cycle normal.
The bold version looks fine.
Original comment by 7evenele...@gmail.com
on 5 Apr 2012 at 10:36
Having the same problem as well. I have a new website, and it was working fine
until today. I'm viewing on a Mac, through Chrome, Firefox 11, and Safari. Only
News Cycle affected. See attached.
Original comment by gaynelle...@gmail.com
on 5 Apr 2012 at 11:20
Attachments:
FWIW, code for News Cycle--shows "normal" rather than "400". Would be great if
this issue could be reviewed and addressed. Thanks.
Original comment by gaynelle...@gmail.com
on 7 Apr 2012 at 10:58
Attachments:
Having the same problem (with Firefox, Chrome and Opera, at least).
A freshly FontSquirreled local version of the font works fine.
Original comment by the...@gmail.com
on 10 Apr 2012 at 6:01
Sorry about this, a FontForge bug mishandled the latin subset file. I fixed
this with
http://code.google.com/p/googlefontdirectory/source/detail?r=90de81f0047a3901d26
0a8e8e5522a98c15b7bb0 and it should go to production servers tomorrow
2012-04-10 in the morning California time
Original comment by dcrossland@google.com
on 10 Apr 2012 at 6:24
Thanks. Looks much better, but now the dots on lowercase i's and j's seem to
have been misplaced.
jsFiddle: http://jsfiddle.net/Cottser/BPZhU/
Original comment by cott...@gmail.com
on 11 Apr 2012 at 12:56
Attachments:
i'm having exactly the same problem with that font. i managed to make it work
for a while, after changing the font-url and setting it back again... maybe
that really helped or google fixed it
Original comment by adis.dur...@gmail.com
on 11 Apr 2012 at 6:09
I'm having the same problem with the dots on the lowercase i and j, even just
created a new page from scratch and the problem still persists.
Original comment by do...@october29.com
on 12 Apr 2012 at 2:59
Is there any plan for this to get fixed? I see this issued was closed and
marked as fixed on April 9 but the problem with the dots on the lower case
letters is still there, I've regenerated the code from Google and that doesn't
fix the problem, see http://allegoriesandexperiences.com/ and
http://gagliostro.com/
Original comment by do...@october29.com
on 13 Apr 2012 at 12:12
i's and j's okay on Chrome, Safari, and Firefox on Mac / iPhone. Took a look at
your sites and they seem to render fine too. Since I've gone back to using News
Cycle on my site, curious to know what browser / system you're using and still
seeing this problem.
Original comment by gaynelle...@gmail.com
on 13 Apr 2012 at 2:51
I'm seeing almost the opposite of #10.
I just tested an array of browsers locally and on BrowserStack. Every browser I
tested on Mac (local and remote via BrowserStack) had messed up i's and j's.
Opera, Chrome, Safari, Firefox.
Every other platform I tested was okay: Windows, iOS, Android, Opera Mobile.
Original comment by cott...@gmail.com
on 13 Apr 2012 at 3:36
I'm using a Mac (OS X 10.6.8), tested on Chrome 18.0.1025.162, Safari 5.1.5 and
Firefox 11.0. Have flushed caches and restarted. (And iOS are fine for me as
well.) One site is a single page, code straight from Google; the other site is
Drupal and code is generated by a module. I really really like this font after
spending hours looking at all sans-serifs so I don't want to switch. And
switching to the FontSquirrel version doesnt' seem an ideal solution.
Original comment by do...@october29.com
on 13 Apr 2012 at 4:36
Hello everyone. I am sorry I made a mistake when updating News Cycle to add a
bold, somehow FontForge got confused and didn't include half the glyphs in the
Latin subset, and I didn't catch this in my QA before pushing it. When I fixed
this I introduced a regression that made the 'i' dots 'fall down' and I have
finally fixed this. The fix should be fully propagated in 48 hours.
Original comment by dcrossland@google.com
on 26 Apr 2012 at 12:58
Thank you!
Original comment by gaynelle...@gmail.com
on 26 Apr 2012 at 1:01
Issue 131 has been merged into this issue.
Original comment by pathum...@gmail.com
on 12 Aug 2014 at 5:37
Original issue reported on code.google.com by
helenthe...@gmail.com
on 5 Apr 2012 at 9:57Attachments: