Follow-up Comment #19, bug #60927 (group groff): [comment #13 comment #13:] > with no discretionary line breaks,
To reiterate what I said in your savannah feature request, it should not fall to the person posting a comment to have to manually insert line breaks to make it render sanely. (As I also point out there, the problem doesn't show up in all browsers. So a user previewing a comment who sees no problem on their own browser has no inkling that these line breaks are even needed for readers using other browsers.) > (e.g. by inserting U+2009 zero width spaces at strategic points), (U+2009 is THIN SPACE; U+200B is ZERO WIDTH SPACE) A bare URL in a comment serves two purposes: it is displayed in the comment, and it is also turned into a hyperlink to be clicked on. Adding characters _within_ the URL to improve its display will sabotage its functionality when clicked. A reasonable workaround for this is to wrap the URL in savannah's [ ] markup, hiding it behind some text. But a user _should_ be able to post a bare URL and have it work sanely. Hence my opening http://savannah.nongnu.org/support/?111307 to address this. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60927> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
signature.asc
Description: PGP signature
