Yes, you're definitely right. I did automatize the process of retrieving the entities from the webpages but I parsed it from the .html files actually. :-) And I use bash, wget and perl for it, which I find much more comfortable in this case than pure perl.

I surrounded the things in subs so it won't get evaluated if someone is only interested in one set and not in others. I should definitely cache the functions' return values. And are you sure it's better to add the semicolons by a map? I didn't really benchmark it, but I think this should be a bit faster and the code is simpler and more transparent, if twice as big. Dunno... it seems to me this is the better way but I am certainly open to counterarguments.

Update: Looking at the .ent files, I see now that half of my effort was needless. :-) Oh well...

---

---

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.