scholar.google.com.au doesn't trigger scholar.google.com translator

CB

I guess the topic title says it all.

scholar.google.com insists on redirecting my searches to scholar.google.com.au. I then get no zotero icon in the FF address bar, so have to manually remove the '.au', and refresh. That gets the translator working, but presumably it should work with the .au version.

cartesian

Core devs - can you open a ticket for this and close it with the following FIX?

Change target regexp of Google Scholar translator from '^http://scholar\.google\.[a-z]+/scholar'
to
'^http://scholar\.google\.'

Question: Current translator already matches:
http://scholar.google.com.ezp1.harvard.edu/scholar
How does it do this???

dstillman

cartesian: Zotero translates EZproxy URLs before the regex comparison, so it's only comparing scholar.google.com, not scholar.google.com.ezp1.harvard.edu.

We'll change the regex so it accepts domains like com.au (and co.uk). Thanks.

dstillman

Pushed an updated translator. Thanks.

CB

That's great, thanks guys.

mark

It doesn't work for scholar.google.nl. Could that be due to the translator?

dstillman

It doesn't work for scholar.google.nl. Could that be due to the translator?

Define "doesn't work".

sean

The site (scholar.google.nl) works fine for me

sybille

I tried, and I am only able to capture Zotero references if cookies are enabled for google.nl. If cookies are not enabled, the "Could not save item" pop-up appears. With cookies allowed, both capturing from the address bar and capturing using the "Import into Endnote" link (set in Google Scholar preferences) work fine for me.

So, mark, do you have cookies enabled for google.nl?

mark

I'm sorry, normally I am on an all-English system and there it does work. But it didn't work (as in the red box appearing but nothing being saved) on a system with the Dutch version of Firefox. I got it working by installing the English version of Firefox; I didn't like the Zotero interface being partly in Dutch anyway.
Which makes it impossible now to determine whether the problem was the language or the cookie. So it might indeed have been the fact that I had cookies disabled for google.nl (though I normally do enable cookies on Google).