Closed
Bug 106413
Opened 23 years ago
Closed 22 years ago
inconsistency in the use of the words "plug-in" and "plugin"
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
mozilla1.1alpha
People
(Reporter: bugzilla, Assigned: serhunt)
References
Details
(Whiteboard: [PL2:NA])
Attachments
(3 files, 1 obsolete file)
975 bytes,
patch
|
Details | Diff | Splinter Review | |
986 bytes,
patch
|
Details | Diff | Splinter Review | |
987 bytes,
patch
|
Details | Diff | Splinter Review |
The help menu in Mozilla talks about "Plug-ins" and so do bugzilla, but the status text talks about "Starting Plugin for type". Which is the correct form: "plugin" or "plug-in" I dont care, just as long as we consistent
Comment 1•23 years ago
|
||
plug-in is linguistically correct
Reporter | ||
Comment 3•23 years ago
|
||
could you also change http://www.netscape.com into http://netscape.com looks much better
Why? Well, I think we should add somebody from the Netcenter to advise on this. Arun, do you know who might be the right person? Or maybe you just know the answer.
Comment 5•23 years ago
|
||
Sending someone to http://www.netscape.com/ and expecting them to find the plug-in stuff in amongst all the portal content is cruel. Point them towards http://home.netscape.com/plugins/ so they at least have a fighting chance.
Comment 6•23 years ago
|
||
NetCenter is interesting to this discussion only from the Plugin Finder Service point of view. I am cc'ing greggl because he's the main person behind this. Thanks for bringing this issue to our attention Henrik!
Reporter | ||
Comment 7•23 years ago
|
||
so it should be http://netscape.com/plugins/ the "www" is just unnessesary information. It takes long to type and say. And there's no need for it.
Attachment #54923 -
Attachment is obsolete: true
Comment 9•23 years ago
|
||
Netscape's URLs have been in the form http://home.netscape.com/ for as long as it's been called Netscape. So I think it should be http://home.netscape.com/plugins/ but I always was a traditionalist.
Comment 10•23 years ago
|
||
yes, using "home" is the most correct. Using http://home.netscape.com/plugins/index.html is the most official. I would prefer to use "home". Also, on the about:plugins page, there is a link to "Netscape Netcenter". This is BAD. Netcenter has been retired for a long time. This needs to be changed to "Netscape.com"
Reporter | ||
Comment 11•23 years ago
|
||
could we at least get rid of the "index.html" so the URL just is: http://home.netscape.com/plugins/
Comment 12•23 years ago
|
||
sure, having "index.html" is not necessary.
Comment 13•23 years ago
|
||
> Also, on the about:plugins page, there is a link to "Netscape Netcenter". This > is BAD. Netcenter has been retired for a long time. This needs to be changed > to "Netscape.com" That would be bug 92457. Also related is bug 80676.
Assignee | ||
Comment 14•23 years ago
|
||
Comment 15•23 years ago
|
||
No trailing slash?
Assignee | ||
Comment 16•23 years ago
|
||
Reporter | ||
Comment 17•23 years ago
|
||
are all the patched now obsolete?
Comment 18•23 years ago
|
||
personally i'd prefer not to include the trailing slash. if at some later point in time netscape.com wanted to make the file name plugins instead of a directory named plugins containing an index file, they could do so if we don't include the /, if we do, we make it harder on them. [ref: http://www.mozilla.org/start wrt the zope mozilla.org rewrite]
Comment 19•22 years ago
|
||
The plug-ins triage team (av, beppe, peterl, serge and shrir) have reviewed this issue and have made the following determination: The status message text is no longer used, so that issue is resolved The default plug-in dialog is being removed, see bug 56229 Both issues discussed in this bug are either 1. fixed, or 2. addressed in another bug. Marking as a dup of the other bug *** This bug has been marked as a duplicate of 56229 ***
No longer blocks: 121075
Status: NEW → RESOLVED
Closed: 22 years ago
Priority: -- → P3
Resolution: --- → DUPLICATE
Whiteboard: [PL2:NA]
Target Milestone: --- → mozilla1.1alpha
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•