Biblatex package has undergone a lot of changes as a consequence of its revision to version 3.0. The back-end namely biber (the modern equivalent of BibTeX program) which is needed to exploit all the features of biblatex has also been upgraded to a newer version with changes in the data structure of resultant bibliographic listing file. Both these revisions have broken the functionality of current version of biblatex.4ht of TeX4ht bundle causing panic among biblatex users, particularly, in the humanities world. This page in github issue tracker of biblatex has a long exchange about the current issues. The noteworthy postings in this page are quoted below:
Archive for the 'TeX4ht' Category
Nasser M. Abbassi had filed a feature request at TeX4ht project for multicolumn support in TeX4ht which is lacking at the moment. This link provides the latest specifications of W3C relating to multicolumn layout in HTML which some of the mainstream browsers support in varying degrees. Our initial efforts are pointed towards multicol package so that TeX4ht provides enough hooks to generate output with multicolumn layout as envisaged in LATEX by multicol package. Support for \twocolumn still remains to be done, though.
Two updates have already been made for biblatex since we tested compatibility problems of TeX4ht with the package last. This time, except for one change of the string, URL, which was hardwired in previous versions, becoming a localization string, all the remaining changes relate to biber, the bib database processor. None of these have any bearing on TeX4ht. However, a thorough run of all example files in the package bundle has been done and could not find any problems in generating HTML output identical to the PDF counterparts.
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.
Mahesh wanted to see the annotated source of the TeX document that generated the output shown here. There are two components in the source: (1) document source, let us call it as test.tex, (2) a custom configuration for TeX4ht, let us call it as my.cfg.
Continue reading ‘An Annotated TeX Source’
Raphaël Pinson has kindly contributed the code that enables TeX4ht to support lettrine package. (lettrine.sty helps to typeset dropped capitals in a LaTeX document.) This probably will solve the long standing problem of drop capital support in TeX4ht, even if all the options of lettrine package are not supported at this time. Hope, Raphaël will continue support to enhance TeX4ht by adding all the missing options of lettrine.
TeX4ht has been updated to cope with the newest incarnation of biblatex ver. 2.2. All its 43 example files provided with documentation have been tested and seem to work fine. Each example file with html output plus all the auxiliary files generated have been archived and provided below for users to check for problems, if any. The revised package of biblatex.4ht is also provided along with recent version of nameref.4ht which some users may not have owing to its recent updation. Older version of nameref.4ht can cause problems when biblatex is run in conjuction with hyperref.
The very powerful LaTeX bibliography processing package namely, biblatex.sty often clashes with TeX4ht. I do not have much knowledge about the innards of biblatex. However, I could fix problems found in biblatex.4ht consequent to two previous revisions. Now one more revision had taken place, as we can expect, TeX4ht fails to work with current version of biblatex (v. 1.7). Therefore, one more revision of biblatex.4ht becomes necessary which has been done now. Since biblatex is widely used by LaTeX users and many biblatex users also deploy TeX4ht for generating HTML versions of their documents, it has now become an absolute necessity to maintain biblatex.4ht in such a way that each revision of the package also triggers a newer releases of biblatex.4ht. Developers of biblatex have notified that we are going to get a major revision (v. 2.0), so we have to work hard to catch up with new releases.
There are four commands which are very useful to write custom configuration for TeX4ht. They are: Continue reading ‘TeX4ht: Low-level Commands’
Recent Comments