> For the complete documentation index, see [llms.txt](https://ayakaleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ayakaleaf-pro.ayaka.space/latex/zh-cn/wen-da/78-my-submission-was-rejected-by-the-journal-because-font-xyz-is-not-embedded-.-what-can-i-do.md).

# 我的投稿因“Font XYZ is not embedded”而被期刊拒稿。我能做什么？

这很可能是由你项目中某些 PDF/EPS 图形中令人头疼的“font-not-embedded”问题引起的，因为创建它们的应用程序没有将字体嵌入到图形中：请参见 [这个链接了解一些背景细节（尤其是第 2 项）](http://tex.stackexchange.com/a/255097/226).

> 关于字体：这里最可能的罪魁祸首是图形文件，格式要么是 eps，要么是 pdf。如果你的图形中包含文本，但没有同时包含该字体，那么文档中也会缺少该字体。这里你基本上有两个选择：a）在你用来创建图形的任何工具中，查找一个能显式将字体包含到导出图形中的选项。b）将文本导出为曲线而不是文本。如果没有文本，就不会缺少字体（这是个丑陋的解决方案）。

更多信息：

* <https://machinelearning1.wordpress.com/2013/03/22/create-eps-file-from-matlab-figures-with-embedded-fonts/>
* <https://sites.google.com/site/xyzliwen/resource/embed_font_ieee_pdf_explore>

最好的解决方案是确保你的 PDF 图像是从其原始应用程序导出时选择了 [嵌入所有字体选项](http://www.latex-community.org/forum/viewtopic.php?p=43537\&sid=bb0b021e3acac54742fecbcb91713fed#p43537)。例如，如果你使用 R 生成图像，可以使用 [`embedFonts` 方法](https://stat.ethz.ch/R-manual/R-devel/library/grDevices/html/embedFonts.html) （也 [此处](http://zevross.com/blog/2014/07/30/tired-of-using-helvetica-in-your-r-graphics-heres-how-to-use-the-fonts-you-like-2/) 和 [此处](http://r.789695.n4.nabble.com/Automatic-way-to-embed-fonts-into-all-pdf-output-td4666773.html)).

或者，你可以让 Overleaf 为你对 PDF 进行后处理，不过这可能会导致你的项目编译时间稍长。首先，在你的项目中添加一个名为 `latexmkrc` （不带扩展名）的文件，然后将以下这一行粘贴到该文件中：

```
$pdflatex = 'pdflatex %O %S; ps2pdf14 -dPDFSETTINGS=/prepress %B.pdf %B-embed.pdf; mv %B-embed.pdf %B.pdf';
```

你可能需要对你的 `.tex` 文件做一些小改动，以触发重新编译并使后处理发生。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ayakaleaf-pro.ayaka.space/latex/zh-cn/wen-da/78-my-submission-was-rejected-by-the-journal-because-font-xyz-is-not-embedded-.-what-can-i-do.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
