On Tue, Dec 03, 2002 at 09:06:18AM -0800, Jonathan Walther wrote:
On Tue, Dec 03, 2002 at 06:01:23PM +0100, Erik Moeller
Tomasz' texvc generates the images in a
directory and re-uses them on
demand (the TeX strings are hashed and stored in a table). I doubt it
would be a performance hit at all, but if it would,
texvc->latex->dvips->convert could easily be executed on a remote
Well, that is fine, but I'd prefer having the TeX text and resulting
images in the database. Makes internal coding a lot easier. We have
namespaces; there is no reason not to use them. Having it in-database
lets us check for orphaned equations trivially.
There is no reason to have the image in the DB. All you need is the
meta-information to do what you want to do. And that's what's already
going to be put into the DB. You can check for orphaned images without
having the actual image in the database.