Closed GoogleCodeExporter closed 8 years ago
This is definitely a bug in the font file. When decompiled in TTX:
<LigatureSet glyph="f">
<Ligature components="i" glyph=".notdef"/>
<Ligature components="l" glyph=".notdef"/>
</LigatureSet>
In other words, if OpenType ligatures are enabled (and in Firefox they are),
the sequences "fi" and "fl" both convert to the glyph for nonexistent
characters. Oops.
Original comment by codeman38
on 24 Feb 2012 at 6:34
Oh, and to add to the bug report, this bug is also present in the original .otf
source file. There, the two ligatures resolve to "glyph65535", which isn't even
a valid character name within the font.
Original comment by codeman38
on 24 Feb 2012 at 6:37
Thanks for this bug report! I've applied a brutal fix of simply removing the
GSUB table. I've asked Eben Sorkin to send a fixed version :)
http://code.google.com/p/googlefontdirectory/source/detail?r=f53e5017795deef169d
c766cc6bb9d2f42ccb313 The fix should go live on Wednesday.
Original comment by dcrossland@google.com
on 25 Feb 2012 at 3:07
[deleted comment]
Just jumping in here, but I'm using Spinnaker as well & it's still displaying
in Firefox 10.0.2 (Mac OS 10.6.8) the non-existent character symbols. All's
good in Safari. Any estimate when this might be fixed/updated?
Thanks!
Original comment by mholm...@gmail.com
on 11 Mar 2012 at 12:07
Or is there a CSS fix on my end?
Original comment by mholm...@gmail.com
on 11 Mar 2012 at 12:08
see also issue # 119 for Spinnaker. <strong>XXX</strong> is not displayed
correctly in firefox. I've abandoned Spinnaker for now ... it's back in the
chute :).
Original comment by n...@woolandcompany.com
on 11 Mar 2012 at 12:13
Love that Spinnaker. When you say it's "in the chute", does that mean the
Google powers-that-be are checking it out?
Original comment by mholm...@gmail.com
on 11 Mar 2012 at 12:49
no idea where google is on this. in the chute - the chute is where spinnakers
are kept on sailboats when they're not in use :)
Original comment by n...@woolandcompany.com
on 11 Mar 2012 at 1:47
Ha! Got it. And well done. ;)
Original comment by mholm...@gmail.com
on 11 Mar 2012 at 2:54
Why is this marked 'fixed'? It is going on the fifth Wednesday since the
Wednesday it was supposed to go live...
Original comment by ramzy...@gmail.com
on 28 Mar 2012 at 2:25
Agreed. Would love an update on the status of this as well. . .
Original comment by mholm...@gmail.com
on 30 Mar 2012 at 4:03
I just designed an entire website using Spinnaker as the primary font, and am
just discovering this really annoying issue now. Luckily, my site is static so
I can hand-input a CSS fix wherever an 'fi' ligature appears. It is just a
simple class for a span of text. This fix is of course ridiculous and I don't
imagine would work if you are using Spinnaker as the font where dynamic content
is generated.
However, if this helps anyone else, my CSS fix is as follows:
.ligature {
letter-spacing: -0.12em;
padding-right: 2px;
}
And the corresponding HTML would look like this:
<p>I like <span class="ligature">fi</span>gure skating.</p>
Original comment by monica.k...@gmail.com
on 28 Aug 2012 at 11:14
Original issue reported on code.google.com by
n...@woolandcompany.com
on 24 Feb 2012 at 5:27Attachments: