TorBrowser-specific problem with bibliography creation problem
Hello!
I stumbled on a very strange problem with this self-made style only when I use it with Zotero in the TorBrowser 4.0 (based on Firefox ESR 31.2.0). In the section
In the same Zotero version in a regular Firefox 32.0.2, the code is executed for all entries I tried so far. I take this as an indicator for the problem resulting from either TorBrowser generally or Zotero in the TorBrowser specifically not passing on all these HTML character codes.
Does anyone have the time to test this as well or to provide general advice about using Zotero in TorBrowser? Thanks and greetings!
I stumbled on a very strange problem with this self-made style only when I use it with Zotero in the TorBrowser 4.0 (based on Firefox ESR 31.2.0). In the section
<if type="article-journal">
the command <text variable="URL" [...]>
is not executed for many entries. For some, it strangely is...In the same Zotero version in a regular Firefox 32.0.2, the code is executed for all entries I tried so far. I take this as an indicator for the problem resulting from either TorBrowser generally or Zotero in the TorBrowser specifically not passing on all these HTML character codes.
Does anyone have the time to test this as well or to provide general advice about using Zotero in TorBrowser? Thanks and greetings!
(The citation formatter in Zotero can be made to add markup like this properly with a small amount of tweaking, if altering the client is something you would contemplate for your use case.)
Anyway, where can I learn about the tweaking required to insert hyperlinks in a more elegant way? I searched around here on the forums before using this style, but found mostly "not currently possible"-like entries.
It may still be worth it to follow up on Frank's suggestion--I think the main issue that you'd expect to see is that, when using the HTML bibliography function in Zotero, angle brackets (<>) would be escaped, which would then break your hyperlinking efforts. If that isn't how you're using this, I think your "literal" approach should be fine.
Case closed: no bug after all; "literal" approach does work.