Azure-Samples / Azure-Samples/document-intelligence-code-samples

Is the SEPARATOR_LENGTH_IN_MARKDOWN_FORMAT necessary? If yes, how to decide it?

Open
#40 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
201
Forks
115
PR merge metrics
No merged PRs in 30d

Description

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
>

### Any log messages given by the failure
>

### Expected/desired behavior
>

### OS and Version?
> Windows

### Versions
> 11

### Mention any other details that might be useful
Thanks for providing a [notebook](https://github.com/Azure-Samples/document-intelligence-code-samples/blob/main/Python(v4.0)/Retrieval_Augmented_Generation_(RAG)_samples/sample_identify_and_merge_cross_page_tables.ipynb) for merging tables across pages
For vertical table, is the SEPARATOR_LENGTH_IN_MARKDOWN_FORMAT necessary? as when there is no paragraph in between, there are only page header/footer/number between two tables, the two tables can be merged if they have the same number of columns.
If it is necessary, how can it be decided? It is “2” in the notebook but due to the inclusion of markdown for page header/footer/number and page break when calculating the offset, there are more than 2 characters between two tables. So 2 is too small.
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.