-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Burke <[EMAIL PROTECTED]> writes:
> As I recall, Publish tries to fit the table into the page width. If the > width is not enough, the font size is reduced to fit, but stopping at > 50% of the font. Chris, That seems reasonable, especially if there were an easy style setting to fix the font, if that was desired. Just by looking at my output, though, one table with only three lines appears to have a slightly larger text than the neighboring paragraph -- not objectionably large, but it does look a slight bit funny. > Otherwise, the rows of a table will be split over pages if necessary. That doesn't seem to work in my case. Instead of splitting, J runs at over 90% of the CPU for a couple of minutes on this three or four page report, and then I stop it. It might run to completion, but that seemed unlikely, as normal processing times seemed more like small numbers of seconds. > You could try fixing your own code, or enhancing Publish - the source is > readily available. Yes, but time is my problem, and this isn't currently a big deal. I cheated and used limit__db to force the tables to a fixed maximum length. As I know it will currently only split into two tables, I hard-coded that. One of these days, I'll consider making it general (split into n tables based on the data). Thanks, Bill - -- Bill Harris http://facilitatedsystems.com/weblog/ Facilitated Systems Everett, WA 98208 USA http://facilitatedsystems.com/ phone: +1 425 337-5541 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: For more information, see http://www.gnupg.org iD8DBQFGs2dK3J3HaQTDvd8RAqmSAJ40xvmdHSPZqGjTxAosW2XyDKgLdQCdH4TK xheSfqtmivrp4cGdYtPa6tg= =8aGn -----END PGP SIGNATURE----- ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
