-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fonts #72
Comments
A candidate upgrade aproach could be based on something like the code below. However, with San Francisco. public enum helveticaNeue: String {
case neue = "HelveticaNeue"
case bold = "HelveticaNeue-Bold"
case boldItalic = "HelveticaNeue-BoldItalic"
case condensedBlack = "HelveticaNeue-CondensedBlack"
case condensedBold = "HelveticaNeue-CondensedBold"
case italic = "HelveticaNeue-Italic"
case light = "HelveticaNeue-Light"
case lightItalic = "HelveticaNeue-LightItalic"
case medium = "HelveticaNeue-Medium"
case mediumItalic = "HelveticaNeue-MediumItalic"
case ultraLight = "HelveticaNeue-UltraLight"
case ultraLightItalic = "HelveticaNeue-UltraLightItalic"
case thin = "HelveticaNeue-Thin"
case thinItalic = "HelveticaNeue-ThinItalic"
public func font(size: CGFloat) -> UIFont {
return UIFont(name: self.rawValue, size: size)!
}
} |
Hi @marc-medley I'd like to take this ticket if possible 😇 🙏 |
I've been preparing a branch but unfortunately I keep getting blocked by the I don't know if that's intentional or hope it's not a noob open-source project security question, but I see elsewhere it's supposed to be in the project.
i was worried it had to do with my |
I an wondering if, as a workaround, one could create such a file (possibly even empty) locally in the project. The real file would contain secrets not meant for a public repository. |
#73 (comment) mentions a workaround: wrapping the inclusion of the plist file in ifdef and removing the file from the xcode project, locally. |
Perhaps yes… I had created this ticket as a reminder for myself for a future phase of development. The uniform use of That said, once v3.5.1 is in the Apple App Store review process I will create a |
Hmmm I cannot seem to reproduce the issue today 🤔 Is this still an issue you reproduce on your ends @krugerk and @marc-medley? |
Font issues for Cyrillic translations surfaced during the release candidate testing of v3.4.13 (which was ultimately released as v3.4.15).
The root cause was found to be the use of the much older
Helvetica
instead ofHelvetica Neue
in some cases.The observed issues were resolved with an update to Fonts.swift.
During the transtion to SwiftUI the following needs to occur:
static var fontfamilyBold17: UIFont
approach.The text was updated successfully, but these errors were encountered: