EDI.Net: Edi Reader does not respect X12 advised control characters
In all known EDI formats there are default control characters these are documented in the default EdiGrammar presets.
EdiGrammar.NewEdiFact()EdiGrammar.NewX12()EdiGrammar.NewTradacoms()
Now in the EdiFact and X12 cases there is a way for the transmitter (he who sends the edi transmission) to advise differently for each of the control characters.
Control characters are considered to be the segment, element & component seperators plus the escape character.
In X12 the current implementation completely ignores them.
About this issue
- Original URL
- State: open
- Created 8 years ago
- Comments: 18 (9 by maintainers)
Commits related to this issue
- Added samples to test for the `\n` issue. related to #19 and #24 — committed to indice-co/EDI.Net by cleftheris 8 years ago
- support new line as a segment terminator in EdiTextReader closes #24 #19 — committed to indice-co/EDI.Net by cleftheris 6 years ago
- Support windows style CRLF endings with \r as the segment terminator in EdiTextReader related to #19 — committed to indice-co/EDI.Net by cleftheris 6 years ago
My idiot vendor now says the terminator should be ~ on all files - I’m reconfirming to be sure - but If so this makes the library work as is without any work around and you can backlog this particular bug for more important work.
I’ll let you know ASAP.
Again, thanks for the wonderful hard work and excellent communication.