The AsciiDoc processor converts the source to DocBook, then uses the DocBook XSL templates to convert to the manpage format.
Therefore, you need to hack the DocBook XSL templates (as if your weekend wasn't long enough ;)) Here's the file where you can see the lists converted to the manpage format. http://docbook.sourceforge.net/release/xsl/current/manpages/lists.xsl You are specifically interested in this template: <xsl:template match="itemizedlist/listitem"> ... </xsl:template> And in particular, the .sp text (short for spacer, I presume) that is added before the list item. You can customize the template, then add it to the %ASCIIDOC%/docbook-xsl/manpage.xsl file. Good luck! -Dan On Sun, Jun 16, 2013 at 8:51 PM, Matthew Spah <[email protected]> wrote: > Hey guys, > > I'm curreI'm currently part of a project that is ntly part of a project > that is writing manpages for the Xen Cloud Platform project. We have been > using the manpage format provided by Asciidoc to write our manpages. For > the most part they look great! > > I'm looking for some input from you guys on a few things... > > Here are a couple of pages that have been rendered: > http://i.imgur.com/UnTZU0X.jpg > http://i.imgur.com/LmSclHI.jpg > > Not to bad eh? > > Is there anyway I can get rid of the new line that is present before the > bullet items? > > The source code can be viewed here for these two pages: > > https://github.com/Xenapi-Admin-Project/xe-manpages/blob/master/docs/source/asciidoc/RELEASE/xe-network-param-list.ad > > https://github.com/Xenapi-Admin-Project/xe-manpages/blob/master/docs/source/asciidoc/RELEASE/xe-pif-param-get.ad > > To display the *management* parameter for a PIF: > > - *xe pif-param-get* uuid=<PIF UUID> param-name="management" > > > We use to do our examples just like we do our parameter descriptions, for > example > > To display the *management* parameter for a PIF: > > - *xe pif-param-get* uuid=<PIF UUID> param-name="management" > > > would look like > > To display the *management* parameter for a PIF: :: > *xe pif-param-get* uuid=<PIF UUID> param-name="management" > > This worked great until we had examples that would require two commands.. > like.. > > To enable changes to the *other-config* field: > > - *xe pif-unplug* uuid=<PIF UUID> > - *xe pif-plug* uuid=<PIF UUID> > > We obviously couldn't go.. > > To enable changes to the *other-config* field: :: > *xe pif-unplug* uuid=<PIF UUID> > *xe pif-plug* uuid=<PIF UUID> > > What do you guys think we should do? Sorry if I'm not that clear.. its been a > long weekend > > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Dan Allen | http://google.com/profiles/dan.j.allen -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/groups/opt_out.
