catharsisfonts / ysabeau Goto Github PK

Hi.

The tilde is rotated a little counterclockwise. I think it should be balanced horizontally.

To easily distinguish the uppercase I from the lowercase L without having a tail on the latter, I like to have crossbars on the former. I don't consider the crossbar a serif. Can you add a character variant that does this?

Several languages spoken across Mexico and Guatemala use the saltillo (representing [ʔ] or [h]) in their orthographies. It’d be awesome if you could add these oft-neglected characters to your typeface :)

U+A78B Ꞌ
U+A78C ꞌ

Hello!

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

The particular version of the font that was tested was archive:.

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 uni048F was not compatible:
  Masters: '', 'wght=250.1318':
    Contour 2 start point differs: 0 in '', 1 in 'wght=250.1318'; reversed: False
  Masters: 'wght=250.1318', 'wght=1.0':
    Contour 2 start point differs: 0 in 'wght=250.1318', 3 in 'wght=1.0'; reversed: False
Glyph uni04B9 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour order differs: [0, 1, 2] in '', [0, 2, 1] in 'wght=1000.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 apologize and ignore & close it.

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

This is one of prettiest & most legible sans-serif fonts I've ever seen. I would like to use it as the default for my ebook reader & all my web browsing when in reader-mode. However, do you think it's possible to create a variation of Ysabeau such that 1) the tops & bottoms of the numerals line up horizontally, and 2) none of the numerals appear to "dip" below other characters in a sentence? My apologies for not having the technical knowledge to describe it in a more precise manner. And sorry for suggesting to make it a little more boring!

I noticed that the shape of the letter Њ (U+040A) was not correct.

The image, compared to several other fonts, shows the problematic part.

Found a few remaining interpolation issues in the Roman source.
YsabeauRoman.glyphs - posted approx. an hour ago.

IJ_acutecomb.liga and whiteCircle do appear broken in the static fonts.
The colonsign and peso.c2sc issues do not appear in the static fonts (because of the variation replacements), but you may still want to fix them.

U+03CF GREEK CAPITAL KAI SYMBOL should be as tall as a capital letter. Here it is beside U+039A GREEK CAPITAL LETTER KAPPA.

I’ve noticed that you have a bunch of local, Mac specific .DS_Store files checked into this repo. They should probably be removed:

ysabeau > find . -name '.DS_Store' -exec git rm {} \;
rm '1. TrueType Font Files/.DS_Store'
rm '2. OpenType Font Files (not up to date)/.DS_Store'
rm '3. Glyphs Source Files/.DS_Store'
rm '4. Legacy Font Files/.DS_Store'

You can then add a new file .gitignore to the root of this repo which contains a single line

.DS_Store

telling git to ignore these files. I’ve got a branch here with the changes, but can’t push; they’re easy enough, though, for you to add them yourself… 😉

Just wanted to say thank you for Ysabeau. I just finished my first real typeset using Ysabeau lined up with EB Garamond.

https://drive.google.com/open?id=16fwqESQ_EYbemv5zgctCGjs-b6y0H6p0

but...

There were some LONG subheadings in this work that forced me to rethink the whole look of the book (like 13 lines of text long the way I originally defined the subheads.) And there's not much out there in the way of tall, narrow fonts that would even begin to blend in. I went with a heavier italic face of Ysabeau so it wasn't so obvious I was squeezing the horizontal, but this only works because this text doesn't use much italic, so you can't see the angle isn't right, with a more advanced typeset (where every body paragraph has 3-10 words italicized, and footnotes have italicized keywords) this cheat won't work. And really, if and when anyone spends much time reading through the subheads, they're going to notice it's squeezed. It's only because these are going to be skipped over most of the time that I did it this way.

So, could you maybe put up a narrow or condensed cut of Ysabeau, (for sale even?) And the same thing for a caption cut for Ysabeau. I have some Bibles with 30-40% footnotes that must be done with a significantly smaller font for annotations, simply increasing the weight doesn't do it completely, I'd need the descenders cropped, and possibly even the ascenders. Both of these cuts would vastly improve the usability of Ysabeau. Currently I don't even try these works with tall fonts, because there's nothing that's close to cutting it. But I believe the whole "put computer shaped text onto paper" thing is wrong... letters like Garamond and Ysabeau are easier to see than letters like Helvetica with no ascender height.

Ok that's all I have to say, I've been looking for something like Ysabeau for a decade. I do love it. You're welcome to close or delete this "issue" once you've read it. :-)

Would it be possible please to make +smcp work for italics? I've faked it in LaTeX by using smaller capital italic characters, but it would be lovely to have it properly

While testing out the font on FontDrop, I noticed that there's lacking a small capital variant for horned lowercase U, as well as the accented variants of it. Below here is the screenshot in action.

Also, it's missing a small caps variant of dotted lowercase Latin U.

As indicated in the title, both files fail to work: trying to open them in KDE's font viewer gives a "font cannot be read" error. Running

otfinfo -i Ysabeau-SemiLight.ttf

I get

otfinfo: Ysabeau-SemiLight.ttf: OTF file corrupted (too small)

