Unable to read a particular page of pdf about tng_statement_in_csv

[Rexpert]

Good morning @junhong0618

Based on my experience with this IndexError, I think the table_regions / table_areas parameter may be the main cause, because camelot couldn't find the table or found multiple table in the range. I suggest you to

1. try switching table_regions or table_areas in your code.
2. try including both table_regions and table_areas with the same value in your code.

For development purpose, please let me know which fix is working... Thank you

[junhong0618]

Thanks for the prompt assistance. As an update, after I replaced table_regions with table_areas and remained the same coordinates, the error is resolved. May I know how should I differentiate these 2 usages?

I am still confused even after reading the info from below link.
[camelot](https://camelot-py.readthedocs.io/en/master/user/advanced.html#specify-table-regions)

[Rexpert]

According to my understanding, the difference is table_areas used to specify exact table coordinates, but if specify table_regions will make camelot search table on the given coordinates.

Based on my experience with this IndexError, I think the table_regions / table_areas parameter may be the main cause,

By the way, I've made this udate on c9b21ac, you can sync my repo (make pull request in your forked repo) in the github web interface and then run this code to sync your local repo

> git pull

P/S: Please don't close this issue, I'll make the improvement on the code with next commit update.

[junhong0618]

Noted. I wont be closing this issue.

From my understanding, pull request to be created when I propose the change to the code owner. Since you have updated on c9b21ac, should I still create any pull request? Apologies for this question as I am new to Github.

[Rexpert]

Yes, when you forked my repo, you create a clone repo to your github. What I mean pull request here is you proposing a change (syncing my repo) to your owned repo.

junhong/TNG:main <-- Rexpert/TNG:main

Below is the demostration:

However, for a quicker way, I just knew we can directly sync the repo with the sync button, sorry I'm also still learning this Github thing.

Source: Syncing a fork branch from the web UI

I think both way works.

[Rexpert]

closes as 78e3774