Obsolete terminology in strings (alias, real email, domain)
flodolo opened this issue · 5 comments
I was running some checks and noticed strings that still used "obsolete" terminology
alias
whatsnew-feature-sign-back-in-heading = Sign back in with your aliases
whatsnew-feature-sign-back-in-snippet = To create a new alias when you’re asked for your email, open…
whatsnew-feature-sign-back-in-description = To sign in with a previously-used alias, open the context menu where the site asks for your email. You’ll be able to select the alias and auto-fill the email field.
whatsnew-feature-forward-some-description = { -brand-name-relay-premium } allows you to block only promotional emails sent to an alias. You’ll receive emails like receipts but not marketing emails.
landing-review-user-four-review-list-2 = Protects ones identity from trackers through generation of aliases where one does not want to share the real email address for various reasons.
banner-download-install-chrome-extension-copy = The { -brand-name-firefox-relay } extension for { -brand-name-chrome } makes creating and using aliases even easier.
multi-part-onboarding-premium-chrome-extension-get-description = The { -brand-name-firefox-relay } extension for { -brand-name-chrome } makes creating and using email aliases even easier.
real email
landing-use-cases-shopping-hero-content2 = Use an email mask whenever you shop online. Get the confirmation sent to your real email and then easily turn the mask off anytime later.
landing-use-cases-on-the-go-receipt-body = Share a custom email mask for in-store shopping receipts without sharing your real email
landing-review-user-four-review-list-2 = Protects ones identity from trackers through generation of aliases where one does not want to share the real email address for various reasons.
How much of this is expected?
I realized the last one for domain is actually correct, so scratch that ;-)
Thanks for being so diligent @flodolo!
The following are expected, because they are news items, i.e. they're in the archive and are from when the old terminology was still active:
whatsnew-feature-sign-back-in-heading = Sign back in with your aliases
whatsnew-feature-sign-back-in-snippet = To create a new alias when you’re asked for your email, open…
whatsnew-feature-sign-back-in-description = To sign in with a previously-used alias, open the context menu where the site asks for your email. You’ll be able to select the alias and auto-fill the email field.
whatsnew-feature-forward-some-description = { -brand-name-relay-premium } allows you to block only promotional emails sent to an alias. You’ll receive emails like receipts but not marketing emails.
The following is expected, because it is a direct quote from a user review:
landing-review-user-four-review-list-2 = Protects ones identity from trackers through generation of aliases where one does not want to share the real email address for various reasons.
The following are indeed deprecated (and marked as such with a comment - I'll need to go through these one of these days to remove them, since their replacement is live):
banner-download-install-chrome-extension-copy = The { -brand-name-firefox-relay } extension for { -brand-name-chrome } makes creating and using aliases even easier.
multi-part-onboarding-premium-chrome-extension-get-description = The { -brand-name-firefox-relay } extension for { -brand-name-chrome } makes creating and using email aliases even easier.
That leaves the following actual errors:
landing-use-cases-shopping-hero-content2 = Use an email mask whenever you shop online. Get the confirmation sent to your real email and then easily turn the mask off anytime later.
landing-use-cases-on-the-go-receipt-body = Share a custom email mask for in-store shopping receipts without sharing your real email
I've created a ticket in our backlog to fix those and remove the deprecated ones. Thanks again!
Given your first comment about landing-review-user-four-review-list-2 being a direct quote, I guess real email should stay as well?
Oh yep, you're right, updated my previous comment to remove it from the list of actual errors! (The ticket in the backlog refers to this issue.)