Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
On a quick check in my development client with the same 1.0.206 processor version used in Zotero 3.0b2, everything comes out correctly when I send an rtf bibliography of those items to the clipboard and open it in OpenOffice. Is it an in-document b…
-
It's not supported at present only because the team hasn't reviewed the code, but that could certainly change down the road. I suspect that it would turn on grounding a round of project funding on multilingual support. I haven't heard anything speci…
-
Stephan, Sync of multilingual data is not yet supported, unfortunately, and the multilingual client is not supported by the core team. The best we can do in the short term would be to get the new duplicates detection mechanism working in the multil…
-
At least the sort appears to be correct, so that's some progress. Can you export the full set of references as Zotero RDF and paste them as a public gist on http://gist.github.com/ so we can try to replicate the issue? If preferred, send me a messag…
-
Can't help with the headline issue, but to quote stuff you can use:Words of great import and significance.
-
I often get the following error "Zotero experienced an error updating your document"You'll have to take advice from the core team about that one. It may or may not arise from a problem in the processor.
-
I get the same result with those references in the latest processor release (checkin #2633). I also tried with the version used in Zotero 2.0.10 (checkin #2572), same thing: http://img402.imageshack.us/img402/6079/screenshotsameauthors.png It's th…
-
Yes, it should show et al. There is a likely cause (et-al-min should be set to at least "2"). Which style are you using? (Edit: disregard this comment, with my apoligies. I misread the issue.)
-
That would be great -- and glad to hear that you've been able to sort it out.
-
To investigate, I would need to reproduce the error locally. I've tried the style and it seems to work correctly. At this stage, the best approach would be to tolerate the stray italics for the remainder of your drafting work, and then strip the Zot…
-
andwin06: If you can identify a specific item or citation that causes the problem, I would be very interested in taking a look at it -- you can export the item as Zotero RDF and paste to gist.github.com as described above. This error shouldn't ever …
-
As noted above, none of us have yet been able to reproduce the error, so we wouldn't know where to start on a fix. It's likely caused by some peculiarity of your local system. Very good to hear you have a workaround that works though.
-
We haven't seen this error in a very long time. If you are using the Turabian style from the repository, can you isolate the item that is causing the fault? If so, please export it as Zotero RDF, paste the RDF to http://gist.github.com/, save it as …
-
We haven't seen this error in a very long time. If you are using the Turabian style from the repository, can you isolate the item that is causing the fault? If so, please export it as Zotero RDF, paste the RDF to http://gist.github.com/, save it as …
-
As far as I know, this was fixed some time ago. If your deadline is pressing, you're probably best off finishing the manuscript, making a submission copy, stripping Zotero codes in the copy, and fixing up the bad delimiters with find and replace. W…
-
It's not stubbornness. The list of labels are shared between three separate parts of the system (Zotero proper, the word processor plugin, and the citation formatter). The need for coordination means that changes of this kind take place at large rel…
-
This is now fixed, and should appear in the next Zotero release. The fault is caused by a cs:text node followed by a cs:number node, wrapped in a cs:group with no delimiter: You can avoid the bug for the present by moving the suffix on the …
-
Definitely a bug. It manifests when a cs:text element is followed by a cs:number element, joined without a delimiter. Should have a fix out in a day or so.
-
I'll leave advice about the workflow to others who know the BibTeX side better than I do, but just for info, the "citationID" is not a key for an individual item; it's a key to the citation as a whole (which may contain multiple items).
-
Which style?
-
I'm working on the style end this week and next. Styles have complex rules for abbreviation of field content, so I need to nail down what goes where before turning back to translator development. Sites mostly provide abbreviated forms in metadata, …
-
I've written to Jonathan to see if he has a local copy of the translator file.
-
I would like to contribute to this on law sites.
-
Jonathan Lewis posted an NDL translator to zotero-dev some time back. If the Files zone of the group has been archived, it could be updated for distribution.
-
I don't see a "Show non-Roman characters" option. Where should I be looking? (Might this be in an OCLC FirstSearch view of WorldCat, rather than Open WorldCat?)
-
Glad to hear the your project is under control. When you get to the other side, let's look more closely at this.
-
Hmm ... maybe we shouldn't write off the possibility that the processor is a fault too soon. I wonder whether Unicode decomposition could lie at the heart of this.
-
I don't know if it's relevant, but I recently fixed a processor bug that did make it possible to get duplicate items in a bibliography listing. The calling application (Zotero) would need to send the processor a list of ids containing duplicates, bu…
-
There is at least on syntax error in the style, at line 803. As a first step, you should validate the style to be sure that the CSL syntax is correct. http://www.zotero.org/support/dev/citation_styles#validation
-
I've been able to isolate the fault. Thanks again for this data, this was exactly what was needed to get to the bottom of this. Bundling up a fresh processor release now, which should work its way into the next Zotero release.