Criticism invited, so here goes.

• I'd write the long text strings as here-docs, or better yet, put them in __DATA__ section at the end.
  Paragraph mode perhaps to cut it up.

  my ($header, $body, $footer) = do { local $/ = ""; <DATA> };
  [download]

• I fail to see the reason to put $find through quotemeta. (And there's also the \Q\E).
• It is advisable to use named constants instead of magic numbers: use constant COLS => 7;
• For loop more concisely written using repetition operator: print $tombolatex $body x (1 + $N / COLS);
• ...
• All in all, it looks like a simple templating job.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.