[wp-trac] Re: [WordPress Trac] #6016: Whitespace is not trimmed from teaser/extended entries

WordPress Trac wp-trac at lists.automattic.com
Wed Feb 27 17:10:39 GMT 2008

#6016: Whitespace is not trimmed from teaser/extended entries
 Reporter:  redsweater  |        Owner:  josephscott
     Type:  defect      |       Status:  new        
 Priority:  normal      |    Milestone:  2.6        
Component:  XML-RPC     |      Version:             
 Severity:  normal      |   Resolution:             
 Keywords:  has-patch   |  
Comment (by redsweater):

 Actually, take a closer look at the patch. The previous code already had
 the "\n" characters hardcoded around the more tag. So what you're
 proposing wasn't exactly possible before, either. The translation you
 describe is exactly what happens *before* my patch, too.

 You're right to notice that WordPress limits how you can play with
 whitespace and the more tag, and it's a valid concern. But at the moment
 there's no way to achieve the types of nuanced behavior you're describing
 through the wp-admin editor, and there are only some very weird ways of
 achieving creative whitespace through the RPC interface.

 A better example of what my patch does is:

 The answer to the question is ...




 The answer to the question is ...

 But go ahead and try the same example in the wp-admin editor, and you'll
 see that my patch achieves parity with that editor.

 What I'm proposing is that we should bring the XMLRPC interface into
 parity first, and then you can consider longer term whether it's desirable
 to respect surrounding whitespace in these components. If it's decided
 that it is, then it will be a good time to tackle the problem both in the
 wp-admin interface and in the XMLRPC interface.

 But this seems like the easiest way to impose some sanity right now.

Ticket URL: <http://trac.wordpress.org/ticket/6016#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list