![]() Obviously, you will have to be consistent and correct in replacing all, particularly the highlighted parts, here (bold, orange) with your own file and path names. So I then defined such a script following T3.’s recommendation: at the directory with the path C:\Users\ ownusername\ DocumentsI placed a text file that I generated myself and that I named viewpdf.bat, into which I placed the following single “ C:/Program Files (x86)/Adobe/Acrobat Reader DC/Reader/AcroRd32.exe” “%~f1” That command would hand over the file path as %, to a script called viewpdf.bat “ C:/Users/ ownusername/ Documents/viewpdf.bat” %.pdf on the Latex.Org forum:ĭefine the command “External viewer” inside TexMaker > Configure TexMaker as follows: #TEXMAKER WINDOWS FULL#So it seems the underlying problem was identified on the forum by T3., in that Adobe Acrobat apparently requires a full file path to open PDFs, and as these seemed to only sometimes get transmitted correctly using the TexMaker interface settings, the workaround that I found worked is as recommended by T3. #TEXMAKER WINDOWS PDF#This points to a problem not along the lines of PDF file missing – that was there all along – but somewhere between TexMaker and Acrobat Reader. ![]() My problem was that not only did the TexMaker program not correctly process a Quick Build made of PDFLaTeX>View PDF, but also, it failed to reliably and always open any existing PDF using the View PDF (F7) command – so, with a PDF safely generated and in place of its file/folder path, repeatedly pressing F7, slowly, then closing the file again, trying again, would not always open the file, only sometimes. As these forums are a bit problematic to enter and register, particularly stackexchange requires some credits before any solution can be posted there, I just put this on my own website here. ![]() The problem was recognized elsewhere, to different degrees.Įven though the problems were described, a missing test remained and that was whether PDFs that did not require prior generation/ building because they were already generated / built would also succumb to this problem. ![]() The problem seems to be that TexMaker fails to reliably open PDF files that it generated using Acrobat Reader as external viewer under Windows 10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |