Closed
Bug 206840
Opened 23 years ago
Closed 22 years ago
Help documentation needs to be updated for the Mozilla Branding Strategy
Categories
(Documentation Graveyard :: Help Viewer, defect)
Documentation Graveyard
Help Viewer
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: danielwang, Assigned: rjkeller)
References
Details
by private e-mail
me > I'm a little bit confused about "mail/news" vs "Messenger".
> Should we edit mozilla.org docs and online Help to reflect
> this distinction?
Christ Blizzard > Hmm. Maybe, yeah.
so... browser -> Navigator, mail & newsgroup -> Messenger
Comment 1•22 years ago
|
||
moving stuff over to an outside-the-firewall email for the time being, looking
for people to pick these Help and doc bugs up for me.
Assignee: oeschger → oeschger
| Assignee | ||
Comment 2•22 years ago
|
||
--> me
What did you have in mind, Daniel? I don't think I agree with changing Mail/News
to Messenger.
Assignee: oeschger → rlk
QA Contact: rudman → stolenclover
| Reporter | ||
Comment 3•22 years ago
|
||
check out www.mozilla.org/releases/mozilla1.4/ . Asa uses "Messenger (Mail &
Newsgroups)"
| Assignee | ||
Comment 4•22 years ago
|
||
OK, after reading the branding docs we should have this. Let's wait until the
mailnews portion of bug 95770 is done.
Status: NEW → ASSIGNED
Depends on: 95770
| Assignee | ||
Updated•22 years ago
|
Summary: Mozilla Online Help not yet updated for Mozilla Branding Strategy → Help documentation needs to be updated for the Mozilla Branding Strategy
Comment 5•22 years ago
|
||
Vendors may (and actually do) use slightly or completely different product
names, so you should not hardcode the product names, but use placeholders like
&brandShortName; or &browserBrandName; or &mailnewsBrandName; or similar. With
that, you can aso easily swtich all docs when mozilla.org changes its names.
Changing summary from
"Help documentation needs to be updated for the Mozilla Branding Strategy"
to
"Help documentation should not hardcode product names"
Summary: Help documentation needs to be updated for the Mozilla Branding Strategy → Help documentation should not hardcode product names
| Assignee | ||
Comment 6•22 years ago
|
||
I don't think that this is what the bug is about, but using a DTD file for the
name will probably be used. That bug will probably be fixed while in the process
of fixing this bug.
Ben: do you know of any DTD file that might contain a &mailnewsBrandName;? I've
only seen &brandShortName;.
Summary: Help documentation should not hardcode product names → Help documentation needs to be updated for the Mozilla Branding Strategy
Comment 7•22 years ago
|
||
> do you know of any DTD file that might contain a &mailnewsBrandName;?
Unfortunately not, it should be created. Should I file a bug against Mailnews or
do you want to add it to the help component?
| Assignee | ||
Comment 8•22 years ago
|
||
I'd like one in MailNews, but I'm not sure how the MailNews team would feel
about this. There must be a reason as to why there isn't one there. If there is
a good reason, then I'll add a new DTD file.
| Reporter | ||
Comment 9•22 years ago
|
||
>> do you know of any DTD file that might contain a &mailnewsBrandName;?
>
> Unfortunately not, it should be created. Should I file a bug against Mailnews or
> do you want to add it to the help component?
Ben, you already did bug 84851
-> wontfix until a decision on bug 206838 is reached
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Comment 10•22 years ago
|
||
Thanks for the hint to bug 84851, I totally forgot about it.
Filed bug 232794.
You need to log in
before you can comment on or make changes to this bug.
Description
•