|
ok then, as a slightly more technical question, would regular expressions + a find replace type statement be about the extent of scripting needs inside a program such as this?
I have been going around in circles about the idea of exposing an object model of the document, and the problem is... as markup changes, the object model can be DRAMATICALLY changed, rapidly... leading to large levels of computing power being needed to update the model after a change. Some of this can be avoided by proper modeling / engineering... some of it can't. Because of this, we have been tempted to only build a stream in/out type interface for outside scripting during editing, leaving the robust stuff for input and output builds.
I find it reassuring to see such a small list of markup types as the core needs of the project. I know that in my editing all I user are those core 8-10 things.
also, since the epub format all ready supports a container to keep everything packaged together, would people like to see it keep your export preferences inside a specially marked e-pub file? Or the more pointed question... do you want to distribute a formated file with your convention preferences intact?
|