Hi!

[EMAIL PROTECTED] wrote:

> > sorry, I still work with 4.03PL1 since the MSSQL-ext. doesn't work in 4.04.
>
> Then upgrade.

Will do it with 4.05 (on an prod.-system I won't work with dev-Versions, till I have a 
test server)

> > But shouldn't that be worth a short comment in the doc (like "inserts XHTML 
>breaks..." instead of "HTML breaks", and
> > when the change (from what) happened?) , since Browsers like Netscape 4.x don't 
>react on <br/>?
> > Or have I missed a section with all these things one has to consider (know) before 
>- or at least after upgrading - (like
> > $array[myfield] and the backward-compatible nl2br "doesn't work anymore")?
>
> It is documented in the English and German docs. For other languages I
> don't know.

May I ask where?
I've searched the whole doc (downloadable from php.net/docs.php, which a target-user 
would use) for:
- "changed", -> nothing with that info
- "4.04" with absolutely no results, and
- "4.05" only found for setcookie.

But back to nl2br():

"nl2br -- Inserts HTML line breaks before ..." and then
"Returns string with '<br />' inserted before all newlines. "

What I meant: Shouldn't HTML be changed to XHTML?
And is it really that bad to write also a note like "Note: In versions older than PHP 
4.04 nl2br() returned a string with
'<br>' inserted before all newlines." ?

For behavior-changes like this: Please have in mind, that there are millions scripts 
running out there, and not all of them
running on the last PHP-version.

> > Is there a consideration for eventually occuring "traps" for the change to 4.05?
> > I assume that it's not really funny if a user - or worse - ISP upgrades, and than 
>can't defend against complaints
> > because of "buggy" scripts (which worked before).
>
> > Anil Madhavapeddy wrote:
> >
> > > > -> would somebody pls. correct <br/> to <br> in both lagunages?
> > >
> > > That's not a typo.  nl2br() uses XHTML <br /> tags since PHP-4.0.4
>
> Thats the correct syntax nowadays.

Agreed.

Regards,
Thomas


Reply via email to