Add WordPress.com wording to 2FA workflow

[mrpolanco]

Fixes #21875

Added clarity to the verification code view that the code is for WordPress.com:

Localization strings edited, and added to missing language (Czech).

To test:

Regression Notes

1. Potential unintended areas of impact

2. What I did to test those areas of impact (or what existing automated tests I relied on)

3. What automated tests I added (or what prevented me from doing so) None

PR submission checklist:

• [ ] I have completed the Regression Notes.

• [ ] I have considered adding unit tests for my changes.

• [ ] I have considered adding accessibility improvements for my changes.

• [ ] I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

• [ ] WordPress.com sites and self-hosted Jetpack sites.
• [ ] Portrait and landscape orientations.
• [ ] Light and dark modes.
• [ ] Fonts: Larger, smaller and bold text.
• [ ] High contrast.
• [ ] VoiceOver.
• [ ] Languages with large words or with letters/accents not frequently used in English.
• [ ] Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• [ ] iPhone and iPad.
• [ ] Multi-tasking: Split view and Slide over. (iPad)

[kean]

Hey, thanks for addressing it, @mrpolanco.

For localization, developers usually add a key with a default localization (English) and let the translators update it for other languages. I would suggest the following changes:

• Add a new localizable string key following the guidelines. It should look something like:

private enum Strings {
    static let details = NSLocalizedString(key: "twoFactorAuthorization.details", value: "Please enter the verification code from your authentication app for your WordPress.com account.", comment: "The details label in the two-factor authorization screen. Note: it has to mention that it's for a WordPress.com account")
}

You can use the comment to clarify how it is used and what it should contain. See other files for reference.

• The string will be picked up during the next release and localized. The old unused key will be removed automatically.

[mrpolanco]

Hi @kean ! Thank you for the feedback. I undid the localizable.string changes and submitted the change only to NSLocalizedString(), as indicated. But I fear I may have updated it incorrectly - my apologies. Please let me know if I can correct on my end.

[mrpolanco]

New PR here @kean : https://github.com/wordpress-mobile/WordPress-iOS/pull/23645