Add self-hosting of fonts-com fonts #34
Comments
Looks like we use it by putting something like this in <link type="text/css" rel="stylesheet" href="https://fast.fonts.net/cssapi/34d68d8f-2eac-4fb7-b0da-1759668cf274.css" />That's probably a personalized url that was issued when we signed up and paid for the service. They use an @import url(/t/1.css?apiType=css&projectid=34d68d8f-2eac-4fb7-b0da-1759668cf274);
Since some of their packages permit self-hosting, I think it would be OK for subfont not to try to enforce anything on their behalf? |
|
Hmm. https://fast.fonts.net/cssapi/34d68d8f-2eac-4fb7-b0da-1759668cf274.css doesn't even annotate The stylesheet itself links to all the fonts, so from that perspective its much easier than with google fonts, where you have to fake a user agent to get it to serve the css with links to the right font format |
It looks like their |
I think we do support that (I'm fairly sure they just default to their initial value, |
|
That seems like a problem though. That CSS you linked to contains a bunch of different variations of Avenir. Light, light + italic, regular, demibold etc. But they are only identified by their unique name. That means that any use of italics or boldness would not enable the browser to switch to a different font-family definition. It would have to faux all of it. But maybe that's mostly a problem with the font service. If one of those unique font names apply based on our calculations, we should still be adhering to whatever the browser interprets it as |
|
Yeah, agreed. It could be that they thought this would be "simpler" for the user, to just use distinct |
We do support that. Added a test here: assetgraph/assetgraph@47c18dc |
|
Turns out we're actually in the process of switching away from fonts.com, so I'm less likely to look into this atm. |
|
I'll get o it eventually. I have a bunch of changes I want to make in the subset transform anyway |
|
@Munter, okay, cool! Which changes are you planning to make? Just so we don't step on each other's toes :) |
Forked from discussion in #31
What does a typical fonts.com css and fonts setup look like when using their service?
How do we determine if self-hosting is permitted?
How do we get at all the font assets. Do they serve browser specific css like google fonts does?
@papandreou
The text was updated successfully, but these errors were encountered: