Richard Owlett wrote:
My question was poorly phrased, but you got me looking in a useful, if
unexpected, direction. I had expected to be pointed to a file on my
machine.

On your local machine, the mentioned files are contained in a file called omni.ja inside your SM application directory. If you copy it somewhere else and rename it to omni.zip, Windows should be able to open it (other tools like current stable 7zip cannot, though). Inside it, the path is chrome\en-US\locale\en-US\communicator\help.

How do words be come targets for the search function?

AFAICT anything in the mentioned RDF files that's inside an nc:name attribute gets added as a possible target. I didn't actually check the code, though.

What can I download to create a local testbed?

For actual development you'd need a (minimal) copy of the source code. For starters: 1. Download and install <http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe>
2. Launch MozillaBuild command line
3. Enter "hg clone http://hg.mozilla.org/comm-central/"; (without quotes) and hit Enter
4. Enter "explorer comm-central" (again without quotes) and hit Enter
5. Navigate to suite\locales\en-US\chrome\common\help.

Or does practicality indicate I should confine myself to the individual
xhtml files above?

Back in the days before omni.ja I would have advised you to just change the files of the local installation for testing purposes. But since omni.ja is not a proper ZIP file, that's not a method I would still recommend. However, if you're a little adventureous, you may give it a try - only on a complete, independent copy of your SM application directory of course. I recommend to use a test profile with that and start SM with parameters -P -purgecaches (show Profile Manager; skip application file caching).

HTH

Jens

--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to