Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
Idle suggestion: Have you tried selecting another style, and then switching back to IEEE?
-
Word can display those fonts.That's my point, actually. If pasting text with the boxes to the website caused the characters to render correctly, that suggests that the character codes delivered by Zotero are correct. If they are not being rendered c…
-
Have you tried selecting that region of text in the Word document and changing the font? (The rectangle is used by Word to stand for characters for which it has no glyph in the current font.)
-
Alright, I think we're clear of this one. I've fixed the corrupted output problem in processor release version 1.0.131, just pushed. Looking at the behavior now, it should be fine even with "mismatched" locales; if the output looks funny, the user c…
-
That's a suggestion, I'm not sure it's the right one. It would turn on whether the typography within a title should be preserved in foreign-language citation styles. Most immediately, I'll fix the processor so that this corruption doesn't show throu…
-
@suki: I see now that this is a genuine error. It will be remedied soon, but please see this other thread for further information.
-
Aha, the user in the other thread didn't come back to insist that the RTF markup was showing through in the word processor, but I now see what is happening. The convention for quotation marks in Germany and Austria is U+201E on the left and U+201C o…
-
What appears in the position of the hash characters instead of ä and ö (which would presumably be correct?)?
-
This was a separate wrinkle, but a newly minted citeproc-js nickel will be up shortly.
-
Yep, confirmed. It's the special handling of institutional authors come 'round again. It's a fairly simple fix, and I should have something out real soon now.
-
I've done something pretty close to that in the fix (sorry for not posting back as promised -- I must have either forgotten to hit the send button, or posted to another thread). The diffs are here: https://bitbucket.org/fbennett/citeproc-js/changes…
-
The choose block inside the substitute element is not valid CSL, and is likely to break things.
-
Depending on your word processor, "alt+F9" will make the hidden codes that control Zotero references in the main text and bibliography visible. The method for making the codes visible may differ for your platform, but it should be accessible via a m…
-
This is a CSL processor error. Please send a copy of the document to biercenator (at-mark-thing) gmail dot com. I'm curious what the cause is, and would like to fix the processor so this can't happen.
-
Great -- amend away!
-
I may have fallen behind on developments. There are separate areas for CSL 1.0 and CSL 0.8.1 in github repo?
-
@bdarcus,I suggest you figure out a solution that is general; I don't want to add a "court-division" variable to CSL, and prefer to avoid adding anything if possible.Not at this stage, but the court division (i.e. Civil, Criminal, Administrative, Fa…
-
Yes, major software upgrades in the midst of a major project (upgrades of any software, not only Zotero) can be risky. Sticking with the environment that you entered the project with is a sound policy, and it's good to hear that you've been able to …
-
Understood; I'll get rid of the spacing nannyism around prefix and suffix. I'll look into the spacing issue with ASA and the discrepant formatting of author and editor names, and post back here.
-
Uhmz, that's a good question. Strictly speaking, there is nothing to fix in the processor, but if the repository styles are still all cast in CSL 0.8.1, we can't drop the text-case attribute in them without breaking things in Zotero 2.0.9 clients. …
-
CSL 1.0 should be able to produce the exact effect you're after, both in sort ordering and the display of names. The options (set by an attribute to the top-level "style" element) are documented here: http://citationstyles.org/downloads/specificati…
-
This turns out to be a style "error". The processor is doing the right thing, but the Chicago styles render ibid with the following construct: . It should be safe to just remove the text-case attribute in the CSL 1.0 version of these styles. In the…
-
I'll let you know in a few minutes. :)
-
Confirmed. Thanks for reporting this. The citation processor is designed to handle this correctly, but something in the Chicago style is tripping up the logic. I'll get this fixed within the day in a fresh processor release, which should make its wa…
-
I am not able to reproduce this error in a simple document, so we'll need more detail on the conditions that trigger it. The following info may be relevant: - The platform (Word, MacOS, etc) - The specific Zotero version - The specific word process…
-
I've included an extended list in a revised version of the processor, just checked in and pushed. @Rintze: If the particle is capitalized in input, the title-case function won't touch it, so it might be safe to add these to the list as well.
-
It shouldn't. But when Zotero touches an author for editing, it compares the fields in JS with known content and selects (or if necessary creates) a database row with the content it sees. So long as JS isn't messing up the content analysis inside Zo…
-
This is very, very odd. It would be good to know how the all-caps form populated to the other entries for the same author. As far as I know, a difference in the data field should prompt Zotero to apply a separate creatorDataID to the two names, but …
-
Aha. I was working on a post, but was called away from my desk before hitting the send button. The text is below -- but the short answer is that there was no reason for the change that I can remember, and restoring the status quo ante is probably th…
-
I've taken a look at the style, which looks fine. I'll need some sample input that causes the failure. It should be triggered by two or more adjacent citations in a single note. If you can narrow it down a bit, please send an RDF export of the citat…