jpt / barlow Goto Github PK
View Code? Open in Web Editor NEWBarlow: a straight-sided sans-serif superfamily
Home Page: https://tribby.com/fonts/barlow
License: SIL Open Font License 1.1
Barlow: a straight-sided sans-serif superfamily
Home Page: https://tribby.com/fonts/barlow
License: SIL Open Font License 1.1
My understanding is this glyph should be vertically centered within the x height. I'm seeing it the same as a period/full-stop — on the baseline.
Real ones! This is a ways off. But I removed the existing faux obliques from the Glyphs file and elsewhere for now; even if the released italics end up being mostly or entirely faux obliques (looked pretty good with "Transformations;Slant:7;SlantCorrection:0;Origin:4;"), the standard workflow seems to be having them in a separate file.
It would be nice to have a slnt
axis, however. Along with #10, I'm thinking a variable font needs to be an entirely separate compilation step that may involve combining compatible masters from separate Glyphs files into one.
Right now I have a lot of brace layers at semicondensed (and everywhere) that I won't need if I just open up the corners of some of the drawings. Should help GX too, which is ready except for #10
Anyway, drawings should be like
this (new)
instead of this (old)
We use Barlow for our admin interface at my company, and we've been having problems with the legibility of the lowercase i at 14px, semi-bold weight -- it's blurry enough to look like a lowercase l (L). (Note: this is not a problem on retina displays, or other high-pixel-density screens.)
In investigating this problem, I was surprised to find that Google font's specimen page for Barlow does not have the same problem. At the same size and weight, the i's details are crisp and distinct, as are certain features of other glyphs, like the top of lowercase "f"s.
After running through all the CSS styles on the text in an attempt to figure out what Google fonts might be doing, I finally tried grabbing the font file that their specimen page uses directly... and I found that I was able to get the crisp version myself. You can see a comparison of the two on this CodePen. And, in case you don't have a screen that produces the same differences, here's a screenshot:
I downloaded the official version of Barlow from this repo and double-checked against the .woff2
versions of the files, just to make sure, and I got the same blurry rendering displayed shown above in the lower example.
For the moment, I've plucked these mysterious versions from the Google fonts specimen page and am using them, which solves my problem, but I'd love to solve the mystery. I'm not a typeface expert, so I don't know if there's a possibility there was some kind of regression involving hinting (?) or something else at some stage in Barlow's development and that Google Fonts has an older version of the file for their specimen page.
Here's an example of how the new version of the files I grabbed changed our admin interface:
BEFORE:
AFTER:
I was hoping someone here might be able to shed some light on the problem. I thought it might be significant for Barlow's use, too, since this has a fairly major effect on Barlow's appearance on many screens at fairly normal size and weight. Thank you!
This is only a proposition - I think, that Barlow font with the polish characters will be presented more better, if the polish "ogonki" gonna be equaled with a dot on letter "i" in one horizontaly position. The images below show also the size of "i" and "ż" ogonki dot, which is not correct (in my opinion) position (red arrows). The proposed correct position is showed by green arrows.
What do you think about it?
Ps.
The font I choosed for images is "Barlow Regular", with 1.104 version.
Hi all,
on Windows PCs we recognized a strange behaviour with barlow. When you turn on MS-Words "show markup" function, in Barlow a space shows a "." glyph instead of a floating point. This makes it really hard to differ spaces from full stops.
I think it is U00B7.
cheers
Sebastian
extensively using MIDDLE DOT but what a pity Barlow puts FULL STOP instead (Mac: alt-shift-9)
The ť glyph (U+0165) uses a wrong caron symbol. You already have the correct caron that should be used in the ď glyph (U+010F).
Applies only to lowercase ť, not to uppercase Ť.
Hello,
This font is great. Clear and professional. And beauty. But, I have found an one big problem with kerning polish "ł" character with some other letters. I have send you an screenshots. It seems, that there is only need to increase a space after and before polish "ł", when this letter appears in pair with most of next characters.
Also, after polish "ą" there is little too big space. But it is not a big problem.
Can you fix this "ł" error? I will be a very thankful! :)
Could you list some examples of Barlow out in the wild? Love how it's being used here: https://tribby.com/fonts/barlow/#specimen
Typography Noob here. But Barlow is perfect. While I reckon the g does lend a personality to the typeface, had to recently switch it out on a project because the client found the g to be an of all amongst all the other letter forms.
Is there a way to tweak the font and add in an extended tail to the g such that it is elongated without looking out of place?
This will add.... 54 more styles, but is this something anyone would want, a Barlow SC, Barlow Condensed SC, Barlow SemiCondensed SC? Does an SC really need to exist can can TT or OTF features be used? I know in CSS it's font-feature-stettings: 'smcp'
, and the woff built from TTF supports it, which for me is "fine for web." I think font-variant: small-caps
is for TTF specifically?
So if it exists in spec of files, does anyone actually have a use case for SC font files? Some print application I am not considering?
Language (code) | Coverage | %Coverage | Missing Characters |
---|---|---|---|
Vietnamese (vi) | 104/157 | 66 | \u2010 (‐), \u0129 (ĩ), \u2032 (′), \u2033 (″), \u0169 (ũ), \u01a0 (Ơ), \u01a1 (ơ), \u1ea1 (ạ), \u1ea3 (ả), \u1ea5 (ấ), \u1ea7 (ầ), \u1ea9 (ẩ), \u1eab (ẫ), \u1ead (ậ), \u1eaf (ắ), \u01af (Ư), \u01b0 (ư), \u1eb1 (ằ), \u1eb3 (ẳ), \u1eb5 (ẵ), \u1eb7 (ặ), \u1eb9 (ẹ), \u1ebb (ẻ), \u1ebd (ẽ), \u1ebf (ế), \u1ec1 (ề), \u1ec3 (ể), \u1ec5 (ễ), \u1ec7 (ệ), \u1ec9 (ỉ), \u1ecb (ị), \u1ecd (ọ), \u1ecf (ỏ), \u1ed1 (ố), \u1ed3 (ồ), \u1ed5 (ổ), \u1ed7 (ỗ), \u1ed9 (ộ), \u1edb (ớ), \u1edd (ờ), \u1edf (ở), \u1ee1 (ỡ), \u1ee3 (ợ), \u1ee5 (ụ), \u1ee7 (ủ), \u1ee9 (ứ), \u1eeb (ừ), \u1eed (ử), \u1eef (ữ), \u1ef1 (ự), \u1ef5 (ỵ), \u1ef7 (ỷ), \u1ef9 (ỹ) |
I'd like to request just a few languages which have over 90% character support and are just missing a few characters according to Unicode CLDR :)
Language (code) | Coverage | %Coverage | Missing Characters |
---|---|---|---|
Romanian (ro) | 101/102 | 99 | \u2010 (‐) |
Estonian (et) | 104/105 | 99 | \u014f (ŏ) |
French (fr) | 111/113 | 98 | \u2010 (‐), \u01d4 (ǔ) |
Indonesian (id) | 73/74 | 98 | \u2010 (‐) |
Serbian (Latin) (sr-Latn) | 83/84 | 98 | \u2010 (‐) |
Dutch (nl) | 107/110 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Polish (pl) | 123/126 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Latvian (lv) | 106/109 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Swedish (sv) | 106/109 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Afrikaans (af) | 105/108 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Icelandic (is) | 100/103 | 97 | \u2010 (‐), \u2032 (′), \u2033 (″) |
German (de) | 121/126 | 96 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u014f (ŏ), \u016d (ŭ) |
Czech (cs) | 125/130 | 96 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u014f (ŏ), \u016d (ŭ) |
Danish (da) | 106/110 | 96 | \u2010 (‐), \u2032 (′), \u2033 (″), \u01ff (ǿ) |
Filipino (fil) | 94/97 | 96 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Croatian (hr) | 86/89 | 96 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Lithuanian (lt) | 102/106 | 96 | \u2010 (‐), \u0129 (ĩ), \u0169 (ũ), \u1ebd (ẽ) |
Slovak (sk) | 126/131 | 96 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u014f (ŏ), \u016d (ŭ) |
Slovenian (sl) | 108/112 | 96 | \u0115 (ĕ), \u012d (ĭ), \u014f (ŏ), \u016d (ŭ) |
Malay (ms) | 80/83 | 96 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Albanian (sq) | 84/87 | 96 | \u2010 (‐), \u2032 (′), \u2033 (″) |
Finnish (fi) | 154/162 | 95 | \u2010 (‐), \u021f (ȟ), \u015d (ŝ), \u0292 (ʒ), \u01e5 (ǥ), \u01e7 (ǧ), \u01e9 (ǩ), \u01ef (ǯ) |
English (en) | 114/121 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
English (United Kingdom) (en-GB) | 114/121 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Spanish (es) | 123/130 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Spanish (Latin America) (es-419) | 123/130 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Portuguese (pt) | 117/124 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Turkish (tr) | 123/130 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Hungarian (hu) | 126/133 | 94 | \u0115 (ĕ), \u012d (ĭ), \u014f (ŏ), \u2052 (⁒), \u016d (ŭ), \u27e8 (⟨), \u27e9 (⟩) |
Portuguese (Portugal) (pt-PT) | 117/124 | 94 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u014f (ŏ), \u016d (ŭ) |
Azerbaijani (az) | 92/97 | 94 | \u2010 (‐), \u2032 (′), \u2033 (″), \u0259 (ə), \u018f (Ə) |
Uzbek (uz) | 82/87 | 94 | \u2010 (‐), \u2032 (′), \u2033 (″), \u02bb (ʻ), \u02bc (ʼ) |
Catalan (ca) | 121/129 | 93 | \u2010 (‐), \u0115 (ĕ), \u012d (ĭ), \u2032 (′), \u2033 (″), \u0140 (ŀ), \u014f (ŏ), \u016d (ŭ) |
There seems to be an issue with the lower case 'c' on certain weights when used with the Adobe Suite.
See the screenshots below for the 'c' used in Illustrator and Sketch with Barlow Semibold.
The 'c' in Illustrator appears to have an extra point along the bottom curve.
I tried self-hosting font files and ran into rendering issues on Windows and Ubuntu that I don't see when using Google Fonts. It looks fine on Mac in both cases.
On Ubuntu and Windows the baseline of the characters is inconsistent, leading to lines with some characters higher than others. Note that this is using the files from a git pull of tag 1.422.
An image showing the problem and the css used to load the font are attached.
First of all thank you for this wonderful font and all its many weights and variants.
I've been using it recently in some Office documents, but due to how windows selects fonts when using "Bold" text in Powerpoint or Word, the results are a bit too heavy. I know that it is also a question of personal aesthetics but please see the example below:
The first line is using Barlow
(weight 400) and the last part is using Word's Bold option. It seems to be selecting the Barlow Bold
font (weight 700)
For comparison's sake, the second line is using Barlow Medium
(weight 500) and when using Word's Bold option, Word interpolates a weight that seems to have quite lighter contrast.
In the third line I have manually selected alternative fonts to arrive at a more pleasing result (for me): Barlow
with Barlow SemiBold
(weight 600) instead of using Word's Bold option.
I'm not sure what an elegant solution would be. As an example, I edited the metadata of Barlow Semi Condensed
and changed its family to Barlow Semi Condensed Standard
thus preventing Word from automatically selecting Barlow Semi Condensed Bold
. You can see the difference below. In the first line I use the official Barlow Semi Condensed
and the second line uses the one with the modified metadata:
As you can see the interpolated option in the second line looks better (again IMHO)
I did a fairly poor job of drawing these Glyphs
Would probably be an improvement for the Bold thru Black weights if it looked more like the currency symbol with only one slash e.g.
Need to figure out if it's possible to have contextual alternates in variable fonts, so if the weight axis is > 700 (or whatever), it switches out
Looking into this... contacted Georg/Ranier in case it is a bracket layer thing. Maybe be due to decomposition of components too... not sure. /V/F/l/i are correct here but all have same weight / width (using font-variation-settings: 'wght' and 'wdth'). Also width goes in reverse order, may be the culprit.. Lots of possibilities.
We have a spec here
Copyright string should be:
Copyright 2017 The Barlow Project Authors (https://github.com/jpt/barlow)
This should also be the first line of the OTF.txt doc
The repo structure should look like the following examples:
Nunito, Montserrat
Font Metadata:
In order to do this, we need to enable Use_Typo_Metrics
We also need to assign all the vertical metric values to each master. To match the same visual linespace and ensure future compatibility, the following values are needed:
typoAscender: 1000
typoDescender: -200
typoLineGap: 0
winAscent: 958 (family ymax bbox)
winDescent: 211 (family ymin bbox)
hheaAscander: 1000
hheaDescnder: -200
Hope this helps, cheers,
Marc
how to build the font without interaction?
It seems like the glyph for unicode Superscript Zero, U2070, is missing. At least on the Semi Condensed fonts. All the other unicode superscript numbers are present. Was the zero skipped on purpose or was that an oversight?
The missing superscript zero is causing me some headaches so unless there's a good reason not to add it I'd love to see it get added.
Thanks for your hard work!
Hi, first of all congratulations for this super font.
I noticed that there is a problem with kerning with uppercase "LT" letter combination, there seems to be too much white space between these two letters.
You can try in example with words like "ALTAIR", "VOLTAGE", and so on, this minor issue is leaving a blank space in the middle of the word that is slightly distracting. It is more prominent with light font weights, but even in heavier ones it is noticeable, and all three variations (regular, condensed and semi) seem to be affected.
Would you consider fixing this?
Thank you.
I'm trying to use Barlow in https://github.com/ltGuillaume/MusicFolderPlayer, thus I'm really happy that the tabular figures were added (#27). For smaller font sizes, the "1" does seem to be off, though (tested the .woff in Firefox and Chromium). The angle seems strange and it's not as sharp as it should be, don't you agree?
I've had a couple requests for this, seems like a common enough feature to support
if add mono space style, that's perfect!
Not sure how to define arbitrary axes in Glyphs but would be cool if the smallcaps could be part of the GX file (or whatever ends up winning on the web)
I absolutely love this font and I've been searching for a free good looking DIN/Highway Gothic alternative for years, but what about Cyrillic support? Any plans for that?
Support all 219 latin unique glyphs, currently at 163.
Hello,
a very nice font!!!! We like it very much. We have the problem, if the font is printed on an HP-Printer, the umlauts are not printed regular. Is this a know problem? What can we do? With other printers it is not problem!??
Best regards
Andreas
The ľ glyph (U+013E) and also upper case Ľ (U+013D) uses a wrong caron symbol. You already have the correct caron that should be used in the ď glyph (U+010F).
Also thank you for good work and great font.
I noticed that when downloading the font at tribby.com/fonts/barlow/, the archive https://tribby.com/fonts/barlow/download/barlow-1.408.zip doesn’t contain many italic font files in the OTF version under fonts/otf/
. As far as I can tell, the italic variants aren’t new, and it looks they should have been included in that file.
In case that’s right, it would be nice if the archive file could be updated to include the italic versions 🙂.
Similar to #9, it also (incidentally) fixes the rendering error in webkit with overlapping shapes in the variable TTF file
I imagine I will write a Glyphs script to do this using its own rounding function, because I would like to maintain a separate source file with a "lossless" (i.e. non-rounded, still has components) version of Barlow. This will be a separate source file step for variable font compilation only I suppose
The ø/Ø-character does not have a full line through it in the bolder versions. This creates low readability, as it is hard to see that it is a Ø and not a O. It's not a "Ø" unless there is a whole line through the "O"!
Suggested solution: Sacrificy some of the boldness of the line in order to have a full line.
Please add a LICENSE file stating the terms of the project :)
Hi!
First of all, thanks for your work on this awesome font.
I am loading Barlow Regular from Google Fonts on a website. When using the interpunct (middot) character, which is a needed character in Catalan language, it is positioned incorrectly. This is how the word "col·laboradors" is rendered, notice the middot on top of the first l:
I am sure I am using the correct middot character (U+00B7). This is definitely not the expected behaviour, but I am not sure if this is a font problem, a Google Fonts problem, or a problem on my end. Could you please investigate this issue and let me know if there is anything I can do on my side to fix this?
Thanks in advance!
Jordi
The link in README.md goes to a suspended account.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.