From af539d6f0a989a3d663ef3a5f324b45d4e5571c8 Mon Sep 17 00:00:00 2001 From: Daniel van Strien Date: Wed, 12 Oct 2022 14:08:48 +0100 Subject: [PATCH] fix MarkupLMProcessor option flag (#19526) --- docs/source/en/model_doc/markuplm.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/en/model_doc/markuplm.mdx b/docs/source/en/model_doc/markuplm.mdx index 66ba7a818..1b3ae46d3 100644 --- a/docs/source/en/model_doc/markuplm.mdx +++ b/docs/source/en/model_doc/markuplm.mdx @@ -178,7 +178,7 @@ processor will use the feature extractor to get all nodes and xpaths, and create dict_keys(['input_ids', 'token_type_ids', 'attention_mask', 'xpath_tags_seq', 'xpath_subs_seq']) ``` -**Use case 5: web page question answering (inference), apply_ocr=False** +**Use case 5: web page question answering (inference), parse_html=False** For question answering tasks (such as WebSRC), you can provide a question to the processor. If you have extracted all nodes and xpaths yourself, you can provide them directly to the processor. Make sure to set `parse_html` to `False`. @@ -243,4 +243,4 @@ dict_keys(['input_ids', 'token_type_ids', 'attention_mask', 'xpath_tags_seq', 'x ## MarkupLMForQuestionAnswering [[autodoc]] MarkupLMForQuestionAnswering - - forward \ No newline at end of file + - forward