No, it is the JavaScript file used by the aTbRef’s search page: see Fuzzy Search for aTbRef.
The issue is the index info is loaded via an AJAX call and that doesn’t wok in a local ‘static’ file but will on a web server (or such is my limited understanding). That aside, all the content is local. IOW, if you run local web server, you can run aTbRef even if not connected to the Web. Actually, the following features won’t work unless toggled out:
- Web search: DuckDuckGo and Google. I really ought to drop these as I don’t think they’ve ever really worked effectively—as in the matches being valid.
- The aTbRef donation link (as it run via PayPal). (Not sure I built a local-export toggle for this.)
- The Google-supplied page translation. I’ve head it’s not great mainly as such tools don’t cope well with technical literature unless something is in a big corpus, e.g. coding Python vs. Action code!
- The Creative Commons link
But, for local (off-Web) use, I think you aren’t actually likely to click any of those.
So solutions are:
- run a local webserver. This is not complex as such, I just don’t recall the right magic incantation to make it happen.
- re-write the JavaScript code loading the index. Likely not a novice task, so the above seems the easiest apprach.