Markus Fischer wrote: > > Your module is only capable of producing RTF right? Not parsing > it?
Yes, well... depends how you interpret the word 'parsing'. If parsing is interpreted in the programmers-sense, i.e. building a parse-tree of any kind: no. I'm not interested in doing a sort of RTF-viewer/mapper or whatever, unless you can give me a good reason to do so. If the word 'parsing' is interpreted as 'scanning': yes it does a tiny little bit of that. It would be fairly easy to check, interprete and generate /par or /font tags or page properties, things like that. Currently Rtf2Mod does only very limited parsing/interpretation, other than to make sure all rtf-tags are complete, and there are no silly line-breaks (since Office 97, M$Word is fortunatly less critical in that respect) and that the some of the initialisation and exit code is actually put befor/after the RTF (as there is no way to put any text outside RTF-tags in a regular word processor) The idea ofcourse would be to produce RTF like HTML or XML, and PHP doesn't do much interpreting of these mark-up languages either. I can give some more clues to Rtf2Mod: The Modula-2 code is embedded in annotations (comments) to the word-document, so every editor (star-office, word) will suite as a "wysiwyg programming tool". Annotations that start with :M2 are interpreted as Modula-2 program code. There are two special tags: :ModuleBegin and :ModuleEnd, with the obvious meaning. Anything in between square brackets is considered a printable variable. Ofcourse in Modula-2 that *must* be a character string, as it's strongly typed. In PHP things would be a *lot* more flexible. I'd suggest a PHP module/class (preferably module) that would work just like that. Keep the word data 'as is' only expanding [$VarName]-like tags (thus making them visible in the original text) into the variable-content on output, and accept PHP code in annotations only (where regular <?php ?> tags could be used as markers) Care should be taken that RTF has a tendency of ignoring anything it won't recognize, and as such not writing them out on 'document save'. So there's no easy way of creating an customized tag, as there is in HTML. RTF would just throw away any carefully crafted PHP-script just like that, and that's not what we want, right ;-) -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
