In principal it won't be such a big deal to write such a parser. But the problems will appear in the details. One has to create a kind of meta syntax - processing statements - for all these R chunks. E.g. @RCODE quiet@ a <- matrix(c(1,2,3,4,5,6), nrow=2 byrow=T) @/RCODE@ foo foo @RCODE insertAsTable noCommandLine@ print(a*2) @/RCODE@ etc. But this would be mean to reinvent the wheel twice in some sense. Markdown to LaText and Sweave for LaTeX works fine. On the other hand I use quite often the R bundle command 'Execute Selection/Document in R and' > 'Insert Result' for such things. Of course, to have such a pre-parser for expanding R code chunks and insert the result depending on the current language (HTML, LaTeX, Markdown, Plain Text) would be nice. --Hans

On Apr 29, 2008, at 9:59 AM, baptiste auguie wrote: It certainly is possible to use Sweave with something other than LaTeX, but someone would have to write the driver. On the other hand, writing in Markdown with <<...>> .... @ blocks for the R and figure code should work just fine, you then just: 1) Run the file through MultiMarkdownToLaTeX to get a LaTeX file with these blocks still there. The tricky part here is getting MultimarkdownToLaTeX to not touch the <...>...@ blocks, though that should be doable I think. Perhaps someone more familiar with the script can tell us how to do that (I believe it would amount to adding some XSLT transformations?) 2) Pass the resulting LaTeX file through the standard Sweave process, to get a pdf 3) There's no step 3. Of course, if you want something like an HTML output, that's another story, though shouldn't be too bad. Perhaps one can have a look at how the R help files (I believe they have a .Rd format) get converted to HTML help pages. Also it would be nice to have the equivalent of \Sexpr{...}. Probably amounts to just another XSLT transformation. Just some thoughts Haris Skiadas Department of Mathematics and Computer Science Hanover College