nickbart
About
- Username
- nickbart
- Joined
- Roles
- Member
Comments
-
@Gracile: No, you shouldn’t have to use double quotes for “ter” (except as a temporary workaround) – “ter” is clearly a non-dropping-particle (CMOS 16e 8.10, and https://forums.zotero.org/discussion/30974/2/any-idea-why-an-a-author-comes-last-in-the…
-
Thank you, adamsmith & bwiernik, that’s all helpful. As to avoiding APA for “sensible citations”, I couldn’t agree more – the blog indeed calls for using, e.g., > Rieber, R. W., & Carton, A. S. (1987). _The Collected Works of L. S. Vyg…
-
Real-world example, adapted from 7.02, example 21, using a title that does not already contain the author’s name: I maintain such a book section in an _authored_ volume should be rendered as: Freud, S. (1953). The method of interpreting dreams: An…
-
My point is merely: There is an existing, well-known workaround for date ranges, using an underscore to have the date exported as "literal", which then gives users the option to fix it manually (or, when using pandoc-citeproc, automatically). Couldn…
-
Pinging this issue – any reason why dates containing underscores should not uniformly be exported to CSL JSON as "literal" – or, even better, properly parsed? Currently, exporting an entry with a date field "2014-01-03_2014-02-04" to CSL JSON produ…
-
What CSL style file are you using? Try one that has “demote-non-dropping-particle="never"” in line 2, OR try wrapping "Van Sittert" in double quotes, OR wait until case-sensitive parsing (which will stop parsing upper-case elements as particles) is …
-
Would this be another case where parsing based on capitalization would be beneficial?Absolutely.… the suppress-parsing workaround …Strictly speaking, I wouldn’t call it a “workaround” – for parsing two-field names with ambiguous particles, it is an …
-
Dutch names: the list at http://www.vernoeming.nl/alle-333-voorvoegsels-tussenvoegsels-in-nederlandse-achternamen contains upper- and lower-case particles – so can Dutch non-dropping particles be upper-case after all, or are these just the capitalis…
-
While retrieved metadata is often inconsistent when it comes to particle capitalization, making particle-identification case-sensitive might make things behave more understandably for the average user. Even if it requires more curation by the user.I…
-
Second, specifically to address one of the fault reports, I have set up the particle sets "de las" and "de le" with a dropping/non-dropping option, defaulting to all-non-dropping.But wouldn’t this give you “De la Fontaine, Jean” now?
-
@Rintze:This may be a rather ignorant question, but are there any cases where an uppercased family name element is actually a particle? (e.g. we just concluded that "La" in "Jean de La Fontaine" is never demoted, so we don't need to treat it as a pa…
-
@fbennett:Where there are multiple entries, the classification of the particle depends on its location (front of the family field, end of the given field). I don't actually know if that is ever desirable, but that's what it does.That’s highly desira…
-
@fbennett: Thank you, but I’m not sure I understand this well enough yet to start patching your code, so a few more questions instead: Why are there different NDP / DP variants? What do the numbers mean – do these stand for the number of words a p…
-
I tried to figure out what the code next to the various particles could possibly mean. This is what I came up with – is this anywhere near correct? If it is, we could use this, minus the code, as a basis for documentation. ["al-", [[[0,1], null],[n…
-
@fbennett: thank you for the “al-” fixes and all your helpful comments. I continue to think that the CSL schema in its current form is sufficient, at least for European and Arabic names. To recap: Certain names start with non-dropping particles, w…
-
This is a reasonably complete list (a/e + sun letters, in the most common transcriptions): at-, ath-, aṯ-, ad-, adh-, aḏ-, ar-, az-, as-, ash-, aš-, aṣ-, aḍ-, aṭ-, aẓ-, al-, an-, At-, Ath-, Aṯ-, Ad-, Adh-, Aḏ-, Ar-, Az-, As-, Ash-, Aš-, Aṣ-, Aḍ-, …
-
“al-” (and its variants, el-, ad-, as-, an-, at-, az-, etc.) are non-dropping particles, i.e., “al-Hakim” has to appear when used in the text itself, though the “al-” may be dropped for sorting and/or display in the bibliography (see Chicago Manual,…
-
@talk2chun: Have you tried wrapping the family name field content in double quotes, i.e., "Vander Maele"? When I last looked this made citeproc-js parse this as a multipart family name without splitting off any particles, and this – correct me if I’…
-
Will do. However, my current suggestion is merely about a quick fix of the inconsistency in how Zotero parses and exports date fields containing underscores.
-
… I'd personally tend to follow the working paper rather than the government report citation rules in Chicago Manual …I totally agree, and would strongly support patching the various Chicago styles to have them format the Zotero (and CSL) “report” t…
-
Whether or not two-field names should be seen as the preferred format for communication between front-end and processor, and whether or not users should be given complete control over the specification of name components in the various front-ends, a…
-
Great, thanks. The earlier report (https://forums.zotero.org/discussion/97/2/book-reviews-another-item-type/) was about something else though: the "by" in front of the reviewed author rendered as expected by citeproc-js but not by pandoc-citeproc. T…
-
Hmm, doesn’t seem to work here (Firefox 37.0.1, Zotero 4.0.26.4). When I create a new entry with just "PMID: 1234567" in the Extra field and export it to CSL JSON, this is what I get:[ { "id": 13925, "t…
-
How is the the "pretty" solution supposed to work? Upon exporting to CSL JSON, are the variables in the "Extra" field moved to their proper places? I.e.,[ { ... "note": "", "PM…
-
Documentation on the "{:DOI: 10.1234/56789}" syntax: http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#supplementary-fields
-
I'd like to return to this issue since, just like aurimas, I feel the current implementation is markedly problematic:It does not conform to the CSL specs (the CSL method of dealing with name parts is very well designed and should not be given up nee…
-
Just to clarify, my initial concern was just that normal DOIs (such as "10.1002/(SICI)1097-0258(19980815/30)17:15/163.0.CO;2-2") in the DOI field make the "DOI:" label clickable whereas shortDOIs (such as "10/aabbe") don’t. It would be nice if this …
-
Info tab of the right column, by clicking on "DOI:".
-
Didn't get around to testing, nor to posting on xbiblio yet, sorry - but does citeproc-js still implement the "dirty trick" of protecting multi-part last names when they are enclosed in double quotes? (see http://gsl-nagoya-u.net/http/pub/citeproc-d…
-
Well, good luck trying to get the Chicago Manual changed then (see CMoS 16e, 15.29). Actually, this issue that has been discussed before: https://forums.zotero.org/discussion/38027/style-error-chicago-authordate-collapse/. No solution though, as of…