|
From: Garth K. <ga...@de...> - 2002-08-20 21:21:44
|
> I didn't mention that the "raw" directive's main function is:: > > .. raw:: html > > <p>Arbitrary raw HTML here, will be inserted as-is > into HTML output.</p> Oh, okay. Whups. So, does raw also work for raw XML to insert into XML output, raw PDF to insert into PDF output, raw PostScript to insert into PostScript output, and so on, or are we assuming that it's only really HTML output that matters? Getting back to the implicit ``text/``, do the MIME content types for all of the suspect reST output types all begin with ``text/``? > Normally, the "raw" directive's content will be supplied > within the document body. So the question becomes, does the > "raw" directive grow an "include" attribute (or optional > argument), or does the "include" directive grow a "raw" > attribute? I'm not sure that "both" is a good answer here. Aah, so that's the distinction. My apologies; I've been tuned out for a little while, and was too lazy to read back on this thread. Oops. I'd say that raw should have a ``:source:`` attribute. To me, ``include::`` would be used to pull in reST content from another document. > > Now, anyone want to explain why it's ``html`` and not a full MIME > > type? :) > > The "text/" part is implicit? ;-) That's enough for me. > But seriously, MIME types > *have* been adopted for reStructuredText-format PEPs Cool! Regards, Garth. |