Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.2.0

Bug #18625 HTML tags followed by space are not rendered correctly
Submitted: 2011-06-23 19:09 UTC
From: kenorb2 Assigned:
Status: Feedback Package: Text_Wiki_Mediawiki (version SVN)
PHP Version: 5.3.1 OS: Mac
Roadmaps: (Not assigned)    
Subscription  


 [2011-06-23 19:09 UTC] kenorb2 (bronek bronowski)
Description: ------------ HTML tags are not rendered correctly if are followed by spaces. Are rendered with some weird character numbers. Related issue: http://drupal.org/node/1196580 Test script: --------------- <pre>Does work!</pre> <pre>Doesn't work!</pre> <table> <tr> <td>Table doesn't work</td> <td>Table doesn't work</td> <td>Table doesn't work</td> </tr> <tr> <td>Table does work</td> <td>Table does work</td> <td>Table does work</td> </tr> </table> Expected result: ---------------- Table is rendered correctly. Actual result: -------------- Code is rendered to something as below with some weird numbers: <pre>Does work!</pre><br /> <pre> 6Doesn't work!7</pre><br /> <table><br /> <pre> 9 10Table doesn't work11 12Table doesn't work13 14Table doesn't work15 16</pre><br /> <tr><br /> <td>Table does work</td><br /> <td>Table does work</td><br /> <td>Table does work</td><br /> </tr><br /> </table> How this looks like in XDebug: => $key = 159 pearwiki_filter/Text/Wiki.php:1081 => $rule = 'Preformatted' pearwiki_filter/Text/Wiki.php:1082 => $opts = array ('text' => ' \0311\031\0312\031subject\0313\031\0314\031predicate\031 5\031\0316\031object\0317\031\0318\031\n ... pearwiki_filter/Text/Wiki.php:1083

Comments

 [2011-06-23 19:13 UTC] kenorb2 (bronek bronowski)
 [2011-06-25 23:35 UTC] ritzmo (Moritz Venn)
Isn't there a better fix than disabling preformatted text, or do I read the patch wrong?
 [2012-01-24 18:10 UTC] doconnor (Daniel O'Connor)
-Status: Open +Status: Feedback
Can you more clearly explain why the preformatted text is wrong (thus -> patch to delete), or give us a reason for disabling it? The below test case isn't specific enough to justify the changes you propose.