docbook: markup for debian package names
Subject:
Re: markup for debian package names
From:
Tabatha Marshall ####@####.####
Date:
17 Jun 2003 02:20:07 -0000
Message-Id: <1055816597.8007.21.camel@mysticchild>
Hi Emma,
That's a tough call. An "application" is the name of a program, but if
you can type in the name of the program and run it, it's a "command."
However, since everything in Linux is a file, it's also a "filename!"
Consider this. If you use <application> it will not change the font of
the text at all, but could be useful in indexing for instances of the
name in the tags. If you use <command>, it will bold the text and use a
slightly different font, if you want the text to appear that way. The
<filename> also changes the text font, but doesn't bold it.
Mind that these are based on the stylesheet being used. IMO it's a
judgment call you'll need to make depending on what suits your own style
(what you think you can remember to use consistently).
Maybe someone else's input can help if this answer wasn't enough!
Tab
On Mon, 2003-06-16 at 14:10, Emma Jane Hogbin wrote:
> Is there a standard on what to use for a debian package name? It's not
> really software so I don't want to use "application", it's a package...
> nor is it a "command".
>
> For those interested, here's the context:
>
> <itemizedlist>
> <listitem>2.4.20 kernel</listitem>
> <listitem>ACPI patch that exactly matches the kernel
> version</listitem>
> <listitem>debian packages: make, bzip2, gcc, libc6-dev, tk8.3,
> libncurses5-dev, kernel-package</listitem>
> <listitem>after you've patched the kernel add the debian packages:
> acpid,
> acpi (Debian testing and unstable only)</listitem>
> </itemizedlist>
>
> Thoughts on what I should be using? I didn't have any HTML markup for them
> in this section. Later I use the generic <var> when referring to them.
>
> emma
--
Tabatha Marshall
Web: www.merlinmonroe.com
Linux Documentation Project Review Coordinator (http://www.tldp.org)
Linux Counter Area Manager US:wa (http://counter.li.org)
