by Luc Saffre · in Developers · assigned to Luc Saffre

Summary

Children

Comments

• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : Fixed. The truncate_comment function now also sanitizes the content. Reorganized the documentation, new page lino.utils.soup. I also wrote a blog entry BeautifulSoup and lxml.
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : And this is touching #5858 (Make links in text fields automatically clickable).
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : The test suite reveals that my little change is not yet the final solution.
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : I pushed a little change to lino for trying to fix this.
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : My suggestion: I'd write some doctest document that shows the change without lino so that we can post this as a question on the lxml mailing list. And then we require lxml<6 and wait a bit.
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : Maybe okay regarding the <p> tag, but there MUST be a space between the word "Try" and the preformatted text ("rm -r /").
• 1 year, 3 months ago by Sharif Mehedi about #6177 (Issues after lxml upgrade) : I checked with the older version of lxml. For the text: "Try<pre>rm -r /</pre>and you might regret.", it used to insert a "p" tag at the beginning, like so: "<html><body><p>Try</p><pre>rm -r /</pre>and you might regret.</body></html>". And now all of a sudden it doesn't insert the "p" tag. In my opi...
• 1 year, 3 months ago by Luc Saffre about #6177 (Issues after lxml upgrade) : Created new Ticket #6177 (Issues after lxml upgrade).