Closed Bug 1137662 Opened 5 years ago Closed 5 years ago

There's a spurious "to" in the mail/ version of smtpAuthChangeEncryptToPlainSsl

Categories

(MailNews Core :: Composition, defect, trivial)

defect
Not set
trivial

Tracking

(thunderbird38+ fixed)

RESOLVED FIXED
Thunderbird 39.0
Tracking Status
thunderbird38 + fixed

People

(Reporter: nONoNonO, Assigned: mkmelin)

References

()

Details

(Keywords: regression)

Attachments

(1 file)

One of the strings modified in bug 952493 is wrong I think...
It says "try changing to the 'Authentication method'" instead of "try changing the 'Authentication method'" in smtpAuthChangeEncryptToPlainSsl.
Keywords: regression
Let's track this in case we decide to do late strings.
Summary: There's a wrong string in the new error messages for composing a mail → There's a spurious "to" in the mail/ version of smtpAuthChangeEncryptToPlainSsl
I don't think we need to bump the key for this - it's not a "real" semantic change. Let's just land it soon so it doesn't confuse localizers unnecessarily.
Assignee: nobody → mkmelin+mozilla
Status: NEW → ASSIGNED
Attachment #8570627 - Flags: review?(syshagarwal)
Comment on attachment 8570627 [details] [diff] [review]
bug1137662_smtpAuthChangeEncryptToPlainSsl_typo.patch

Review of attachment 8570627 [details] [diff] [review]:
-----------------------------------------------------------------

Sorry for this mistake.

::: mail/locales/en-US/chrome/messenger/messengercompose/composeMsgs.properties
@@ +94,1 @@
>  

Looks good now.
Attachment #8570627 - Flags: review?(syshagarwal) → review+
https://hg.mozilla.org/comm-central/rev/97ae639ce53d
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 39.0
Attachment #8570627 - Flags: approval-comm-aurora+
Is it worth mentioning in m.d.l10n, just in case?
Flags: needinfo?(mkmelin+mozilla)
Tried it, but posts don't seem to go through. Is mozilla.dev.l10n moderated now?
Post went through with tb31.
Flags: needinfo?(mkmelin+mozilla)
You need to log in before you can comment on or make changes to this bug.