> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/validation-screen/troubleshooting/missing-text-in-ocr-extraction.md).

# OCR 提取中缺少文本

## **问题**

在某些情况下，**OCR View** 中可能会缺少文本，因此无法使用提取功能提取这些文本。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-38905b23cc965d0c464c08d32fb1178c50bdb668%2Ftroubleshooting_ocr_5.png?alt=media" alt=""><figcaption></figcaption></figure>

要确认这一点，请点击右侧工具栏中的 **OCR View** 按钮。如果其中没有显示该文本，就表示无法提取它。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-0607533fd4dbffa32484f8ecc2877c3f8eda8646%2Ftroubleshooting_ocr_6.png?alt=media" alt=""><figcaption></figcaption></figure>

## **原因**

最可能的原因是，您尝试提取的文本位于文档中的图像内（例如徽标或扫描的内容）。\
启用 E-Text 功能后，图像或徽标中的文本不会包含在提取的文本层中。因此，无法通过标准提取逻辑访问或提取这些文本。

## **解决方法**

要解决此问题，请禁用 E-Text 功能：可以针对[特定供应商](#disable-e-text-for-a-specific-supplier)禁用，也可以针对[整个组织](#disable-e-text-for-the-entire-organization)禁用。停用 E-Text 后，DocBits 将仅使用 OCR，从而能够从文档中的图像和徽标提取文本。

### **针对特定供应商禁用 E-Text** <a href="#disable-e-text-for-a-specific-supplier" id="disable-e-text-for-a-specific-supplier"></a>

1. 在 **Field Validation** 中打开一份来自该供应商的文档。
2. 点击右侧工具栏中的三点菜单。

   <figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-2a7d9474cf03d32987e69b40f7a8e9bc4a948102%2Ftroubleshooting_ocr_2.png?alt=media" alt=""><figcaption></figcaption></figure>
3. 取消勾选 **Use E-Text if available**。

   <figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-f89cccdd444f03093ff1995d787e03878ed6ccb7%2Ftroubleshooting_ocr_3.png?alt=media" alt=""><figcaption></figcaption></figure>
4. 点击 **Confirm**，重新启动该文档的处理。

   <figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-05d67bea927fa93604cfa8efd0faac3f4a127d17%2Ftroubleshooting_ocr_4.png?alt=media" alt=""><figcaption></figcaption></figure>

### 针对整个组织禁用 E-Text <a href="#disable-e-text-for-the-entire-organization" id="disable-e-text-for-the-entire-organization"></a>

1. 前往 **Settings → Document Processing → OCR Settings**。

   <figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-d7b5210d472e53682e0a713263ebc8f128759da9%2Fsettings_ocr.png?alt=media" alt=""><figcaption></figcaption></figure>
2. 在 **General OCR Settings** 下，取消勾选 **Use E-Text if available** 选项。

   <figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-11968f849fcfd3add748999ee9c91357e5d3a33e%2Ftroubleshooting_ocr_1.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/validation-screen/troubleshooting/missing-text-in-ocr-extraction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.