Most of my friends know I stay next to St. Vincent’s High School in Camp, Pune. This is where I studied from class VI to XII after we moved here from Bombay, and where I’ve lived for just over two decades. Our brass band has cyclic quality which changes over the years; it improves as the students get better but quality can drop when there is a sudden influx of new guys. The last three to four years have been particularly good though.
Sometimes the band beats your alarm clock to the punch, which is mostly pleasant, but I wish they would learn more tunes!
I released FireBible 1.4 early this morning, this release fixes issues with recent Java 7 updates and Firefox 16 and above, as discussed in my last post. I also threw in a few minor bug fixes.
A longer term update:
- FireBible still won’t work with the IcedTea Java plugin on Linux (unless you remove almost all security settings, not recommended). So you will still need an Oracle Java installation on Linux for FireBible to work.
- Still no av11n (alternate versification) support as I need to wait for this to be added to the JSword library. Full support for deuterocanonical books (including the Catholic Bible ) therefore not present yet. Hopefully soon.
- Ubiquity support still cool (I consider this to be one of FireBible’s best features) – but you need the privately maintained Ubiquity 0.6 version or higher; you can get that here (download the file and select it in the File > Open dialog to install).
- Will investigate the viability of switching to the native Sword libraries as opposed to Java based JSword:
- No Java installation required, extension should work out of the box.
- Security issues keep cropping up with “Java in the browser”. There are restrictions that are either imposed by Firefox itself or changes in Java internals that affect “not so common” use of Java. Hopefully we’ve seen the last of these.
- av11n support already present in native Sword libraries.
- Will lose JSword specific UI such as the module installer and settings.
- Implementation will be harder and take time which I do not currently have.
- Will need to build separate versions of the extension for each platform (currently not required due to the use of Java libraries).
Unfortunately there have been a couple of issues rendering FireBible defunct on recent versions of Firefox.
- First, there was a security vulnerability in Java 7 update 6 and below. This lead to these versions of Java being disabled; if you updated your Java installation, it would be enabled again, but loading text in FireBible fails with
org.xml.sax.SAXException: Could not compile stylesheet javax.xml.transform.TransformerConfigurationException: Could not compile stylesheet at org.crosswire.common.xml.TransformingSAXEventProvider.provideSAXEvents(TransformingSAXEventProvider.java:174) at org.crosswire.common.xml.XMLUtil.writeToString(XMLUtil.java:85) at …
I’m not too sure if this was caused by changes in Java 7 update 7 (or later) or if it was the switch to JAXP 1.4.6 in Java 7 update 4 – nevertheless, you are now forced to use a version of Java in which the above error occurs.
- The second issue is a change in Firefox version 16 (16.0.1 is now current) where the “java” global variable was removed. I was warned by the addons team in advance, but failed to make changes in time (however, we’d still be stymied by the above problem).
The good news is that I do know how to solve both problems, but am currently looking for a better solution for the first of these. I’ll try to release a fix ASAP.
This extension has always been a technical challenge, which is fun most of the time, but the battle with Java in the browser has been a PITA – it still won’t work with IcedTea due to more permission problems. I’m wondering if I should go native instead and switch from JSword to Sword, the crossover will be quite expensive in terms of time and effort, but will probably add long term stability to FireBible. A Java installation (specifically, the Oracle one) would no longer be required and we wouldn’t be plagued by these incessant security issues.
I released FireBible 1.3 last weekend, with the following key fixes. If you already have FireBible installed, you can check for updates, or head on to the FireBible page to get it.
Changes in 1.3:
- Will automatically download and install JSword.
- Can automatically install books if none found.
- You can now type book names first in Ubiquity (don’t need to start with ‘sword’).
- Fixed Ubiquity command installation issues.
- Fixed issue with Sun’s Java 7 browser plugin.
- Raised compatibility to work with more recent Firefox versions.
For those of you having issues getting Ubiquity to work with recent Firefox releases, please download this file and open it (File > Open File…) using Firefox. This is a version of Ubiquity being maintained by satyr.
- Getting FireBible working with OpenJDK / IcedTea browser plugin (still only works with Sun’s VM and plugin) but OpenJDK and IcedTea compatibility seems more possible than GCJ support.
- Integration of a newer version of JSword with av11n support (which is still being developed) so I can finally support Catholic Bibles.
Announcing the release of DataFox 1.9.5, with:
- Support for selfcare.ndc.bsnl.co.in, thanks to Rohit Singh for the help. The “charged usage” is displayed as 0, (at least for his account) and this is the value DataFox uses to display the progress; so if your account has this same problem, you will not see a progress bar at all and the surplus calculations will be off. Hopefully BSNL fixes this problem soon. If you manually enter selfcare.wdc.bsnl.co.in in the domain field, DataFox might work for that too because they appear to use the same backend. Unfortunately, because nobody has sent me their credentials, I have been unable to test this or add support if required.
- Increased Firefox compatibility range to 15 – I don’t want to be forced to release a new version every couple of months with these monthly major version changes.
As always, if you want support for the selfcare portals, please send me your credentials or I have no way of implementing support and I will have to simply ignore and / or delete your comments.