Skip to content
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

Open
marc-medley opened this issue Dec 15, 2023 · 7 comments
Open

Fonts #72

marc-medley opened this issue Dec 15, 2023 · 7 comments
Assignees

Comments

@marc-medley
Copy link
Member

Font issues for Cyrillic translations surfaced during the release candidate testing of v3.4.13 (which was ultimately released as v3.4.15).

Bulgarian_Video

The root cause was found to be the use of the much older Helvetica instead of Helvetica Neue in some cases.

The observed issues were resolved with an update to Fonts.swift.

private struct Strings {
    static let courier = "Courier"
    static let helveticaBold = "Helvetica-Bold"
    static let helveticaNeueMedium = "HelveticaNeue-Medium"
    static let helvetica = "Helvetica"
}

During the transtion to SwiftUI the following needs to occur:

  1. Update all "system fonts" use to the current system font type which is San Francisco
  2. Review the use of Courier
  3. Consolidate all the font references to into the application fonts manager. There are still many font references scattered across the storyboards.
  4. Upgrade the static var fontfamilyBold17: UIFont approach.
@marc-medley
Copy link
Member Author

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)!
    }
}

@jamie-brannan
Copy link

Hi @marc-medley I'd like to take this ticket if possible 😇 🙏

@jamie-brannan
Copy link

I've been preparing a branch but unfortunately I keep getting blocked by the GoogleService-Info.plist that's missing from the project with my fresh clone? 🤔

Screenshot 2024-01-05 at 11 55 28 AM

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 pod install but I just can't find it anywhere to get up and running.

@krugerk
Copy link

krugerk commented Jan 5, 2024

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.

@krugerk
Copy link

krugerk commented Jan 5, 2024

I've been preparing a branch but unfortunately I keep getting blocked by the GoogleService-Info.plist that's missing from the project with my fresh clone? 🤔

Screenshot 2024-01-05 at 11 55 28 AM

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 pod install but I just can't find it anywhere to get up and running.

#73 (comment) mentions a workaround: wrapping the inclusion of the plist file in ifdef and removing the file from the xcode project, locally.

@marc-medley
Copy link
Member Author

I'd like to take this ticket if possible 😇 🙏

Perhaps yes…

I had created this ticket as a reminder for myself for a future phase of development.

The uniform use of HelveticaNeue resolved the Cyrillic inconsitancy issues for the current releases, so this ticket is currently a non-urgent enhancement.

That said, once v3.5.1 is in the Apple App Store review process I will create a develop-fonts branch based on v3.5.1 and then return to review what would be the hand-off scope with you.

@jamie-brannan
Copy link

Hmmm I cannot seem to reproduce the issue today 🤔

Simulator Screenshot - iPad (10th generation) - 2024-01-08 at 18 20 23

Is this still an issue you reproduce on your ends @krugerk and @marc-medley?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants