Hope everyone had a nice weekend, To recap the status quo on sentence case: Currently, CSL recommendations are to store titles in sentence case and to not use the text-case="sentence" attribute on titles.
Something that had escaped me is that "sentence case" isn't actually uniform in the US. In particular, styles that derive broadly from the APA manual (i.e. a lot of the social sciences & education) capitalize the first letter of the subtitle (i.e. after the colon) as in "Cooked: A natural history of transformation," while styles derived from the NLM's "Citing medicine" don't, as in "Cooked: a natural history of transformation". There is currently no good way to handle this via CSL, though I think it's clear that I should be. I see two possibilities, but there may be more: 1. Format titles and subtitles separately. In that case we could simply add a "capitalize-first" for the subtitle in APA style. This may also be nice as different languages have different title-subtitle delimiters. This is also what BibLaTeX is doing, so it'd work nicely with citeproc-hs. The big downside, of course, is that the demands on data are significant and very few datasource apart from MARC records separate titles and subtitles, so I'm not sure this is going to be feasible. 2. I think this is what I'd prefer, because it's simple&easy: We recommend users store titles in "NLM" style sentence case, which is also what MARC and PubMed have. Then we re-purpose/redefine text-case="sentence" to no longer force lowercase, but instead capitalize the first letter after the colon (and quotation/exclamation mark) and apply that for APA and related styles. The pro here is the ease with which we could make this work. The downsides are a) that I'm not sure that using text-case="sentence" that way makes a lot of intuitive sense (so we could also add a different option) and b) it's probably the less thorough and systematic solution, so it'll only work 98% of the time. Thoughts? -- Sebastian Karcher ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
