closes#1709: [patch] citeproc-js 1.0.51 compatibility patch: makeBibliography() return value
closes#1712: [patch] citeproc-js 1.0.52 compatibility patch
From Frank's notes for 1.0.52:
In this release, the following change may require accomodation
within the calling application:
The processor quashes double spaces in the output.
RTF control words can be terminated with a space, but
this causes an immediately following space to be lost
from the output. To avoid this, the RTF output mode of
the processor has been adjusted to terminate RTF control
words with {} rather than space. Applications that convert
processor output between other formats (such as HTML)
may need to be adjusted to accomodate this new behavior.
Also in this release:
Reverse the RTF-related conservatism in the quashing
of duplicate spaces that was introduced in 1.0.51.
Add missing parens to suspect test condition (not
related to any known bug).
From Frank's notes for 1.0.51:
The API return value changes slightly with this version:
For styles that have no bibliography element, the command
makeBibliography() now returns false, rather than a
stub bibliography object. Code adjustments in the
calling application may be required to accommodate
this change in behavior.
In other bibliography and citation returns, the processor
now provides new arrays, bibliography_errors and
citation_errors respectively, with information on
bibliography entries or cites that produce no meaningful
rendered output. Details are in the processor manual:
http://gsl-nagoya-u.net/http/pub/citeproc-doc.html#handling-items-with-no-rendered-form
Also in this release:
Fix string breakage affecting text-case="title".
Fix over-aggressive quashing of spaces, which affected
spacing following RTF entities.
- Adding reference book support to CrossRef
per http://forums.zotero.org/discussion/12942
- Changing authorship of NZ Herald to match usual standard.
- Adding support for patent issue dates in RIS import and export
discussed somewhere; patch has been laying about for some time
this currently leaks a hidden browser object, since deleting it seems to cause the print command to fail. this may not be a big issue, since this feature is used so rarely anyways...
