-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML or direct PDF output #8
Comments
You can then convert latex document to pdf using a tool |
texi2pdf works on the resulting TeX file - but for some reason the escaping of various chars ( '_' , '#', etc) wasn't occuring correctly on my pull, so a manual fixup was required before it would convert correctly. Seems the script has the sed lines to do it, so i don't know why it was failing. |
|
Agreed - it was really difficult to get this to work with .tex -- lots of dependencies involved. I tried for 30 min before giving up. |
on debian even install texlive-full did not fully do the trick: pdflatex -interaction=nonstopmode report... does compile with lot of warnings Tried something with lots of vulnerabilities cumbersome If I had a wish: HTML |
I also cannot get the latex to compile properly (openSUsE 15.1) I get lots of the 'Undefined control sequence' errors as well |
Getting latex setup can be...challenging at the best of times. If flan must output to latex, please lets put a viable latex install in the docker image, and do the conversion there - it'll save a lot of frustration out here. |
So, since I was able to get the TeX to PDF working mostly cleanly, here's what TeX/PDF packages I have in stalled in my Ubuntu 18.04.3 (bionic) system:
and PDF:
|
Picking up on docker self containement: I started to develop another way of getting a pdf report as outlined by Chris Moffitt (hxxps://pbpython.com/author/chris-moffitt.html) here hxxps://pbpython.com/pdf-reports.html. |
Latex on CentOS? Pure frustration ... |
|
I've had the same problem and have added pdf conversion + upload (in the container, not the host system) in pr #42 . It increases image build time and container size a lot, but getting a pdf is really essential for my use case. |
#41 |
or even not:; |
can you share the invalid latex document that you have? |
obviously the issues ly in the way the description text of the vulnerability is writen: So I helped myself out with adding Bad thing you cannot control what peaple put in the description of vulnerability. I do not know Latex: Ist there an equivalent for the html pre tag as this might be able to solve this challenge And maybe we can do all this sanatizing in get_description(vuln, type) in file output_report.py by using |
here is the invalid dcument
|
@moosbaue thanks, I can see what the problem is. Could you maybe also share the |
here they are: |
I was able to have a quick pdf quality result by just pasting the tex file content (you can import the file too) into the online tool from here https://www.overleaf.com/ and then using Recompile and pdf download |
I was really excited to try this out, but then really bummed by only having XML or LaTeX output - I can't read either. I spent like 20 minutes trying to set up a Tex distribution and going through the loop of compiling, failing, installing another Tex style, and repeating until I gave up because of some weird error about the fontawesome style.
My point is, it would be awesome if flan output some easily human readable format directly, without the need for some external dependencies to process it (no Tex, no XML parser, etc.). For now, I'm sorta stuck squinting at these XML files....
The text was updated successfully, but these errors were encountered: