Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 1/6/19 7:49 AM, Stephan Witt wrote: > Am 06.01.2019 um 09:57 schrieb Enrico Forestieri : >> On Sun, Jan 06, 2019 at 12:29:40AM +0100, Stephan Witt wrote: >>> I did it with the wrapper script approach and pushed it with commit >>> caa1dd2aee. >> Strangely enough, your commit didn't show up on the lyx-cvs list. > Yes, I’ve noticed that and have no idea what happened :( > > Riki, I’d like this change to back port to 2.3.x. This will solve the > problem reported by Prof. Robert Betz. > > https://www.lyx.org/trac/changeset/caa1dd2aeed97330e05c0e96ae7e5bb929b0866d/lyxgit OK! Riki
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 06.01.2019 um 09:57 schrieb Enrico Forestieri : > > On Sun, Jan 06, 2019 at 12:29:40AM +0100, Stephan Witt wrote: >> >> I did it with the wrapper script approach and pushed it with commit >> caa1dd2aee. > > Strangely enough, your commit didn't show up on the lyx-cvs list. Yes, I’ve noticed that and have no idea what happened :( Riki, I’d like this change to back port to 2.3.x. This will solve the problem reported by Prof. Robert Betz. https://www.lyx.org/trac/changeset/caa1dd2aeed97330e05c0e96ae7e5bb929b0866d/lyxgit Stephan > >> I’ve tested it on Mac extensively. It shouldn’t change anything on other >> platforms. >> But I’d be glad to hear if you can test it on Linux too and tell me it >> works for you. > > Yes, the change does not affect all other platforms. > >> So, we postpone the problem - but this is ok for me. >> >> Thank you for the discussion. > > You're welcome. > > -- > Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Sun, Jan 06, 2019 at 12:29:40AM +0100, Stephan Witt wrote: > > I did it with the wrapper script approach and pushed it with commit > caa1dd2aee. Strangely enough, your commit didn't show up on the lyx-cvs list. > I’ve tested it on Mac extensively. It shouldn’t change anything on other > platforms. > But I’d be glad to hear if you can test it on Linux too and tell me it > works for you. Yes, the change does not affect all other platforms. > So, we postpone the problem - but this is ok for me. > > Thank you for the discussion. You're welcome. -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 05.01.2019 um 12:03 schrieb Enrico Forestieri : > > On Fri, Jan 04, 2019 at 11:30:08PM +0100, Stephan Witt wrote: >> Am 04.01.2019 um 18:54 schrieb Enrico Forestieri : >>> >>> On Fri, Jan 04, 2019 at 05:19:57PM +0100, Stephan Witt wrote: Am 04.01.2019 um 17:05 schrieb Enrico Forestieri : > Then why not using a wrapper that takes the specified paths, makes them > absolute by prefixing the current directory if they are relative and then > calls the inkscape shell script? Because it’s tedious and error prone to handle all possible parameters and care for spaces in path names and don’t change other parameters. >>> >>> I see. In this case, in order to keep the same meaning, "$$i" and "$$o" >>> should always produce relative paths and the code should be audited for >>> adding "$$p" where actually needed. >>> >> The argument from JMarc about possible breaking existing user preferences >> is a real strong one. I don’t have a better idea... > > Note that we have the pref2prefs.py script for converting user preferences. > It would suffice replacing "$$i" with "$$p$$i" and "$$o" with "$$p$$o" > where appropriate. So, no breaking would occur. > >> the attached patch would >> be a real pragmatic approach, IMO. Furthermore it gives the possibility to >> solve (or hide) the problem in 2.3.x branch too. > > I really don't like the different meaning that is attached to "$$p" in this > case. This is bound to bite in the future. > >> If this patch is not acceptable I think the next best move is to catch the >> relative path names in the Mac specific inkscape wrapper script. Just as you >> proposed it. I thought about it and think it’s doable because the calls from >> Converters::convert use normalized file names without spaces returned by >> DocFileName::mangledFileName. >> >> What do you think? > > The wrapper is the quickest solution, maybe, but the unification of the > meaning of "$$i" and "$$o" is the cleanest. However, if you do not have > time to tackle it, pragmatically, I would say go with the wrapper approach, > as this issue has seemingly always been there and only showed in the > particular case of the Mac. Yes, this means postponing the problem but we > often have to live with compromises. I did it with the wrapper script approach and pushed it with commit caa1dd2aee. I’ve tested it on Mac extensively. It shouldn’t change anything on other platforms. But I’d be glad to hear if you can test it on Linux too and tell me it works for you. So, we postpone the problem - but this is ok for me. Thank you for the discussion. Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Fri, Jan 04, 2019 at 11:30:08PM +0100, Stephan Witt wrote: > Am 04.01.2019 um 18:54 schrieb Enrico Forestieri : > > > > On Fri, Jan 04, 2019 at 05:19:57PM +0100, Stephan Witt wrote: > >> Am 04.01.2019 um 17:05 schrieb Enrico Forestieri : > >>> Then why not using a wrapper that takes the specified paths, makes them > >>> absolute by prefixing the current directory if they are relative and then > >>> calls the inkscape shell script? > >> > >> Because it’s tedious and error prone to handle all possible parameters and > >> care for spaces in path names and don’t change other parameters. > > > > I see. In this case, in order to keep the same meaning, "$$i" and "$$o" > > should always produce relative paths and the code should be audited for > > adding "$$p" where actually needed. > > > The argument from JMarc about possible breaking existing user preferences > is a real strong one. I don’t have a better idea... Note that we have the pref2prefs.py script for converting user preferences. It would suffice replacing "$$i" with "$$p$$i" and "$$o" with "$$p$$o" where appropriate. So, no breaking would occur. > the attached patch would > be a real pragmatic approach, IMO. Furthermore it gives the possibility to > solve (or hide) the problem in 2.3.x branch too. I really don't like the different meaning that is attached to "$$p" in this case. This is bound to bite in the future. > If this patch is not acceptable I think the next best move is to catch the > relative path names in the Mac specific inkscape wrapper script. Just as you > proposed it. I thought about it and think it’s doable because the calls from > Converters::convert use normalized file names without spaces returned by > DocFileName::mangledFileName. > > What do you think? The wrapper is the quickest solution, maybe, but the unification of the meaning of "$$i" and "$$o" is the cleanest. However, if you do not have time to tackle it, pragmatically, I would say go with the wrapper approach, as this issue has seemingly always been there and only showed in the particular case of the Mac. Yes, this means postponing the problem but we often have to live with compromises. -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 04.01.2019 um 18:54 schrieb Enrico Forestieri : > > On Fri, Jan 04, 2019 at 05:19:57PM +0100, Stephan Witt wrote: >> Am 04.01.2019 um 17:05 schrieb Enrico Forestieri : >>> Then why not using a wrapper that takes the specified paths, makes them >>> absolute by prefixing the current directory if they are relative and then >>> calls the inkscape shell script? >> >> Because it’s tedious and error prone to handle all possible parameters and >> care for spaces in path names and don’t change other parameters. > > I see. In this case, in order to keep the same meaning, "$$i" and "$$o" > should always produce relative paths and the code should be audited for > adding "$$p" where actually needed. > > -- > Enrico The argument from JMarc about possible breaking existing user preferences is a real strong one. I don’t have a better idea... the attached patch would be a real pragmatic approach, IMO. Furthermore it gives the possibility to solve (or hide) the problem in 2.3.x branch too. If this patch is not acceptable I think the next best move is to catch the relative path names in the Mac specific inkscape wrapper script. Just as you proposed it. I thought about it and think it’s doable because the calls from Converters::convert use normalized file names without spaces returned by DocFileName::mangledFileName. What do you think? Stephan GraphicsConverter.patch Description: Binary data
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Fri, Jan 04, 2019 at 05:19:57PM +0100, Stephan Witt wrote: > Am 04.01.2019 um 17:05 schrieb Enrico Forestieri : > > Then why not using a wrapper that takes the specified paths, makes them > > absolute by prefixing the current directory if they are relative and then > > calls the inkscape shell script? > > Because it’s tedious and error prone to handle all possible parameters and > care for spaces in path names and don’t change other parameters. I see. In this case, in order to keep the same meaning, "$$i" and "$$o" should always produce relative paths and the code should be audited for adding "$$p" where actually needed. -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Le 04/01/2019 à 17:49, Stephan Witt a écrit : Yes, I mean sweave/knitr. Because of the $$p$$i and $$p$$o parameters. This cannot work for both converter code paths, IMO. In case of inkscape this works for TeX conversion and fails with on-screen conversion (graphics loader). $$p is not substituted and replaced by the process number + p. But as I said - I cannot test it. Is it possible to preview sweave/knitr snippets on Linux? No, it is not how it works. They are used through converters via literate programming support. However, the idea of previewing these is intriguing. The main problem is that they should be done all at once, and the processing time can be large. JMarc
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 04.01.2019 um 17:39 schrieb Jean-Marc Lasgouttes : > > Le 04/01/2019 à 16:00, Stephan Witt a écrit : >> IMO the different meaning of $$i and $$o in LyX converters is a bug too. >> And this bug we can fix. > > I did not have time to look at this at all, but I agree that having a > different meaning for these two things is bad. However, fixing it would mean > that users' preference files would become invalid, which is definitely not > good. > > Why makes you think that Rscripts (I presume you mean sweave/knitr) are > broken too, BTW? Yes, I mean sweave/knitr. Because of the $$p$$i and $$p$$o parameters. This cannot work for both converter code paths, IMO. In case of inkscape this works for TeX conversion and fails with on-screen conversion (graphics loader). $$p is not substituted and replaced by the process number + p. But as I said - I cannot test it. Is it possible to preview sweave/knitr snippets on Linux? Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Le 04/01/2019 à 16:00, Stephan Witt a écrit : IMO the different meaning of $$i and $$o in LyX converters is a bug too. And this bug we can fix. I did not have time to look at this at all, but I agree that having a different meaning for these two things is bad. However, fixing it would mean that users' preference files would become invalid, which is definitely not good. Why makes you think that Rscripts (I presume you mean sweave/knitr) are broken too, BTW? JMarc
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 04.01.2019 um 17:05 schrieb Enrico Forestieri : > > On Fri, Jan 04, 2019 at 04:00:51PM +0100, Stephan Witt wrote: >> >> The inkscape binary on Mac is a shell script inside the Inkscape.app bundle. >> It has the drawback that it internally does a cd (change directory) and later >> tries to access the files given from command line. This must fail with >> relative >> path name arguments. One may call it a bug of the inkscape script but it’s >> as it >> is. The author of the script did it to solve another problem with the >> Inkscape >> application. > > Then why not using a wrapper that takes the specified paths, makes them > absolute by prefixing the current directory if they are relative and then > calls the inkscape shell script? Because it’s tedious and error prone to handle all possible parameters and care for spaces in path names and don’t change other parameters. Because it’s a work-around for a flaw in LyX converters. BTW, I fear Rscript conversion is broken already too. Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Fri, Jan 04, 2019 at 04:00:51PM +0100, Stephan Witt wrote: > > The inkscape binary on Mac is a shell script inside the Inkscape.app bundle. > It has the drawback that it internally does a cd (change directory) and later > tries to access the files given from command line. This must fail with > relative > path name arguments. One may call it a bug of the inkscape script but it’s as > it > is. The author of the script did it to solve another problem with the Inkscape > application. Then why not using a wrapper that takes the specified paths, makes them absolute by prefixing the current directory if they are relative and then calls the inkscape shell script? -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 04.01.2019 um 15:42 schrieb Enrico Forestieri : > > On Fri, Jan 04, 2019 at 01:38:27PM +0100, Stephan Witt wrote: >> Am 04.01.2019 um 10:27 schrieb Enrico Forestieri : >>> >>> On Mon, Dec 24, 2018 at 11:02:10AM +0100, Stephan Witt wrote: Am 23.12.2018 um 23:03 schrieb Stephan Witt : >>> [...] > The python script generated on the fly by LyX has two superfluous „$$p“ in > front of the real path names of in and out files. > > # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + > ' --export-png=$$p' + '"' + outfile + '"' + '') != 0: > > This is a consequence of the auto detected converter configuration line in > ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults > > \converter svgpng"inkscape --without-gui --file=$$p$$i > --export-png=$$p$$o""", > > I’m not sure how this should work - obviously it doesn’t work. To be more explicit: it doesn’t work on Mac with inkscape installed. One possible work around for you would be to change the converter definitions for SVG to PNG and SVGZ to PNG. Remove the $$p from the converter parameters (see attached screen shot). >>> >>> Note that the $$p are explicitly added by configure.py only for Mac (search >>> for inkscape_fileprefix in configure.py). >> >> Yes, I have seen this. Jürgen did it this way because he had a problem with >> the non-special case on Linux. Probably the same we have now on Mac: the >> on-screen rendering of SVG is broken in case of having inkscape installed. >> >>> So, maybe it suffices not to >>> special case the Mac here? >> >> >> You mean to pass directory name for $$p and use it on all platforms for >> inkscape? >> And don’t change the other converters so they all use relative path names >> for both conversions? > > I mean changing only configure.py by removing inkscape_fileprefix so that > the converters on Mac are defined exactly as on all other platforms, i.e., > without $$p. I see. But this breaks the export with inkscape to e.g. PDF. There the $$i and $$o are not absolute path names but relative to the temporary directory. The inkscape binary on Mac is a shell script inside the Inkscape.app bundle. It has the drawback that it internally does a cd (change directory) and later tries to access the files given from command line. This must fail with relative path name arguments. One may call it a bug of the inkscape script but it’s as it is. The author of the script did it to solve another problem with the Inkscape application. In principle this may happen with every external converter. IMO the different meaning of $$i and $$o in LyX converters is a bug too. And this bug we can fix. Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Fri, Jan 04, 2019 at 01:38:27PM +0100, Stephan Witt wrote: > Am 04.01.2019 um 10:27 schrieb Enrico Forestieri : > > > > On Mon, Dec 24, 2018 at 11:02:10AM +0100, Stephan Witt wrote: > >> Am 23.12.2018 um 23:03 schrieb Stephan Witt : > > [...] > >>> The python script generated on the fly by LyX has two superfluous „$$p“ in > >>> front of the real path names of in and out files. > >>> > >>> # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + > >>> ' --export-png=$$p' + '"' + outfile + '"' + '') != 0: > >>> > >>> This is a consequence of the auto detected converter configuration line in > >>> ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults > >>> > >>> \converter svgpng"inkscape --without-gui --file=$$p$$i > >>> --export-png=$$p$$o""", > >>> > >>> I’m not sure how this should work - obviously it doesn’t work. > >> > >> To be more explicit: it doesn’t work on Mac with inkscape installed. One > >> possible work around for you would be to change the converter definitions > >> for > >> SVG to PNG and SVGZ to PNG. > >> > >> Remove the $$p from the converter parameters (see attached screen shot). > > > > Note that the $$p are explicitly added by configure.py only for Mac (search > > for inkscape_fileprefix in configure.py). > > Yes, I have seen this. Jürgen did it this way because he had a problem with > the non-special case on Linux. Probably the same we have now on Mac: the > on-screen rendering of SVG is broken in case of having inkscape installed. > > > So, maybe it suffices not to > > special case the Mac here? > > > You mean to pass directory name for $$p and use it on all platforms for > inkscape? > And don’t change the other converters so they all use relative path names > for both conversions? I mean changing only configure.py by removing inkscape_fileprefix so that the converters on Mac are defined exactly as on all other platforms, i.e., without $$p. -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 04.01.2019 um 10:27 schrieb Enrico Forestieri : > > On Mon, Dec 24, 2018 at 11:02:10AM +0100, Stephan Witt wrote: >> Am 23.12.2018 um 23:03 schrieb Stephan Witt : > [...] >>> The python script generated on the fly by LyX has two superfluous „$$p“ in >>> front of the real path names of in and out files. >>> >>> # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + >>> ' --export-png=$$p' + '"' + outfile + '"' + '') != 0: >>> >>> This is a consequence of the auto detected converter configuration line in >>> ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults >>> >>> \converter svgpng"inkscape --without-gui --file=$$p$$i >>> --export-png=$$p$$o""", >>> >>> I’m not sure how this should work - obviously it doesn’t work. >> >> To be more explicit: it doesn’t work on Mac with inkscape installed. One >> possible work around for you would be to change the converter definitions for >> SVG to PNG and SVGZ to PNG. >> >> Remove the $$p from the converter parameters (see attached screen shot). > > Note that the $$p are explicitly added by configure.py only for Mac (search > for inkscape_fileprefix in configure.py). Yes, I have seen this. Jürgen did it this way because he had a problem with the non-special case on Linux. Probably the same we have now on Mac: the on-screen rendering of SVG is broken in case of having inkscape installed. > So, maybe it suffices not to > special case the Mac here? You mean to pass directory name for $$p and use it on all platforms for inkscape? And don’t change the other converters so they all use relative path names for both conversions? Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Mon, Dec 24, 2018 at 11:02:10AM +0100, Stephan Witt wrote: > Am 23.12.2018 um 23:03 schrieb Stephan Witt : [...] > > The python script generated on the fly by LyX has two superfluous „$$p“ in > > front of the real path names of in and out files. > > > > # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + > > ' --export-png=$$p' + '"' + outfile + '"' + '') != 0: > > > > This is a consequence of the auto detected converter configuration line in > > ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults > > > > \converter svgpng"inkscape --without-gui --file=$$p$$i > > --export-png=$$p$$o""", > > > > I’m not sure how this should work - obviously it doesn’t work. > > To be more explicit: it doesn’t work on Mac with inkscape installed. One > possible work around for you would be to change the converter definitions for > SVG to PNG and SVGZ to PNG. > > Remove the $$p from the converter parameters (see attached screen shot). Note that the $$p are explicitly added by configure.py only for Mac (search for inkscape_fileprefix in configure.py). So, maybe it suffices not to special case the Mac here? -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 02.01.2019 um 16:36 schrieb Stephan Witt : > > Am 01.01.2019 um 19:57 schrieb Enrico Forestieri : >> >> On Tue, Jan 01, 2019 at 02:10:37PM +0100, Stephan Witt wrote: >>> Hi all, >>> >>> first I wish all of you a Happy New Year. >>> >>> I investigated the cause of the issue with displaying SVG (including our own >>> icons in Users Guide) on-screen. >>> >>> IMO the root cause is the existence of two ways to use the configured >>> converters: >>> 1. the conversion process to load external material to present it on-screen >>> (build_script in GraphicsConverter.cpp) and >>> 2. the conversion process to prepare external material for use by external >>> programs like LaTeX (Converters::convert) >>> >>> Both are using the utilities detected by lib/configure.py. But the meaning >>> of >>> the „$$i“ and „$$o“ placeholders is different. (1) is passing the complete >>> absolute path of input and output file. (2) is operating in the temporary >>> directory and uses relative path names only. On Mac the inkscape binary is a >>> shell script itself and it’s not working with relative path names for input >>> and output files. Therefore I added the prefix „$$p“ in front of the names >>> to >>> get absolute path names. Unfortunately this breaks the conversion (1). >>> >>> One possible solution for the current issue is it to change (1) to replace >>> „$$p“ with an empty string. Is this a good idea or is some more fundamental >>> change to unify the converters to prefer? Any other ideas? >> >> What about changing (1) to use relative path names for "$$i" and "$$o" >> and then adding "$$p" to obtain absolute ones? In this way "$$p" maintains >> its meaning in both cases. > > Ok, that’s a possibility - and I like it. But it would be a „more fundamental > change“, IMO. > I’ll see how much work it is and if I can test it. I’m trying to verify how this can work without regressions. ATM, I don’t understand how the Rscript converters can work - there are $$p$$i and $$p$$o parameters for converter configuration in configure.py already. Does it work on Linux and how? I don’t have it here and cannot test it. Stephan
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 01.01.2019 um 19:57 schrieb Enrico Forestieri : > > On Tue, Jan 01, 2019 at 02:10:37PM +0100, Stephan Witt wrote: >> Hi all, >> >> first I wish all of you a Happy New Year. >> >> I investigated the cause of the issue with displaying SVG (including our own >> icons in Users Guide) on-screen. >> >> IMO the root cause is the existence of two ways to use the configured >> converters: >> 1. the conversion process to load external material to present it on-screen >> (build_script in GraphicsConverter.cpp) and >> 2. the conversion process to prepare external material for use by external >> programs like LaTeX (Converters::convert) >> >> Both are using the utilities detected by lib/configure.py. But the meaning of >> the „$$i“ and „$$o“ placeholders is different. (1) is passing the complete >> absolute path of input and output file. (2) is operating in the temporary >> directory and uses relative path names only. On Mac the inkscape binary is a >> shell script itself and it’s not working with relative path names for input >> and output files. Therefore I added the prefix „$$p“ in front of the names to >> get absolute path names. Unfortunately this breaks the conversion (1). >> >> One possible solution for the current issue is it to change (1) to replace >> „$$p“ with an empty string. Is this a good idea or is some more fundamental >> change to unify the converters to prefer? Any other ideas? > > What about changing (1) to use relative path names for "$$i" and "$$o" > and then adding "$$p" to obtain absolute ones? In this way "$$p" maintains > its meaning in both cases. Ok, that’s a possibility - and I like it. But it would be a „more fundamental change“, IMO. I’ll see how much work it is and if I can test it. Thanks, Stephan > > Happy New Year to all. > > -- > Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On Tue, Jan 01, 2019 at 02:10:37PM +0100, Stephan Witt wrote: > Hi all, > > first I wish all of you a Happy New Year. > > I investigated the cause of the issue with displaying SVG (including our own > icons in Users Guide) on-screen. > > IMO the root cause is the existence of two ways to use the configured > converters: > 1. the conversion process to load external material to present it on-screen > (build_script in GraphicsConverter.cpp) and > 2. the conversion process to prepare external material for use by external > programs like LaTeX (Converters::convert) > > Both are using the utilities detected by lib/configure.py. But the meaning of > the „$$i“ and „$$o“ placeholders is different. (1) is passing the complete > absolute path of input and output file. (2) is operating in the temporary > directory and uses relative path names only. On Mac the inkscape binary is a > shell script itself and it’s not working with relative path names for input > and output files. Therefore I added the prefix „$$p“ in front of the names to > get absolute path names. Unfortunately this breaks the conversion (1). > > One possible solution for the current issue is it to change (1) to replace > „$$p“ with an empty string. Is this a good idea or is some more fundamental > change to unify the converters to prefer? Any other ideas? What about changing (1) to use relative path names for "$$i" and "$$o" and then adding "$$p" to obtain absolute ones? In this way "$$p" maintains its meaning in both cases. Happy New Year to all. -- Enrico
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Hi all, first I wish all of you a Happy New Year. I investigated the cause of the issue with displaying SVG (including our own icons in Users Guide) on-screen. IMO the root cause is the existence of two ways to use the configured converters: 1. the conversion process to load external material to present it on-screen (build_script in GraphicsConverter.cpp) and 2. the conversion process to prepare external material for use by external programs like LaTeX (Converters::convert) Both are using the utilities detected by lib/configure.py. But the meaning of the „$$i“ and „$$o“ placeholders is different. (1) is passing the complete absolute path of input and output file. (2) is operating in the temporary directory and uses relative path names only. On Mac the inkscape binary is a shell script itself and it’s not working with relative path names for input and output files. Therefore I added the prefix „$$p“ in front of the names to get absolute path names. Unfortunately this breaks the conversion (1). One possible solution for the current issue is it to change (1) to replace „$$p“ with an empty string. Is this a good idea or is some more fundamental change to unify the converters to prefer? Any other ideas? Best regards, Stephan > Am 24.12.2018 um 11:02 schrieb Stephan Witt : > > Am 23.12.2018 um 23:03 schrieb Stephan Witt : >> >> Am 23.12.2018 um 19:28 schrieb Robert Betz : >>> >>> Anders, >>> >>> Stephen Witt mentioned that he was using RSVG-convert. So I installed, >>> using macports librsvg. I did a reconfigure on Lyx, and now the svgz >>> snippets show up. >>> >>> Don’t know why it is required to have this package, as Lyx should supply >>> everything it needs to make all these conversions work. >> >> It’s a little bit more convoluted than you think. >> >> I’ve tried to disable rsvg-convert by making it a non-executable and the >> shell didn’t find it - but LyX detected it and couldn’t run it. So, it was >> not right to say, I’m having the same problem as you. My problem was to have >> a non-working rsvg-convert. Then I renamed rsvg-convert and the preview of >> SVG graphics snippets worked out-of-the-box again. Next I’ve installed >> inkscape 0.91 and immediately had your problem after reconfiguring LyX. LyX >> was able to find end execute inkscape but the converter script used contains >> a strange command line and the conversion failed because of it. >> >> The python script generated on the fly by LyX has two superfluous „$$p“ in >> front of the real path names of in and out files. >> >> # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + ' >> --export-png=$$p' + '"' + outfile + '"' + '') != 0: >> >> This is a consequence of the auto detected converter configuration line in >> ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults >> >> \converter svgpng"inkscape --without-gui --file=$$p$$i >> --export-png=$$p$$o""", >> >> I’m not sure how this should work - obviously it doesn’t work. > > To be more explicit: it doesn’t work on Mac with inkscape installed. One > possible work around for you would be to change the converter definitions for > SVG to PNG and SVGZ to PNG. > > Remove the $$p from the converter parameters (see attached screen shot). > > Stephan > >
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 24/12/2018 14:30, Kornel Benko wrote: Am Montag, 24. Dezember 2018 11:17:14 CET schrieb Daniel : On 24/12/2018 01:04, Richard Kimberly Heck wrote: On 12/23/18 3:23 PM, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 21:13:49 CET schrieb Kornel Benko : Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel : On 23/12/2018 20:52, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : On 23/12/2018 20:27, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz : Anders, Stephen Witt mentioned that he was using RSVG-convert. So I installed, using macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show up. Don’t know why it is required to have this package, as Lyx should supply everything it needs to make all these conversions work. No. rsvg-convert is independent of lyx, as is also inkscape or any other executable. While Inkscape is not provided with LyX, rsvg-convert is, at least on Windows. Daniel By lyx? (If yes, then I think that is not OK, since it is not a program we created). I am pretty sure by LyX since it is in the LyX bin directory. (I guess it is OK as long as no licenses are violates. On Windows, which has no package dependency system like some Linux distributions, it is pretty common that applications come with such helper applications, especially for open source software.) Daniel I am surprised. Riki, is that part of our installation script? Kornel OK, found a file with a list of executables development/Win32/packaging/installer/include/filelist.nsh. Very strange policy for a unix user. Yes, there's a bunch of stuff we install with LyX on Windows. My understanding, as Daniel said, is that this is because configuring this kind of thing on Windows is very difficult, due to path issues and the registry, etc, etc. Riki Do you happen to know where the rsvg-convert.exe installed with LyX comes from, e.g. where it can be obtained? Daniel Don't know from where it comes to lyx, but a short googling reveals https://opensourcepack.blogspot.com/2012/06/rsvg-convert-svg-image-conversion-tool.html (rsvg-convert-2.40.20.7z) Seems pretty old, but OTOH, on my linux it is even older version ... $ rsvg-convert --version ==> rsvg-convert version 2.40.13 Kornel Thanks. The version with LyX is actually a bit newer. Anyway, seems like there is no installer for it. So, LyX probably couldn't reliably find it without it being shipped with LyX. Which seems like a good case for installing it with the LyX installer. Daniel
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am Montag, 24. Dezember 2018 11:17:14 CET schrieb Daniel : > On 24/12/2018 01:04, Richard Kimberly Heck wrote: > > On 12/23/18 3:23 PM, Kornel Benko wrote: > >> Am Sonntag, 23. Dezember 2018 21:13:49 CET schrieb Kornel Benko > >> : > >>> Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel > >>> : > On 23/12/2018 20:52, Kornel Benko wrote: > > Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel > > : > >> On 23/12/2018 20:27, Kornel Benko wrote: > >>> Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz > >>> : > Anders, > > Stephen Witt mentioned that he was using RSVG-convert. So I > installed, using macports librsvg. I did a reconfigure on Lyx, and > now the svgz snippets show up. > > Don’t know why it is required to have this package, as Lyx should > supply everything it needs to make all these conversions work. > >>> No. > >>> rsvg-convert is independent of lyx, as is also inkscape or any other > >>> executable. > >> While Inkscape is not provided with LyX, rsvg-convert is, at least on > >> Windows. > >> > >> Daniel > >> > > By lyx? (If yes, then I think that is not OK, since it is not a program > > we created). > I am pretty sure by LyX since it is in the LyX bin directory. > > (I guess it is OK as long as no licenses are violates. On Windows, which > has no package dependency system like some Linux distributions, it is > pretty common that applications come with such helper applications, > especially for open source software.) > > Daniel > > >>> I am surprised. Riki, is that part of our installation script? > >>> > >>> Kornel > >>> > >> OK, found a file with a list of executables > >> development/Win32/packaging/installer/include/filelist.nsh. > >> Very strange policy for a unix user. > > > > Yes, there's a bunch of stuff we install with LyX on Windows. My > > understanding, as Daniel said, is that this is because configuring this > > kind of thing on Windows is very difficult, due to path issues and the > > registry, etc, etc. > > > > Riki > > Do you happen to know where the rsvg-convert.exe installed with LyX > comes from, e.g. where it can be obtained? > > Daniel > Don't know from where it comes to lyx, but a short googling reveals https://opensourcepack.blogspot.com/2012/06/rsvg-convert-svg-image-conversion-tool.html (rsvg-convert-2.40.20.7z) Seems pretty old, but OTOH, on my linux it is even older version ... $ rsvg-convert --version ==> rsvg-convert version 2.40.13 Kornel signature.asc Description: This is a digitally signed message part.
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 24/12/2018 01:04, Richard Kimberly Heck wrote: On 12/23/18 3:23 PM, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 21:13:49 CET schrieb Kornel Benko : Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel : On 23/12/2018 20:52, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : On 23/12/2018 20:27, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz : Anders, Stephen Witt mentioned that he was using RSVG-convert. So I installed, using macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show up. Don’t know why it is required to have this package, as Lyx should supply everything it needs to make all these conversions work. No. rsvg-convert is independent of lyx, as is also inkscape or any other executable. While Inkscape is not provided with LyX, rsvg-convert is, at least on Windows. Daniel By lyx? (If yes, then I think that is not OK, since it is not a program we created). I am pretty sure by LyX since it is in the LyX bin directory. (I guess it is OK as long as no licenses are violates. On Windows, which has no package dependency system like some Linux distributions, it is pretty common that applications come with such helper applications, especially for open source software.) Daniel I am surprised. Riki, is that part of our installation script? Kornel OK, found a file with a list of executables development/Win32/packaging/installer/include/filelist.nsh. Very strange policy for a unix user. Yes, there's a bunch of stuff we install with LyX on Windows. My understanding, as Daniel said, is that this is because configuring this kind of thing on Windows is very difficult, due to path issues and the registry, etc, etc. Riki Do you happen to know where the rsvg-convert.exe installed with LyX comes from, e.g. where it can be obtained? Daniel
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 12/23/18 3:23 PM, Kornel Benko wrote: > Am Sonntag, 23. Dezember 2018 21:13:49 CET schrieb Kornel Benko > : >> Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel : >>> On 23/12/2018 20:52, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : > On 23/12/2018 20:27, Kornel Benko wrote: >> Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz >> : >>> Anders, >>> >>> Stephen Witt mentioned that he was using RSVG-convert. So I installed, >>> using macports librsvg. I did a reconfigure on Lyx, and now the svgz >>> snippets show up. >>> >>> Don’t know why it is required to have this package, as Lyx should >>> supply everything it needs to make all these conversions work. >> No. >> rsvg-convert is independent of lyx, as is also inkscape or any other >> executable. > While Inkscape is not provided with LyX, rsvg-convert is, at least on > Windows. > > Daniel > By lyx? (If yes, then I think that is not OK, since it is not a program we created). >>> I am pretty sure by LyX since it is in the LyX bin directory. >>> >>> (I guess it is OK as long as no licenses are violates. On Windows, which >>> has no package dependency system like some Linux distributions, it is >>> pretty common that applications come with such helper applications, >>> especially for open source software.) >>> >>> Daniel >>> >> I am surprised. Riki, is that part of our installation script? >> >> Kornel >> > OK, found a file with a list of executables > development/Win32/packaging/installer/include/filelist.nsh. > Very strange policy for a unix user. Yes, there's a bunch of stuff we install with LyX on Windows. My understanding, as Daniel said, is that this is because configuring this kind of thing on Windows is very difficult, due to path issues and the registry, etc, etc. Riki
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 23.12.2018 um 19:28 schrieb Robert Betz : > > Anders, > > Stephen Witt mentioned that he was using RSVG-convert. So I installed, using > macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show > up. > > Don’t know why it is required to have this package, as Lyx should supply > everything it needs to make all these conversions work. It’s a little bit more convoluted than you think. I’ve tried to disable rsvg-convert by making it a non-executable and the shell didn’t find it - but LyX detected it and couldn’t run it. So, it was not right to say, I’m having the same problem as you. My problem was to have a non-working rsvg-convert. Then I renamed rsvg-convert and the preview of SVG graphics snippets worked out-of-the-box again. Next I’ve installed inkscape 0.91 and immediately had your problem after reconfiguring LyX. LyX was able to find end execute inkscape but the converter script used contains a strange command line and the conversion failed because of it. The python script generated on the fly by LyX has two superfluous „$$p“ in front of the real path names of in and out files. # if os.system(r'inkscape --without-gui --file=$$p' + '"' + infile + '"' + ' --export-png=$$p' + '"' + outfile + '"' + '') != 0: This is a consequence of the auto detected converter configuration line in ~/Library/Application\ Support/LyX-2.3/lyxrc.defaults \converter svgpng"inkscape --without-gui --file=$$p$$i --export-png=$$p$$o""", I’m not sure how this should work - obviously it doesn’t work. It would be good to file a trac ticket about this issue. Stephan > > Just thought I would let you and others following this thread that this is > what made it work (for me anyway). > > > Regards, > > Bob > > > PROFESSOR ROBERT BETZ > School of Electrical Engineering and Computing > Faculty of Engineering and Built Environment > > T: +61 2 4921 6091 > M: +61 (0)419 249 948 > E: robert.b...@newcastle.edu.au > > The University of Newcastle (UoN) > University Drive > Callaghan NSW 2308 > Australia > > CRICOS Provider 00109J > > > > >> On 23 Dec 2018, at 3:06 pm, Anders Ekberg wrote: >> >>> >>> On 23 Dec 2018, at 13:05, Stephan Witt wrote: >>> >>> Am 22.12.2018 um 23:59 schrieb Robert Betz : Daniel, I have tired all sorts of things on Mac OS X Mojave but I cannot get either SVG or SVGZ files to render in Lyx. Just get error generating loadable format. I was wondering if any other users on Mac OS X Mojave are having problems with rendering SVG and/or SVGZ? An easy way to test this is to load up the User Manual in Lyx and scroll down until you hit the small svgs snippets in the text (used to store pictures of screen buttons in the file). >>> >>> I’m sure it worked for me in the past. So I gave it a try on Mojave and it >>> works. >>> >>> Then I tried to break it and this is easy. My converter configuration does >>> the SVG to PNG conversion with rsvg-convert because I’ve installed it from >>> MacPorts. But the idea was to have a reasonable fallback for those not >>> having it. It looks like not working anymore. I changed my system to make >>> rsvg-convert unavailable and now I cannot display SVG anymore too. >>> >>> I’ll investigate the issue and report back. >>> >>> Stephan >> >> F.Y.I. svgs in the LyX 2.3.2 User’s guide do not render for me on Mojave >> with Inkscape installed, but no special converters defined. (No idea how it >> was before upgrading though…) >> >> /Anders >> >> >>> @Daniel: Does it work on Windows without inkscape? >>> Thanks. Regards, Bob PROFESSOR ROBERT BETZ School of Electrical Engineering and Computing Faculty of Engineering and Built Environment T: +61 2 4921 6091 M: +61 (0)419 249 948 E: robert.b...@newcastle.edu.au The University of Newcastle (UoN) University Drive Callaghan NSW 2308 Australia CRICOS Provider 00109J > On 20 Dec 2018, at 2:20 pm, Daniel wrote: > > On 20/12/2018 12:00, Robert Betz wrote: >> I don’t know whether anyone else is having trouble with the snippets in >> the Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the >> svgz snippets all get errors as below >> I anyone else having this problem. The Inkscape converter seems to be >> having problems with these. Works fine in Ubuntu. >> Regards, >> Bob > > Works fine under Win10. > > Daniel >
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am Sonntag, 23. Dezember 2018 21:13:49 CET schrieb Kornel Benko : > Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel : > > On 23/12/2018 20:52, Kornel Benko wrote: > > > Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel > > > : > > >> On 23/12/2018 20:27, Kornel Benko wrote: > > >>> Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz > > >>> : > > Anders, > > > > Stephen Witt mentioned that he was using RSVG-convert. So I > > installed, using macports librsvg. I did a reconfigure on Lyx, and > > now the svgz snippets show up. > > > > Don’t know why it is required to have this package, as Lyx should > > supply everything it needs to make all these conversions work. > > >>> > > >>> No. > > >>> rsvg-convert is independent of lyx, as is also inkscape or any other > > >>> executable. > > >> > > >> While Inkscape is not provided with LyX, rsvg-convert is, at least on > > >> Windows. > > >> > > >> Daniel > > >> > > > > > > By lyx? (If yes, then I think that is not OK, since it is not a program > > > we created). > > > > I am pretty sure by LyX since it is in the LyX bin directory. > > > > (I guess it is OK as long as no licenses are violates. On Windows, which > > has no package dependency system like some Linux distributions, it is > > pretty common that applications come with such helper applications, > > especially for open source software.) > > > > Daniel > > > > I am surprised. Riki, is that part of our installation script? > > Kornel > OK, found a file with a list of executables development/Win32/packaging/installer/include/filelist.nsh. Very strange policy for a unix user. Kornel signature.asc Description: This is a digitally signed message part.
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am Sonntag, 23. Dezember 2018 21:07:50 CET schrieb Daniel : > On 23/12/2018 20:52, Kornel Benko wrote: > > Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : > >> On 23/12/2018 20:27, Kornel Benko wrote: > >>> Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz > >>> : > Anders, > > Stephen Witt mentioned that he was using RSVG-convert. So I installed, > using macports librsvg. I did a reconfigure on Lyx, and now the svgz > snippets show up. > > Don’t know why it is required to have this package, as Lyx should supply > everything it needs to make all these conversions work. > >>> > >>> No. > >>> rsvg-convert is independent of lyx, as is also inkscape or any other > >>> executable. > >> > >> While Inkscape is not provided with LyX, rsvg-convert is, at least on > >> Windows. > >> > >> Daniel > >> > > > > By lyx? (If yes, then I think that is not OK, since it is not a program we > > created). > > I am pretty sure by LyX since it is in the LyX bin directory. > > (I guess it is OK as long as no licenses are violates. On Windows, which > has no package dependency system like some Linux distributions, it is > pretty common that applications come with such helper applications, > especially for open source software.) > > Daniel > I am surprised. Riki, is that part of our installation script? Kornel signature.asc Description: This is a digitally signed message part.
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 23/12/2018 20:52, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : On 23/12/2018 20:27, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz : Anders, Stephen Witt mentioned that he was using RSVG-convert. So I installed, using macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show up. Don’t know why it is required to have this package, as Lyx should supply everything it needs to make all these conversions work. No. rsvg-convert is independent of lyx, as is also inkscape or any other executable. While Inkscape is not provided with LyX, rsvg-convert is, at least on Windows. Daniel By lyx? (If yes, then I think that is not OK, since it is not a program we created). I am pretty sure by LyX since it is in the LyX bin directory. (I guess it is OK as long as no licenses are violates. On Windows, which has no package dependency system like some Linux distributions, it is pretty common that applications come with such helper applications, especially for open source software.) Daniel
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am Sonntag, 23. Dezember 2018 20:34:39 CET schrieb Daniel : > On 23/12/2018 20:27, Kornel Benko wrote: > > Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz > > : > >> Anders, > >> > >> Stephen Witt mentioned that he was using RSVG-convert. So I installed, > >> using macports librsvg. I did a reconfigure on Lyx, and now the svgz > >> snippets show up. > >> > >> Don’t know why it is required to have this package, as Lyx should supply > >> everything it needs to make all these conversions work. > > > > No. > > rsvg-convert is independent of lyx, as is also inkscape or any other > > executable. > > While Inkscape is not provided with LyX, rsvg-convert is, at least on > Windows. > > Daniel > By lyx? (If yes, then I think that is not OK, since it is not a program we created). Kornel signature.asc Description: This is a digitally signed message part.
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 23/12/2018 20:27, Kornel Benko wrote: Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz : Anders, Stephen Witt mentioned that he was using RSVG-convert. So I installed, using macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show up. Don’t know why it is required to have this package, as Lyx should supply everything it needs to make all these conversions work. No. rsvg-convert is independent of lyx, as is also inkscape or any other executable. While Inkscape is not provided with LyX, rsvg-convert is, at least on Windows. Daniel
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am Sonntag, 23. Dezember 2018 18:28:57 CET schrieb Robert Betz : > Anders, > > Stephen Witt mentioned that he was using RSVG-convert. So I installed, using > macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show > up. > > Don’t know why it is required to have this package, as Lyx should supply > everything it needs to make all these conversions work. No. rsvg-convert is independent of lyx, as is also inkscape or any other executable. > Just thought I would let you and others following this thread that this is > what made it work (for me anyway). > Others reported problem with rsvg-convert, for them was inkscape the solution. We try to find a suitable executables existing on the users platform, so as to not mess with other existing workflows there. > Regards, > > Bob Kornel signature.asc Description: This is a digitally signed message part.
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Anders, Stephen Witt mentioned that he was using RSVG-convert. So I installed, using macports librsvg. I did a reconfigure on Lyx, and now the svgz snippets show up. Don’t know why it is required to have this package, as Lyx should supply everything it needs to make all these conversions work. Just thought I would let you and others following this thread that this is what made it work (for me anyway). Regards, Bob PROFESSOR ROBERT BETZ School of Electrical Engineering and Computing Faculty of Engineering and Built Environment T: +61 2 4921 6091 M: +61 (0)419 249 948 E: robert.b...@newcastle.edu.au The University of Newcastle (UoN) University Drive Callaghan NSW 2308 Australia CRICOS Provider 00109J > On 23 Dec 2018, at 3:06 pm, Anders Ekberg wrote: > >> >> On 23 Dec 2018, at 13:05, Stephan Witt wrote: >> >> Am 22.12.2018 um 23:59 schrieb Robert Betz : >>> >>> Daniel, >>> >>> I have tired all sorts of things on Mac OS X Mojave but I cannot get either >>> SVG or SVGZ files to render in Lyx. Just get error generating loadable >>> format. >>> >>> I was wondering if any other users on Mac OS X Mojave are having problems >>> with rendering SVG and/or SVGZ? An easy way to test this is to load up the >>> User Manual in Lyx and scroll down until you hit the small svgs snippets in >>> the text (used to store pictures of screen buttons in the file). >> >> I’m sure it worked for me in the past. So I gave it a try on Mojave and it >> works. >> >> Then I tried to break it and this is easy. My converter configuration does >> the SVG to PNG conversion with rsvg-convert because I’ve installed it from >> MacPorts. But the idea was to have a reasonable fallback for those not >> having it. It looks like not working anymore. I changed my system to make >> rsvg-convert unavailable and now I cannot display SVG anymore too. >> >> I’ll investigate the issue and report back. >> >> Stephan > > F.Y.I. svgs in the LyX 2.3.2 User’s guide do not render for me on Mojave with > Inkscape installed, but no special converters defined. (No idea how it was > before upgrading though…) > > /Anders > > >> @Daniel: Does it work on Windows without inkscape? >> >>> >>> Thanks. >>> >>> >>> Regards, >>> >>> Bob >>> >>> >>> PROFESSOR ROBERT BETZ >>> School of Electrical Engineering and Computing >>> Faculty of Engineering and Built Environment >>> >>> T: +61 2 4921 6091 >>> M: +61 (0)419 249 948 >>> E: robert.b...@newcastle.edu.au >>> >>> The University of Newcastle (UoN) >>> University Drive >>> Callaghan NSW 2308 >>> Australia >>> >>> CRICOS Provider 00109J >>> >>> >>> >>> On 20 Dec 2018, at 2:20 pm, Daniel wrote: On 20/12/2018 12:00, Robert Betz wrote: > I don’t know whether anyone else is having trouble with the snippets in > the Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz > snippets all get errors as below > I anyone else having this problem. The Inkscape converter seems to be > having problems with these. Works fine in Ubuntu. > Regards, > Bob Works fine under Win10. Daniel smime.p7s Description: S/MIME cryptographic signature
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Anders, That is the configuration that I have — I have Inkscape installed, and this is the File Converter that is being used for SVG and SVGZ files. I ran Lyx in debug mode and I could see that there was some sort of a failure surrounding using Inkscape as the converter. As I understand it, Inkscape is installed as part of the Lyx installation, so I assumed that it is using its own local copy. Is there an alternative way to set this up so that another render engine is used that works? Thanks is advance for any advice. Regards, Bob PROFESSOR ROBERT BETZ School of Electrical Engineering and Computing Faculty of Engineering and Built Environment T: +61 2 4921 6091 M: +61 (0)419 249 948 E: robert.b...@newcastle.edu.au The University of Newcastle (UoN) University Drive Callaghan NSW 2308 Australia CRICOS Provider 00109J > On 23 Dec 2018, at 3:06 pm, Anders Ekberg wrote: > >> >> On 23 Dec 2018, at 13:05, Stephan Witt wrote: >> >> Am 22.12.2018 um 23:59 schrieb Robert Betz : >>> >>> Daniel, >>> >>> I have tired all sorts of things on Mac OS X Mojave but I cannot get either >>> SVG or SVGZ files to render in Lyx. Just get error generating loadable >>> format. >>> >>> I was wondering if any other users on Mac OS X Mojave are having problems >>> with rendering SVG and/or SVGZ? An easy way to test this is to load up the >>> User Manual in Lyx and scroll down until you hit the small svgs snippets in >>> the text (used to store pictures of screen buttons in the file). >> >> I’m sure it worked for me in the past. So I gave it a try on Mojave and it >> works. >> >> Then I tried to break it and this is easy. My converter configuration does >> the SVG to PNG conversion with rsvg-convert because I’ve installed it from >> MacPorts. But the idea was to have a reasonable fallback for those not >> having it. It looks like not working anymore. I changed my system to make >> rsvg-convert unavailable and now I cannot display SVG anymore too. >> >> I’ll investigate the issue and report back. >> >> Stephan > > F.Y.I. svgs in the LyX 2.3.2 User’s guide do not render for me on Mojave with > Inkscape installed, but no special converters defined. (No idea how it was > before upgrading though…) > > /Anders > > >> @Daniel: Does it work on Windows without inkscape? >> >>> >>> Thanks. >>> >>> >>> Regards, >>> >>> Bob >>> >>> >>> PROFESSOR ROBERT BETZ >>> School of Electrical Engineering and Computing >>> Faculty of Engineering and Built Environment >>> >>> T: +61 2 4921 6091 >>> M: +61 (0)419 249 948 >>> E: robert.b...@newcastle.edu.au >>> >>> The University of Newcastle (UoN) >>> University Drive >>> Callaghan NSW 2308 >>> Australia >>> >>> CRICOS Provider 00109J >>> >>> >>> >>> On 20 Dec 2018, at 2:20 pm, Daniel wrote: On 20/12/2018 12:00, Robert Betz wrote: > I don’t know whether anyone else is having trouble with the snippets in > the Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz > snippets all get errors as below > I anyone else having this problem. The Inkscape converter seems to be > having problems with these. Works fine in Ubuntu. > Regards, > Bob Works fine under Win10. Daniel smime.p7s Description: S/MIME cryptographic signature
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
> On 23 Dec 2018, at 13:05, Stephan Witt wrote: > > Am 22.12.2018 um 23:59 schrieb Robert Betz : >> >> Daniel, >> >> I have tired all sorts of things on Mac OS X Mojave but I cannot get either >> SVG or SVGZ files to render in Lyx. Just get error generating loadable >> format. >> >> I was wondering if any other users on Mac OS X Mojave are having problems >> with rendering SVG and/or SVGZ? An easy way to test this is to load up the >> User Manual in Lyx and scroll down until you hit the small svgs snippets in >> the text (used to store pictures of screen buttons in the file). > > I’m sure it worked for me in the past. So I gave it a try on Mojave and it > works. > > Then I tried to break it and this is easy. My converter configuration does > the SVG to PNG conversion with rsvg-convert because I’ve installed it from > MacPorts. But the idea was to have a reasonable fallback for those not having > it. It looks like not working anymore. I changed my system to make > rsvg-convert unavailable and now I cannot display SVG anymore too. > > I’ll investigate the issue and report back. > > Stephan F.Y.I. svgs in the LyX 2.3.2 User’s guide do not render for me on Mojave with Inkscape installed, but no special converters defined. (No idea how it was before upgrading though…) /Anders > @Daniel: Does it work on Windows without inkscape? > >> >> Thanks. >> >> >> Regards, >> >> Bob >> >> >> PROFESSOR ROBERT BETZ >> School of Electrical Engineering and Computing >> Faculty of Engineering and Built Environment >> >> T: +61 2 4921 6091 >> M: +61 (0)419 249 948 >> E: robert.b...@newcastle.edu.au >> >> The University of Newcastle (UoN) >> University Drive >> Callaghan NSW 2308 >> Australia >> >> CRICOS Provider 00109J >> >> >> >> >>> On 20 Dec 2018, at 2:20 pm, Daniel wrote: >>> >>> On 20/12/2018 12:00, Robert Betz wrote: I don’t know whether anyone else is having trouble with the snippets in the Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz snippets all get errors as below I anyone else having this problem. The Inkscape converter seems to be having problems with these. Works fine in Ubuntu. Regards, Bob >>> >>> Works fine under Win10. >>> >>> Daniel >>> >>> >> >
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Am 22.12.2018 um 23:59 schrieb Robert Betz : > > Daniel, > > I have tired all sorts of things on Mac OS X Mojave but I cannot get either > SVG or SVGZ files to render in Lyx. Just get error generating loadable > format. > > I was wondering if any other users on Mac OS X Mojave are having problems > with rendering SVG and/or SVGZ? An easy way to test this is to load up the > User Manual in Lyx and scroll down until you hit the small svgs snippets in > the text (used to store pictures of screen buttons in the file). I’m sure it worked for me in the past. So I gave it a try on Mojave and it works. Then I tried to break it and this is easy. My converter configuration does the SVG to PNG conversion with rsvg-convert because I’ve installed it from MacPorts. But the idea was to have a reasonable fallback for those not having it. It looks like not working anymore. I changed my system to make rsvg-convert unavailable and now I cannot display SVG anymore too. I’ll investigate the issue and report back. Stephan @Daniel: Does it work on Windows without inkscape? > > Thanks. > > > Regards, > > Bob > > > PROFESSOR ROBERT BETZ > School of Electrical Engineering and Computing > Faculty of Engineering and Built Environment > > T: +61 2 4921 6091 > M: +61 (0)419 249 948 > E: robert.b...@newcastle.edu.au > > The University of Newcastle (UoN) > University Drive > Callaghan NSW 2308 > Australia > > CRICOS Provider 00109J > > > > >> On 20 Dec 2018, at 2:20 pm, Daniel wrote: >> >> On 20/12/2018 12:00, Robert Betz wrote: >>> I don’t know whether anyone else is having trouble with the snippets in the >>> Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz >>> snippets all get errors as below >>> I anyone else having this problem. The Inkscape converter seems to be >>> having problems with these. Works fine in Ubuntu. >>> Regards, >>> Bob >> >> Works fine under Win10. >> >> Daniel >> >> >
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
Daniel, I have tired all sorts of things on Mac OS X Mojave but I cannot get either SVG or SVGZ files to render in Lyx. Just get error generating loadable format. I was wondering if any other users on Mac OS X Mojave are having problems with rendering SVG and/or SVGZ? An easy way to test this is to load up the User Manual in Lyx and scroll down until you hit the small svgs snippets in the text (used to store pictures of screen buttons in the file). Thanks. Regards, Bob PROFESSOR ROBERT BETZ School of Electrical Engineering and Computing Faculty of Engineering and Built Environment T: +61 2 4921 6091 M: +61 (0)419 249 948 E: robert.b...@newcastle.edu.au The University of Newcastle (UoN) University Drive Callaghan NSW 2308 Australia CRICOS Provider 00109J > On 20 Dec 2018, at 2:20 pm, Daniel wrote: > > On 20/12/2018 12:00, Robert Betz wrote: >> I don’t know whether anyone else is having trouble with the snippets in the >> Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz >> snippets all get errors as below >> I anyone else having this problem. The Inkscape converter seems to be >> having problems with these. Works fine in Ubuntu. >> Regards, >> Bob > > Works fine under Win10. > > Daniel > > smime.p7s Description: S/MIME cryptographic signature
Re: Lyx V2.3.2 - Issues with svgs snippets on Mac OS X
On 20/12/2018 12:00, Robert Betz wrote: I don’t know whether anyone else is having trouble with the snippets in the Lyx User Guide, but on my Machine (Mac OS X V10.14.2 Mojave) the svgz snippets all get errors as below I anyone else having this problem. The Inkscape converter seems to be having problems with these. Works fine in Ubuntu. Regards, Bob Works fine under Win10. Daniel
