On Mon, Oct 5, 2009 at 8:08 AM, blues <[email protected]> wrote:
>
> i also added an example at that page of a problem i am having:
>
> //Page last updated on//
> //[(time {(lastmodified)} "%d %b %Y, %H:%M:%S")] //
>
> inserts both a <br/> and a <p> between the two lines.
I'm not sure this is a bug. It seems perfectly expected. Any line
followed by a single line break gets a <br /> added to the end of the
line. Any line followed by two line returns gets wrapped in <p> tags.
The html output on that text is:
<em>Page last updated on</em><br />
<p><em>05 Oct 2009, 06:06:56 </em></p>
We could run a scan perhaps and convert all <br />\n<p> to \n<p>, but
I'm not sure that is essential or desired. It displays properly with
the default css and I'm pretty sure it validates...
> the problem exists only if it is the first lines on the page and
> without the <markup> (it works inside there as espected).
The reason it probably "works" there is that there are not two lines
trailing the second line of text. Thus no <p> tags. Again, as expected
if you understand the design. For instance compare these two on a
page:
<html>
//Page last updated on//
//[(time {(lastmodified)} "%d %b %Y, %H:%M:%S")] //
</html>
and
<html>
//Page last updated on//
//[(time {(lastmodified)} "%d %b %Y, %H:%M:%S")] //
</html>
(That html markup is a pretty cool tool isn't it?)
We still haven't really resolved the problem of what to do for the
last paragraph, if it is not trailed by two line returns. I suppose we
could just append \n\n to the zone automatically... But that might
disrupt existing skins where some zones suddenly start getting p tags
at the end where nothing was there before. I may tinker and see how
disruptive it is to my sites...
Hey I tried it. Change line 1091 in engine.php to this (adds the \n\n)
and nothing is disrupted on the default skin as far as I can tell.
Except the last line gets paragraphized as desired.
$page = BOLTloadpage($link) . "\n\n";
If others could try this change and report adverse affects, I'd be
appreciative. I'm inclined to put this in the next release. It should
help with this problem that has been reported several times before.
Cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
