[Feature/Bug] Poor handling of pre-formatted plain text articles #8328
Description
Is your feature request related to a problem? Please describe.
Some feeds (official and web-scraped) do not return content well suited for FreshRSS or rss reader apps pulling from FreshRSS. In my case, these feeds return pre-formatted plain text intended to be displayed with monospace.
Use case
The FreeBSD project provides two easily scrapable pages listing announced security notices and security vulnerabilities. The "articles" are PGP-signed files that are formatted to be viewable in less or vi
Describe the solution you’d like
A simple checkbox to mark the feed articles as pre-formatted plain-text would work fine. A more well-thought solution could allow the user to transform the article content in some arbitrary way (i.e: to entrap the escaped content in a <pre><code> block). Maybe a list of sed-like expressions such as s/.*/<pre><code>\(1)</code></pre>/g?
Describe alternatives you’ve considered
- An extension. This would work similarly to the official YouTube-to-embed extension, however as extensions can't have per-feed settings (afiak), it wouldn't be very flexable.
- Using a custom stylesheet. This works, however only in FreshRSS. External RSS readers, even if they were sent the custom CSS, would be unlikely to respect it.
Additional context
An example article displayed as-is:
An example article with white-space: pre; font-family: monospace; applied to .content .text:
