Hello, "Bruce D'Arcus" <bdar...@gmail.com> writes:
> On Wed, May 26, 2021 at 4:39 PM Nicolas Goaziou <m...@nicolasgoaziou.fr> > wrote: > >> The processor uses the "en-US" CSL locale file shipped with Org for rendering >> localized dates and terms in the references, independently of the language >> settings of the Org document. Additional CSL locales can be made available >> by setting `org-cite-csl-locales-dir' to a directory containing the locale >> files in question (see <https://github.com/citation-style-language/locales> >> for such files). The directory must contain at least the "en-US" CSL locale. > > So if I setup a separate directory for different locales files, I also > have to include the default locale that's already shipped with org? > > That seems a bit odd. Yes, it seems so. I think I fixed it. You may want to update. > Related, could we also have a `org-cite-csl-styles-dir' defcustom, to > avoid having to specify the full path? Good idea. Also implemented. > > And/or alternately just `org-cite-csl-dir' for both locales and > styles? I'd rather keep the two directories separate. > Also, is it possible for me to set things up so that export to latex > runs through the oc-biblatex processor, but otherwise it uses oc-csl, > where I have (obviously) different styles for each? It is not possible to set export processor per export back-end, but you can set your more common processor in `org-cite-export-processor' and use a different "cite_proc" keyword when you need it (and comment it when you don't). Is that tolerable? Regards, -- Nicolas Goaziou
