Closed Bug 203873 Opened 21 years ago Closed 21 years ago

Mozilla Branding document doesn't specify when the point 6 is applicable

Categories

(Developer Documentation Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jmg, Assigned: endico)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030429 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030429 Mozilla Firebird/0.6

Currently, there are different interpretations about when the point 6 ("Product
Naming in resources, executables and on the desktop") of the Mozilla Branding
document is applicable, and about if -until Mozilla 1.4- "Mozilla Firebird" and
"Mozilla Thunderbird" are just project names (like SeaMonkey), or also the
public product/program names on the desktop.

That is to say, it is not clear if after Phoenix 0.5, the first public release
of the new browser from the Mozilla Firebird Project should show "Mozilla
Firebird 0.6" or "Mozilla Browser 0.6" as the public name on the desktop.

For the full details, see bug 203786 ("Renaming Mozilla Firebird application to
Mozilla Browser"), temporarily invalid until this is clear.


Reproducible: Always

Steps to Reproduce:
1. Read the new Mozilla Branding document (April 25, 2003).
2. Read the bug 203786 ("Renaming Mozilla Firebird application to Mozilla Browser").

Actual Results:  
In the Mozilla Branding document, it should be clear when its point 6 ("Product
Naming in resources, executables and on the desktop") is applicable.

Expected Results:  
It is not clear, according to different branding interpretations in the bug 203786.
doc is obsolete
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.