You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently discovered the Open Sans library via Google Fonts is missing the trademark symbol. It's currently an issue with a website I'm working on, and was able to verify it with the font preview tool on Google Fonts.
Although Adobe's version of the library has the TM. Any chance of getting the Google hosted library fixed?
I have checked this issue with a CodePen, and the Trademark (™) sign is showing as intended. You can have a look at the CodePen here
However, I can also confirm that that the Google Font preview tool, doesn't show the ™ mark in any font, as I've tried with it. May be it's an issue with preview tool, not with the font. Hope this get fixed.
@enathu I just made a slight edit to the CodePen and was able to reproduce the issue. Remove "sans-serif" from after Open Sans and the TM becomes a [TM] in a box, broken character. I believe the library may still be missing this item and when "sans-serif" is supplied it defaults to the system sans-serif font which does contain that character.
@criana Alright, that makes sense, now. So, I think it's an issue with GF API, since it's showing the same cross (missing glyphs) for all other fonts for trademark sign. Even though the trademark sign is inside the font file, as I just checked with the GF hosted Open Sans files.
The directory's preview isn't an accurate reflection of the characters available in the font. The sans-serif thing is interesting, I'm not sure what is happening there... my guess is that when you add sans-serif then the browser uses the ™ that is in the default sans-serif font (likely Arial on windows) but when sans-serif is not there, is uses a default font (not sure what) which for some reason has this character in a box like that.
I'm using a mac right now, and the ™ in the codepen does look slightly different with/without the sans-serif, but there is no box shape.
The unicode U+2122 is not in the latin subsets, though, and thus isn't being served... so it could be a candidate for inclusion in the latin-ext subset.
@davelab6,
Thanks for looking into this more. I've attached a screen shot of what I see in CodePen. I'm running Chrome on a Mac with OS 10.10.4. I also do no have any versions of OpenSans running locally on my machine. This is only when sans-serif is removed from the font-declaration.
What I remembered was that Roozbeh left Google in the middle of this effort and no one picked it up since. Let's assign it to me and eventually we will deal with it
Activity
enathu commentedon Jul 14, 2015
I have checked this issue with a CodePen, and the Trademark (™) sign is showing as intended. You can have a look at the CodePen here
However, I can also confirm that that the Google Font preview tool, doesn't show the ™ mark in any font, as I've tried with it. May be it's an issue with preview tool, not with the font. Hope this get fixed.
Cheers.
criana commentedon Jul 14, 2015
@enathu thanks for sharing, that's very interesting. I wonder why on our site pulling the Open Sans font gives us the TM in a box representation.

criana commentedon Jul 14, 2015
@enathu I just made a slight edit to the CodePen and was able to reproduce the issue. Remove "sans-serif" from after Open Sans and the TM becomes a [TM] in a box, broken character. I believe the library may still be missing this item and when "sans-serif" is supplied it defaults to the system sans-serif font which does contain that character.
Does that make sense?
enathu commentedon Jul 14, 2015
@criana Alright, that makes sense, now. So, I think it's an issue with GF API, since it's showing the same cross (missing glyphs) for all other fonts for trademark sign. Even though the trademark sign is inside the font file, as I just checked with the GF hosted Open Sans files.
Pinging @davelab6 for fix. :)
davelab6 commentedon Jul 17, 2015
The directory's preview isn't an accurate reflection of the characters available in the font. The
sans-serifthing is interesting, I'm not sure what is happening there... my guess is that when you addsans-serifthen the browser uses the ™ that is in the defaultsans-seriffont (likely Arial on windows) but whensans-serifis not there, is uses a default font (not sure what) which for some reason has this character in a box like that.I'm using a mac right now, and the ™ in the codepen does look slightly different with/without the
sans-serif, but there is no box shape.The unicode U+2122 is not in the latin subsets, though, and thus isn't being served... so it could be a candidate for inclusion in the
latin-extsubset.https://github.com/google/fonts/blob/master/tools/encodings/latin_unique-glyphs.nam
https://github.com/google/fonts/blob/master/tools/encodings/latin-ext_unique-glyphs.nam
[-]Open Sans Library Missing Trademark[/-][+]Add U+2122 (™) to latin-ext[/+]codeman38 commentedon Jul 17, 2015
U+2122 is part of the legacy Latin character sets for both Windows and Mac OS, so it feels like it should possibly even be included in
latin.criana commentedon Jul 17, 2015
@davelab6,
Thanks for looking into this more. I've attached a screen shot of what I see in CodePen. I'm running Chrome on a Mac with OS 10.10.4. I also do no have any versions of OpenSans running locally on my machine. This is only when sans-serif is removed from the font-declaration.
davelab6 commentedon Jul 17, 2015
Here's what I see in Chrome 46, also 10.10.4, also none installed locally...
criana commentedon Jul 17, 2015
I was able to verify this too after a thorough cleaning of fonts and caches on my machine. Sorry for the mixup.
davelab6 commentedon Jul 20, 2015
No worries @criana - the suggestion to add ™ is a good one :)
BenRacicot commentedon Oct 9, 2015
Hey @davelab6 any updates on this? I'm having the exact same issue as @criana perhaps someone has a nicer fix than adding a fallback font?
34 remaining items
code23-isaac commentedon Jan 21, 2019
davelab6 commentedon Dec 2, 2021
What I remembered was that Roozbeh left Google in the middle of this effort and no one picked it up since. Let's assign it to me and eventually we will deal with it
davelab6 commentedon Dec 2, 2021
Actually @RosaWagner says she can take the next steps on this so reassigning
davelab6 commentedon Dec 2, 2021
Haha after looking further, this is already fixed
https://fonts.googleapis.com/css?family=Open+Sans has
So u+2212 there means it will be provided by default when it exists in the font
Thanks @RosaWagner for looking closer at this :)
Merge pull request #78 from googlefonts/RosaWagner-ElementGrid
Merge pull request #78 from moyogo/fy-fix_base_exemplar