You might have noted that biblatex has been updated to version 2.3 and the documentation documentation says:
If an entry in the revision history states that a feature has been improved or extended, this indicates a modification which either does not affect the syntax and behavior of the package or is syntactically backwards compatible (such as the addition of an optional argument to an existing command). Entries stating that a feature has been modified, renamed, or removed demand attention. They indicate a modification which may require changes to existing styles or documents in some, hopefully rare, cases.
This time biblatex does not have any modification or removal requiring changes to TeX4ht packages. The revision history says:
- Better detection of situations which require a Biber or LaTeX re-run
- Extended auxiliary indexing macros
- Added
csfieldandusefield- Added starred variant of
usebibmacro- Added
ifbibmacroundef,iffieldformatundef,iflistformatundefandifnameformatundef- Misc bug fixes
Apparently, nothing seems to affect the functionality of TeX4ht. However, I did a thorough re-run of all the example files provided with the biblatex bundle to see if all files generated HTML output comparable to corresponding PDF output and, indeed, it did. As such, I can confirm that TeX4ht is fully compliant with the newly upgraded version 2.3 of biblatex.
The test suit is available here as a composite tarball.
Thank you so much for your work on TeX4ht, in particular for your efforts in making it compatible with biblatex.
There are a few issues with biblatex-chicago, however, described in http://tex.stackexchange.com/questions/87160/biblatex-chicago-and-mk4ht-oolatex-formatting-errors, and I wonder whether you could help out here, too – either by fixing TeX4ht, or, if a fix would rather be needed on the biblatex-chicago side, by sending the appropriate hints of what to do to the biblatex-chicago author (for name and email see http://www.tug.org/texlive/Contents/live/texmf-dist/doc/latex/biblatex-chicago/biblatex-chicago.pdf).
Thank you very much.
Thanks for the bug report. My preliminary testing confirmed your errors. I think, the errors pertain to TeX4ht. I will fix these as soon as possible, but be warned, I am in the middle of a day job that at times dictates my schedules.
Anna,
A simple change in the
babelpackage option made things easier. All errors disappeared except the missing space between title and next field in report item. Languageamericanis not supported, so I changed to:usepackage[english]{babel}For your confirmation, my test results are available here.
Amazing – this did the trick, except for the missing space between title and next field in @report entries. – Thank you so much!