Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
I have identified the source of the fault in the processor, in a reset operation meant to cope with styles in which first and subsequent citations have different et-al constraints. The saving of parameters is just happening at the wrong location in …
-
I can confirm this. In a quick test, names added for disambiguation do not receive the first name. I've confirmed that Zotero is delivering the first name to the processor, so the problem must lie inside the processor itself. I'll look into this.
-
I haven't been able to reproduce this. Investigating it did turn up a (different) bug in the processor, and I've just filed an update that covers that. But assuming that all authors are entered in two-field mode, I seem always to get et al. when the…
-
The mystery of the missing "use existing partner" selection has been resolved. The UI for duplicates detection was written last summer, and when I found it rather slow, I set it aside, until dusting it off a month or so ago during the push to get mu…
-
Alright, that was simple to fix. Apparently I missed out the file that carries the attachment box code from one of my patches from the trunk. I've made the necessary adjustments, and it works now. It will either come through as an automatic update t…
-
Ah, I got you. The right panel doesn't appear for file attachments. Thanks for the report, I'll take care of it soon.
-
Looking through the changelog for 2.1beta, I don't see a mention of an extra item window. When you get a chance, could you clarify that on this separate thread?
-
@cumuluss, Thanks for the clarification. I'll look at it; post if you notice a pattern to the failure. Re missing features of 2.1, thanks for pointing this out; some heavy code refactoring was needed to keep up with changes on the trunk, and some …
-
The "use existing partner" option should only appear on items that are color-coded in the Duplicates View. Items without a color highlight (white items) are masters, and cannot be merged. Are you failing to get the "use existing partner" selection o…
-
Well, that's certainly an unexpected use case. :) The behavior you're seeing is caused by an undocumented feature of the citation processor, intended for the support of institutional authors. It is treating the middle portion of the string as a set…
-
Yes, that would do the trick for pure numeric ranges. I'm just a little reluctant about introducing a facility that catches only some cases (although admittedly pure numeric ranges are the most common). Ideally, my own sense, at least, is that chang…
-
On a separate note, selecting all items and opening Duplicates View is pretty demanding on the system. Since it must compare everything with everything, the number of operations required expands dramatically on a large library. The number of operati…
-
That's the right thing to do with a Report ID generally speaking, but the multilingual version is my own experimental thing at this point, and not supported by the core developers. I'm not sure what we do in this situation ...
-
It would be quite tough to do this. It would need to work for all ranges, and you'd be surprised at the variety of "numbers" that occur in citations. Open ranges are one obvious item, but a harder case is ranges of compound numbers (which the proces…
-
Did you mark any entries to be checked as "new" as shown in the screencast? If no items are flagged as new (yellow), you'll always get an empty view. The code was tested with a library of 1200 entries before release, selecting all items in the libra…
-
annekebatenburg, It's a separate topic, but are you finding that the extraneous names issue that we discussed earlier has been resolved in new documents?
-
Good news. The localeCompare() operator is doing its job correctly, but it was being foiled by an unnecessary operation (forcing the characters to lowercase) that I was performing before it was invoked. I'll check in the repaired processor immediate…
-
Okay, I can confirm that this is (yet another) problem with the Firefox localeCompare() method that I have relied on for sorting. Which is annoying, because this is a standard Javascript function that the citation formatter uses because it is meant …
-
Those two characters set as titles on dummy items come out in the right order on my Linux system under 2.1b7. I'm not sure if it's relevant, but what are your operating system and Firefox versions? As another thought, this might be a problem with th…
-
Ah. That's helpful. So the document can't be read in Open Office in this form. I understand now, thanks.
-
I have a copy of the document (originally in Word, as a docx file) here, and I'm slightly puzzled by one thing. Simon may be able to clear up my confusion. The document is built with "Field" as the fieldType. I assume that this stands for Bookmarks,…
-
I'm not sure, but there might be a possibility that the ordering is being thrown off by the way the character is encoded behind the scenes. As Avram notes, sorting will ordinarily work correctly (and I just tested this one in Zotero 2.1b7 to be sure…
-
If poss -- if it's inside several megabytes -- also send along a copy of the zotero.sqlite (gear menu, Preferences, Advances, Show Data Folder) on which the document depends. Failing that, an RDF export of the references it uses.
-
Ah, thanks, this is all useful. Good to know that this is triggered by a particular document. Good move with downgrading; the continued failure tells us that a change in Firefox is not the cause. Together, those two observations suggest that there …
-
mcsugarfree, Do you get this with a fresh document, or does it only affect a particular document? Here's the thinking. The error you're getting comes from the citation processor. It looks as though it is getting stuck in a loop while attempting to…
-
John, I think what you want is after-collapse-delimiter, available in Zotero 2.1, which supports CSL 1.0. From the CSL upgrade notes by Rintze Zelle: http://citationstyles.org/downloads/upgrade-notes.html#citation-collapsing
-
The style validates, and everything seems to be in order, apart from one small point. You're using font-weight="bold" on the name node, as well as on the group wrapper. Try removing it from the name node; the processor might (might -- I haven't chec…
-
I think this is probably right. On thing that may (I hope) be coming down the road is support for a user-defined, document-specific "hereinafter" form for titles, supplied via an external abbreviations list. Setting the short title as its own variab…
-
To simplify the task, I can send along an Excel file that contains all of the texts used in Zotero. I can't speak for the team, but if you or another user with a stake in support for Bahasa Indonesia can provide the translations, I would think that …
-
@annekebatenburg, That sounds promising. The processor would not "taint" the existing citations, even though they are incorrect. If the problem corrects itself when citations are edited, this may be the fix we were aiming for. Keep an eye on it, an…