在端的更新
在经历了非常痛苦的更新过程之后,很大程度上是因为PDF导出使用了XeLaTeX,而我一直倾向于使用LaTeX,所以需要不同的包).
(重要的是:我认为pandoc希望在软件包MS中找到everyshi.sty,但如CTAN所报道不再在该包中)
PDF创建失败,此信息来自服务器:
notebook.tex:1678: Unable to load picture or PDF file '
dvipdfmx:fatal: Image inclusion failed for "attachment:9e002d53-d7a5-42e1-8b51-0fdec8f4dad5.png".
No output PDF file written.
Sorry, but xelatex did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:\Users\usernamehere\AppData\Local\MiKTeX\2.9\miktex\log\xelatex.log
xelatax.log显示:
2021-06-10 08:02:26,620+0100 INFO xelatex.core - start process: miktex-dvipdfmx.exe --miktex-enable-installer -q -E -o notebook.pdf
2021-06-10 08:02:28,594+0100 FATAL xelatex.core - Invalid argument
2021-06-10 08:02:28,594+0100 FATAL xelatex.core - Function: fwrite
2021-06-10 08:02:28,594+0100 FATAL xelatex.core - Result: 22
2021-06-10 08:02:28,594+0100 FATAL xelatex.core - Data: <no data>
2021-06-10 08:02:28,594+0100 FATAL xelatex.core - Source: Libraries\MiKTeX\TeXAndFriends\include\miktex/C4P/C4P.h:646
2021-06-10 08:02:28,594+0100 FATAL xelatex - Invalid argument
2021-06-10 08:02:28,594+0100 FATAL xelatex - Info:
2021-06-10 08:02:28,594+0100 FATAL xelatex - Source: Libraries\MiKTeX\TeXAndFriends\include\miktex/C4P/C4P.h
2021-06-10 08:02:28,594+0100 FATAL xelatex - Line: 646
2021-06-10 08:02:28,596+0100 INFO xelatex - this process (37528) finishes with exit code 1
如果我们在miktex-dvipdfmx.log中查找调用的另一端.
2021-06-10 08:02:26,808+0100 INFO miktex-dvipdfmx - this process (4364) started by 'xelatex' with command line: miktex-dvipdfmx.exe --miktex-enable-installer -q -E -o notebook.pdf
2021-06-10 08:02:28,558+0100 ERROR miktex-dvipdfmx - Image inclusion failed for "attachment:9e002d53-d7a5-42e1-8b51-0fdec8f4dad5.png".
2021-06-10 08:02:28,559+0100 INFO miktex-dvipdfmx - this process (4364) finishes with exit code 1
所以。图像包含对于png失败,这是一个标记单元格中的附件(以前输出的屏幕抓取,这样长时间运行的代码就不必总是被重新运行)。
是否可以确认这一点应该有效--(我在很久以前就在标记单元格中看到了一些问题),,如果是的话,解释如何解决这个问题?
更新I 29/06/2021
在xelatex日志中:有一个“无效的参数消息”,上面的参数"-q -E -o“用于miktex-dvipdfmx.exe,但是引用dvipdfmx手册我找不到-q,-o参数.
然后检查dvipddf基本手册 ()和选项,-o是输出文件名(并不令人惊讶),但仍然没有-q选项的迹象。
这至少是一致的但是..。什么?多么?等等
29/06/2021最新情况
更新的miktex;找到一个新项目miktex-dvipdfmx-bin-x64-2已经安装!重新运行笔记本电脑出口。不同的错误:
nbconvert failed: PDF creating failed, captured latex output:
Failed to run "xelatex notebook.tex -quiet" command:
notebook.tex:561: Undefined control sequence
检查我找到的miktex-dvipdfmx.log
2021-06-10 08:02:26,808+0100 INFO miktex-dvipdfmx - this process (4364) started by 'xelatex' with command line: miktex-dvipdfmx.exe --miktex-enable-installer -q -E -o notebook.pdf
2021-06-10 08:02:28,558+0100 ERROR miktex-dvipdfmx - Image inclusion failed for "attachment:9e002d53-d7a5-42e1-8b51-0fdec8f4dad5.png".
2021-06-10 08:02:28,559+0100 INFO miktex-dvipdfmx - this process (4364) finishes with exit code 1
因此,参数错误(大概)是通过使用miktex-dvipdfmx-bin-x64-2来解决的,而现在tex本身还存在一些其他问题。
不幸的是,对C:\和单独的文档驱动器的全面搜索无法找到notebook.tex,所以这里是调查的死胡同。
但是,请注意,PDF导出对于没有嵌入“附件”的笔记本可以正常工作--我想知道它是否只是找不到附件“文件”。
来自jupyter的最后错误报告为500服务器错误:
nbconvert failed: PDF creating failed, captured latex output:
Failed to run "xelatex notebook.tex -quiet" command:
notebook.tex:496: Undefined control sequence [17 times]
...
notebook.tex:2119: Unable to load picture or PDF file '
dvipdfmx:fatal: Image inclusion failed for "attachment:9e002d53-d7a5-42e1-8b51-0fdec8f4dad5.png".
No output PDF file written.
Sorry, but xelatex did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:\Users\Julian\AppData\Local\MiKTeX\2.9\miktex\log\xelatex.log
而xelatex日志上说没有数据
2021-06-29 08:30:42,590+0100 INFO xelatex.core - start process: miktex-dvipdfmx.exe --miktex-enable-installer -q -E -o notebook.pdf
2021-06-29 08:30:43,984+0100 FATAL xelatex.core - Invalid argument
2021-06-29 08:30:43,984+0100 FATAL xelatex.core - Function: fwrite
2021-06-29 08:30:43,984+0100 FATAL xelatex.core - Result: 22
2021-06-29 08:30:43,984+0100 FATAL xelatex.core - Data: <no data>
2021-06-29 08:30:43,984+0100 FATAL xelatex.core - Source: Libraries\MiKTeX\TeXAndFriends\include\miktex/C4P/C4P.h:646
2021-06-29 08:30:43,984+0100 FATAL xelatex - Invalid argument
2021-06-29 08:30:43,984+0100 FATAL xelatex - Info:
2021-06-29 08:30:43,984+0100 FATAL xelatex - Source: Libraries\MiKTeX\TeXAndFriends\include\miktex/C4P/C4P.h
2021-06-29 08:30:43,984+0100 FATAL xelatex - Line: 646
2021-06-29 08:30:43,986+0100 INFO xelatex - this process (38968) finishes with exit code 1
可能相关:github nbconvert转换问题
发布于 2021-06-28 14:12:44
我在这里也有同样的问题。现在,我的临时解决方案只是使用Chrome浏览器功能的打印(另存为pdf),但标题部分和脚注只是看起来如此乏味和烦人。
发布于 2022-09-25 04:08:41
我也遇到了这个问题。
我的解决方案.使用图像附件定义中的完整路径,而不是相对路径。尽管当我这样做时,它不会在VS代码中呈现,但它确实允许nbconvert现在成功地找到文件并创建PDF。
有问题的代码:(test image)[test_image.jpg]
工作代码:(test image)[C:\test_image.jpg]
我不能肯定地说,但我在错误日志中注意到,它正在将临时文件写入AppData。我怀疑它当时并没有把图像拉进去,然后没有找到它们相对于那个临时文件。
https://stackoverflow.com/questions/67916736
复制相似问题