You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm having an issue with the table areas. When I use the webserver to select an area to extract, I can get the table.
But it is not corresponding with an other area selection in pdf with an other software (adobe, pdfviewer or pdf2img).
So when I put the table_areas param with the true values (which I supposed are from adobe, and other 😄 ), camelot is extracting the wrong areas.
Is it possible to unify this ?
In addition, why making a list of string ["area1", "area2"] instead of list of list [[area1],[area2]].
It is memory lighter and don't need to split on string to extract x1,y1,x2,y2
Can you take a look ?
PS : I sent you a mail about a new method mixed of Lattice and Stream
The text was updated successfully, but these errors were encountered:
Hi,
I'm having an issue with the table areas. When I use the webserver to select an area to extract, I can get the table.
But it is not corresponding with an other area selection in pdf with an other software (adobe, pdfviewer or pdf2img).
So when I put the table_areas param with the true values (which I supposed are from adobe, and other 😄 ), camelot is extracting the wrong areas.
Is it possible to unify this ?
In addition, why making a list of string ["area1", "area2"] instead of list of list [[area1],[area2]].
It is memory lighter and don't need to split on string to extract x1,y1,x2,y2
Can you take a look ?
PS : I sent you a mail about a new method mixed of Lattice and Stream
The text was updated successfully, but these errors were encountered: