fbennett
About
- Username
- fbennett
- Joined
- Roles
- Member
Comments
-
For a webpage item, with data similar to your first example, I get this as bibliography output in the APA style:Doe Inc. (n.d.). Retrieved June 1, 1965, from http://example.com/What type do you have set on the Delaware item? (Edit: sorry, I see you…
-
There is an extra at lines 122 and 124 or so. If those are removed, the style validates. In the test fixture, running with the style (in all three versions -- before and after the "choose" fix, and even with initialize-with="." set on the cs:name …
-
If you can paste your style code to http://gist.github.com/, save it as a "public gist", and post the URL from the address bar back here, I'll take a look. It's probably a small thing.
-
I've built a processor test for this, and as far as I can tell, initialize-with does not implicitly turn on given name disambiguation. With the CSL you've posted above, I get this output:(Doe 1965a; 1965b)
-
Hmm. That's not particularly good, but do I take it that removing the attribute gets things working correctly?
-
It's the hard return after ASTRACT:. Remove the hard return, and the style should validate and function normally.
-
With the preservation of links when items are merged, there's not much difference between catching duplicates during translation and catching them later.
-
I thought of that, but the cs:citation block above doesn't appear to invoke given name disambiguation.
-
As far as I can tell, that should produce the result you want. (The initialize-with attribute is unnecessary, but it shouldn't do any harm.)
-
The updates are signed, and auto-update should work.
-
notice that as soon as I posted it. I was effectively creating a second cs:name definition which was blank and superceding the proper one right?Yep. It was not valid CSL, but the processor did its best with it. you wouldnt happen to know how to trun…
-
Many thanks for reporting this. I've applied a fix, and pushed a fresh version of the processor (1.0.197). The multilingual build has been reissed with the new processor version, so if you update, the problem should go away.
-
The problem is [well, was :)] in the tag, three lines up from the bottom in the macro. If you remove that, things should work a bit better.
-
I've opted to treat strings containing numbers as mixed-case. This will preserve all all-caps words as all-caps where a number occurs, which covers the sample case. If we see more exceptions, there may be a case for quoted-escaping, but for now let'…
-
The last time we hit this, I think I said I was unable to reproduce, we were unsure whether there might be a problem with your system, and it faded from the radar. It looks like my test was flawed. I've been able to reproduce it this time, and I fo…
-
@poirmw, There is definitely a syntax error in your edited version of the style, and it will definitely be simple to fix. Please paste a copy of the edited style (the version that produces the error) to http://gist.github.com/, save it as a "publi…
-
Great to hear! Glad it's working for you.
-
While it's not an official guide, the Purdue OWL has clear examples that include the comma when the ampersand is preceded by more than one name. The stray "D. " in "D. Borsboom" is almost certainly due to another cite with Borsboom as the first aut…
-
The form in which it appears in the document is the output string: that's everything we need. This case (no pun intended -- really) is skirting close to the point of diminishing returns in smartening up the conversion. I think we have three choices…
-
According to this test, this should already be working correctly -- see the samples in the RESULT block. @gingerbrioche: If you're getting an unexpected result, could you post the input string that produces it?
-
So the idea would be that:A Semiotic Analysis of Mr Blobbyshould become:A semiotic analysis of Mr Blobby But:Showdown at the WTO panel hearingshould become:Showdown at the WTO Panel Hearing That is, things that are in all-caps should just stay in al…
-
Have checked in the fix, in citeproc-js release 1.0.195.
-
This combination fell through the cracks, and was missing from the test suite. Thanks for the heads-up, will be fixed soon.
-
(It looks like the 1.0.192 processor hasn't been added to the trunk yet, but it should go in reasonably soon.)
-
You would craft a CSL style that includes abstracts, and use it to produce your annotated bibliographies when needed. When producing documents that don't need the abstract information, you would just use another style.
-
Yes, you can do this. Zotero items have an Abstract field, the content of which is passed to the CSL processor (the tool that generates formatted bibliographies) in the CSL "abstract" variable. Information on editing citation styles is available her…
-
Glad to hear it works! I'll look into hooking up the missing links in the add-ons manager, and straightening out the help text. The anchor mode locks onto the current history list. Ordinarily, clicking on a collection in the left panel will open th…
-
Okay, I think I have the full picture now. There is an API command to the document plugins, "setBibliographyStyle()", which initializes the values of the "Bibliography-1" style (in LibreOffice, maybe the style name is slightly different in other wor…
-
I've at least taken a look at styles in the RTF output in a document with a generated bibliography. I see a style declaration in the RTF for "Bibliography 1", which seems to correspond to the "Bibliography-1" style shown in the word processor (Libre…
-
From tinkering around with the sample files and saving things as RTF, I think I've figured out a simple markup strategy for this. It just needs a block-indent tab and first-line reverse-tab on the date + cite blocks, which looks simple enough to sti…
Upgrade Storage