[prev in list] [next in list] [prev in thread] [next in thread] 

List:       phpdoc
Subject:    Re: [PHP-DOC] PHD renders <para> and <formalpara> as <p> tags in HTML; this is problematic.
From:       Levi Morrison <morrison.levi () gmail ! com>
Date:       2013-06-30 18:38:26
Message-ID: CAFMT4NomyxSCYUATr-TK37h2Ex=jV2FRMsnvXD=cVJLpecOQ8Q () mail ! gmail ! com
[Download RAW message or body]

> This certainly feels like something we should be doing in PhD-land.
>>>  "Fixing" the docs would be a nightmare, we wrap everything in <para>s. And
>>> remember that HTML isn't the only output format for our docs, any changes
>>> to the DocBook structure must take the other media into consideration.
>>>
>>
>> The general impression I had was that I should get more feedback from
>> this. Do I have a green light from Peter Cowburn alone or should I be
>> waiting for other responses?
>>
>
> Hold on, you haven't even gotten a "green light" from me!  What is the
> ultimate aim here? To get HTML that is "valid"? To fix a rendering bug? If
> it's the former, then making PhD spew out "valid" HTML is the task and if
> you really want to spend the time working on it, no-one will stop you! If
> the latter, I would probably look instead at fixing the broken CSS.
>

In this case we have a rendering bug that's caused by invalid HTML. To be
clear, my purpose was to render valid HTML as the means of fixing the bug
rather than trying to work around it with clever CSS.

[Attachment #3 (text/html)]

<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div \
class="h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div \
dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div>This certainly \
feels like something we should be doing in PhD-land.  &quot;Fixing&quot; the docs \
would be a nightmare, we wrap everything in &lt;para&gt;s. And remember that HTML \
isn&#39;t the only output format for our docs, any changes to the DocBook structure \
must take the other media into consideration.</div>



</div></div></div></div></blockquote><div><br></div><div>The general impression I had \
was that I should get more feedback from this. Do I have a green light from Peter \
Cowburn alone or should I be waiting for other responses?</div> </div>
</blockquote></div><br></div></div></div><div class="gmail_extra">Hold on, you \
haven&#39;t even gotten a &quot;green light&quot; from me!  What is the ultimate aim \
here? To get HTML that is &quot;valid&quot;? To fix a rendering bug? If it&#39;s the \
former, then making PhD spew out &quot;valid&quot; HTML is the task and if you really \
want to spend the time working on it, no-one will stop you! If the latter, I would \
probably look instead at fixing the broken CSS.</div> \
</div></blockquote><div><br></div><div>In this case we have a rendering bug \
that&#39;s caused by invalid HTML. To be clear, my purpose was to render valid HTML \
as the means of fixing the bug rather than trying to work around it with clever CSS. \
</div> </div><br>



[prev in list] [next in list] [prev in thread] [next in thread]