Closed Bug 287689 Opened 19 years ago Closed 6 years ago

Venkman should not hardcode "Mozilla" as the suite name

Categories

(Other Applications Graveyard :: Venkman JS Debugger, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: kairo, Assigned: rginda)

References

Details

(Whiteboard: [good first bug])

Instead of using the hardcoded word "Mozilla" as the brand name of the suite
Venkman can run in, it should use the &brandShortName; entity from brand.dtd
(or the brandShortName string from brand.poperties).
That way it's easier for the new suite project to rebrand the suite (see bug
285696) as well as for some distributor to change to his brand.
Where it can't be avoided, a hardcoded change or inclusion of the new suite name
(tba) might be a good idea (see "reasonable hardcoding" in list below).

(I'm marking this blocking suite-rebranding though it's no hard blocker on that
bug, esp. as calendar isn't part of the default build)

Here's a list of affected files/locale strings:
venkman.properties: cmd.about-mozilla.help
venkman.properties: cmd.about-mozilla.label
venkman.properties: cmd.quit.help
venkman.properties: cmd.release-notes.help
venkman.properties: cmd.mozilla-help.help
QA Contact: caillon → venkman
Whiteboard: [good first bug]
See also bug 287687. Since Venkman mostly uses the same backend API as ChatZilla, it should be easy to migrate that fix to Venkman.
This string is also affected:
venkman.properties: cmd.cmd-mozilla-prefs.label
Component is obsolete so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.