Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Several strings are not localized in onboarding and autofill screens #1009

Closed
2 of 3 tasks
TheoChevalier opened this issue May 23, 2019 · 5 comments
Closed
2 of 3 tasks
Labels
blocks-l10n Issues that block exposing new string exports for localization defect Issue describes a defect that negatively impacts use. feature-localization

Comments

@TheoChevalier
Copy link

TheoChevalier commented May 23, 2019

Multiple strings are either hardcoded, haven’t been exposed to the xliff file, or are not used. Adding screenshots below

IMG_5183

IMG_5189

IMG_5190

@TheoChevalier TheoChevalier changed the title “Deselect iCloud Keychain” is not localized Several strings are not localized May 23, 2019
@TheoChevalier
Copy link
Author

Morphing this bug to include additional missing strings:

IMG_5189

IMG_5190

@devinreams devinreams added feature-localization defect Issue describes a defect that negatively impacts use. labels May 23, 2019
@devinreams
Copy link
Contributor

Thanks for the report @TheoChevalier. We'll look at this shortly...

@devinreams devinreams changed the title Several strings are not localized Several strings are not localized in onboarding and autofill screens May 29, 2019
@devinreams devinreams self-assigned this May 29, 2019
@devinreams devinreams added the blocks-l10n Issues that block exposing new string exports for localization label May 29, 2019
@devinreams
Copy link
Contributor

“Sync between devices with secure 256-bits encryption” → Exposed, but not used

@sashei I can't tell why this one may not be connecting up:

“Sync between devices with secure 256-bits encryption” → Exposed, but not used

Anything obvious jump out at you? I'll look more tomorrow

@sashei
Copy link
Contributor

sashei commented May 30, 2019

@devinreams we are doing manual interpolation to put the link in for 256-bit encryption. Looking at some languages, we expect the storyboard text to match exactly a different piece of text that's localized as Constant.string.onboardingSecurityPostfix. The string formatting is definitely failing because the strings (the one in the storyboard + the one in the generic Localizable.strings) don't line up. I think we need to tweak how we are getting that string interpolated + localized to work (although I'm not sure why it would fall back to English when the string formatting fails??).

All that to say, we need a bigger string change, which I think would be best addressed after l10n is shipped. For a quick fix, we could remove the string formatting (lines 60-77) in the OnboardingConfirmationVIew and ship the initial localized version without the explainer encryption link.

@sashei
Copy link
Contributor

sashei commented Jun 18, 2019

I've filed a new ticket for the encryption text issue: #1061

@sashei sashei closed this as completed Jun 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocks-l10n Issues that block exposing new string exports for localization defect Issue describes a defect that negatively impacts use. feature-localization
Projects
None yet
Development

No branches or pull requests

3 participants