Open GoogleCodeExporter opened 8 years ago
Hi Google wiz and original poster,
We are also about to go live with a website using Cuprum and I just noticed the
problem with the letter "å" as well. Any update on when this issue might be
fixed?
Kind regards,
Adam Bäckman
Graphical Designer/Partner
Langustus Industrier
Gamla Rådstugugatan 1B
602 24 Norrköping
Sweden
Original comment by maria.as...@gmail.com
on 22 Sep 2011 at 8:29
What may be going on here is that the string may be getting converted into
standard decomposed Unicode form which the font can't display. Decomposition is
used on the Mac platform, at least for filename strings. This leads to font
substitution for the missing combining ring character. You end up with the ring
being substituted from Lucida Grande or Helvetica, which looks bad - wrong
position and weight.
Fix is to add the combining ring character U+030A and ligature actions for all
expected use cases to the font.
e.g.
This is the system string decomposition Å --> A + ̊
This is the font ligature action needed to map the sequence back to the
precomposed glyph A + ̊ --> Å
Å U+00C5 LATIN CAPITAL LETTER A WITH RING ABOVE
A U+0041 LATIN CAPITAL LETTER A
̊ U+030A COMBINING RING ABOVE
Original comment by loft...@apple.com
on 23 Sep 2011 at 3:58
We fixed the issue by installing the font on the server and using that instead
of the one on google fonts. The font you can download from google fonts is fine
and by installing that and linking to that fixes the issue. It is strange that
the font you can download and the font that you link to in the code is not the
same.
Original comment by partn...@bandp.dk
on 23 Sep 2011 at 8:50
The downloaded font and the file typically served by the Google Web Fonts API
are not the same; the typical API file is a latin subset. You can download it
directly here:
http://googlefontdirectory.googlecode.com/hg/cuprum/Cuprum.latin
I looked at this file and it seems okay to me (outline directions, composite
chars)
Original comment by dcrossland@google.com
on 23 Sep 2011 at 9:00
Original issue reported on code.google.com by
partn...@bandp.dk
on 28 Jun 2011 at 7:54Attachments: