OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: DOCBOOK: structured funcsynopsis formatting

I would like it if the following:

    <funcdef>void <function>gimp_pixel_rgn_init</function></funcdef>
    <paramdef>GPixelRgn* <parameter>pr</parameter></paramdef>
    <paramdef>GDrawable* <parameter>drawable</parameter></paramdef>
    <paramdef>int <parameter>x</parameter></paramdef>

were formatted more like this:

void gimp_pixel_rgn_init(GPixelRgn* pr,
                         GDrawable* drawable,
                         int        x);
than this:

void gimp_pixel_rgn_init (GPixelRgn* pr, GDrawable* drawable, int x);

As when a function has enough arguments that they wrap around more than
one line in the output, readability drops considerably.  Any pointers on
how to achieve this?  Funcsynopsis seems to ignore line breaks and
indentation even when used in a linespecific programlisting.

Also, I would like to provide syntax highlighting (aka prettyprinting)
in included programlistings.  Anyone have a trick for this?  Lacking any
better ideas, the source can always be marked by hand with <type>,
<varname>, <function>, etc, if the sample is small enough.

But there is one element found in most prettyprinters that DocBook
lacks, though: a source-comment tag, to mark up /* this */ .


  - Kevin

Kevin.Turner@oberlin.edu | OpenPGP encryption welcome here, see X-DSA-Key

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC