Tagesanzeiger.ch: Wrong translator used

Hi,

when browsing
http://www.tagesanzeiger.ch/wirtschaft/konjunktur/Spass-beim-MonopolySpiel/story/30309064
Zotero should offer importing via a tagesanzeiger.ch site translator (which works, I checked using scaffold). However, there is only the option of importing via RDF, which produces bogus data. How do I get around that?

Zotero, otherwise, is absolutely wonderful.

Martin
  • I get the correct icon and a working import. Is this consistent? Just for that one page?
  • It works now. I don't get it, it didn't this afternoon. Thank you for checking,

    Martin
  • It happened again! It's probably got to do with an iframe on the page that advertises a price comparison engine (preisvergleich.tagesanzeiger.ch).

    Martin
  • Sorry, the URL it happened on just now:
    http://www.tagesanzeiger.ch/panorama/vermischtes/Kein-Geld-mehr-fuer-die-Scheidung/story/11438639

    Martin
  • And I still can't confirm it... So this is intermittent for you too?
  • I can confirm that it's intermittent - I happened to follow the link right when it was posted and got the RDF translator. Now I'm seeing the tagesanzeiger one on the very same page. bizarre.
  • It's definitely the preisanzeiger advertisement. Apparently, it's only sometimes on the page, maybe depending on what time it is in switzerland or something. I worked around it by blocking preisanzeiger.* with Adblocker.

    So if an ad includes RDF data that overrides a working translator. How does Zotero decide on which translator to use if there's more than one option? In my opinion, the most specific should always be used. So that RDF, Coins, and all the other generic stuff get selected only if there isn't a more specific translator for the site in question. What do you think?
  • So that RDF, Coins, and all the other generic stuff get selected only if there isn't a more specific translator for the site in question.
    that's exactly what Zotero does (or should do) but for some reason the preisanzeiger thing keeps Zotero from recognizing that a specific translator exists for the page.
  • Yeah, the priority doesn't matter for this—it'd be the URL regexp and/or detectWeb() that would be off (though from a quick glance at the translator it looks like it shouldn't be triggering on a subdomain of tagesanzeiger.ch other than 'www').
  • Yes-- I already checked the translator and it looks fine. This probably has to do with some funny stuff they're doing while loading the iframe, but it's probably not worth looking too deeply into this. Just use AdBlock and we can write this off as a funny quirk of the web.

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