|
From: David G. <go...@us...> - 2002-08-21 04:07:58
|
Garth Kidd wrote: > 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, Yes. > or are we assuming that it's only really HTML output that matters? Never! > Getting back to the implicit ``text/``, do the MIME content > types for all of the suspect reST output types all begin with ``text/``? I don't know about PDF, but I suspect this is a red herring. I don't think we have a big enough set of formats to justify using MIME types. We've already got a set of identifiers that are perfectly suitable: the Writer format names. OTOH, MIME types *are* future-proof. (This was the reasoning behind the PEP decision.) But they feel like over-engineering, a classic case of "don't add functionality before it's needed". I'd rather wait until significant use cases present themselves, if ever. > I'd say that raw should have a ``:source:`` attribute. To me, > ``include::`` would be used to pull in reST content from another > document. Noted. And I tend to agree. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |