The issue here is a serious one for TeX/LaTeX. The originator of tex4ht died suddenly. The macro system is, according to Karl Berry (who is a very savvy TeX/LaTeX person), one of the most complex he has ever examined. He is, as an outsider, trying to maintain it, amidst the usual issues - upgrades of other packages, etc.
In LaTeX, there are many packages that have not been touched in 5-6 years. Many are quite antiquated. I myself wrote a class (newlfm) which is used to compose letters, faxes, and memos. I haven't looked at it in some time, since no one writes letters. But, as a general issue, who will maintain these packages over time, as developers lose interest or die? ________________________________________ From: Andrew Goldstone [[email protected]] Sent: Wednesday, October 05, 2011 11:03 AM To: Thompson,Paul Cc: [email protected] Subject: Re: [tex4ht] Again biblatex Sounds about right, Paul... my modified biblatex.4ht has \let\abx@aux@page\@gobbletwo \let\abx@aux@fnpage\@gobbletwo % this is the added kludge line \AtEndDocument{% \def\abx@aux@page#1#2{\blx@addpagesum{#1}{#2}}% \def\abx@aux@fnpage#1#2{\blx@addpagesum{#1}{#2}}} % I'd need to spend more time with the sources before I could understand just what these macros are doing. With this kludge I'm still getting some odd behavior with tex4ht converting my longer documents into ODT. I'm trying to track it down. Would very much appreciate thoughts (or patches) from you or others who understand the code. Andrew On Wed, Oct 05, 2011 at 02:46:18AM +0000, Thompson,Paul wrote: > Googling, I find: > > \def\abx@aux@fnpage#1#2{\blx@addpagesum{#1}{#2}} > > This also rings a faint bell, but I cannot find other comments about it. I > think that it is an asynchronous update. > > > ________________________________________ > From: [email protected] [[email protected]] on behalf of Andrew > Goldstone [[email protected]] > Sent: Tuesday, October 04, 2011 1:14 PM > To: [email protected] > Subject: Re: [tex4ht] Again biblatex > > Today I hit the same error with biblatex and tex4ht described in this thread: > footnote citation styles produce a "Missing \begin{document}" error in the > tex4ht run. Just in case it's some help to the maintainers as they debug, may > I mention a kludge which seems to help? > > Noticing that the error had to do with the biblatex package variable > \abx@aux@fnpage, I checked to see how biblatex.4ht treats this variable. > Answer: not quite analogously to how it treats \abx@aux@page. So I tried > simply adding the line > > \let\abx@aux@fnpage\@gobbletwo > > right after biblatex.4ht, l. 170 (this is in the biblatex.4ht in the trunk of > the svn repository). Cf. biblatex.sty as well for the handling of this > variable. > > Now I can htlatex a test file, with footnote cites, and not get errors during > the tex4ht run. The resulting HTML looks correct. Obviously I haven't tested > this much, and I do not understand the underlying biblatex or tex4ht code. > But maybe this idea will help zero in on the problem. > > Now really I don't want to produce HTML but ODT. oolatex also runs without > errors, and produces correct-looking footnotes. But there is a separate bug > in oolatex's code for handling the list of references (\printbibliography), > which comes out blank. I have some ideas about that, but that's for another > thread. > > Best, > Andrew Goldstone > > ----------------------------------------------------------------------- > Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > privileged and confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply e-mail and destroy > all copies of the original message. > ----------------------------------------------------------------------- Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain privileged and confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
