Skip to content
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

Parsing ICL with image data #123

Merged
merged 6 commits into from
Oct 27, 2020
Merged

Conversation

jenakan
Copy link
Contributor

@jenakan jenakan commented Sep 25, 2020

Line length changes to support ASCII encoded ICLs with type(52) ImageData. Implemented a secondary format that will scan for lines based on control bytes defined by spec rather than CRLF line breaks.

Not sure if this counts as a format as mentioned in #111.

jenakan added 2 commits September 25, 2020 09:16
… should use to parse file. Add a secondary format X9100ascii to handle parsing ascii encoded ICLs without CRLF to indicate line breaks.
@jenakan jenakan marked this pull request as ready for review September 27, 2020 04:20
@adamdecaf
Copy link
Member

Awesome, thanks @jenakan!

jenakan added 4 commits October 9, 2020 13:21
Only the file record count (Type 99; field 3) includes all record types. The bundle item count (Type 70; field 2), cash letter item count (Type 90; field 3) and file item count (Type 99; field 2) refer to the number of check records (type 25) or return records (type 31). These fields do not include headers, controls or addendums.

const (
// Discover format
Discover Format = iota
Copy link
Member

Choose a reason for hiding this comment

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

What if we renamed this to Detect? I'm worried Discover (the company) might have an X9 format we run into one day...

Copy link
Contributor Author

@jenakan jenakan Oct 26, 2020

Choose a reason for hiding this comment

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

@adamdecaf Thinking of dropping the Format enum. It's too restrictive.

DTSU can be read/written as ASCII, but FRB adoption of DTSU requires EBCDIC encoding. I'm making some changes to allow reading/writing with configurable options. It should allow more flexibility for others.

Copy link
Member

Choose a reason for hiding this comment

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

Okay. We'll write up a matrix to explain the known combinations.

@jenakan jenakan mentioned this pull request Oct 26, 2020
@atonks2 atonks2 merged commit 5511e76 into moov-io:master Oct 27, 2020
@jenakan jenakan deleted the parse-ascii-images branch October 28, 2020 21:20
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.

3 participants