Upgrade Storagefbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
Fix applied in processor tag 1.4.61
-
Response on the other thread.
-
Yes, this is the fault of citeproc-js. An issue was raised about recognizing en-dash in page ranges for pluralization etc.,[^1] because imported data often uses en-dash to express page ranges. The change should have been limited specifically to the …
-
Hello @geraldineblanche. If your error report was sent to Zotero, you may be running an old version of Jurism, so let's check that first. In the client, when you do Preferences -> Help -> About Jurism (or Zotero), what does it show? (The curre…
-
@zinigrad: Sorry for the delay in responding. You are running version 5.0.89m9 of the client. The current version is 5.0.89m14. The client is meant to update itself every 24 hours, but you can force an update with Help -> Check for updates. The …
-
@hakan.d: A fix for this is in the works. Thanks for reporting the problem.
-
@nithin.ramakrishnan: The Jurism connector hadn't been updated in quite some time, and that may be the cause. I have just released a new version of the Jurism client (v. 5.0.89m1), and a connector update for Firefox (v. 5.0.89.2). I have also submi…
-
@nathan.hopson: Oh, wait. Are the entries that are adding the comma set to "Japanese" (the word) in the Language field? If that's the case, it should be a BCP47 language code (either "ja" or "ja-JP" should work). We fudge "English" by lowercasing an…
-
@dstillman: I'll test this out, but I don't think it's a regression. As far as I remember, nothing has changed around name joins in years. Hi @nathan.hopson! Feel free to contact me direct on multilingual issues if you like (as we're neighbors). Wi…
-
This may be fixed, in release 5.0.83m6. Your client may already have updated, if not you can pull in the changes with Help -> Check for updates. Jurism was using an outdated version of the Zotero word processor plugins. As a result, the word pro…
-
@Ewelch99: I see from your earlier post that you are in the OSCOLA style, and also require treaties and EU directives (at minimum). To save you time with examples, we can use OSCOLA for reference. If you can indicate which sections of the guide need…
-
@Ewelch99: Improved documentation for legal citations in Jurism is in development, but I can advise here on your immediate requirements. To that end, a couple of questions: Which jurisdictions are you needing to reference? Is your main need for ICC …
-
@rtk12: The advice of @dstillman should apply equally to Jurism. Jurism uses the same word processor integration plugins as Zotero. To avoid possible mis-communication between Word and the Jurism client, be sure that Zotero is not also running (nor…
-
@KallistiMan:This should now be fixed, in Jurism release 5.0.83m5, which just went live for Linux, Windows and Mac. Your client should update within 24 hours, or you can update manually from Help -> Check for updates. In my own testing, the erro…
-
@KallistiMan: I just had a report on the Jurism mailing list, pointing back to this post. Sorry for missing you. Your report ID has expired, but I'll work with the other user, and post back here when we have resolved the issue.
-
@Ewelch99: It is as @bkorn says, with one exception: Juris-M and Zotero use the same word processor plugin, so you shouldn't need to touch Word. Restarting your computer as a first step in debugging will assure that neither Juris-M nor Zotero are ru…
-
I haven't worked directly with court documents in the wild, so my approach in Jurism is not proven, but the Case type has a field Document Name, which maps unimaginatively to a CSL-M variable document-name. It's intended for court filings: we can ap…
-
I'm fishing for advice on another matter, and will be writing sometime soon.
-
Understood. If you are using Jurism, JM OSCOLA will be better at handling cite forms across multiple jurisdictions. UN document cites are a work in progress, so feel free to post concerning things that are not coming out correctly. In OSCOLA 2006 i…
-
The bug in date handling was unrelated to jurisdiction settings. If you select a jurisdiction on a legal type, and tick the "default" box next to the field, that jurisdiction will be used as the default when creating new items. Is that not working f…
-
Are you using Zotero or Jurism for these materials?
-
Which version of OSCOLA are you using (either the OSCOLA style in the Zotero styles repository, or the JM OSCOLA style that ships with Jurism)?
-
This is now fixed, in version 5.0.83m4 of Jurism. Your client should update automatically within 24 hours, or you can trigger an update by clicking Help -> Check for Updates.
-
The Word conflicts and Zotero/Jurism sync conflicts would be unrelated. Hard to say what's happening on the Word side without more information, but it may be related to track changes, if you have that turned on. If that's the case, check to see if W…
-
(I should note that the bug doesn't affect the data that you have collected. The Jurism client appears to be applying a US-style date parsing rule to the standard date value stored in the Accessed field when running with the UK locale, which is stra…
-
@Ewelch99 I can confirm this, and it's a bug specific to Jurism. I'll post here again when a fix is available, probably within the day.
-
This is fixed in processor tag 1.2.33. The revised processor should appear in Zotero at the next release, and in Jurism shortly thereafter.
-
Does look like a bug, doesn't it. Did some processor work yesterday, I guess there will be a little more today. More soon...
-
FWIW I have always assumed that OSCOLA would apply brackets to paragraph numbers across all forms of a citation. As an out-of-scope aside, and while I've just noticed that I only mention it in passing in the docs, this use case prompted an extensio…
-
(A less elegant route would be to just kludge the Chinese names as single-field values, of course. Not sure whether that would create any other problems.)