Closed Bug 806581 Opened 8 years ago Closed 8 years ago

Translate Facebook Chat

Categories

(Thunderbird :: Instant Messaging, defect)

18 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 19.0

People

(Reporter: az, Assigned: az)

Details

Attachments

(1 file, 1 obsolete file)

Create a new chat account. 

Facebook chat is not a proper name, it has a Swedish translation. The name is hardcoded in file http://mxr.mozilla.org/comm-central/source/chat/protocols/facebook/facebook.js#49
Could you come up with a patch ?
Attached patch Facebook Chat label (obsolete) — Splinter Review
Comment on attachment 676675 [details] [diff] [review]
Facebook Chat label

>diff --git a/chat/locales/en-US/facebook.properties b/chat/locales/en-US/facebook.properties
> FacebookProtocol.prototype = {
>   __proto__: GenericProtocolPrototype,
>   get normalizedName() "facebook",
>-  get name() "Facebook Chat",
>+  get name() "network.label",
You'll need to call the translation function like on http://mxr.mozilla.org/comm-central/source/chat/protocols/facebook/facebook.js#32, so this would be _("network.label"). I don't find this name to be very descriptive, however. Maybe something like "facebook.name"?

Would we want to do this for all of our JS protocols? (GTalk, Facebook, XMPP, IRC, Twitter) Florian?

Also, I wonder why Facebook have its own properties file, GTalk just has its strings inside of xmpp.properties...
Attachment #676675 - Flags: feedback+
Attachment #676675 - Attachment is obsolete: true
Comment on attachment 676677 [details] [diff] [review]
Facebook chat name

I'll test this out later tonight.
Attachment #676677 - Flags: review?(clokep)
Comment on attachment 676677 [details] [diff] [review]
Facebook chat name

Looks good to me! Thanks. :)
Attachment #676677 - Flags: review?(clokep) → review+
Assignee: nobody → az
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: checkin-needed
https://hg.mozilla.org/comm-central/rev/b11e3f92b12b

Thanks for the patch! One request - to make life easier for those checking in on your behalf, please make sure that your future patches follow the guidelines below so that all the necessary checkin metadata is present. Thanks!
https://developer.mozilla.org/en-US/docs/Creating_a_patch_that_can_be_checked_in
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: in-testsuite-
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 19.0
You need to log in before you can comment on or make changes to this bug.