On Mon, Jun 26, 2017 at 09:50:30AM -0400, Cris Fuhrman wrote:
> On Sun, Jun 25, 2017 at 7:41 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> 
> > I'm not sure exactly what happens and if there is platform-specific
> > behavior. To see the discussion I was referencing, see:
> >
> >     https://www.lyx.org/trac/ticket/9778
> 
> 
> Thanks for the details. Clearly LyX is trying to render SVG without using
> conversion rules. In https://www.lyx.org/trac/ticket/9778#comment:10 a
> work-around to force LyX to use the conversion rules is to remove a library
> file. I tried this on my Windows 10 (it's a DLL) and it breaks the GUI of
> LyX.
> 
> Because SVG is a moving standard (1.1 is last official one and was released
> in 2011, 1.2 is still a draft, Tiny 1.2 exists as a separate standard, 2.x
> is still in draft mode, etc.), LyX users should have more control over how
> SVG is rendered with the tool they prefer. SVG is not like GIF or JPEG
> (yet).
> 
> I see there was already a patch
> https://www.lyx.org/trac/changeset/6bd5263405/lyxgit that was supposed to
> make this work. But from my experiences with 2.2.3 in Windows, it doesn't
> seem to be working (anymore).
> 
> Would it be constructive to make a feature request in LyX to allow the
> option of bypassing native SVG rendering?

Enrico proposed a patch for stable that might make it in 2.2.4 [1]. If
you think there's room for improvement, yes please go ahead and make
a separate feature request.

Scott

Reply via email to