Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
Word is doing something odd here. The numbering style (roman versus arabic numerals) is controlled by Word, not by Zotero, so the route to fix that would be through the Word menus. It's odd, though, that the references are appearing as footnotes in…
-
That's is the multilingual version. To be sure that I pick up queries about this experimental branch, you can flag queries with "[Multilingual]" in the message subject. It looks like there was a bug affecting attempts to save an item containing "re…
-
I was thinking that a loop variable might get clobbered during sync.
-
It doesn't give me much pleasure to say so, but this might have been caused by flaws in the code of citeproc-js. The version of the processor running in Zotero 2.1.6 contains a number of bad variables (undeclared global variable assignments, in Java…
-
@adamsmith: You wrote:This is not the behavior I would have expected, though - I'd have thought disambiguation just defaults to the long form of the author when called - i.e. initials when there is an 'initialize-with' term, full first name when the…
-
I had a similar experience myself this evening with Chicago Author-Date. The fix I applied cleared things up here, and I've released the code. When the new processor version is picked up by Zotero (probably a matter of a few days), should find that …
-
There is currently a rendering bug in the processor that affects some styles, which could produce this behavior. Choosing a different style may allow the citation insert ot go forward. The bug will be fixed in the next Zotero release.
-
Ha. Before posting to the CSL list I checked the specification, and the behavior you desire (a jump straight from short form to full name) is listed as the correct behavior when initialize-with is not set. It's right there in the disambiguation sect…
-
Great, thanks for getting back. I'll follow this up, and post back to this thread if I have anything definite. It's easy to adjust the processor to do this; it's just a question of whether the change would cause a ruckus among users who expect somet…
-
Chinese characters in UTF-8, at least, shouldn't cause any problems with the DB.
-
Interesting. If the exported RIS passes through in-field formatting, it may be possible to preserve some of it on Zotero-side now.
-
(If there is to be further discussion of this sorting behavior, it should probably take place on a separate thread, since this one started off of a different issue, although a related one.)
-
I've gone ahead and implemented grouped sorting in author-date styles in a fresh release of the citeproc-js CSL processor. It's automatic: no change to styles is required, it will just sort in that mode if citation collapsing is enabled. A simple so…
-
Yes, that would turn off disambiguation entirely, and use the long form only. I'm sorry about getting the behavior wrong; it was late at night when I wrote that last response, and I misinterpreted the behavior exhibited in one of my own tests. It s…
-
I've introduced a fix, and made a fresh processor release. You should find that this problem goes away in the next Zotero version.
-
I'll just offer a quiet, despairing one-line rant over the persistence of EUC-JP and Shift-JIS.
-
It depends on whether you need initials for the Western authors, or whether jumping from family-only to full-name for those as well is acceptable. If the latter, you can remove the initialize-with attribute from the name node, and disambiguation sho…
-
The processor will automatically apply the correct word-ordering to names written with the Chinese and Japanese character sets. If I remember correctly, I've implemented the processor to apply abbreviations, though, because the first character of th…
-
Two problems were reported in this thread -- the case name appearing twice, and the reporter name disappearing in subsequent citations. The first issue has been resolved, and the second issue was due to bad input at the user end. You should find tha…
-
As noted on the other thread where you posted this, this is due to a processor bug that has been fixed. The issue should go away with the next Zotero release.
-
(The stray year-suffix issue is due to a bug in the processor that was recently fixed. The updated processor will appear in the next Zotero release.)
-
I haven't tried sync today, but I hear that Amazon Web Services (the "cloud" where zotero.org and the rest of the Zotero online presence resides) was down for over 24 hours. If if works now, that would be the reason.
-
@ikeda_t: probably the simplest solution is to install Quick Locale Switcher, and set the Firefox interface locale to en-US (you need to dig into the QLS options to set that up, it doesn't set the UI locale by default).
-
I've just worked out how to control this, and the fix will be included in the next processor release. (The hack above doesn't quite get things right, actually: if the short cite without locator comes at the end of the citation, the closing period ne…
-
I've been looking at Chicago Fullnote in connection with this issue, and it looks like the stray period is being inserted by the processor itself, without any authority from the style. It's a bug, but the code here is (unfortunately) quite complex, …
-
I completed the rewrite this morning, and the new code, when it is released and finds its way into the next or a subsequent release of Zotero, will suppress only the author variable.
-
While the delimiter issue and the sorting issue in this thread affect the same category of citations, the sorting thing is separate from the headline issue of the thread. Further discussion should be taken up elsewhere, or in a fresh thread. In pass…
-
In the test suite of the latest (still unreleased) processor code, this is working correctly, if it hasn't been fixed already.
-
As you have probably noticed, from Zotero 2.1.6, the handling of single and multiple fields has returned to the earlier behavior.
-
An issue that may have produced this error has recently been fixed. If the behavior is not already correct in 2.1.6, you should find that it is corrected in the following release.