Re: [xbiblio-devel] Title-case questions

I agree: neither parentheses (nor [] or {}, for that matter), nor quotes (plain or curly, single or double), nor HTML-like markup should disable conversion to title case. On 15 November 2015 at 06:04, Frank Bennett wrote: > Sounds good. That was my question on that one. >

Re: [xbiblio-devel] Title-case questions

I do think italics and small-caps (and possibly superscript/subscript too) markup should disable title casing. Example: L-Malic acid formation by immobilized Saccharomyces cerevisiae amplified for fumarase http://dx.doi.org/10.1016/0141-0229(91)90122-Q "L-Malic acid" starts with an all-caps

Re: [xbiblio-devel] Title-case questions

Yes, definitely. Since there is no mechanism to explicitly force uppercase, the titlecaser needs to be inclusive by default, and we must be able to selectively suppress capitalisation where it is incorrect. `` markup, e.g., `The Arabidopsis lyrata genome sequence and the basis of rapid genome

Re: [xbiblio-devel] Title-case questions

Thanks Frank! >("explicit is better than implicit"). was exactly my thinking wrt casing and rich text, so very much agree with you on that. On Sun, Nov 15, 2015 at 4:22 PM, Frank Bennett wrote: > Thanks to all for the feedback. > > Disabling of no-case in quoted text is

Re: [xbiblio-devel] Title-case questions

Thanks to all for the feedback. Disabling of no-case in quoted text is now available for testing in the latest citeproc-js release, and in the Propachi plugins for Zotero: https://bitbucket.org/fbennett/citeproc-js/src https://juris-m.github.io/downloads/#csl-stuff The i, b, sc, sub,

Re: [xbiblio-devel] Title-case questions

That's getting rather tricky and we're hitting the limits of what simple rich text markup can do: For species, Rintze is correct: - Lowercase the second part of a species name, such as *fulvescens* in *Acipenser fulvescens*, even if it is the last word in a title or subtitle. but that's not the

Re: [xbiblio-devel] Title-case questions

sorry for chiming in late, the original e-mail had actually gotten caught in Spam. I agree with bwiernik -- while the two other issue you raise are right, quotation marks shouldn't disable casing. See e.g. Bruccoli, Matthew J., ed. *“An Artist Is His Own Fault”: John O’Hara on Writers and

Re: [xbiblio-devel] Title-case questions

Sorry, I wasn't very clear. I included the citation just to give an example set of data for which the quote rule would not always work--didn't mean to illustrate a specific format. The title is stored in the reference manager as: “General intelligence,” objectively determined and measured

Re: [xbiblio-devel] Title-case questions

I don't think the literal tags for words in quotes are correct. For example, this reference: Spearman, C. (1904). “General intelligence,” objectively determined and measured. The American Journal of Psychology, 15(2), 201–292. http://doi.org/10.2307/1412107 "General intelligence," should

Re: [xbiblio-devel] Title-case questions

On Sun, Nov 15, 2015 at 1:37 PM, bwiernik wrote: > I don't think the literal tags for words in quotes are correct. For example, > this reference: > > Spearman, C. (1904). “General intelligence,” objectively determined and > measured. The American Journal of Psychology, 15(2),

Re: [xbiblio-devel] Title-case questions

Sounds good. That was my question on that one. On Nov 15, 2015 14:38, "Sebastian Karcher" wrote: > sorry for chiming in late, the original e-mail had actually gotten caught > in Spam. I agree with bwiernik -- while the two other issue you raise are > right, quotation

[xbiblio-devel] Title-case questions

Nick Bart caught a flaw in the citeproc-js title-casing method, and Emiliano Heyns has done a bunch of additional testing. I've rewritten part of the code for it, mostly to get nested tags to work correctly. None of the changes impact existing tests, but a few things came up that I thought I