on Win64, including the .NET projects.

lesson to you: unit tests are good.

that anything outside the dirty rectangle is guaranteed to be unchanged, but
we currently mark far too many cells as dirty. This must be optimised.

Dirty rectangles are an upcoming optimisation that will tell the output
drivers which portion of the canvas has been really modified since the
last blit.

play with the Windows port, there is a 90-day evaluation version
available for free on the Microsoft website.

frame separator. Not extremely robust yet.

code for clarity.

rely on .la files for library dependencies.

readability of fullwidth characters better by not placing cell
boundaries between them unneccessarily

the output is now labelled as XHTML 1.0 Strict, since it does conform
to that DTD. also removed spurious cellpadding and cellspacing from
<div /> markup. also handle non-characters by conversion to
replacement character, and handle more control characters by
conversion to no-break space. finally, switch from &nbsp; to the
equivalent &#160; so that a non-validating XML parser (which is most
of them) can correctly parse this document.

degenerate cases this will lead to incorrectly-displayed tables. i
don't yet have a solution.

and fill the canvas up to the tab stop with it. once that works,
support will be added here (treating it as space.) also, fewer columns
are now generated. apparently generating a minimal number of them
fixes a bunch of the table-layout bugs.

characters and non-unicode codepoints when generating HTML.

optimize by merging cells

cells on any row of the table then the very first row does not use the
cell-merging optimization; this appears to fix the last of the table
layout bugs seen in truecolor.php; also fix the foreground and
background color bugs seen in truecolor.php.

get hopelessly lost.