On 11/03/2012 22:30, Ary Manzana wrote:
<snip>
Give me an example of a macro you'd use in your documentation, that's not:
bold, italic,
underlined, lists, tables, links, named sections, code blocks and images.
<snip>
Emphasis possibly. Inline code snippets. Possibly sample input/output.
But even if you do come up with a list of things that have a genuine use case that you
think is exhaustive, someone'll sooner or later come up with another one that isn't on
your list.
Moreover, macros aren't just to provide access to the features of the target documentation
format. They're also used to enable specific uses of these features to be written in the
source more nicely. For example, I've just found myself setting one up for links to
issues on Bugzilla.
Stewart.
