-
Notifications
You must be signed in to change notification settings - Fork 38
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
[Need help or bug] Fields skipped in a state loop? #48
Comments
Can you provide an example PDF and yaml that shows this behavior? |
Same as #47 -- sensitive data. If a way to change the field content without altering the PDF otherwise exists, please let me know. |
You could use |
I'll try to get it done this or next weekend. |
So here's the yaml. It's the last version before I gave up in January with textricator-10.0**.67**. Some replacements have a debugging label prepended, e.g.,
|
Noyannus - I assume this is still a problem? I'm trying to figure out how to replicate it. I wonder if this may also be a localization issue like #47 - but have no evidence one way or the other. Can you point me to where in your yaml file the problem occurs and the matching area in all-p1-redact.pdf? I'm making the assumption that is the general structure of the document you're parsing. Maybe with those two pieces of information, I can start to build a model of what's going on and zero in on something specific. |
Sorry for the delayed answer (life has a way to get in the way). And thank you for your kind offer. I will try a simplified version first making use of the y-values I have shunned so far (#47). That made the conditions overly complicated; and I want reduce the likelihood that I have introduced a bug there. If this does not work, I'll be back here. |
I'm using
textricator form
to extract text fields that in a short stretch of the input PDFs occur in varying orders (field1-field2-field3 or field1-field3-field2 or field3-field1-field 2; ...).A state with multiple conditions is iterated through to go through all states of the variedly-ordered fields, eight such fields plus an exit and a loop condition.
When none of the conditions but the next field after these fields match, iteration stops and the machine moves to that state.
At least, that's what it's supposed to do. It does not fully work. In different PDFs it skips fields, but different fields in different PDFs. Why?
textricator text
CSV files.ulx
) to formulate a match.Am I overlooking something basic? Could there be a bug that causes skips in a lenghty 'condition:... nextState:...` sequence?
The text was updated successfully, but these errors were encountered: