Re: 2.4.0~RC1 hangs on macOS
Thanks, el. Getting rid of macports for homebrew is not an option for me. In my profile file, I have this: alias python=/opt/local/bin/python3 which is macports. Does LyX see this? This alias points to Python 3.9.18. There is a utility to switch to other versions. I already have the command line tools installed, with Python 3.9.6 at /usr/bin/phython3. I just now tried switching to this line in my profile file: alias python=/usr/bin/python3 with the same result. Remember that LyX 2.3.7 works fine. Jerry > On Jan 24, 2024, at 12:10 AM, Dr Eberhard Lisse wrote: > > Unload the macports python and install the XCode Command line tools > which has Python 3.9.6 in /usr/bin/python3. > > If that works, perhaps even unload Macports and install Homebrew. If > you have many packages installed, make a list. > > I use Homebrew including basictex (plus some addtional stuff) and copied > 2.4 RC1 over the 2.3.7 provided from Homebrew. On Ventura and Sonoma (on > the latter on Intel and Silicon) > > greetings, el > > On 2024-01-24 01:51 , list_em...@icloud.com wrote: > [...] While LyX is hanging as above, Activity Monitor indicates that LyX has launched one instance of Python and repeatedly launches and stops a second instance. My current Python is 3.9 but versions up to 3.12 are installed by macports. LyX 2.3.7 still works. I notice that I got this version through MacPorts. I just now updated all my macports stuff which includes Python and texlive. 2.4 still hangs on launch. > [...] > > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0~RC1 hangs on macOS
Unload the macports python and install the XCode Command line tools which has Python 3.9.6 in /usr/bin/python3. If that works, perhaps even unload Macports and install Homebrew. If you have many packages installed, make a list. I use Homebrew including basictex (plus some addtional stuff) and copied 2.4 RC1 over the 2.3.7 provided from Homebrew. On Ventura and Sonoma (on the latter on Intel and Silicon) greetings, el On 2024-01-24 01:51 , list_em...@icloud.com wrote: [...] >>> While LyX is hanging as above, Activity Monitor indicates that >>> LyX has launched one instance of Python and repeatedly launches >>> and stops a second instance. My current Python is 3.9 but >>> versions up to 3.12 are installed by macports. >>> >>> LyX 2.3.7 still works. I notice that I got this version through >>> MacPorts. >>> >>> I just now updated all my macports stuff which includes Python >>> and texlive. 2.4 still hangs on launch. [...] -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0~RC1 hangs on macOS
Unload the macports python and install the XCode Command line tools which has Python 3.9.6 in /usr/bin/python3. If that works, perhaps even unload Macports and install Homebrew. If you have many packages installed, make a list. I use Homebrew including basictex (plus some addtional stuff) and copied 2.4 RC1 over the 2.3.7 provided from Homebrew. On Ventura and Sonoma (on the latter on Intel and Silicon) greetings, el On 2024-01-24 01:51 , list_em...@icloud.com wrote: [...] >>> While LyX is hanging as above, Activity Monitor indicates that >>> LyX has launched one instance of Python and repeatedly launches >>> and stops a second instance. My current Python is 3.9 but >>> versions up to 3.12 are installed by macports. >>> >>> LyX 2.3.7 still works. I notice that I got this version through >>> MacPorts. >>> >>> I just now updated all my macports stuff which includes Python >>> and texlive. 2.4 still hangs on launch. [...] -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: 2.4.0~RC1 hangs on macOS
Main notes listed inline below. Jerry > On Jan 20, 2024, at 11:14 PM, Richard Kimberly Heck > wrote: > > On 1/20/24 18:08, list_em...@icloud.com wrote: >> Thanks, el. >> >> I did as you suggested but there was no improvement and little change to the >> problem. As the rapidly cycling status messages continue in the Welcome >> file, I am able to start a new file and make a PDF of it. But I can’t close >> either the new (unsaved) file or the Welcome file because it says it can’t >> quit because of a background process. Normal quitting method has the same >> result. Clicking on the spinning circle or red dot has no effect. I tried >> this multiple times, each time deleting the Support file as you suggested. >> >> Next, I deleted the app as well as these: >> >> org.lyx.LyX-2.4.plist >> org.lyx.lyx.plist >> org.lyx.lyx.savedState (a folder) >> >> and re-downloaded and re-launched the app. Now the behavior is worse, >> getting only the app main menu with Apple logo and “LyX” item, and then >> nothing but pinwheeling. It doesn’t even open the Welcome file or finish >> drawing the main menu. I put the three deleted items back but it still hangs >> on launch. Definitely going in the wrong direction here. >> >> While LyX is hanging as above, Activity Monitor indicates that LyX has >> launched one instance of Python and repeatedly launches and stops a second >> instance. My current Python is 3.9 but versions up to 3.12 are installed by >> macports. >> >> LyX 2.3.7 still works. I notice that I got this version through MacPorts. >> >> I just now updated all my macports stuff which includes Python and texlive. >> 2.4 still hangs on launch. > > I'm going to guess a few things here. > > I guess the first problem is the hanging on launch. LyX can seem to hang when > it's reconfiguring. Deleting the user directory will have forced this. One > symptom of this would be seeing various LaTeX-related processes being called > over and over again. I have (now) had LyX hanging on launch for about two hours with the behavior described earlier. I see two Pythons which re-launch every few seconds. I also see pdftex starting and quitting every few seconds. For the pdftex process, Activity Monitor lists a Python as the parent process and the Process Group as LyX. > > If you can get LyX to launch, then we need to find out what this process is > that's stopping LyX from closing. Do you have images in the documents you're > opening? Lots of math? If the latter, are you using math preview? Or is this > just a basic document? As above, LyX won’t finish launching. I believe it is trying to open only the Welcome file. There is a slight possibility that it is also trying to open a test document that I tried earlier (and described earlier in this thread) but which was open when I force-quit LyX but had not been saved to disk. This test was only a default new file with only a few words of text, which at the time did create a PDF. > > Another possibility is that the PDF creation process is not exiting properly. > I'm not sure how to debug that. Again, a symptom would be some LaTeX process > still running. > > One thing that might help (with both problems) is if you could start LyX from > a terminal and post the output. This should let us see what processes LyX is > launching, and where things are getting stuck. OK. See the attached text file. This is a portion of the output after maybe five seconds. This portion, beginning with LyX: reconfiguring user directory repeats about once a second or two. I suppose this is the same frequency as the Python and pdftex repeating things mentioned above. The only thing that I see odd in this output is that it does not see my Firefox or BibDesk apps. Jerry MBP:~ me$ /Applications/LyX.app/Contents/MacOS/lyx qt.qpa.fonts: Populating font family aliases took 250 ms. Replace uses of missing font family "Serif" with one that exists to avoid this cost. LyX: reconfiguring user directory +Running LyX configure with Python 3.9.18 checking for a Latex2e program... +checking for "latex"... yes checking for pLaTeX, the Japanese LaTeX... +checking for "platex"... not in path checking for a java interpreter... +checking for "java"... yes checking for a perl interpreter... +checking for "perl"... yes checking for xsltproc... +checking for "xsltproc"... yes Could not find Inkscape binary. /bin/sh: inkscape-binary: command not found checking for a Tgif viewer and editor... +checking for "tgif"... no checking for a FIG viewer and editor... +checking for "xfig"... no +checking for "jfig3-itext.jar"... no +checking for "jfig3.jar"... no checking for a Dia viewer and editor... +checking for "dia"... no checking for an OpenDocument drawing viewer and editor... +checking for "libreoffice"... no +checking for "lodraw"... no +checking for "ooffice"... no +checking for "oodraw"... no +checking for "soffice"... no checking for a Grace viewer and editor...
Re: Graphics Conversion
On Tue, 23 Jan 2024 at 18:35, Pavel Sanda wrote: > On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote: > > pdftoppm -r 72 -png -singlefile $$i > $$o > > This is new route in 2.4 which can be used to avoid IM problems in linux. > We perhaps triggerred unnecessary problems on Windows. > This could be sovled by making pdftoppm addition conditional on IM fail. > > And we should perhaps chech, whether accented characters are not problem > on linux too... > > Could anyone on Windows post the output of Reconfigure command (you should > be > able to see that list in Messages pane)? > Here it is, copied from the Messages pane. It's really from Reconfigure, as the first call to configure.py happens with the installer. 21:13:12.436: (dialog-show aboutlyx) 21:13:17.534: Running configure... 21:13:17.664: python -tt "C:/Program Files/LyX 2.4/Resources/configure.py" --binary-dir="C:/Program Files/LyX 2.4/bin/" 21:13:17.768: +Running LyX configure with Python 3.11.2 21:13:17.770: checking for DVI to DTL converter... 21:13:17.774: +checking for "dv2dt"... yes 21:13:17.775: checking for DTL to DVI converter... 21:13:17.778: +checking for "dt2dv"... yes 21:13:17.779: checking for a Latex2e program... 21:13:17.780: +checking for "latex"... yes 21:13:17.781: checking for pLaTeX, the Japanese LaTeX... 21:13:17.781: +checking for "platex"... yes 21:13:44.327: (guessed encoding #3: ASCII = utf8)checking for a java interpreter... 21:13:44.332: +checking for "java"... yes 21:13:44.333: checking for a perl interpreter... 21:13:44.343: +checking for "perl"... yes 21:13:44.345: checking for xsltproc... 21:13:44.354: +checking for "xsltproc"... yes 21:13:45.988: checking for a Tgif viewer and editor... 21:13:46.003: +checking for "tgif"... no 21:13:46.004: checking for a FIG viewer and editor... 21:13:46.018: +checking for "xfig"... no 21:13:46.034: +checking for "jfig3-itext.jar"... no 21:13:46.049: +checking for "jfig3.jar"... no 21:13:46.051: checking for a Dia viewer and editor... 21:13:46.065: +checking for "dia"... no 21:13:46.066: checking for an OpenDocument drawing viewer and editor... 21:13:46.080: +checking for "libreoffice"... no 21:13:46.096: +checking for "lodraw"... no 21:13:46.111: +checking for "ooffice"... no 21:13:46.126: +checking for "oodraw"... no 21:13:46.142: +checking for "soffice"... no 21:13:46.144: checking for a Grace viewer and editor... 21:13:46.157: +checking for "xmgrace"... no 21:13:46.159: checking for a FEN viewer and editor... 21:13:46.176: +checking for "xboard"... no 21:13:46.178: checking for a SVG viewer and editor... 21:13:46.192: +checking for "inkscape.exe"... yes 21:13:46.193: checking for a raster image viewer... 21:13:46.209: +checking for "xv"... no 21:13:46.226: +checking for "gwenview"... no 21:13:46.242: +checking for "kview"... no 21:13:46.256: +checking for "eog"... no 21:13:46.271: +checking for "xviewer"... no 21:13:46.285: +checking for "ristretto"... no 21:13:46.300: +checking for "gpicview"... no 21:13:46.315: +checking for "lximage-qt"... no 21:13:46.329: +checking for "xdg-open"... no 21:13:46.344: +checking for "gimp-remote"... no 21:13:46.359: +checking for "gimp"... no 21:13:46.361: checking for a raster image editor... 21:13:46.374: +checking for "gimp-remote"... no 21:13:46.388: +checking for "gimp"... no 21:13:46.389: checking for a text editor... 21:13:46.404: +checking for "xemacs"... no 21:13:46.418: +checking for "gvim"... no 21:13:46.433: +checking for "kedit"... no 21:13:46.448: +checking for "kwrite"... no 21:13:46.463: +checking for "kate"... no 21:13:46.476: +checking for "nedit"... no 21:13:46.490: +checking for "gedit"... no 21:13:46.504: +checking for "geany"... no 21:13:46.519: +checking for "leafpad"... no 21:13:46.532: +checking for "mousepad"... no 21:13:46.552: +checking for "xed"... no 21:13:46.556: +checking for "notepad"... yes 21:13:46.571: +checking for "WinEdt"... no 21:13:46.587: +checking for "WinShell"... no 21:13:46.603: +checking for "PSPad"... no 21:13:46.604: checking for a lilypond editor... 21:13:46.618: +checking for "frescobaldi"... no 21:13:46.632: +checking for "xemacs"... no 21:13:46.646: +checking for "gvim"... no 21:13:46.659: +checking for "kedit"... no 21:13:46.674: +checking for "kwrite"... no 21:13:46.689: +checking for "kate"... no 21:13:46.704: +checking for "nedit"... no 21:13:46.721: +checking for "gedit"... no 21:13:46.736: +checking for "geany"... no 21:13:46.754: +checking for "leafpad"... no 21:13:46.771: +checking for "mousepad"... no 21:13:46.786: +checking for "xed"... no 21:13:46.792: +checking for "notepad"... yes 21:13:46.809: +checking for "WinEdt"... no 21:13:46.824: +checking for "WinShell"... no 21:13:46.838: +checking for "PSPad"... no 21:13:46.839: checking for gnumeric spreadsheet software... 21:13:46.854: +checking for "gnumeric"... no 21:13:46.856: checking for an HTML previewer... 21:13:46.869: +checking for
Re: RC1: Unable to read files with accents in names on Windows
On Tue, Jan 23, 2024 at 02:58:37PM -0500, Richard Kimberly Heck wrote: On 1/23/24 14:51, Enrico Forestieri wrote: On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote: The conversion script has: infile = "C:/Users/Thibaut/Desktop/p k .pdf" when the input file was: ~\Desktop\píkà.pdf. The accented characters have been stripped. This is not a surprise, though, since toFilesystemEncoding has a comment that says it does not work with non-ASCII characters on Windows. The puzzle is why this worked on 2.3.7. None of this code has changed, so far as I can see. Note that this might be a red herring. toFilesystemEncoding only encodes file names and not the content of a file that is utf8. The fact that the accented characters seem to have disappeared may simply be due to the fact the terminal on Windows is not able to display utf8 characters. So, the output should be redirected to a file to be sure. Can you explain to Didier how to do that on Windows? This may be impossible because the distributed version of lyx is a gui application and prints nothing to the terminal. Thibaut said he could reproduce. I'm reattaching his test files and logs. The logs were copied from the Messages pane, he said. Yes, I get the same mangled name in the message pane: infile = "C:/work/test/p�k�.pdf" but everything works fine for me. Seemingly, the problem with the message pane is peculiar to the Windows native version because on cygwin I instead correctly get: infile = "/c/work/test/píkà.pdf" However, I don't know why that is so. -- Enrico -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: RC1: Unable to read files with accents in names on Windows
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote: The conversion script has: infile = "C:/Users/Thibaut/Desktop/p k .pdf" when the input file was: ~\Desktop\píkà.pdf. The accented characters have been stripped. This is not a surprise, though, since toFilesystemEncoding has a comment that says it does not work with non-ASCII characters on Windows. The puzzle is why this worked on 2.3.7. None of this code has changed, so far as I can see. Note that this might be a red herring. toFilesystemEncoding only encodes file names and not the content of a file that is utf8. The fact that the accented characters seem to have disappeared may simply be due to the fact the terminal on Windows is not able to display utf8 characters. So, the output should be redirected to a file to be sure. -- Enrico -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Graphics Conversion
On 1/23/24 12:33, Pavel Sanda wrote: On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote: pdftoppm -r 72 -png -singlefile $$i > $$o This is new route in 2.4 which can be used to avoid IM problems in linux. We perhaps triggerred unnecessary problems on Windows. This could be sovled by making pdftoppm addition conditional on IM fail. The conversion on 2.3.7 is to EPS (according ot the posted logs), rather than PNG, which is why it works better. I'm not sure why we're choosing PNG instead on 2.4. On my system here, it chooses EPS. Didier, do you have a PDF to EPS converter listed in your 2.4 install? And we should perhaps chech, whether accented characters are not problem on linux too... It shouldn't be. This is the toFilesystemEncoding vs toSafeFilesystemEncoding issue again, where the former is known not to work with non-ASCII characters on Windows, whereas it does work (at least according to the comments) on *nix and derivatives. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: RC1: Unable to read files with accents in names on Windows
On Mon, Jan 22, 2024 at 06:21:42PM -0500, Richard Kimberly Heck wrote: On 1/22/24 17:53, Thibaut Cuvelier wrote: On Mon, 22 Jan 2024 at 23:00, Richard Kimberly Heck wrote: On 1/22/24 16:53, didiergab...@free.fr wrote: I also realize that I can no longer load images whose names contain accents. In any case, that’s what’s happening with the file I just sent you. If I rename the file: SchemaCinematique.pdf to SchemaCinématique.pdf then I can read “Error converting to a readable format.” That's a serious bug. Can anyone on Windows check this? I can reproduce with PDF files whose names have accents, but not PNG (with the same file name apart from the extension). If I export the file to LyX 2.3 and load it with LyX 2.3.7, the PDF file doesn't have any issue (with MikTeX, up to date). I'm attaching the logs (View > Messages Pane, with all logs enabled) and the corresponding test files (LyX 2.3 and 2.4). The conversion script has: infile = "C:/Users/Thibaut/Desktop/p k .pdf" when the input file was: ~\Desktop\píkà.pdf. The accented characters have been stripped. This is not a surprise, though, since toFilesystemEncoding has a comment that says it does not work with non-ASCII characters on Windows. The puzzle is why this worked on 2.3.7. None of this code has changed, so far as I can see. Enrico, do you know if there is a reason not to use toSafeFilesystemEncoding here instead? This is in GraphicsConverter.cpp, line 139. I am not able to reproduce the problem. We should try to understand what is the real issue before changing the source. -- Enrico -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Graphics Conversion
On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote: > pdftoppm -r 72 -png -singlefile $$i > $$o This is new route in 2.4 which can be used to avoid IM problems in linux. We perhaps triggerred unnecessary problems on Windows. This could be sovled by making pdftoppm addition conditional on IM fail. And we should perhaps chech, whether accented characters are not problem on linux too... Could anyone on Windows post the output of Reconfigure command (you should be able to see that list in Messages pane)? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Graphics Conversion
Here it is. Here is the command I can see under Tools> Preferences> File Handling> Converters, at the PDF to PNG converter: « pdftoppm -r 72 -png -singlefile $$i > $$o » as you said... I’ll try to increase the dpi ps : On these computer svg from inkscape preview is ok so good point. - Mail original - | On 1/23/24 04:06, didiergab...@free.fr wrote: | | I am currently in front of my Windows 10 PC at my workplace with | | which I am experiencing exactly the same symptoms. | | | I followed your instructions, and you will find the requested file | | attached. | | | I will do the same thing again this evening at home, with my | | personal | | computer. | | This is plenty good enough. The difference is indeed what converter | is being called. In your case, it looks to be low resolution. I'm | puzzled why this is different on 2.3.7. You could try running the | same test with it. That would tell us. | You could also look under Tools> Preferences> File Handling> | Converters, at the PDF to PNG converter. The command listed there | will be: | pdftoppm -r 72 -png -singlefile $$i > $$o | The -r 72 is controlling resolution. You could try increasing that. | | ps: The Schemacinematic.pdf document was created with inkscape... | | Which I sometimes export to pdf because I cannot activate, in the | | Lyx window, the preview of inkscape documents in the native svg | | format. However, adding an inkscape in float fig document works | | very | | well in pdfLaTex export, so I often do without the preview. Should | | the preview of inkscape svg documents be operational or is it a | | configuration problem / choice of settings that I made incorrectly? | | It should work. Here, the SVG to PNG converter is inkscape itself. | Maybe LyX is not finding it. Again, check the list of converters, | and see if you have anything for SVG. | Riki 18:13:11.027: (dialog-toggle progress) 18:13:35.144: Ouverture du document G:\CPGE\PTSI\DS\DS-2023-2024\DS3\MWE-PDF preview.23.lyx... 18:13:35.225: Document G:\CPGE\PTSI\DS\DS-2023-2024\DS3\MWE-PDF preview.23.lyx ouvert. 18:13:35.225: (file-open: Ctrl+O)Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (391): Recognised Fileformat: latex Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (391): Recognised Fileformat: latex Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (391): Recognised Fileformat: latex Format.cpp (507): will guess format from file extension: lyx -> lyx Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389): filetools(getFormatFromContents) File type not recognised before EOF! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (396): filetools(getFormatFromContents) Couldn't find a known format! Format.cpp (389):
Re: Graphics Conversion
On 1/23/24 04:06, didiergab...@free.fr wrote: I am currently in front of my Windows 10 PC at my workplace with which I am experiencing exactly the same symptoms. I followed your instructions, and you will find the requested file attached. I will do the same thing again this evening at home, with my personal computer. This is plenty good enough. The difference is indeed what converter is being called. In your case, it looks to be low resolution. I'm puzzled why this is different on 2.3.7. You could try running the same test with it. That would tell us. You could also look under Tools> Preferences> File Handling> Converters, at the PDF to PNG converter. The command listed there will be: pdftoppm -r 72 -png -singlefile $$i > $$o The -r 72 is controlling resolution. You could try increasing that. ps: The Schemacinematic.pdf document was created with inkscape... Which I sometimes export to pdf because I cannot activate, in the Lyx window, the preview of inkscape documents in the native svg format. However, adding an inkscape in float fig document works very well in pdfLaTex export, so I often do without the preview. Should the preview of inkscape svg documents be operational or is it a configuration problem / choice of settings that I made incorrectly? It should work. Here, the SVG to PNG converter is inkscape itself. Maybe LyX is not finding it. Again, check the list of converters, and see if you have anything for SVG. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Poor PDF preview quality - LyX 2.4.0, Release Candidate 1
There is the latexdiff tool, but I do not know if it works on WIidoze. el On 2024-01-22 23:13 , Jean-Marc Lasgouttes wrote: [...] > Different font, maybe ? Do you have the possibility to find what is the > difference between 2.4 LaTeX output and 2.3 LaTeX output ? [...] -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Poor PDF preview quality - LyX 2.4.0, Release Candidate 1
Didier, which export are you using? I like pdf5 (lualatex which is powerful and slow'ish) and then there is pdf4 (pdflatex). el On 2024-01-22 22:41 , didiergab...@free.fr wrote: > Hi, > > Compared to version 2.3.7 and from the default settings the > difference is obvious. The PDF (graphic) option is set to pdfview... > But by changing the parameters (custom, default system...) It's still > just as ugly... On the other hand, the pdflatex export is very good. > This is an installation under Windows 10. Do you have an idea? > > Didier > > ps: Thanks to the whole team for this great tool! > > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: ...
I am currently in front of my Windows 10 PC at my workplace with which I am experiencing exactly the same symptoms. I followed your instructions, and you will find the requested file attached. I will do the same thing again this evening at home, with my personal computer. ps: The Schemacinematic.pdf document was created with inkscape... Which I sometimes export to pdf because I cannot activate, in the Lyx window, the preview of inkscape documents in the native svg format. However, adding an inkscape in float fig document works very well in pdfLaTex export, so I often do without the preview. Should the preview of inkscape svg documents be operational or is it a configuration problem / choice of settings that I made incorrectly? - Mail original - | It looks OK here, though I see how bad the text is in yoru image. | Probably this is a matter of what program is being used to do the | conversion from PDF to something LyX can display. At this point, | that is all cached, so we need to clear that. If you go to your user | directory, you can clear out the cache subdirectory. | Then launch LyX and, before opening the file, go to View> Messages, | then in the pane that opens up, to Settings, choose to show | "Selected" messages, and select choose graphics. Then open the file, | and email the output in the messages pane. This will let us see what | programs are being called to do the conversion. | Riki | On 1/22/24 17:15, didiergab...@free.fr wrote: | | I may have expressed myself incorrectly... Exporting to pdf format | | is | | perfect for me too. It is the appearance of the preview in the lyx | | window which is very degraded compared to version 2.3.7 ps : | | | I am also attaching the screen copy in response to José Matos' | | question which is clearly not getting through... - Mail | | original | | - | | | | On 1/22/24 16:24, didiergab...@free.fr wrote: | | | | | | | Thank you for your reply. | | | | | | | | | I had to remove some things from your preamble to compile it, but | | | when I just took everything out of the preamble, I generated the | | | attached. It looks fine to me. Are you getting something | | | different? | | | | | | Riki | | | | -- | | Richard Kimberly (Riki) Heck | Professor of Philosophy | Brown University | Pronouns: they/them/their | Website: http://rkheck.frege.org/09:42:39.409: (dialog-toggle progress) 09:45:35.685: Ouverture du document G:\CPGE\PTSI\DS\DS-2023-2024\DS3\MWE-PDF preview.lyx... 09:45:35.773: Document G:\CPGE\PTSI\DS\DS-2023-2024\DS3\MWE-PDF preview.lyx ouvert. 09:45:35.773: (file-open: Ctrl+O)insets\InsetGraphics.cpp (161): Token: 'filename' insets\InsetGraphics.cpp (161): Token: 'lyxscale' insets\InsetGraphics.cpp (161): Token: 'width' insets\InsetGraphics.cpp (161): Token: '\end_inset' insets\InsetGraphics.cpp (161): Token: 'filename' insets\InsetGraphics.cpp (161): Token: 'width' insets\InsetGraphics.cpp (161): Token: '\end_inset' support/lyxmagic.h (67): Magic: libmagic support not configured Format.cpp (372): Recognised Fileformat: latex Format.cpp (473): will guess format from file extension: lyx -> lyx Format.cpp (372): Recognised Fileformat: pdf6 graphics\GraphicsCacheItem.cpp (391): [CacheItem::Impl::convertToDisplayFormat] Attempting to convert image file: G:/CPGE/PTSI/DS/DS-2023-2024/DS3/Docs/SchemaCinematique.pdf with displayed filename: G:\CPGE\PTSI\DS\DS-2023-2024\DS3\Docs\SchemaCinematique.pdf Format.cpp (372): Recognised Fileformat: pdf6 graphics\GraphicsCacheItem.cpp (398): The file contains pdf6 format data. frontends\qt\GuiApplication.cpp (264): The image loader can load the following directly: frontends\qt\GuiApplication.cpp (273): bmp, frontends\qt\GuiApplication.cpp (273): cur, frontends\qt\GuiApplication.cpp (273): gif, frontends\qt\GuiApplication.cpp (273): ico, frontends\qt\GuiApplication.cpp (273): jpeg, frontends\qt\GuiApplication.cpp (273): jpg, frontends\qt\GuiApplication.cpp (273): pbm, frontends\qt\GuiApplication.cpp (273): pgm, frontends\qt\GuiApplication.cpp (273): png, frontends\qt\GuiApplication.cpp (273): ppm, frontends\qt\GuiApplication.cpp (273): svg, frontends\qt\GuiApplication.cpp (273): svgz, frontends\qt\GuiApplication.cpp (273): xbm, frontends\qt\GuiApplication.cpp (273): xpm, graphics\GraphicsCache.cpp (81): LyX recognises the following image formats: graphics\GraphicsCache.cpp (83): bmp, graphics\GraphicsCache.cpp (83): gif, graphics\GraphicsCache.cpp (83): jpg, graphics\GraphicsCache.cpp (83): pbm, graphics\GraphicsCache.cpp (83): pgm, graphics\GraphicsCache.cpp (83): png, graphics\GraphicsCache.cpp (83): ppm, graphics\GraphicsCache.cpp (83): xbm, graphics\GraphicsCache.cpp (83): xpm, graphics\GraphicsCacheItem.cpp (347): Unable to convert from pdf6 to bmp graphics\GraphicsCacheItem.cpp (347): Unable to convert from pdf6 to gif graphics\GraphicsCacheItem.cpp (347): Unable to convert from pdf6 to jpg
