in reply to Re: HTML printing
in thread HTML printing

If you want more query string values in one url in order to do cool things, just separate them with '&'.
Which of course, you must write as &, so when you send out the html, it looks like this: 
<a href="http://my.server.com/multipage.pl?page=2&amp;book=3">Show pag
+e 2 of book 3</a>

[download]
Please don't make the same mistake the monestary makes, which forces the browser to error-correct all the links, sometimes in surprising ways.

And someday, I'll lean on his vroom-ness to fix this, but so far I'm just waiting for him to be enlightened on his own. {grin}

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
Re: Re: Re: HTML printing
by dvergin (Monsignor) on Feb 17, 2001 at 09:46 UTC
    With great respect and appreciation for Randal... and not a little trepidation, let me quote two bits of tested perl code that each print '&' into an HTML page without making use of the '&amp' entity.

    The first example prints the '&' as displayed, plain text.
    The second example prints the '&' inside an HTML tag: 

       print "Let's show a query string: ?key1=one&key2=two\n";
   print "<a href='$my_url?key1=one&key2=two'>Click here</a>\n";

    [download]
    The HTML '&amp' entity does have its use. A prime example of which is the fact that I had to type '&amp;amp' to get the third word in the previous sentence to appear correctly!

    Update: This is bad advice!! Read the next post for the correction. (This post left in place so that Randal's next post will make sense.)

[reply]
[d/l]
      Both of those generate invalid HTML when displayed in a browser, which a browser must error correct to understand that "&key2" is not an entity. Try your experiment with "key2" replaced with "copy" and you'll get copyright symbols all over the place.

      I stand by my first statement. Dumping HTML to the browser, whether in the body of the text, or in the parameter of a tag, must be properly entity-escaped, and if not, you are relying on the error-correction behavior of the browser to correct for your avoidable failure. Please don't, and please don't tell others to copy your mistake.

      -- Randal L. Schwartz, Perl hacker

[reply]
        Thanks, Randal. Yes, of course you are right. I would have done better to put my post in the form of a question. (E.g. "but this seems to work, please explain... etc. etc.")

        And your explanation makes clear why I have gotten away with this with known keys that happened not to be any of the 100 or so named HTML entities.

        The fact that my suggestion works much of the time makes it all the more dangerous -- since it will lead to complacency and a rude awakening down the line.

        I did say "considerable trepidation". Perhaps there is solice in the thought that this exchange will be instructive to others. <brave grin>

[reply]

In Section Seekers of Perl Wisdom