Google Scholar Translator Problem

Hi All,

When I search Google Scholar through my library's proxy, the translator doesn't come up (i.e., no icon appears in the address bar in Firefox).

Looking at the .js file, I realize that the problem is likely with this regular expression:
"target": "^https?://scholar\\.google\\.(?:com|com?\\.[a-z]{2}|[a-z]{2}|co\\.[a-z]{2})/scholar(?:_case)*",

because the URL that I have for a search is:
https://scholar-google-com.eres.library.manoa.hawaii.edu/scholar?hl=en&q=dogside+story&btnG=&as_sdt=1%2C5&as_sdtp=

The problem is, I'm not very comfortable with regular expressions. Can anyone help me figure out how to change it so it catches my URL?
  • edited June 8, 2015
    scholar\\.google\\. --> scholar[.\\-]google[.\\-]

    the problem is the stupid replacing of periods with hyphens in the URL that some proxys perform.
  • Thanks very much, Adam!

    Your suggestion didn't quite work, but it was enough to get me fiddling through to a workable solution.

    I ended up with this:

    "target": "^https?://scholar[\\.\\-]google[\\.\\-](?:com|cat|(?:com?\\.)?[a-z]{2})(?:\\.eres\\.library\\.manoa\\.hawaii\\.edu)?/(?:scholar(?:_case)?\\?|citations\\?)",
  • Actually, that replacing of periods with hyphens isn't entirely stupid. It allows the proxy to use a single, low-cost wildcard SSL certificate to cover all proxied domains. I'm actually trying to get our University library to turn this feature on, so that HTTPS connections to more than a handful of services can be served with a valid certificate. Currently - and for months past - almost all of our proxied content breaks Zotero. The only slim ray of hope that I have for eventually one day regaining access to our collections from off campus is the EzProxy HttpsHyphens option, so I'm actually rather fond of it.

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.