Offer a way to unpack/repack omni.ja after switch to Brotli compression




Networking: JAR
3 months ago
3 months ago


(Reporter: flod, Unassigned)


(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [necko-would-take])



3 months ago
After switching to Brotli compression in bug 1352595, there's no easy way to edit the content of omni.ja files.

Before, it used to be possible to use tools like 7zip or unzip to hack on the browser.

I personally used omni.ja files to do quick tests that don't require a full build system:
* Making local changes to localization files before committing them to repository, either to test length issues or errors.
* Minor changes to XHTML or JS file that don't affect tests.
You can already unpack a full firefox directory with mach python toolkit/mozapps/installer/ (but you need to at least build $objdir/dist/host/bin/bro, which you can do with something like mach configure ; mach build pre-export mozilla-config.h modules/brotli/host)

Also note that bug 1352595 is not riding the trains yet.
I should add: does take care of chrome.manifest files, so that the resulting directory contains a working firefox without any omni.ja.

Comment 3

3 months ago
This method requires having a full clone of mozilla-central (or mozilla-unified), and a system with the packages needed to build Firefox. 

I think that's too big of a requirement for someone who just wants to tinker with omni.ja

Side note: this needs updates

Comment 4

3 months ago
I just quickly ran some tests, and for now, I can use unzip for the use-cases I have. Those mostly revolve around debugging and inspecting the results of l10n repacks. And as those don't create brotlis yet, unzip -p of those just works.
Whiteboard: [necko-would-take]
Bulk change to priority:
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.