Upgrade Storagenickbart
About
- Username
- nickbart
- Joined
- Roles
- Member
Comments
-
you can't have observed this in ZoteroSure – “Extra” field:{:publisher-place: West Virginia University} I do feel fixing this in the style is warranted – even if it’s just for users who know precisely what they are doing with the “Extra” field, or a…
-
Just pinging. Any progress since 2014? Did the xbiblio discussion provide any additional insights? Specifically, are there any reservations about adding(see above) to chicago-author-date.csl and other styles? (pandoc and others that can access data…
-
The BibLaTeX (and Better BibLaTeX) export filters export this to “pagetotal”, which is an official BibLaTeX field. Does that help?
-
I guess you saw the post by Carles Pina on xbiblio. It seems Mendeley is not using the renamed-styles.json file, which would speak against retiring harvard1.csl altogether in the immediate future. On the other hand, he does not seem to see any pro…
-
Pardon me for being insistent, but have you considered that the current way EDTF Level 0 date strings are parsed does not make the least bit of sense – in particular the appearance of the bizarre “season” element?We’re just talking about the pattern…
-
Thank you, that’s fantastic. I'm really looking forward to this.
-
Surprising to hear that it works, given that Zotero 4.0.28.6 still does not seem to be using the simplified parsing (since leading lowercase strings in the family field that are *not* on the list do not seem to be detected). Do we have an ETA for t…
-
For the moment, keep enclosing the last name in double quotes. A new processor version should be out soon that no longer parses any capitalised elements as particles. From then on, the double quotes will no longer be needed.
-
@Rintze: both points, spot on.
-
Whatever this means for the GUI, we cannot get around the fact that we need to be able to protect leading lowercase fixed parts of a family name, aka non-particles. Enclosing these in double quotes has been an adequate solution so far, and I feel st…
-
Lowercase non-particles do not seem to be that rare. CMoS, 16e, 8.5 and 16.71, lists the following: - Walter de la Mare; de la Mare - Paul de Man; de Man - Daphne du Maurier; du Maurier - Robert van Gulik; van Gulik - Wernher von Braun; von Braun …
-
What's more, it turns out that {:issued: 2012-01-22/2012-02-23} in Zotero's "Extra" field is exported as is – and, provided the "Date" field itself is empty, citeproc-js can actually parse and render this date range correctly, including both months …
-
Ok, I'll try again from a somewhat different angle: Zotero does use somewhat hackish solutions at times if necessary, e.g., specifying additional fields in the "Extra" field. I don't really understand why an even less hackish approach can't be tri…
-
Just posted on xbiblio. As to harvard-anglia-ruskin-university.csl and harvard1.csl, shouldn't we turn harvard1.csl into an unmodified dependent style of harvard-anglia-ruskin-university.csl, regardless of the outcome? Both rely on one single “doc…
-
Well, functioning CSL JSON export of either of the two ("DOI: …" and others at the beginning of a line, or "{:DOI: …}" and others anywhere in the Extra field) would do nicely … :-)
-
Most people, it seems, are using the "report" type for working papers, and I’d say this works quite well.
-
Thank you, but my question was not about the Zotero -> citeproc-js -> word processor workflow (which works well), but about Zotero’s export to a CSL JSON file (for which conversion to “proper” fields has been announced but isn’t there yet, exc…
-
Ok, now in 4.0.28.3, PMID works as described, but DOI still doesn’t, and neither does {:DOI:10.1234/567}. Is this getting any closer to being rolled out? Let me add that I continue to feel it’d be much better to move (rather than copy) the fields …
-
Two Four apparent processor bugs (observed with 1.1.19): When there’s a suffix, a preceding (dropping) particle is not parsed at all: [Author] [Ann de, III] is parsed as"family": "Author", "given": "Ann de", "suffix": "III" Parsing is not exhaustive…
-
@NMonteix: - I trust “Della Corte, Matteo” is what you expected? - If you get “Corte, Matteo Della” if the family/given fields contain [Della Corte][Matteo], I would guess you are not using the latest processor version, so try https://github.com/Jur…
-
@aurimas: Not sure what you meant by “Given correct data entry, the dropping particle has no significance for CSL or Zotero, so we can ignore parsing that part altogether.” – In fact, dropping particles need to be parsed just like non-dropping ones:…
-
@Rintze: I’d say all the particles from the Dutch list should be treated as potentially non-dropping – but: the "auf *" (except "auf ter"), "aus *", "unter", "von *" (except "von 't/von t"), "vor *", "zu" ones may just as well be German particles, s…
-
Great. – Just a few things that don't seem to be correct yet: - duplicates: "'t", "ben" and "bin" - "van" should be "either" - since "van" in "Ludwig van Beethoven" is dropping - "de'" should be "either" - since "de'" in "Lorenzo de' Medici" is drop…
-
Zotero is currently loading the citeproc-js module to pre-parse names […]Thank you, that was essential for understanding what’s going on. I see that in the latest “Propachi: monkey-patch for Zotero CSL processor (standard version), 1.1.16” parsing i…
-
@Gracile: “(Please correct me if I'm wrong)” – Not at all, I totally agree. @fbennett: Ok, now I see a little clearer what you meant by “We'll need support for particle adjustments in the Zotero UI before changing the processor.” Looks interesting …
-
@NMonteix: Specifically, the question is, for persons named “D’Annunzio”, “Da Ponte”, or “Della Robbia”, do “Annunzio”, “Ponte”, or “Robbia” ever appear _without_ “D’”, “Da”, or “Della”? If not, “D’”, “Da”, “Della” are not particles in the CSL sens…
-
In fact all of them are always non-dropping particles in Italian.Not quite, in fact none of them are (they are either fixed parts of the family name or dropping particles): CMS, 16e, 8.9 “Italian names”:Particles in Italian names are most often uppe…
-
But the use case flagged by stroom is about data import, not about parsing. A list might help when importing or manually copy-pasting names, but even if stroom, quite rightly, observes, “Using the 333-list would settle that for most _Dutch_ cases” …
-
I’m not sure I understand: Changes in the Zotero UI are, in all likelihood, still a long way off. What we can do _now_ is to improve the algorithms for parsing the existing two-field names. Zotero has begun to parse names itself when exporting CSL…
-
Do you have any specific worries? Re-reading previous discussions on Arabic names on this forum (https://forums.zotero.org/discussion/30974/2/any-idea-why-an-a-author-comes-last-in-the-bibliography/, https://forums.zotero.org/discussion/28457/arabic…