If you are going to rename the repo to Ysabeau, do it ASAP as the name-change will require manually updating local repos. Certainly before any Beta or Alpha releases.

The diaereses of U+01D7 LATIN CAPITAL LETTER U WITH DIAERESIS AND ACUTE and U+01DB LATIN CAPITAL LETTER U WITH DIAERESIS AND GRAVE are interpolated incorrectly. Here they are in Ysabeau Regular:

i don't know is it ok, but the descenders in uppercase letters are different from lowercase ones

Hello!

This is an automatically-generated report about possible interpolation problems in YsabeauOffice-Italic[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 uni030A0301 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour 2 interpolation is underweight: '', 'wght=1000.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.

Hello!

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

The particular version of the font that was tested was archive:.

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 uni048F was not compatible:
  Masters: '', 'wght=250.1318':
    Contour 2 start point differs: 0 in '', 1 in 'wght=250.1318'; reversed: False
  Masters: 'wght=250.1318', 'wght=1.0':
    Contour 2 start point differs: 0 in 'wght=250.1318', 3 in 'wght=1.0'; reversed: False
Glyph uni04B9 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour order differs: [0, 1, 2] in '', [0, 2, 1] in 'wght=1000.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 apologize and ignore & close it.

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

I know that the capital i is shorter than the lowercase l, but sometimes that difference is not enough:

Is it possible to make the lowercase l a bit different? Perhaps with a small hook, like on the italic version?

Many thanks for your work!

[side note: I'm testing Eau De Garamond on a document together with Cormorant Garamond (for headings) and EBGaramond (for body text) and it is great! Now I need to find a suitable monospaced font ;) ]

As the title says, the SemiLight and UltraBold weights are not included in Version 2.000 while they were included in the previous version.

I'd like to merge this font with LXGW WenKai for LXGW Bright, which needs the SemiLight weight.

I've observed that with the macOS programs Pages and Keynote the line height changes depending on the weight of the font.
This may not be an issue with Ysabeau itself, because in Word, and even in Text Edit I don't get the behavior. But in Pages and Keynote there are two line heights, that Ysabeau produces, one for thinner weights and another one for heavier weights (it only happens with Ysabeau, to my knowledge not with other fonts).
All the lighter weights behave normally up to Regular.
Italics now adds a few points to the line height and all the heavier weights keep the lines further apart. And then all the heavier weights keep the bigger line height.

Check these images:

Hello!

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

The particular version of the font that was tested was archive:.

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 dollar.BRACKET.varAlt01 was not compatible:
  Masters: '', 'wght=1.0':
    Contour order differs: [0, 1, 2] in '', [0, 2, 1] in 'wght=1.0'
    Contour 1 start point differs: 0 in '', 2 in 'wght=1.0'; reversed: False

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 apologize and ignore & close it.

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

Hello!

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

The particular version of the font that was tested was archive:.

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 uni048F was not compatible:
  Masters: '', 'wght=250.1318':
    Contour 2 start point differs: 0 in '', 1 in 'wght=250.1318'; reversed: False
  Masters: 'wght=250.1318', 'wght=1.0':
    Contour 2 start point differs: 0 in 'wght=250.1318', 3 in 'wght=1.0'; reversed: False
Glyph uni04B9 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour order differs: [0, 1, 2] in '', [0, 2, 1] in 'wght=1000.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 apologize and ignore & close it.

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

Thank you for the great font! It is very fresh and beautiful! Definitely one of the best fonts I’ve ever seen.

Yet there’s a small change that can make it even better.

The thing is that the “square” top of Cyrillic lowercase italic “л“ does not fully corresponds with the “handwriting-like” character of italics. It is more common to see the left leg slightly rounded at top, like in Calibri or Corbel:

Best regards!

Hello,

I'm commissioned to prepare Ysabeau for release on Google Fonts.

There are some aspects of the font which are not following GF specs. I'll start with the most glaring example, which makes Ysabeau unpublishable in its current shape: The weight setup.

You've reused weight classes several times in three instances, but weight classes must be unique, allowing a maximum of 9 instances (from 100 to 900). GF specs also allow weight class 1 and 1000, tho they are currently not yet supported by the API, meaning they will be dropped, but in future updates those could be made available.

See https://googlefonts.github.io/gf-guide/variable.html#wght
and https://github.com/googlefonts/axisregistry/blob/main/Lib/axisregistry/data/weight.textproto

Given that you've carefully spaced out the weights across the axis, I'm not sure how to continue.

But tbh, I don't think there's a way around redefining the weights to meet the specs. Any way I look at it, only a maximum of 11 weights are possible for Google Fonts, with only 9 being publishable right away, with the other 2 (1 & 1000) having to wait until they are officially supported (and we shouldn't wait for that)

The modifier left and right half rings are more or less deformed in the regular, extra-light, light, semi-light, and medium weights. In the italics of these weights, the percent sign is also defective. (I haven’t checked the infant fonts).

Thanks for making fonts with modifier half rings; they’re essential in my work!

Trying to set some works, and these Glyphs added in Unicode 13 are still not in any useful form/font. Babelstone Han is closest, but it's a "HAN" font, and LibreOffice doesn't (properly) subset... so adding this one glyph adds tens of megs to file size just to properly include an abbreviation.

Letter like symbols about rights usage:
01F10D - OpenLicensed
01F10F - NonCommercial
01F12E - Warenzeichen
01F12F - Copyleft
01F16A - Marque de Commerce
01F16B - Marque deposee
01F16C - Marca registrada
01F16D - Creative Commons
01F16E - Public Domain
01F1AD - Mask work

(And although these last glyphs have no letters in them, they belong in this list because where they get used is intermixed with text, and having a font that deals with all of them and a full set of letters makes typesetting it much simpler.)
01F10E - ShareAlike
01F16F - Attribution

Also, there are other useful items in that unicode block (Enclosed aphanumeric supplicement U1F100 - U1F1FF) which might help others using Ysabeau. I use Ysabeau as a pro level typographic font, and the glyphs I've listed will help me in listing rights and attribution properly. Ysabeau already supports a few of these (copyright, protected, Trademark, etc.) This longer list seems like it belongs...

(and for Cormorant too. But a sans font is what I always use for rights declaration. I won't personally use these emblems in Cormorant.)

Hello CatharsisFont,

I recently discovered your Ysabeau font on Google Fonts, and downloaded it. It is gorgeous. Compliments for your wonderful work. I appreciate not only the beauty of the design but also the richness of the glyphs set, which would make it perfect for linguistics, an important field for me.

Unfortunately, I have a problem, which in practice makes the font unusable for most texts. While the font shows correctly on Google Fonts, when downloaded in my computer (Mac) some "negative" white spaces appear in intersections of shapes in common letters, where they should be black (see picture). I have the same issue in Word, TextEdit, Font Book, LibreOffice.

I'm not an expert of fonts or coding (I actually just signed up here just to write this to you), but I like them a lot and have a lot, and I think this is the first time that I've found a difference between how the font appears on Google Fonts and how it appears on my computer.

Do you think it could be fixed?

Thank you and keep up the good work.

Request support for raised ordinals (with ordn on) like in 1er, 1st, 52nd, etc.

Ysabeau + ordn currently only substitutes raised letters a and o following figures. For at least Spanish and (archaically) English, ordinals with other letters are also written like this.

Based on the spec and this Glyphs discussion, if this is implemented, this would be a contextual substitution of \d[a-z]+ but it seems some popular fonts substitute all lowercase Latin with their raised glyphs regardless of context, which was unexpected for me.

In any case, the user still has to use ordn based on semantic context, e.g. not for most English style guides and to avoid messing up non-ordinals like "a11y."

By the way, I just discovered Ysabeau today and it is absolutely stunning and supports just about every feature I was looking for—open license, Greek, small caps, dotted zero, and more. It seems amazing for scientific writing using modern web typography tech. Thank you!

interpo error between first 3 masters

Maybe I’m missing something but although the parenthesis change correctly in size the figures do not:

Especially in headlines with dates that are typeset in all smallcaps it would be nice if the figures would align to the roman. What do you think?

Ulrich

I was thinking of creating a monospaced version of this font, I think it would make a great competitor to Operator Mono!

Any thoughts?

In the README:

If you wish to use the Ysabeau type family on your website, you will be able to obtain it from the Google Fonts service once it is finished.

But I can't find any fonts on Google Fonts when searching ysabeau. Is it finished?

In bold variants, some characters are not generated correctly: U+003A, U+003B, U+02BC. It seems to me that everything else is as it should be.

EDIT: In fact, I have now noticed that it is the same with Ysabeau-Hairline.

This is because, GlyphsApp is only available in macOS.

This is self-explanatory, although the TrueType font files should still work on web browsers.

Hello!

This is an automatically-generated report about possible interpolation problems in YsabeauInfant-Italic[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 uni030A0301 was not compatible:
  Masters: '', 'wght=1000.0':
    Contour 2 interpolation is underweight: '', 'wght=1000.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'll start by saying this is probably just down to personal preference, but let's have a look at the uppercase W of your previous font, Commorant (that seems to me as pretty much a companion to this one):

Now let's have a look at EauDeGaramond's uppercase W:

Aside from one being a serif font and the other being sans-serif, what's the big difference? The first has four upper-terminals while the second has three. More than that, while on the first the lines meet a little before their end, in the second they meet right at the end-point.

And why is it a problem?

Well, as I said, it's mostly down to personal preference, but 3 upper-terminals that meet right at the end-point is a bit... bland. Every sans-serif font does it. Arial does it, Calibri does it, Franklin Gothic does it, even Roboto does it. It's bland. Not only that, but I feel like it does not go well with the 4 terminals of Commorant.

Compare with something like Scala Sans:

Four upper-terminals in sans-serif makes the font a bit more unique, but it's also not so uncommon that it seems more like the designer is just trying to bring attention to themselves.

Of course, a similar effect can be achieved by just moving the meeting point between the two central lines of the central upper-terminal little below their current position, cutting one of them short, but I believe 4 upper-terminals would be a more elegant solution.