-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Why is position of first character of input row changed to last character of the same line in output table? #215
Comments
You can see in snapshot below that first character from row no 2-10 is cropped and append as last character in output table. The input files is : Any idea,why this is happening and how can it be fixed. Thanks. |
i am also having the same issue related to first character position. |
Hi @amdhacks and @abhibisht89! Thanks for the report, this is a known issue (more details here #170 and here #213). You can expect a fix by the end of this week. Till then, you can try the workaround mentioned in #170, by finding the path where camelot is installed and passing |
My base.py file after the change given below:
But I do not see any improvement. First character is still shown as last character of the same row in output. Am I missing something? |
Sorry, I should've been more specific. You need to add |
@vinayak-mehta, I have updated camelot version to 0.4.1 but first character which was showing as last earlier is now appearing as a single character in first column like below: Please suggest. |
@amdhacks Please install the latest version i.e. v0.5.0. The table isn't being detected correctly for this case. You'll need to specify a table area. $ camelot --format csv --output output.csv stream -T 70,690,550,170 input.pdf |
@vinayak-mehta I'm having the exact same issue as @amdhacks, and I have version 0.7.3 Also, the table boundaries in the Input PDF as as clearly defined as they can be. |
Will share input file shortly. Unable to share from restricted network at this moment.
The text was updated successfully, but these errors were encountered: