Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #12010

Re: finding newlines

Show all headers | View raw

bill wrote:

> On 11/27/2013 10:56 AM, Thomas 'PointedEars' Lahn wrote:
>> bill wrote:
>>> I create the progress note in another script that is POSTed to
>>> this one.
>>>
>>> looking at progress note tells me that is is as I said, actually,
>>> I copied it from the display of the debug statement:
>>>
>>> echo basename(__FILE__) . ": " . __LINE__ .
>>> ":progNote=>$progressNote<<br />";
>>                             ^
>> This is almost certainly an error.  Also, you want to htmlspecialchars()
>> etc. the value of $progressNote.
> 
> actually, not an error.  I use the open and close bracket
> characters to help me see the string and not miss spaces on
> either end.

“<br />” is either XHTML or HTML5 syntax.  In HTML, in XHTML and in other 
XML applications, “<” and ”>” are special markup characters (Start-Tag Open 
[STAGO] and Tag Close [TAGC]).  You need to escape literal ”<” (in order to 
prevent it from being parsed as STAGO, at least when a letter follows) and 
you should escape literal ”>” (if only to avoid confusion).  PHP's 
htmlspecialchars() also does that for you.

<http://validator.w3.org/>


PointedEars
-- 
Prototype.js was written by people who don't know javascript for people
who don't know javascript. People who don't know javascript are not
the best source of advice on designing systems that use javascript.
  -- Richard Cornford, cljs, <f806at$ail$1$8300dec7@news.demon.co.uk>

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

finding newlines bill <william@TechServSys.com> - 2013-11-25 11:12 -0500
  Re: finding newlines Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-25 17:32 +0100
    Re: finding newlines bill <william@TechServSys.com> - 2013-11-26 09:36 -0500
  Re: finding newlines Richard Yates <richard@yatesguitar.com> - 2013-11-25 08:34 -0800
  Re: finding newlines Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-25 20:11 +0000
    Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-25 22:23 +0100
    Re: finding newlines Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-26 18:05 +0000
      Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-26 19:46 +0100
        Re: finding newlines Wizard-Of-Oz <somewhere@over.rainbow.com> - 2013-11-30 16:50 +0000
          Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-12-01 17:11 +0100
  Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-25 22:18 +0100
  Re: finding newlines Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-25 16:36 -0500
    Re: finding newlines bill <william@TechServSys.com> - 2013-11-27 05:11 -0500
      Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-27 16:56 +0100
        Re: finding newlines bill <william@TechServSys.com> - 2013-11-28 11:42 -0500
          Re: finding newlines Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-28 20:20 +0100
          Re: finding newlines Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-29 00:57 +0000
      Re: finding newlines Jerry Stuckle <jstucklex@attglobal.net> - 2013-11-27 11:47 -0500
        Re: finding newlines bill <william@TechServSys.com> - 2013-11-28 11:09 -0500

csiph-web