Justin Ruggles <[email protected]> writes: > On 03/24/2011 06:42 PM, Måns Rullgård wrote: > >> Justin Ruggles <[email protected]> writes: >> >>> --- >>> doc/texi2pod.pl | 6 ++++-- >>> 1 files changed, 4 insertions(+), 2 deletions(-) >>> >>> >>> diff --git a/doc/texi2pod.pl b/doc/texi2pod.pl >>> index aa3273e..84c36ff 100755 >>> --- a/doc/texi2pod.pl >>> +++ b/doc/texi2pod.pl >>> @@ -231,10 +231,12 @@ while(<$inf>) { >>> >>> # Single line command handlers. >>> >>> - /^\@(?:section|unnumbered|unnumberedsec|center)\s+(.+)$/ >>> + /^\@(?:section|unnumbered|unnumberedsec|center|heading)\s+(.+)$/ >>> and $_ = "\n=head2 $1\n"; >>> - /^\@subsection\s+(.+)$/ >>> + /^\@(?:subsection|subheading)\s+(.+)$/ >>> and $_ = "\n=head3 $1\n"; >>> + /^\@(?:subsubsection|subsubheading)\s+(.+)$/ >>> + and $_ = "\n=head4 $1\n"; >>> >>> # Block command handlers: >>> /^\@itemize\s*(\@[a-z]+|\*|-)?/ and do { >> >> Patch looks OK as such, but why? > > Headings are so we can separate per-codec options into logical sections > with headers without creating way too many numbered levels in the table > of contents. It just looks nicer that way. subsubsection is for when > we actually do want to go another level deeper with numbered sections. > > I'm working on the per-codec AC3 encoder options, and separating them > into logical sections without too much heirarchical nonsense is nice.
Very well then, push it. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
