Closed
Bug 87487
Opened 23 years ago
Closed 23 years ago
Dude, Where's My Help?
Categories
(SeaMonkey :: Help Documentation, defect)
SeaMonkey
Help Documentation
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: doctor__j, Assigned: oeschger)
References
Details
Attachments
(3 files)
16.50 KB,
image/png
|
Details | |
10.81 KB,
image/png
|
Details | |
1.07 KB,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.1+) Gecko/20010622
BuildID: 2001062211
Coming to your local theatres NOW.
Reproducible: Always
Steps to Reproduce:
1. See the Premiere photo shoot!!
Assignee | ||
Comment 5•23 years ago
|
||
Dang it if this bug isn't true! I checked in some updates on Friday that ought
to have remedied this, but I verify that in the 2001062504 build, the help
locale stuff is not being seen. All of the resources are placed correctly (i.e.,
the help chrome is in the help.jar and the localizable stuff--which includes the
menu item, the table of contents, and the content itself--is in en-US.jar), but
the entry is not being written correctly to the installed-chrome.txt file.
cc'ing ssu. Sean, what's not happening here? When I update the entry in the
installed-chrome.txt file to point to the en-US.jar, everything is cool. But
until I do this, that file is still looking in a subdirectory of help.jar.
Status: NEW → ASSIGNED
Comment 6•23 years ago
|
||
this is a problem on linux too (build 2001-06-25-08)
OS: Windows 98 → All
Hardware: PC → All
Assignee | ||
Comment 7•23 years ago
|
||
Boris and DrJ: How did you come by these builds? Were they the nightlies you got
from the mozilla splash page?
I need to make sure that this is an issue with a recent installer version rather
than a zip file (which might have something like an old installed-chrome.txt
left over from before my updates late 6/21). I believe we verified that the help
locale stuff was building and installing correctly after the packaging updates.
Thanks for getting back to me about this.
Comment 8•23 years ago
|
||
I'm using the build from the corresponding directory on the Mozilla ftp site.
I'm also using the tarball (no installer), so a stale installed-chrome.txt could
well be the issue.
I'm getting all Moz builds from the ftp site too.
Too lazy/dumb to build one myself...
Comment 10•23 years ago
|
||
Assignee | ||
Comment 11•23 years ago
|
||
Ah, good spot Stephen. I spaced out on the makefiles (and updated only the
jar.mn up there). I will get this in as soon as I can. Thanks!
Comment 12•23 years ago
|
||
*** Bug 88009 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 13•23 years ago
|
||
Just checked in walk84's fix for this on the branch (but not yet on the trunk,
where smoketests are still being done). Should see this problem resolved (but
I'm going to wait a little bit before marking this fixed).
Also noting Asa and Leaf's suggestion that, in some cases, this has to do with
the fact that the zips made available recently from mozilla.org didn't have the
re-registered JARs.
Comment 14•23 years ago
|
||
sr=waterson
Assignee | ||
Comment 15•23 years ago
|
||
Coming in behind waterson to provide some context to his review here: I checked
this fairly urgent into the branch yesterday (a=asa and, IIRC, rs=blizzard), but
am going back and getting it reviewed in earnest. This same fix has to be
applied on the commercial side (for which I have a patch posted in 5687), where
I believe waterson has sr'd too.
As soon as the tree(s) open, I will do moz trunk, comm branch, comm trunk with
this fix.
Assignee | ||
Comment 16•23 years ago
|
||
Checked in a fix for this today. Mozilla branch and trunk now package
localizable stuff in en-US.jar (as opposed to help.jar) successfully. Marking
FIXED.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 17•23 years ago
|
||
Dude, there it is...
Confirming on build 2001-06-30-08, Win2kn sp2 from installer.
Comment 18•23 years ago
|
||
Um, clarification...
Confirming FIXED. Sorry for the confusion!
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•