andré wrote:
Due to an important (to me) bug being rejected as WONTFIX, I have been
making a cludge patch to Seamonkey for several years, to remove a
useless display that takes up a large part of screen space.
Once omni.jar and then omni.ja arrived, I have been extracting the one
file in question, making minor modifications, and re-importing it.
This worked up to Seamonkey 2.17.1, after which the omni.ja file format
changed.
It is no longer recognized on my (Linux) system as an archive, and
although unzip can still extract the file (with the usual error message,
since it is no longer a zip format), zip can no longer import the
modified file in place, and thus a large part of Seamonkey no longer
functions.
So I'm looking for a workaround. Possible solutions I see are :
1) Somehow loading the changed file separately from omni.ja, to replace
the original file.
(Maybe some sort of *.xpi, but I'm not sure that I know how to ensure
that it would work.)
2) Unpacking the omni.ja and repacking the contained files in fully
zip-compatible *.jar files, configured so they would load properly.
I'm not sure how to do this either.
Note that with my pre-omni repacking of *.jar files, I loaded at least
as fast as with omni.jar. The previous distributed *.jar files were
uncompressed and painfully slow to load.
(In passing, it would have been wiser to just compress the distributed
*.jar files, but I guess omni.jar was a more interesting project.)
3) Find the tools needed to repack the existing omni.ja file so it will
load. I've tried simply packing it as a compressed zip file (with the
.jar or .ja suffix, but that doesn't work.
I've listed this in order of preference :
(1) because it would probably be the fastest,
(2) being my preferred solution (easier to avoid loading unwanted
modules by renaming or deleting them, and at least as fast as omni.ja), and
(3) because with the right tools (evidently used by mozilla), it is
sure to work.
Also, I would like to install any changes globally, if possible. Older
methods don't seem to work.
Including an xpi-based language pack.
Thanks in advance for any suggestions :)
André, you have posted this SeaMonkey enquiry to the mozilla.general
newsgroup, which is normally used for general, worldly, discussions, not
technical enquiries.
A more appropriate group might be mozilla.support.seamonkey or even
mozilla.dev.apps.seamonkey, so I have cross-posted this to both those
groups and then set follow-up to mozilla.support.seamonkey, so that is
where your answer may be found.
Cross-posted to m.d.a.seamonkey and m.s.seamonkey with follow-up set to
m.s.seamonkey
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101
Firefox/25.0 SeaMonkey/2.22 Build identifier: 20131023190942
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
