Libre Baskerville font missing the italic variant

[wonrax]

Describe the feature you'd like to request

The Libre Baskerville font on Fontsource currently doesn't contain the italic variant, which is different than the normal variant with italic font style. For reference, this font on Google Fonts features 3 styles - Regular, Regular Italic and Bold.

References:
https://github.com/impallari/Libre-Baskerville
https://fonts.google.com/specimen/Libre+Baskerville

Describe the solution you'd like

Add the italic variant.

Describe alternatives you've considered

No response

Additional context

No response

[wonrax]

I just went to look for other fonts and discovered that actually all of them don't have any italic version while the ones on Google Fonts do. This seems to be a larger problem than a single font's mistake.

This is the Playfair Display font with the Regular Italic variant on Google Fonts:

And this is the Playfair Display Regular on Fontsource with italic style enabled:

I don't know why the Fontsource's font curator made the decision to exclude the italic variants when generating and bundling fonts, but for people that use the italic variant for display, this really matters. If you slap a font-style: italic on a regular variant, it doesn't look the same as using the italic variant.

[ayuhito]

Good catch! This is a bug with the website rather than the actual files itself. We weren't updating the CSS to point to the italic variants when switching the style. I'll look into it.

[ayuhito]

This should be fixed with #927. However, just noting that you will notice Libre Baskerville 700 Italic won't load, which is a separate bug tracked in #855 where some fonts support 400, 400i, 700 but not 700i.

[wonrax]

Thanks for your work. I think this is why Google Fonts displays all the variants on the same page instead of organizing into categories (i.e. normal and italic).

[ayuhito]

Yup, the issue stems deeper for us since our original API implementation didn't consider this to be a possibility, so it's a little difficult to workaround with since our website relies on said API.