Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
Be sure that you have a good backup of your data directory. With that caveat, the links to previous releases just follow the version numbers: 3.0b2, 3.0.2. It's worth sticking with this thread and following through on debugging when the core develo…
-
Okay, this is now fixed, in processor release 1.0.289. The bad behavior will disappear when the processor is picked up for the next Zotero release. I didn't trace the exact logic of the hang, but it was triggered by an attempt to initialize the giv…
-
... and the good news is that I can reproduce the fault here. Dinnertime now, but I'll have some more news when this has been fixed. Thanks for taking such care over the report.
-
I don't doubt you, but with that config line in a test fixture and input as you describe, the processor runs fine and produces the expected result. We should start by checking your Zotero version. If you're not yet on 3.0.3 you should upgrade befor…
-
As adamsmith says, the processor has some extended capabilities for handling institutional names. The processor will recognize the publisher variable as a name, in fact, but unfortunately that will not cover your use case. The one situation where t…
-
No. Only in the Firefox client.
-
You wrote that you see a beautiful report. How are you generating it?
-
I don't use reports, but from Zotero within Firefox, it looks like they come up as a formatted page in the browser. Using the browser print function, I can print the report directly as a PDF, or using the browser page save function, I can save it to…
-
Try these steps first: http://www.zotero.org/support/word_processor_plugin_troubleshooting#debugging_broken_documents
-
The processor has been able to do this since July 2010. The last logged tweak to the functionality, in connection with a major refactoring of the code for formatting names, was done on April 18, 2011. If you need this in your style, you can add it …
-
Version 3.5 will be the target for a large overhaul of metadata. Input from area specialists like yourself will be valuable in that project.
-
If it's (2), then yes, it can't be expressed in a single item. You can store two separate references and relate them, and they can be joined in a multiple citation (using a prefix or suffix through the word processor plugin). But there is no provisi…
-
The multilingual storage layer in MLZ may be intended for something slightly different. There are two possible use cases for other-language data. (1) When a resource is cited outside of its original language domain, citations need to be adapted to …
-
Doesn't the cut of the film sometimes vary between distributors?
-
I've just checked in a release that addresses these items, as well as several things related to locale handling that had piled up. For "Anglais" and "Inglês", I've added a processor method for setting arbitrary English overrides in the instantiate…
-
I've set the processor up to force a "page-range-delimiter" value into all locales. For locales beginning with "fr", the fixed value is set to hyphen, and for other locales it is en-dash. The new behavior will appear in the next release. This is a …
-
Sorry for the long delay over this. I've added the Unicode ranges for Arabic and Persian to the "roman-like" test function of in the processor. In the next release, a space should be inserted between the elements of names written in Persian script.
-
@Rintze: The logic is in there already; Dan's concern is just that users are having to learn the rules by coming to the forums for guidance, and some will not notice, or will give up before they get here. We're just exploring ways of smoothing the t…
-
As Rintze notes, the bibliography (CSL) locale governs the behavior of items with no Language field value, so we're covered there. One other thing: looking at some values on the server, "Anglais" is quite common, and "Inglês" appears as well. If thi…
-
Yes, with the stream of queries over our first step into the multilingual domain, this needs to be sorted out. Here is a set of proposals: Treat an empty Language field as non-English if the CSL locale is set to a non-English value. As Dan says, tha…
-
It's the only option at present. I would guess this is not a high priority for the core developers, since (as far as I know) things work fine if the project is split into separate chapter documents. About all you would lose is the ability to automat…
-
I've added the locale to the citeproc-js source, so that it will roll out with the next release.
-
A single variable like "frontmatter", with a controlled list for content and corresponding localized terms should do the trick. It would need UI support and a small extension to CSL.
-
Yes, that seems pretty useless as a referencing mechanism, and would be difficult to implement. Might as well just add the pinpoints by hand in that case.
-
What do these styles do if there are multiple references? Do the page references accumulate in some way, or do they cut a separate item entry for each reference? If the latter, it could be implemented as a note style, with the "bibliography" shifted…
-
@cudell: The Page field data that you insert via the Word plugin is recorded in the document, and will appear in citations in non-numeric styles. Pinpoint page numbers are not shown in the bibliography, in any style that I know of (including IEEE), …
-
The Item History plugin was broken in FF10 (and maybe other recent versions) due to some bad version detection code. It's been fixed, and should now install and run okay.
-
For the syntax to work, single-field creators need to be flagged as institution names, which is not done by the official Zotero client (for good reasons). To make use of institutional names formatting, you would need to use the MLZ client, which is …
-
There is an experimental CSL syntax for this that is recognized by the processor, but it's not yet available in the official client.
-
Yep, that would be due to the period, which the processor sees as a full stop ending a sentence. We're coming up against the rule that you can't please all of the use cases all of the time here. We may be able to cover this with a heuristic, but thi…