texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [5193] clarify @itemize behavior (no text before first @item), and @


From: Patrice Dumas
Subject: Re: [5193] clarify @itemize behavior (no text before first @item), and @ set allowed in the midst of a line
Date: Sat, 23 Feb 2013 10:24:45 +0100
User-agent: Mutt/1.5.20 (2009-12-10)

On Sat, Feb 23, 2013 at 12:56:16AM +0000, karl wrote:
> ===================================================================
> --- trunk/README-hacking      2013-02-23 00:12:40 UTC (rev 5192)
> +++ trunk/README-hacking      2013-02-23 00:56:16 UTC (rev 5193)
> @@ -152,3 +152,5 @@
>    ... announcements:
>  news item at savannah.
>  send announcement to info-gnu, cc bug-texinfo.
> +
> +  ... update on CPAN.
> 

I was not clear, I believe, the point is not, at least for now, to
update (or release) on CPAN, but rather to make sure that the system of
scripts that allow for building and installing a standalone module
works (which would be a prerequisite for releasing and, later on, 
updating on CPAN).  In fact in Fedora, the idea is already to 
install the modules in the system perl paths (which is something I agree
with, when I put my ghostly fedora packager hat).

> +On the other hand, normal text before the first @code{@@item}
> +(``outside'' of any item) produces a warning, since some output
> +formats (e.g., HTML, Docbook) strictly require all text inside an
> +itemized list to be associated with an item.

That is not true, something may appear before the first @item.  This 
may lead to an output that is not what the user want, but it is always 
possible and in the tree, there is a specific element for that, with 
type 'before_item'.

> +Index entries and comments are allowed before @code{@@item}, though,
> +including the first, since historically this has been a common
> +practice.  They automatically moved (internally) to after the
> address@hidden@@item}, so the output is as expected.

So, here the point of the previous paragraph should not be that 
they are allowed, but rather that they are moved, as already said.

-- 
Pat



reply via email to

[Prev in Thread] Current Thread [Next in Thread]