I'm building a CMS that does heavy parsing of a "HTML shorthand" plain text to XHTML strict, in a similar way to Textile <http://www.textism.com/tools/textile/>.
The problem is this conversion might take place on 2-3 columns of text, and unlimited other fields (my CMS has user-defined data models),
Could you please provide a short example or an URL of your data model? This would clear things a little bit.
2. [...] I'm going to be storing a LOT of data in the DB.
Why not save both as files? Maybe you find a structure for this, i.e. http://example.org/articles/2004/02/19/text34_v3.html or something like this. You save the "editfiles" and cache the xhtml-output.
3. write a reverse set of functions which converts the XHTML back to the shorthand on demand for editing -- this seems great, but I don't like the idea of maintaining two functions for such a beast.
Only parse one way. I mean only from your format to XHTML. There is no need for converting back (I believe). your people edit the text, after that they open up the browser and hitting refresh. So that's when your parser comes in play. And with caching only once per document.
-- Torsten
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
