[wp-trac] Re: [WordPress Trac] #5964: Multi-word tags encoded incorrectly

[WordPress Trac]

#5964: Multi-word tags encoded incorrectly
---------------------------+------------------------------------------------
 Reporter:  DavidMeade     |        Owner:  anonymous
     Type:  defect         |       Status:  new      
 Priority:  normal         |    Milestone:  2.6      
Component:  General        |      Version:           
 Severity:  normal         |   Resolution:           
 Keywords:  tags, tagging  |  
---------------------------+------------------------------------------------
Comment (by Nazgul):

 Replying to [comment:6 lloydbudd]:
 > davidmeade, you are very generous with applying the term standard. As I
 wrote, long before this Microformat, web developers and search engines
 have standardized on using dash in URLs to mean a space.
 Lloyd, the + sign as a space is more prevalent than you might think.

 If we look at the good old HTML 4.01 specs, and section 17.13.4 in
 particular (http://www.w3.org/TR/html401/interact/forms.html#h-17.13.4) we
 see:
   Control names and values are escaped. Space characters are replaced by
 `+', and then reserved characters are escaped as described in [RFC1738],
 section 2.2.

 You can also see this behaviour in the PHP urlencode function which
 converts spaces to plus signs.

 > %20 is ugly and awkward. Suggesting part of my argument is irrelevant
 does not further yours. It is relevant when I go to a blog and know that
 you have tagged articles about "daisy chains" so I can enter the URL
 http://example.com/tag/daisy-chains . That is an elegant web.
 I agree that %20 is ugly, but http://example.com/tag/daisy+chains isn't
 and it's standards compliant.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5964#comment:7>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software