@davelab6 Open Sans is one of the most widespread fonts in Bulgaria (mainly on websites). This font family still doesn't have a Bulgarian Cyrillic, it is why I have developed versions with Bulgarian Cyrillic. See the pictures below. The sorce files are here.
I hope there will be plans for an upgrade of the Open Sans font family so that the Bulgarian letter form models to be a part of the future project.

Size: 16

The registered trademark sign appears usually as superscript, but not in Open Sans. See https://fonts.google.com/specimen/Open+Sans?preview.text=test®&preview.text_type=custom

On the screenshot you can see the registered trademark sign in the input appearing as superscript, but not in the rendered version with the Open Sans font:

I'm confused.

• If I go to the font "home" and download/unzip the .TTFs, they have file versions of 1.10.
• If I go to the GitHub page from the "About" page and download the .TTFs, they also have file versions of 1.10, but they were loaded under a PR with a name indicating they are v1.101.
• If I go to the Source page referenced from the GitHub page and download the .TTFs, they have a file version of 2.01.
• None of them have the same checksums, and neither of the repositories is a fork of the other.
• None of them have release notes.

Which is the official release, and what is the version?

If I compare the masters in https://github.com/laerm0/opensans/blob/master/source/OpenSans-Roman.glyphs against the fonts we currently serve, we can see they're different.

Outline in Blue is from the Bold Variable font instance. Outline in grey is from the Bold we currently serve on Google Fonts. No kerning present in either fonts.

It isn't just the outlines, the glyph's horizontal metrics also differ.

Bold metric differences

Upsilontonos 1278.0 1565.0
uni1F4D 1630.0 1712.0
threequarters 1822.0 1804.0
uni0485 0.0 1182.0
Iotatonos 678.0 1049.0
uni0486 0.0 1182.0
uni0512 1526.0 1675.0
Omicrontonos 1630.0 1712.0
uni0513 1321.0 1483.0
IJ 1356.0 1475.0
onehalf 1822.0 1804.0
seveneighths 1822.0 1804.0
circumflex 869.0 1243.0
napostrophe 1606.0 1595.0
uni0483 0.0 1141.0
uni0484 0.0 1182.0
oneeighth 1822.0 1804.0
macron 600.0 1243.0
onequarter 1822.0 1804.0
threeeighths 1822.0 1804.0
equal 1162.0 1169.0
uni0478 2743.0 2701.0
uni0479 2433.0 2345.0
Etatonos 1567.0 1710.0
CR 532.0 1044.0
ij 1250.0 1210.0
fiveeighths 1822.0 1804.0
Epsilontonos 1147.0 1290.0
uni0511 1137.0 1139.0
uni04FC 1366.0 1499.0
uni04FD 1184.0 1321.0
uni04F9 1882.0 1741.0

Light metric differences

uni03D2 1104.0 1081.0
uni03D1 1208.0 1238.0
Upsilontonos 1321.0 1081.0
uni03D6 1587.0 1594.0
uni1F4D 1632.0 1565.0
dotaccent 483.0 389.0
threequarters 1516.0 1592.0
uni0485 1182.0 0.0
Iotatonos 602.0 516.0
uni0486 1182.0 0.0
uni0462 1378.0 1345.0
Omicrontonos 1577.0 1565.0
cedilla 420.0 445.0
hungarumlaut 1182.0 1162.0
uni0463 1241.0 1195.0
ring 1182.0 4.0
tonos 1182.0 1123.0
onehalf 1516.0 1592.0
grave 1182.0 9.0
seveneighths 1516.0 1592.0
circumflex 1182.0 582.0
uni0483 1141.0 0.0
uni0484 1182.0 0.0
oneeighth 1516.0 1592.0
uni0489 1958.0 1989.0
uni0488 2025.0 2024.0
macron 1141.0 52.0
onequarter 1516.0 1592.0
threeeighths 1516.0 1592.0
uni02BC 297.0 310.0
uni0472 1565.0 1551.0
uni0473 1200.0 1166.0
uni0474 1210.0 1267.0
uni0475 973.0 1000.0
uni0476 1210.0 1267.0
uni0477 973.0 1000.0
uni0478 2335.0 2337.0
uni0479 2093.0 2140.0
Etatonos 1563.0 1473.0
breve 1182.0 56.0
CR 1044.0 532.0
ij 926.0 889.0
fiveeighths 1516.0 1592.0
Epsilontonos 1221.0 1130.0
uni04E8 1565.0 1551.0
uni04E9 1200.0 1166.0
tilde 1182.0 93.0
uni04BB 1167.0 1208.0
acute 1182.0 9.0
uni01F0 463.0 426.0
uni04EB 1200.0 1166.0
uni04EA 1565.0 1551.0
jcircumflex 463.0 426.0
caron 1182.0 582.0
Omegatonos 1608.0 1587.0
dieresistonos 1182.0 1133.0
uni04FC 1192.0 1102.0
uni04FD 1036.0 1020.0
fraction 246.0 216.0
dieresis 1182.0 1266.0
uni04F9 1481.0 1628.0
j 463.0 426.0
ogonek 356.0 8.0
cyrillichookleft 418.0 348.0

Since both the Light and Bold masters have metric issues, the Regular is getting distorted to an unacceptable level.

Open Sans VF regular instance vs Open Sans Regular on Google Fonts

For a font which is requested ~27 billion times a week and served on 25 million+ sites, there shouldn't be any document reflow.

Please check the screenshot, there is a display issue of the font style of Open Sans in the Word font list. I think the Regular rather than the Italic style should be displayed.

It's very appreciate if you can check and fix this issue.

hi, i try using illustrator but it was looking for OpenSans-SemiBold (no gap between open sans), the font i download from google name was Open Sans-Semibold (with gap )
how can i rename or download the old version with opensans? thanks

All styles which are currently being served must exist

Please use GitHubs release feature to mark this as a particular release. Nobody knows what version these are. Tell us?

Hello!

This is an automatically-generated report about possible interpolation problems in OpenSans[wdth,wght].ttf, as found in the Google Fonts catalog.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph uni05D7 was not compatible:
  Masters: '', 'wdth=75.0':
    Contour 0 has a kink at 28: '', 'wdth=75.0'
Glyph uni05E4 was not compatible:
  Masters: '', 'wdth=75.0':
    Contour 0 has a kink at 32: '', 'wdth=75.0'
Glyph uni05E8 was not compatible:
  Masters: '', 'wdth=75.0':
    Contour 0 has a kink at 5: '', 'wdth=75.0'

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please accept our apologies and ignore / close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

Please note that I am doing this as a community service and do not represent Google Fonts.

I believe I have finally reached the end of a long road VTT hinting Open Sans VF. Here are some fun facts.

First off, pixel deltas in variation CVTs are not possible. The method is to open the variation CVT window, choose a variation, and apply the delta as you would to a standard CVT...only this is just for font unit deltas. Those are only really appropriate for stem weights, really, and even then it's a bit fidgety. So, as far as heights not matching between the VF and static fonts currently served, nothing further can be done to improve it at this time. (With some time, I can maybe write some functions to help us out, but I'd have to see what the variation support in functions is like.)

Personally, I think that we should just back away from this and call it finished until there are improvements to VTT (and, ultimately, hinting bytecode). Mike @ MS says this is unlikely in the near future, and, really, that makes sense: with DirectWrite, this level of granular control is not often necessary.

Second, DWrite is also a reason why I say we should let this be. There are some stem weight issues on a handful of glyphs at a couple sizes, and individual glyph deltas aren't something @davelab6 wants me to spend time on. The percentage of browsers out there old enough to not use DWrite is less than 1%. Everything else is fine. Let's not worry about tweaking things for ClearType ever again. 🎉

Now then, between this and #11, we are going to break the internet. I don't know what to say to that.

GF API now accepts all msft registered axes, so make Open Sans with wght and wdth and slnt, instead of separate families with wght only

(or is the italics non interpolable?) :)

@davelab6

@m4rc1e and I were talking about the plans to hint this and we won't be able to get total quality on ttfautohint with its defaults, so hinting it in Glyphs seems like best way; that is to say, export the fonts, have glyphs send them through ttfautohint, and then fix the ones that need fixing in Glyphs.

I am currently ensuring point compatibility between weights (hinting point compatibility is more strict than interpolation point compatibility) so that when we fix the glyphs that need better hinting, we only need to fix the regular weight and the hints will get applied to all masters.

