On Wed, Sep 20, 2017 at 10:20:04PM +0200, Stephan Witt wrote: > I’m in favor of a working SVG to PNG conversion for systems without a > SVG to PDF or EPS converter.
> Ideally for inset-info only and for SVG > graphic insets presenting an error message. Interesting idea to consider. I wonder if this could be easy to implement. Could we define a new format svgdoc, and a corresponding new converter that could potentially convert to a bitmap, and have the icon-inset convert using that format? > But this is too complex for 2.3.0, IMO. So I’d put my patch in and > let some nice guys change the splash files. Sounds good. > Shouldn’t the Linux packagers > made aware of the dependency of LyX on Inkscape? I don't know. Currently, the "lyx" package on Ubuntu lists "inkscape" as a "suggested" package. > (Yes, I know, on Linux it would work without it by using convert. But > this isn’t good - an error should be raised on Linux too. :) About raising an error instead of converting a vector silently to bitmap, when I said that, it was my personal opinion. I don't have a release-manager opinion on that. If we want to change 2.2.x behavior in 2.3.0, we should discuss this more widely. I suppose the proposal would be to remove convert (and its new binary name) as converter of any vector format from configure? > > I think that after 2.3.0 is out, we should prioritize fixing the root > > issue. It is important that users be able to compile help files > > out-of-the-box. In some sense, this was already not the case because we > > ask users to install certain LaTeX packages to compile the help files, > > but additionally asking them to install a program (especially Inkscape, > > which I imagine is heavy) does not seem like an acceptable long-run > > solution in my opinion. > > Yes, I think so too. > > > By the way, the following is a useful thread: > > > > > > https://tex.stackexchange.com/questions/2099/how-to-include-svg-diagrams-in-latex > > The solutions to output SVG to printable files with LaTeX are using > the „evil“ shell escape, BTW. Yes there are a lot of answers but I don't see any that practically help us. > > One of the answers > > > > https://tex.stackexchange.com/a/2150/12212 > > > > suggests a program called SVG Rasterizer, which apparently can convert > > to PDF (I believe without rasterizing, as e.g. ImageMagick would) [1], > > is open source under the Apache License [2], is under active development > > [3], and has a detailed list of exactly which features of SVG are > > supported [4]. > > I read the text you’ve referred to with [1]. Of course I don’t know more > but if a tool can output PNG, JPEG, TIFF and PDF I’d bet the PDF is a > container for a rastered image only. Ah good to know then. I must have misinterpreted the text. In any case (as mentioned below), doesn't seem worth the time to find out. > > But I don't imagine we would want to depend on a Java app, especially > > since Mac does not ship anymore with the JRE [5]. I was surprised to see > > that in configure we do check for a Java interpreter (see e.g. > > 81633176), and for certain .jar binaries (e.g. 'htmltolatex.jar'). But I > > suppose that checking for system-installed jar files and shipping a jar > > file are different things. Nonetheless, since I know nothing about Java, > > I leave my above investigation on the 0.1% chance it is useful. > > The additional dependency would be bad and should better be avoided. Makes sense. Scott
signature.asc
Description: PGP signature
