On 2009-04-23, Jean-Marc Lasgouttes wrote: > Guenter Milde <mi...@users.berlios.de> writes: >> Sorry, I choose the first (and wrong) auto-completion.
>> (What is an OutputTye, by the way?) > It used to tell what output routine we should invoke for export (mainly > latex or docbook). Now it can take 3 different values: > /// The different output types > enum OutputType { > /// > LATEX = 1, > /// > DOCBOOK, > /// > LITERATE > }; > I am not sure that the inclusion of LITERATE as an output type was a > good move, but it is probably enough for now. It means "latex plus some > literate programming tool". I suppose the use of LITERATE will be superseded by the new, open, layout/module-settable OutputFormat parameter. Do you plan to obsolete OutputType completely or should it remain to signify LATEX vs. DOCBOOK based output, so that we have e.g. OutputType OutputFormat LATEX noweb Literate programming with noweb: write a LaTeX file with specials that are converted to "true" LaTeX with the noweb->latex converter. LATEX lilybook Musiktheorie with lilybook: write a LaTeX file with lilypond specials that are converted to "true" LaTeX with the lilybook->latex converter. DOCBOOK foobar write a docbook file with foobar specials that are converted to docbook with the foobar->docbook converter Günter