I noticed that the current license, "SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007", states that any redistribution of Open Sans must have the same license. However, Google lists the license as "Apache License, Version 2.0" on its website.

https://fonts.google.com/specimen/Open+Sans#license

Which would be the appropriate license to include in my usage of Open Sans?

The GF release has SS03. This repo has up to SS02. We should make sure that all glyphs are accessible using the same inputs as the previous release.

this started to happen from the last font update

The italic versions of the lower a and alpha are almost indistinguishable. This can lead to some confusion in mathematical equations. Is it possible to change either character.

This problem appears only in the italic version (second row). The regular version is ok (first row):

Example of problem in mathematical equation:

Thank you ever so much for all your work! We recently started using Open Sans, but I can’t seem to find an alternative l design that will make eg. this more readable:

Would be great to be able to switch to it via CSS (if not have it as default). Or is this really a feature request for Noto Sans?

Thought I'd just do a QA before you start hinting:

I genned static ttfs from Open Sans V.glyphs. I've only compared the Regular

Diffenator

OpenSans-Regular.ttf vs OpenSans-Regular.ttf

attribs 22 modified

mkmks 26 new

kerns 315 new

kerns 111 modified

kerns 7660 missing

metrics 798 modified

names 16 modified

names 2 missing

marks 3061 new

glyphs 142 new

glyphs 317 modified

glyphs 29 missing

Report images are here:
Open-Sans-diffs.zip

Just for an overview, here's the modified glyphs:

full size image in zip

Here's a report culled to 1,000 diffs
open-sans-report.txt

To fix #37 I wanted to check the build-script from the Noto Source. The build-script is mentioned here;

But in the repo there is no sources/build_masters_from_noto.sh

‘Okina is a required glyph for the Hawaiian language. The Google Fonts Glyphs Set includes the ‘Okina glyph (U+02BB). However, this font currently does not cover the ‘Okina glyph when it does cover the other required glyphs, /Amacron, /Emacron, etc.

The letter "J" in Open Sans extends past the left edge of where it should. This causes several problems:

