Following up on my original post, I have tried to follow Bastien Dumont's advice to get book titles in title case (i.e. 'add title-case="title" in the relevant places') , however I am having no luck and running into what seems to me to be a curious issue.
> -----Ursprüngliche Nachricht-----
> Von: pandoc-...@googlegroups.com <pandoc-
> dis...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von Bastien DUMONT
> Gesendet: Freitag, 20. Mai 2022 15:43
> An: pandoc-...@googlegroups.com
> Betreff: Re: Divergent styling when using CSL in pandoc(?)
>
> [...] On the other hand,
> the specification does not define the expected behaviour for all cases. The
> issue documented by your first screenshot is a good example of that. The
> "title" macro is called on l. 332 with the attribute text-case="title", but the
> <text> element on l. 117 included in this macro has text-case="lowercase":
> which one should have the precedence? Unless I have missed something, the
> CSL specification does not define that, so Pandoc applies the attribute value
> set on the upper-most element and citeproc-js that of the inner-most
> element. Neither is wrong, so the only solution is to avoid such conflicts in
> your stylesheet (e.g. by removing the attribute on l. 332).
Good catch. I'll open an issue on the CSL schema repo. But concerning precedence have a look at https://docs.citationstyles.org/en/stable/specification.html#inheritable-name-options where you'll find:
> When an inheritable name attribute is set on cs:style, cs:citation or cs:bibliography, its value is used for all cs:names elements within the scope of the element carrying the attribute. If an attribute is set on multiple hierarchical levels, the value set at the lowest level is used.
That's about inheritable name attributes, sure. But I'd infer from that that there seems to be a preference for settings at lower levels.
Maybe we should prohibit the use of styles and text-casing with macros as these run somewhat against the purpose of macros...
Denis