I’ve started checking out the biblatex-chicago examples 
(http://mirrors.ctan.org/macros/latex/contrib/biblatex-contrib/biblatex-chicago/doc/examples/dates-test.bib; 
there's also a notes-test.bib I will have a look at later). A few things I 
noticed here are the following:

- "~" is used in author and editor fields, e.g., "Author = {Author, 
Margaret~M.}," or "Editor = {Ross, W.~D.},"

I don't think there's a reason not to treat these as spaces, and to output

  author:
    given:
    - Margaret
    - M.

instead of 

  author:
    given:
    - ! "Margaret\_M."

- "\ " is used in various fields, e.g., "Publisher = {Oxford Univ.\ Press 
and Sandpiper Books},"

In latex, the "\ " does *not* stand for a no-break space, but indicates 
that a single space is to be used, e.g., after an abbreviation dot. If 
vanilla latex sees just ". ", it assumes it's the end of a sentence and 
outputs two spaces. Since pandoc (quite sensibly, see CMoS) does not add 
extra space after sentences, there is, again, no reason not to treat latex 
"\ " like a normal space char. Or use the "punctuation space" char, U+2008. 
(Also, to follow CMoS recommendations, "\frenchspacing" could be added to 
the preamble of default.latex to suppress printing two spaces after a 
period.)

BTW, I realize that "\_" in yaml does work, at least pandoc output seems 
correct, but I find the notation of "\_" for protected space in yaml mildly 
irritating. If it's treated like a normal space by pandoc anyway, as it 
seems to be, why not use a normal space in yaml, too? And if "\_" is 
intended to represent a genuine no-break space, is this the only 
alternative? I for one would prefer using Unicode wherever possible, in 
this case a no-break space, U+00A0, would do nicely.

- Interestingly, while the biblatex date field is restricted to (variations 
of) yyyy-mm-dd, the year field can contain pretty much anything, and 
biblatex-chicago uses this option, so it would be good if pandoc-citeproc 
could map everything it finds in a year field that is not a number, after 
expanding it as necessary, to yaml as a literal string to "issued:  other:" 

biblatex-chicago examples include:

    Year = {1860s}
    Year = {\mkbibbrackets{1957?}}
    Year = {[1920?]}
    Year = {\bibstring{nodate}}}

These could be mapped to CSL "issued" as follows:

  issued:
    other: 1860s

  issued:
    other: [1957?]

  issued:
    other: [1920?]

  issued:
    other: no date

The following is a special case:

    Year = {\autocap{f}orthcoming}
    Year = {forthcoming}

should be mapped to CSL "status" (!):

   status: forthcoming

(\autocap{} can be disregarded; CSL can do its own capitalization here, if 
needed.)

The biblatex-chicago examples also include things such as "year = 
{1951--63}," and "{1951\---63},", but I would regard these as malformed 
(should be "date = {1951/1963}" etc.).


The biblatex-chicago example databases also include a number of 
\bibstring{} commands, and it would be nice if pandoc-citeproc could expand 
these. I have added the  English equivalents (usually the short ones from 
/usr/local/texlive/2013/texmf-dist/tex/latex/biblatex/lbx/english.lbx; 
pseudonym and revisededition from 
/usr/local/texlive/2013/texmf-dist/tex/latex/biblatex-chicago/cms-american.lbx):

\bibstring{and}             -> and
\bibstring{by}              -> by
\bibstring{edition}         -> ed.
\bibstring{introduction}    -> intro.
\bibstring{jourser}         -> ser.
\bibstring{newseries}       -> new ser.
\bibstring{nodate}          -> no date
\bibstring{number}          -> no.
\bibstring{pseudonym}       -> pseud.
\bibstring{reviewof}        -> review of
\bibstring{revisededition}  -> rev. ed.

I’d suggest using the long form of "no date" since this is a CSL "term" and 
can be processed (e.g., shortened) by CSL only if it appears exactly in 
this form.

There's also one command in the example databases that could be translated:

\partedit                   -> ed. by

(defined in 
/usr/local/texlive/2013/texmf-dist/tex/latex/biblatex-chicago/chicago-authordate.cbx)

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/551cc4f2-546c-4386-8d61-e8ea8d3220fc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.