• In HTML, it will be clipped in containers with overflow: hidden. Example: (copied from google/fonts#4266)

• It will look out of alignment with other fonts. Example: the top line is Open Sans, the line below is another Google font, Inter

This doesn't seem be to specific to web clients, because here's the same issue showing up in Microsoft Word (on MacOS). Note the J extends past the left edge of the caret.

This issue is a dupe of google/fonts#4266 but this problem seems to be font-specific so I guessed that its natural home would be here instead of in the general Google Fonts repo. Feel free to close whichever one of these issues is in the wrong home.

If a fix is straightforward, I'd be happy to submit a PR but would need some direction as I know zero about building fonts!

I find that Open Sans works beautifully as a font face for scientific plots (ticks and labels), and I would like to use it as default theme for a scientific visualization library (see these examples).

The only issue I've encountered so far is that it does not support some characters needed for "log scale plots" to simulate exponents, namely superscript minus ⁻ and dot operator ⋅.

Compare Open Sans version (using light weight for ticks)

with Fira Sans version (always light weights for ticks)

Would it be possible to add those two glyphs?

It's especially jarring at large sizes and weights:

I see in the gf central repo tracker there's plenty of open Open Sans issues; please triage and close those that the VF upgrade resolved :)

The variable version of Open Sans was created with equal metrics between weights. This is ideal so there is no reflow as the user/designer changes sizes. However, this will certainly cause reflow all over the internet if designers switch from the static weights to the variable fonts on their pages. As @m4rc1e puts it, this will break the internet.

I am of the mindset that we should move forward with this, but it would take a sustained PR campaign for designers to become aware of this and decide if they want to go to the VF or stay static (good luck to @davelab6), so I also think that Open Sans VF should be served as a different family so this doesn't happen.

As this is the first substantial remastering of a static family for VF that we are preparing to release, I feel like we should set a precedent and try to stick to it. Should we serve VF fonts alongside their static versions, or should we essentially overwrite static fonts with their variable versions?

I can see a plan where we have a Google Variable Fonts – with variable fonts being the focus and static fonts being deprecated – but this certainly entails a substantial reworking of...uhh, everything associated with this project.

Anyone who has opinions, please share them.

The original Open Sans has a kern table (not GPOS).

Should we use a kern table or use GPOS kerns?

I'm guessing old ms apps/browsers don't like gpos kerning?

Easiest approach is to just use the old kern table.

The family is loaded 30 billion times a week so it may be best to do this.

When I download opensans-main.zip, I find two folders: Once the ttf folder, then the noto-set folder, whose fonts contain almost five times the number of glyphs as those from the ttf folder. Except for the clear difference in glyphs, I basically don’t understand what the difference is between these fonts, or what the second folder has to do with the noto font. Is the latter just a derivative of Noto and not a “real” Open Sans? Can someone explain me the differences in more detail? Thank you.

Thank you for creating a ''regular'' weight of Open Sans Condensed here in the Github repo.

So, Open Sans Condensed now includes a Regular weight here in the Github repository, but Google fonts is showing only the '300 Light' and '700 Bold' weights:

There is none, which is odd.

See also: #30 and google/fonts#3411

The glyphs in the VTT hinted sources have nodes which don't match the glyphs generated from the build chain. This means we won't be able to successfully transfer the hints from the VTT sources to the build chain fonts.

glyph: a | top path: build chain | bottom path: VTT source

If I run gftools check-vtt-compatibility --compatible ./source/TTF_VTT_source/OpenSans-Roman.ttf ./fonts/variable_ttf/OpenSans-Roman-VF.ttf, I get the following incompatible glyphs:

partialdiff, ycircumflex, dollar.rvrn, alpha, ucircumflex, g893, uni047C, ae, ecircumflex, comma, D, divide, estimated, braceleft, g887, jcircumflex, ring, exclamdown, quotedblbase, adieresis, tildecomb, X, upsilondieresis, wcircumflex, semicolon, quotereversed, seven.numr, U, phi, V, tau, Abreve, ccaron, germandbls, obreve, perthousand, d, circumflex, OE, emacron, ldot, greater, quotedbl, copyright, R, rcaron, sigma, longs, S, j, g888, brokenbar, periodcentered, A, product, equal, c, umacron, theta, less, r, zeta, G, ccedilla, uni047C.rvrn, xi, second, Idieresis.ss01, hungarumlaut, Lambda, slash, amacron, ubreve, Aringacute, numbersign, Oslash, notequal, K, ampersand, kgreenlandic, nine, gravecomb, backslash, caron.alt, iogonek, aogonek, uring, one.lf, lambda, p, uni047F, g, ecaron, zero.osf, itilde, Idotaccent.ss01, hyphen, thorn, aring, endash, ordfeminine, dieresis, three.numr, ocircumflex, y, braceright, idieresis, g891, one.numr, two.numr, zdotaccent, psi, omicron, gcircumflex.ss02, underscore, gbreve, e, Omegatonos, macron, tonos, sterling, three.osf, dieresistonos, Uhorn, Thorn, ohorn, g.ss02, six.osf, scedilla, Pi, g890, Phi, guilsinglleft, ogonek, napostrophe, infinity, quotedblright, hbar, Q, bracketleft, x, period, bar, bullet, t, gcircumflex, cyrillicbighookUC, Amacron, five.osf, Lslash, eight, dollar, W, two, iacute, ydieresis, dotaccent, question, AE, radical, h, H, s, N, gamma, fraction, logicalnot, franc, anoteleia, quoteright, zero.numr, Imacron, four.numr, z, eight.numr, parenleft, daggerdbl, rho, ebreve, minus, Y, gdotaccent.ss02, peseta, Ibreve.ss01, nine.numr, quotesingle, E, g889, acutecomb, at, asterisk, oe, Z, aringacute, one.osf, asciicircum, asciitilde, emdash, quotedblleft, dcroat, I.ss01, delta, wdieresis, scircumflex, pi, cyrillicbighookLC, paragraph, trademark, l, florin, zcaron, L, multiply, Iotadieresis.ss01, seven, o, Psi, quotesinglbase, Hcircumflex, c.rvrn, ccircumflex, edotaccent, four.osf, two.osf, udieresis, tbar, nu, uni047B, Ldot, ordmasculine, uhungarumlaut, upsilon, abreve, uogonek, gbreve.ss02, Acircumflex, chi, underscoredbl, Adieresis, k, Eth, m, bracketright, P, Aogonek, omega, Emacron, one, Aringacute.rvrn, igrave, Icircumflex.ss01, ellipsis, dotbelowcomb, lessequal, gdotaccent, lozenge, dagger, oslash, B, odieresis, uni047A, ncaron, zero, hcircumflex, Sigma, Ohorn, n, g894, scaron, ohungarumlaut, cedilla, summation, epsilon, uni047D, a, O, three, Imacron.ss01, percent, Eogonek, icircumflex, colon, edieresis, M, registered, integral, Gamma, cent, u, uhorn, guilsinglright, kappa, breve, four, b, cdotaccent, v, currency, J, omacron, degree, beta, Upsilon, q, g892, T, f, hookabovecomb, cyrillichookleft, iota, dong, greaterequal, Tbar, quoteleft, section, minute, Eng, nine.osf, acircumflex, six.numr, plus, parenright, ibreve, seven.osf, lira, F, I, eogonek, approxequal, eight.osf, Xi, Omacron, C, five.numr, yen, Iogonek.ss01, eng, six, plusminus, i, Umacron, eth, caron, imacron, five, w, Theta, exclam, eta, lslash, iotadieresis, uni047E

Hello!

This is an automatically-generated report about possible interpolation problems in OpenSans-Italic[wdth,wght].ttf, as found in the Google Fonts catalog.

To download a PDF version of this report with helpful visuals of the problems, click here; Or to view it on the GitHub website, click here.

The report follows:

Glyph six.osf was not compatible:
  Masters: 'wght=700.0', 'wght=800.0':
    Contour 0 has a kink at 14: 'wght=700.0', 'wght=800.0'

This report was generated using the fonttools varLib.interpolatable tool. We understand that sometimes the tool generates false-positives. Particularly for more complicated font designs. If you did not find this report useful, please accept our apologies and ignore / close it.

To give feedback about this report, please file an issue or open a discussion at fonttools.

Please note that I am doing this as a community service and do not represent Google Fonts.

See google/fonts#3411

• /Open Sans Condensed Italic.glyphs should be removed, and its contents included in the main OpenSans-Italic.glyph file.
• /hinted_ttfs should be renamed /fonts
• /ttfs should either be deleted, or kept in /fonts/unhinted if needed for some reason
• /docs should be added with a sample.something document source and sample.png export of it
• README.md should be filled out, with the PNG /docs/sample.png inlined
• Other things should be done, to make this repo one of the exemplary ones that will pass all the FB checks I've requested :)

In several indigenous languages throughout Australia there are several words that include ḻ, ṉ, ṯ or ṟ characters to indicate a retroflexed consonant.

Unfortunately none of these are supported.

I would like to be able to use these characters rather than many string replacements to underline the character across a website like this one https://parksaustralia.gov.au/uluru/discover/culture/language/.

Hello,
Where can I download the font version with PostScript/CFF outlines?
If there is no such version, please release version otf with psautohint (and woff2 based on this version).

Hey! I am wondering the plan for supporting the Bitcoin (U+20BF, ₿) glyph?

My client’s printer asks for an OTF version of the OpenSans font, is one available? They claim they get errors with the ttf version.

Grateful for any pointers,
thanks,
Fredrik

When you use the medium variant and set it to certain font sizes the font looks very choppy. You can try it out yourself by simply setting the font size in Googe Fonts to 14px and 15px.

https://fonts.google.com/specimen/Open+Sans#standard-styles

Here are example. Look at the "e"s and "o"s.

14px

15px

A super wrote me

this page does not contain the expected font style

  Open Sans Condensed BoldItalic

which combines (!) the styles bold and italic. 

Although there is a style "OpenSans-BoldItalic.ttf" 
a similar one is not available for the condensed font.

I expected to see a file like OpenSans-CondBoldItalic.ttf or OpenSans-CondLightBoldItalic.ttf which both do not exist.

@laerm0 are those available?

If I inspect ./fonts/ttf/OpenSans-Regular.ttf I see there is no U+202F NARROW NO-BREAK SPACE. Since it's a whitespace, some renderers fall back to U+2009 THIN SPACE but for great and reproducible typography this space is needed.

Examples of usage

Some examples in German for dates, units and phone-numbers:

Source

Inspection

Source

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

Artifacts Found

• sources/ttfautohint-vf

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

Is it possible to have a true variable font for Open Sans contained in a single file instead of the current two set of files that need to tbe downloaded to support Regular and Italic?