Jim Giner wrote:
> I am outputting to a <textarea> on an html page. A <br> doesn't work, nor
> does \n, hence the
. Of course, if I don't need the & then I've
> just saved two keystrokes. :) Also - I do believe I tried ($i+1) and
> that didn't work either.
> "Paul M Foster" <pa...@quillandmouse.com> wrote in message
>> On Tue, Mar 22, 2011 at 10:50:54PM -0400, Jim Giner wrote:
>>> Yes - it is J and I. I tried using $i+1 in the echo originally but it
>>> wouldn't run. That's why I created $j.
>> Yes, the substitution creates a syntax error unless surrounded by
>> parentheses or the like.
>>> And just what is wrong with the old cr/lf sequence? How would you have
>> You're using HTML-encoded entities for 0x0d and 0x0a. You can simply
>> use 0x0d and 0x0a instead. If you're running this in a web context, you
>> should use "<br/>" instead of CRLF. At the command line, I'm not
>> familiar with running PHP on Windows. In *nix environments, it's enough
>> to use "\n", just as they do in C. It might even work in Windows; I
>> don't know. If not, you should be able to use "\r\n". You can also try
>> the constant PHP_EOL, which is supposed to handle newlines in a
>> cross-platform way.
>> Paul M. Foster
It's possibly worth reinforcing at this stage of the game that
are incorrectly formed strings to represent CR and LF, in that they should
have a closing semicolon to delimit the end of the entity. I think this was
pointed out elsewhere but I believe it deserves repeating.
Sumo Wrestling: survival of the fattest.
Today is Pungenday, the 10th day of Discord in the YOLD 3177.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php