If using drush_html_to_text instead of drupal_html_to_text, and if the release notes are from a Drupal 7 project instead of a Drupal 6 project, then the releasenotes will be missing line breaks which are otherwise present.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | drush-no-drupal-html-to-text.patch | 4.58 KB | greg.1.anderson |
| #6 | drush-rln-linebreaks-2.patch | 4.1 KB | greg.1.anderson |
| #2 | drush-rln-linebreaks.patch | 2.39 KB | greg.1.anderson |
Comments
Comment #1
moshe weitzman commentedI've run into this too. To reproduce it, browse to some non drupal directory and run
drush rln webform-7.xComment #2
greg.1.anderson commentedThis patch adjusts the formatting in the default implementation in drush_html_to_text to better handle linebreaks in Drupal release notes.
Also adds --html option, which is useful for debugging if nothing else.
Comment #3
jonhattanIt still doesn't work for
drush rln webformfrom a drupal7 site. I've traced drupal_html_to_text() with no luck and found this ugly workaround to work:Comment #4
moshe weitzman commentedI find it odd that drupal.org would format drupal 7 releases differently. How do we know that this is the right condition?
Comment #5
moshe weitzman commentedOh, I get it now. drupal_html_to_text() varies by release. That makes more sense. I'm fine with jonhattan's suggestion if it works for Greg.
Comment #6
greg.1.anderson commentedUnfortunately, there are other problems, and they seem to be in d7. If you compare the releasenotes between webform and logintoboggan on d7, you'll see that the former breaks issues via
, and the later breaks via
Since there does not seem to be a good way to work around the d7 problem, this patch invariantly uses our simple version of html to text to print release notes.
Probably need to put an issue in the d7 queue too.
Comment #7
jonhattanOther than this one, the patch looks good.
Comment #8
jonhattanWait. It seems this is no longer needed...
Comment #9
greg.1.anderson commentedI left it that way on purpose, so that other code that may want to convert html to text still has access to the Drupal version. Should we just get rid of that in favor of consistency? The caller can always decide to call drupal_html_to_text if it is desired.
Comment #10
jonhattanI prefer get rid of it.
Comment #11
greg.1.anderson commentedHere it is, all gone. As an added bonus, this patch also remembers to convert > and such to their plaintext equivalents.
Comment #12
moshe weitzman commentedrtbc.
Comment #13
greg.1.anderson commentedCommitted.