I somehow wound up owning python-sphinx_rtd_theme, I think probably because I was the first person to attempt to do a build that needed it. :-) Anyhow, I am not at all sure that I am competent to be the maintainer. I need some advice. There is a new upstream version available, 0.4.0. I am looking at it right now, and my attempts at unbundling fonts from this package seem to be unraveling.
Three font families are bundled: fontawesome, Roboto Slab, and Lato. We have all 3 of these in Fedora, but the problem is that this package wants the web versions of these fonts, too. We have fontawesome-fonts-web, but we do not have .eot, .woff, or .woff2 files available for the other 2 fonts, so far as I am able to determine. Since the .ttf files of those fonts are not byte-equivalent to the ones we ship ... I'm not sure what is safe to do here. I am not any kind of font expert.
The upstream tarball is here: https://files.pythonhosted.org/packages/source/s/sphinx_rtd_theme/sphinx_rtd.... Any advice on how to deal with those fonts is most welcome. Any offers from someone more competent than me to maintain this package would be gratefully received.
Regards,
On 7.6.2018 03:05, Jerry James wrote:
I somehow wound up owning python-sphinx_rtd_theme, I think probably because I was the first person to attempt to do a build that needed it. :-) Anyhow, I am not at all sure that I am competent to be the maintainer. ... Any advice on how to deal with those fonts is most welcome. Any offers from someone more competent than me to maintain this package would be gratefully received.
I'm not a font expert either. However feel free to add @python-sig as a comaintainer.
On 7.6.2018 03:05, Jerry James wrote:
I somehow wound up owning python-sphinx_rtd_theme...
And BTW whatever you do, please don't do it before the Python 3.7 rebuild. python-sphinx_rtd_theme is somewhat critical and if we break it or add more deps, the entire Python 3.7 think might be stuck. Thanks
Le mercredi 06 juin 2018 à 19:05 -0600, Jerry James a écrit :
I somehow wound up owning python-sphinx_rtd_theme, I think probably because I was the first person to attempt to do a build that needed it. :-) Anyhow, I am not at all sure that I am competent to be the maintainer. I need some advice. There is a new upstream version available, 0.4.0. I am looking at it right now, and my attempts at unbundling fonts from this package seem to be unraveling.
Three font families are bundled: fontawesome, Roboto Slab, and Lato. We have all 3 of these in Fedora, but the problem is that this package wants the web versions of these fonts, too.
And that's 100% unnecessary cargo culting from their part, you would make upstream a huge service to patch it out so it only uses the opentype version
Notice how opentype css fonts work in every single browser today except opera mini.
It already worked in IE9 for christsakes, even Microsoft got it right in *2011*, anyone running older ancient browsers will have javascript failing right and left and a mass of security issues.
Regards
Le mercredi 06 juin 2018 à 19:05 -0600, Jerry James a écrit :
We have fontawesome-fonts-web,
which was needless ignorance of Fedora guidelines BTW
Since the .ttf files of those fonts are not byte-equivalent to the ones we ship ... I'm not sure what is safe to do here.
The safe part is just to update the Fedora font packages to the latest upstream version of the fonts if we do not ship it yet. You can ignore byte-equivalency, fortunately font libs are robust enough they do not depend on a particular version of font files (and websites update fonts all year round without you noticing). The only 'risk' is downgrading to earlier font versions that may lack glyphs added in later versions.
And btw, browsers are free to ignore whatever css font web designers try to feed them (and have to since some web designers like to specify fonts that lack the coverage needed to display anything more complex than basic latin), so if anything in the theme relies on custom font modifications it's broken by design.
Regards,
Nicolas,
On Fri, Jun 29, 2018 at 1:23 PM Nicolas Mailhot nicolas.mailhot@laposte.net wrote:
The safe part is just to update the Fedora font packages to the latest upstream version of the fonts if we do not ship it yet. You can ignore byte-equivalency, fortunately font libs are robust enough they do not depend on a particular version of font files (and websites update fonts all year round without you noticing). The only 'risk' is downgrading to earlier font versions that may lack glyphs added in later versions.
And btw, browsers are free to ignore whatever css font web designers try to feed them (and have to since some web designers like to specify fonts that lack the coverage needed to display anything more complex than basic latin), so if anything in the theme relies on custom font modifications it's broken by design.
Thank you so much for the information. That is exactly what I needed to know. Once the python 3.7 builds are merged back into Rawhide, I will attempt this update.