Closed
Bug 432118
Opened 16 years ago
Closed 15 years ago
"My Yahoo" should be "My Yahoo!" in the list of feed handlers
Categories
(Firefox Graveyard :: RSS Discovery and Preview, defect)
Firefox Graveyard
RSS Discovery and Preview
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 3.7a1
People
(Reporter: kliu, Assigned: mozilla.bugs)
References
Details
(Keywords: polish, productization)
Attachments
(1 file)
441 bytes,
patch
|
sayrer
:
review+
|
Details | Diff | Splinter Review |
This bug is similar to bug 264822. According to bug 264822 comment 14, Yahoo!'s name should have an exclamation point. I assume that this is true for "My Yahoo!" as well? Fortunately, unlike bug 264822, the feed settings are not saved based on the name, so it's possible to change the name without disrupting user settings. Since it's so late, I assume that this is something for the next release? (BTW, AFAIK, this and bug 264822 are the only two places missing the "!"--the mail handler got it right.)
Assignee | ||
Comment 1•15 years ago
|
||
This is also the case in 104 locales http://mxr.mozilla.org/l10n-central/search?string=my+yahoo[^!]®exp=on&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=l10n-central I leave it to Kev and Axel to determine if we should also change those.
Attachment #401867 -
Flags: review?(sayrer)
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → mozilla.bugs
Status: NEW → ASSIGNED
Updated•15 years ago
|
Keywords: productization
Comment 2•15 years ago
|
||
kev, does this change need to be made?
Comment 3•15 years ago
|
||
It should be made, if it can be without mucking things up. "Yahoo!" is the proper name/trademark, and should be used when referencing Yahoo! or a Yahoo! property where possible.
Comment 4•15 years ago
|
||
should we change all the locales with one patch? I'm not really sure what the etiquette is here.
Comment 5•15 years ago
|
||
we should probably do this in 3.6, and ask l10n to coordinate with the regional localization teams to make the changes to theit specific locales. this is how we've done other changes that affect the product as a whole.
Comment 6•15 years ago
|
||
There is no "one patch" possible, as we're having separate repos per locale. If we decide that we want to do it, it's probably on stas' lap to rewrite and land as there's out-of-band tracking to make sure that the productization files don't get broken, which he maintains.
Assignee | ||
Comment 7•15 years ago
|
||
Axel, Kev: If there is anything that I could do to help, just let me know.
Assignee | ||
Comment 8•15 years ago
|
||
Should this be an l10n bug now? And should we reassign to stas, since I have the en-US patch and the other patches would be done by him?
Updated•15 years ago
|
Attachment #401867 -
Flags: review?(sayrer) → review+
Assignee | ||
Updated•15 years ago
|
Keywords: checkin-needed
Comment 9•15 years ago
|
||
The patch didn't apply, probably because it didn't have any context at all. http://hg.mozilla.org/mozilla-central/rev/72074ac5a64e
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a1
Assignee | ||
Comment 10•15 years ago
|
||
Verified Fixed on Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a1pre) Gecko/20091017 Minefield/3.7a1pre (.NET CLR 3.5.30729) ID:20091017051221 Stas, Kev, Pike: Do we want an l10n bug for the other localizations?
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•