FS#44935 - [asciidoc] Text isn't wrapped properly when inside a code listing table

Attached to Project: Community Packages
Opened by red solja (redsolja) - Monday, 11 May 2015, 14:16 GMT
Last edited by Florian Pritz (bluewind) - Monday, 28 March 2016, 21:04 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The AsciiDoc package includes the "volnitsky" and "flask" themes.

These versions (I don't know if there are newer ones) suffer from a bug that was reported back in 2013: https://groups.google.com/forum/#!topic/asciidoc/mHejFrekcwk

When you generate an html file with a command such as:
"asciidoc -a data-uri -a icons -a toc2 -a theme=volnitsky -a max-width=55em whatever.txt"
code listings that are long without changing a line, overflow the code listing borders.

If the same html file is generated without the "-a theme=volnitsky" parameter:
"asciidoc -a data-uri -a icons -a toc2 -a max-width=55em whatever.txt"
the problem does not show because the volnitsky and flask css files aren't updated to include the asciidoc.css patch that should read:

"white-space: pre-wrap;" at line 80

So in essence, adding the "white-space: pre-wrap;" at line 80 at both the flask.css and volnitsky.css fixes the bug.
This task depends upon

Closed by  Florian Pritz (bluewind)
Monday, 28 March 2016, 21:04 GMT
Reason for closing:  No response
Comment by Florian Pritz (bluewind) - Monday, 11 May 2015, 17:36 GMT
The report you linked has been fixed by upstream and the fix is part of 8.6.9. If you still have an issue I suggest you contact upstream directly since I can't/won't fix this issue in our package. I only fix issues related to packaging.
Comment by Jelle van der Waa (jelly) - Monday, 28 March 2016, 09:43 GMT
8.6.9 is out and in our repos, so can't we close this bug?
Comment by Florian Pritz (bluewind) - Monday, 28 March 2016, 21:04 GMT
Well we already had 8.6.9 when this bug was created so it should not have happened. But since we didn't get any response from the submitter I'll close this.

Loading...