[Top][All Lists]

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

Re: Have you all gone crazy? Was: On being web-friendly and why info mus

From: Yuri Khan
Subject: Re: Have you all gone crazy? Was: On being web-friendly and why info must die
Date: Tue, 23 Dec 2014 00:37:48 +0700

On Mon, Dec 22, 2014 at 2:58 PM, David Kastrup <address@hidden> wrote:

>>> <a 
>>> href="79/lily-83620d4b.ly"><p>&lsquo;<tt>accidental-ancient.ly</tt>&rsquo;
>>> </a>    <p>
>>>  <a href="79/lily-83620d4b.ly">
>>>   <img align="middle"
>>>        border="0"
>>>        src="79/lily-83620d4b.png"
>>>        alt="[image of music]">
>>>  </a>
>>> </p></p>

> Well, apart from the unhelpful alt text (which is not easy to make more
> helpful, actually, given the way this is generated), that would be the
> responsibility of texi2html.

Sure. I’m just amazed that this bug exists and has likely existed
since the HTML output was introduced and no one has noticed.

> Probably worth reporting to the Texinfo
> list and/or proposing a fix.  Now <p> does not need to nest in HTML, and
> I can't vouch definitely that the second </p> might not belong to some
> starting <p> I have not cut&pasted.

<p>’s *cannot* nest. By definition, each next <p> causes the previous
unclosed <p> to auto-close.

> But it's not really pretty and could probably be fixed by just removing
> the generation of any </p>.

That would be just ugly.

I’m a firm believer in closing tags explicitly and properly.
Especially when the markup is not hand-written but generated. There’s
just no excuse for generating invalid or sloppy markup.

reply via email to

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