andrew-paglinawan / quicksandfamily Goto Github PK

i see that Į capital symbol is missing in regular and medium fonts. Can you fix that?

I discovered yesterday that the Greek lowercase mu (μ) character seemed to be missing from the regular and medium weights.

On the Google Fonts page for Quicksand (https://fonts.google.com/specimen/Quicksand), I see this:

I also used another site (http://torinak.com/font/lsfont.html) to view all the available characters and noticed the same thing:

The kerning on the number 4 seems to have quite a lot of extra space, so creates a separation when used to show numbers, eg:

This is font weight 700 and a font-size of 1.4em

When opening some Quicksand TTF files, the Windows font installer shows the font name as "Quicksand Light."
I keep trying to reference this font in code and seeing "Quicksand Medium not installed" /etc errors.

2.1 is lacking Italic sources. Is this intentional. The ReadMe states - Added true italics for each weight

Old release on GF features Italics.

Cheers,
Marc

MacBook running 10.15.6 (19G2021)
Google Chrome Version 85.0.4183.83 (Offizieller Build) (64-Bit)
Using the woff2 from Google Fonts

So I'm trying to use Quicksand font (really like the look) for a document in Word (O365 v16) and for some reason, sometimes the font looks like this:

Sometimes it looks like this:

Same document. Same font/size. Nothing changed.
Tried opening in different computer; same issue.

Any idea why is this happening?

Note: headings are using LATO font. Body is QUICKSAND.

This issue has been reported in google/fonts repo: google/fonts#2642

• division sign is lower than the other signs
• mathematical signs are generally a bit low to get along with lining figures as default style.

The Indian Rupee symbol is a welcome addition. It has a small issue which hampers its recognisability. The middle horizontal bar is smaller than the top bar. Ideally, they should be equal in width. Looks odd with the smaller bar.


Reference: https://en.wikipedia.org/wiki/Indian_rupee_sign

Please forgive me if this isn’t due to font support, but to me it seems like the variable quicksand font doesn’t support tabular nums:

font-variant-numeric: tabular-nums;

(See https://developer.mozilla.org/en-US/docs/Web/CSS/font-variant-numeric)

Would be an even greater font if tabular nums are suported so that numbers can be shown better in tables or when they frequently change ❤️

I created a poster with the font Quicksand. The printer sent me the «printing approval» and it suddenly shows errors in the font (see picture). Is there an explanation or a solution?

Hey folks,

I'm not aware of the brief but we have 4 weights in the Roman, Light, Regular, Medium and Bold.

In the v2.0 folder we had 3 seperate .glyphs files for Light Italic, Regular Italic and Bold Italic. I combined them and they're not compatible, hence why Medium is screwed.

Are we releasing the Italics as 3 weights or do we need 4 weights. Sorry I expected this to be in better condition or maybe I'm missing something?

@ThomasJockin @davelab6

Cheers,
Marc

Hi,

Are there any plans to add Cyrillic alphabet support?

Thank you in advance.

Thanks for this awesome font!

We found that the rendering / kerning of numbers is irregular (using Google Fonts). This makes it hard to use the font for prices, e.g. "147.- €".

Is there a way to fix this in CSS which works across browsers? Or does the font need to be adjusted?

Hello.

The Ukranian [і] and [ї] character is displayed as an empty box when [Quicksand] is used as font.

This one will probably have an issue too: [ґ].

The german letter "ß" is not rendered correctly. There is an additional point on the left side of the letter that is not supposed to be there. See attached screenshot:

I just noticed that Google Fonts has Semibold (600) which this repo doesn't contain. Glyphs file as well doesn't even seem to contain Semibold.

@m4rc1e @andrew-paglinawan Do you have an internal newer version of the sources at Google Fonts? Please let me know.
Also I noticed that the build.sh script creates a statics directory without actually generating statics in it.

https://github.com/andrew-paglinawan/QuicksandFamily/blob/master/documentation/OFL.txt#L2 has an RFN

A reserved font name isn't a good idea for 2 reasons.

1. It makes the process of collaboration via github cumbersome; if a
   memberof the general public clicks the 'fork' button up top right, they
   must either seek permission from you before-hand to use the RFN, or to
   immediately change the font name in the files as part of their first
   modification, and then you'll have to change it back.
2. Many websites who self host the font files will modify them, doing
   subsetting and format conversion, which are both explicitly defined in the
   OFL as kinds of modification subject to the RFN restriction. SIL have been
   willing to offer their view that the most popular web font formats are not
   format conversions subject to the RFN restriction, but popular web font
   bundling service Font Squirrel includes the less popular formats too, which
   do. And subsetting remains. So, changing the name or contacting you are
   both administrative burdens for these downstream users, and if they do
   contact you, for you; and many people won't think carefully about this and
   will just do so without asking, which formally terminates their license.
   Putting them in that position is not a good situation.

So not having any RFNs is my best recommendation. To do this, just remove that line. Note that only @andrew-paglinawan can do this :)