You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2018. It is now read-only.
I am not certain if it is possible to have an entire font family in the same file, but in case you have each font weight in a separate file (like RobotoSlab-Light.ttf, RobotoSlab-Bold.ttf, etc.) then only the first one will be registered - since the test for registering only queries to see if the font family is present.
For iOS/Swift 3 this can be fixed by changing the Font convenience initializer in the fonts/swift3.stencil to have the following check:
if !UIFont.fontNames(forFamilyName: font.family).contains(font.name) {
font.register()
}
Do you agree that this is a sensible way to perform the check? If so, I can create a pull request with changes for all swift versions and both iOS/macOS.
The text was updated successfully, but these errors were encountered:
I am not certain if it is possible to have an entire font family in the same file, but in case you have each font weight in a separate file (like RobotoSlab-Light.ttf, RobotoSlab-Bold.ttf, etc.) then only the first one will be registered - since the test for registering only queries to see if the font family is present.
For iOS/Swift 3 this can be fixed by changing the Font convenience initializer in the fonts/swift3.stencil to have the following check:
Do you agree that this is a sensible way to perform the check? If so, I can create a pull request with changes for all swift versions and both iOS/macOS.
The text was updated successfully, but these errors were encountered: