There is too much space between “i” and “x”. Try the word, “Pixels”.

Symbols ™ or © are not well sized or placed (see https://fonts.google.com/specimen/Urbanist?preview.text=%E2%84%A2%C2%A9&preview.text_type=custom)

Thanks

Tops and bottoms of the curves on abdghmnpqu are pretty pinched.
The highest and lowest points of the curves on these offset shapes should be more offset.

Hi there!

After comparing different Google sources I loved yours.
When using it I have found an issue between the letters "i" and "g" when using the word "design". This can be seen in the heavier variants.
It would be great to correct it if you have time. I'll let you know if I find more.

Greetings.
Carlos.

h and m could use more thinning where the strokes join

The degree symbol is not displayed correctly -> '60o'
I don't mean the glyphs.
60ª
60º

Thanks for your work

i have zero knowledge of typography, but i'll show changes visually

• 4 looks too weird, especially with larger text size and lighter weights
• 0 is too fat
  
  Legend:
  First column: Proposed change
  Second column: Urbanist 1.303
  Third column: Proposed vs original - proposed changes are in red

The interior section of the bold f really doesn't work well. Could use a more "defined" top hook.

Love this font - is it possible to add support for tabular figures, such that 111 and 123 take up the same amount of space when using the following CSS properties?

font-variant: tabular-nums;
-moz-font-feature-settings: "tnum";
-webkit-font-feature-settings: "tnum";
font-feature-settings: "tnum"

Do you plan to introduce the Cyrillic alphabet?

The images in the README show lowercase 't' with a crossbar lined up with x-height, which looks very nice, but the current font files render 't' with a much lower crossbar that appears out of place next to most other characters (particularly 'r' and 'z'). 'f' shares the same crossbar height, but is less awkward looking due to its taller ascender.

Símbolo de grado y ordinal confuso. Se muestra como parecido a esto '60o'.

• 60ª
• 60º

Una gran fuente. He encontrado una buena sustituta a la Futura :)

Thank you very much!

First off, I just want to say good job on this font. It's coming along rather nicely.

I've noticed some kerning offset gradually appearing between certain characters as the font gets bolder.
Notice the i's spacing progressively getting unbalanced between the two bordering t's:

I'm no typographer so I don't know how I could help, but I thought I'd point this out as it can sometimes become pretty apparent with headings (and kerning can be troublesome to fix at specific places when using the font for web)

Fontbakery report

Fontbakery version: 0.7.15

--- Rationale ---

There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.

If Font Bakery is not running on an OSX machine, the machine running Font
Bakery could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure
call (rpc).

There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/master/prebuilt/workarounds/ftxvalidator/ssh-implementation/ftxvalidator

Summary

Note: The following loglevels were omitted in this report:

• SKIP
• INFO
• PASS
• DEBUG

Diff images: urbanist_qa.zip

The “corners” of the rounds seem kind of little pushed in. See COobpq (in bold especially). Also the hmn shoulders particularly feel kind of slumped so we could try bringing them out a bit more.

See google/fonts#3411

Can you reorder the instances in the sources from Thin to Black ?

Are there any plans to release a woff2 variant of the variable font? This would help massively with our bundlesize

I recently downloaded the latest release of the font, due to an issue with the version hosted on Google Fonts regarding the trademark symbol.

The latest version does fix the trademark issue, but the registered symbol now looks banged up.

Google Fonts version:

Current release:

Hey Corey,

I found a not smooth curve in the capital "B".
It is seen more in Bold, ExtraBold and Black.
Attached capture.

Cheers.
Carlos.

Sorry I haven't spotted it earlier, your design is missing anchors, preventing from generating a proper mark_to_mark feature. This feature allow combination of accents for non-encoded letters. you can add them with cmd+u in glyphs. Then make sure your accented letters have automatic alignment, and adjust positon of accents by moving the anchors.

the tuto is pretty straightfoward : https://glyphsapp.com/learn/diacritics

Hello,
Liked this font so much, I want to use it on my website. But I can't use it because there is no support for Turkish letters. Can you please add Turkish letters like İ, Ğ, Ü, Ş, Ç, Ö, ğ, ü, ş, ç, ö?

While testing Version 1.310 of the typeface, I realized that a (U+61 LATIN SMALL LETTER A) is not properly slanted in thicker weights! (Especially the Regular weight, of course.) Below here is the screenshot of Ubanist Black Italic on Windows 10 Pro, version 21H2 (Build 19044.1706):

Polish language is based on Latin script with addition of a few diacritics.
Polish diacritics are ą Ą ć Ć ę Ę ł Ł ń Ń ó Ó ś Ś ż Ż ź Ź.

Looks like the font currently handles almost all of them correctly, only ł Ł are unable to be rendered. Checked in the Google Fonts preview.

Polish language is the 7th language with most native speakers in Europe with ca. 40 million native speakers. Millions of Polish speakers can also be found in countries such as Germany, Czech Republic, Slovakia, Canada, Argentina, Brazil, Israel, Australia, the United Kingdom and the United States.
I think adding missing Polish diacritics would make sense for the font, especially that most letters (standard Latin + most of Polish diacritics) for Polish are already implemented.

In STAT:

• Double Black instances.
• Regular instance should be elidable.
• Italic instances are missing (two instances: Roman, elided, and Italic).

In fvar and name:

• postscriptNameID should have a nameID 25 component.

gftools gen-stat could solve these issues.

Noticed some extra spacing between some letters from the Medium weight up to the Black weight.

Screenshots Below

| | |

Hey, I just found this font on Google Fonts and I love it.

I've found that the i's have too much space when next to an a, v or e.

I attached some screenshots.

Not sure if it's intentional, but I think it would look better if it had a little less spacing after the i'

Thank you for the great font.

Axis mapping for weight axis is linear when could profit from a non-linear progression
example: https://glyphsapp.com/learn/creating-a-variable-font (axis mapping section at the bottom of the page)

The entire Polish alphabet is supported except for the letter ł (and capital version Ł).

It's seems the kerning on V, T and Ws in caps is too wide when pairing it with As or Os. Should be more compressed. It's very noticeable in the word FOV where the V is very far away.

Maybe there are other combinations, but I haven't seen them so far.

Please see screenshot compared with other fonts.

When using Illustrator I can use optical kerning and that (kinda) fixes it but that option not available when importing the font to software like UE5.

Not sure if it matters, but I'm using Windows

Letters ū Ū get distorted on chromium based browsers when they have any character before or after it. The dash above the letter gets moved to the right side of the letter.
Issue can be reproduced on google fonts using any chromium based browser.
No issue on firefox though.

Ss should be pretty symmetrical right now. Maybe try shrinking the size of the upper half of these glyphs