Call for HTML exporter wrong-code bugs

With my latest commit (well, with the change that was later blindly
generalized to become my latest commit), guadec-5.zabw now exports
correctly to HTML. By correctly, I mean data is not lost (AFAICT),
there are no garbage tags, and it is perfectly valid HTML (validated and
everything, yes).
Which means I'm running low on wrong-code html bugs again. Lately
sum1's done a fine job of filing them so far, but if you kids have any
wrong-code or abort (or other, as always) html export bugs, as a coder
I'd ask that you please not hesitate to file them. While naturally I
enjoy squishing all kinds of bugs (as evidenced by the scores of smashed
flies drying on the mirrors and windows in my current apartment), I'm
particularly interested in regressions since 2.2 and getting them fixed
before 2.4. Not just because they're probably my fault either, I swear.
After that, of course, comes any regression since 2.0 (that I can fix,
anyway) that isn't already filed (tisk tisk).

/* Bayesian-clustered trivia, brought to you by Google AdWords(tm):
As a QA persona I'd chime in that regressions as well as wrong-code bugs
(which are typically dataloss) in any core (not plugin) importer or
exporter are always of serious and urgent importance. These components,
beyond HTML export, include the importers and exporters of RTF, .doc,
ABW, XHTML and so forth because such bugs not only harm interoperability
but are particularly user-visible bugs lacking user-visible causes.
*/

Best regards
-MG
Received on Wed Jun 29 07:34:04 2005