Skip to content

Conversation

@cneud
Copy link
Member

@cneud cneud commented Oct 30, 2025

No description provided.

Copy link
Contributor

@kba kba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, much improved docs, many thanks.

But can we keep the PEP8 changes out of it for now? They will be cleaned up later but there's now multiple branches changing code in utils and if we can minimize the number of conflicts, we should ;)

@@ -1,7 +1,8 @@
# Eynollah

> Document Layout Analysis, Binarization and OCR with Deep Learning and Heuristics
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> Document Layout Analysis, Binarization and OCR with Deep Learning and Heuristics
> Document Layout Analysis, OCR, Binarization, Reading Order Detection and Image Enhancement with Deep Learning and Heuristics

If we could have a terse consistent, complete description, we should reuse that everywhere, like in the CLI.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am hesitant to list all the (sometimes confusing) features here already - sth simple and concise like "Historical Document Layout Analysis and Recognition" would be better for the first line of README imho...

See the flowchart below for the different stages and how they interact:

![](https://user-images.githubusercontent.com/952378/100619946-1936f680-331e-11eb-9297-6e8b4cab3c16.png)
<img width="810" height="691" alt="eynollah_flowchart" src="https://github.com/user-attachments/assets/42dd55bc-7b85-4b46-9afe-15ff712607f0" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add the image and diagram source to the docs folder as well - @vahidrezanezhad can you share those with me, I'll add them.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Comment on lines +33 to +36
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could automate that with https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version. Though I think trove classifiers for Python version has been deprecated in favor of requires-python pyproject.toml field. In any case, we should also adopt requires-python.

#print(x_end,'x_end')
if len(new_main_sep_y)>0:

min_ys=np.min(y_sep)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no qualms with autopep8-ing the code, but to make our life easier when we merge #206 and the upcoming refactorings, can we skip the PEP8 changes for now pls?

@cneud
Copy link
Member Author

cneud commented Oct 30, 2025

LGTM, much improved docs, many thanks.

But can we keep the PEP8 changes out of it for now? They will be cleaned up later but there's now multiple branches changing code in utils and if we can minimize the number of conflicts, we should ;)

Sure, I can revert those later.

@cneud cneud changed the title Documentation updates and minor PEP-8 fixes Documentation updates Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants