Closed
Bug 627429
Opened 14 years ago
Closed 14 years ago
update text on About Firefox menu
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
INCOMPLETE
Future
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | - |
People
(Reporter: jslater, Unassigned)
Details
The copy on the About Firefox menu is certainly not wrong in any major way, but it'd be nice to be more consistent with the way we're describing Mozilla & Firefox elsewhere.
Recognizing the l10n challenges, is it at all feasible to get this updated for Fx4? If not, what about a dot release in the near future?
Comment 1•14 years ago
|
||
Not possible for Firefox 4, and I'd ask you to familiarize yourself with the discussion in bug 579547 before making revised proposals. Not saying that you must make it like that, but at least so you're caught up on how we got to where we are.
Also: is there a guide referencing the way we're describing Mozilla & Firefox elsewhere? I'm all for consistency, but I'd like to know with what we're being consistent!
blocking2.0: --- → -
Updated•14 years ago
|
Target Milestone: Firefox 4.0 → Future
| Reporter | ||
Comment 2•14 years ago
|
||
Thanks for the tip on bug 579547 - I wasn't aware of that, and there are certainly lots of great points and lively discussion in there.
I understand it's late in the cycle and after reading through 579547 I'm more fully aware of the time that's already been spent on that text, so of course this is something that can and should wait until a later release.
When the time is right, though, I would like to continue tweaking it to ensure greater consistency with our other communications. And in a more meta point, I find it a little frustrating that I (or someone else in engagement, at least) never got looped into that conversation. Going forward, I'd love to get to a point where I or someone on my team is more actively involved in the way we represent the brand or describe ourselves within the product. Very important to have clarity & consistency there.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•