Single Comment

Instead of trying to make one solution fit all rendering methods, I have begun to implement scaling for every rendering method that didn't already have it. The PNG, GIF, and JPG methods already had scaling. These methods resize the image generated for the diagram. For boards rendered as tables, it changes the width and height values for table cells and piece images. This is all done in HTML without affecting the graphics used to display the pieces, allowing them to be cached and reused. For boards rendered with CSS, CSS is used to resize the board, and adjusted width and height values in the IMG tag are used to resize the pieces. I tried a purer CSS solution at first, but it had glitches. Like scaling with tables, this does all the rescaling by changing the HTML, not by making new graphic images. As was originally intended with CSS rendering, this allows the same graphics to be cached and reused. Finally, ASCII rendered boards are rescaled by adjusting the point size. Since this is done with CSS, I don't know if it will work with Lynx.

I have not yet implemented scaling for every board shape, and I have not yet made use of the rescaling for optimizing the board display in mobile devices. I'll do this in due time.