News for hackers. Stuff that matters.

A comment on Bokeh – a Python interactive visualization library. Parent comment

Re:Bokeh – a Python interactive visualization library by dbyte on Wednesday February 10, 2016 @07:39PM (#11077417)
Working on SVG? What about EPS instead? For scientific publishing EPS is much better unless your visualisation is pretty much an high entropy one.
[ Parent | on HN ]
Re:Bokeh – a Python interactive visualization library by Rapidwire on Wednesday February 10, 2016 @09:46PM (#11077920)
Please explain why EPS is better.
[ Parent | on HN ]
Re:Bokeh – a Python interactive visualization library by me2i81 on Wednesday February 10, 2016 @10:15PM (#11078015)
Most imaging for offset printing is done in PostScript, which can render EPS directly, so there's no format conversion. For web publishing that's not the case, and either is probably fine depending on the workflow.
[ Parent | on HN ]
Re:Bokeh – a Python interactive visualization library by Fomite on Wednesday February 10, 2016 @10:53PM (#11078128)
I've never submitted to a journal that took SVG, nearly everyone I submit to takes EPS.
[ Parent | on HN ]
Re:Bokeh – a Python interactive visualization library by dbyte on Tuesday February 16, 2016 @08:54AM (#11109765)
Reason is quite simple. EPS is based on PostScript. PDF specification contains a subset of PostScript. Embedding EPS into PDF is trivial and yields high quality results. For a printing publication workflow having EPS files at hand saves a lot of time and problems.

SVG is nice too, just needs few more intermediate steps.

[ Parent | on HN ]