Closed
Bug 413176
Opened 18 years ago
Closed 18 years ago
Make Sparkle update messages localizable
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Camino1.6
People
(Reporter: m.testi, Assigned: stuart.morgan+bugzilla)
Details
(Keywords: fixed1.8.1.13)
Attachments
(1 file)
|
2.93 KB,
patch
|
mikepinkerton
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; it; rv:1.8.1.12pre) Gecko/20080118 Camino/1.6b2 (like Firefox/2.0.0.12pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; it; rv:1.8.1.12pre) Gecko/20080118 Camino/1.6b2 (like Firefox/2.0.0.12pre)
I don't know if it's even possible, but it would be great if the messages that show up with the update notice (the ones related to Camino, not Sparkle's own interface) were localizable and served using the same reasoning behind web content negotiation.
Reproducible: Always
| Assignee | ||
Comment 1•18 years ago
|
||
Well, we could probably add another parameter to the update request with the language Camino is running in, and have the script I need to write for serving appcasts pull in the appropriate content.
Flagging so we at least think about this again for 1.6.
Flags: camino1.6?
| Assignee | ||
Comment 3•18 years ago
|
||
I'll have to think some more about the best way to stitch things together on the server, but we should ship the client functionality to make it possible. Plus, this will give us interesting data about the breakdown of non-English use.
Assignee: nobody → stuart.morgan
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #305945 -
Flags: superreview?(mikepinkerton)
| Assignee | ||
Updated•18 years ago
|
Flags: camino1.6? → camino1.6+
Target Milestone: --- → Camino1.6
Comment 4•18 years ago
|
||
Comment on attachment 305945 [details] [diff] [review]
send language
sr=pink
Attachment #305945 -
Flags: superreview?(mikepinkerton) → superreview+
| Assignee | ||
Comment 5•18 years ago
|
||
Landed on trunk and MOZILLA_1_8_BRANCH.
I'll make a note in the server-side bug to do the harder part of this.
You need to log in
before you can comment on or make changes to this bug.
Description
•