Constantinos Leftheris

take a look this is what I found about what X12 990 looks like. Its a sample I found googling about it ``` ISA*00*          *00*          *12*4405197800     *01*999999999      *111219*1742*U*00400*000000003*0*P*> ```

Ok according to [these guys here](http://edi.aaltsys.info/01_standards.html) > EDI data is exchanged in text files. With this in mind, EDI standards recommendations **do not result in a viewable file**, and common...

@raholland79 I can see if I can make this work but I need you to send me the original sample file (not tampered with), If this is sensitive information involved...

@raholland79 Ok the issue here is that the new line `\n` is used as the special character for Segment Termination. This is considered as whitespace throughout the `EdiTextReader` and will...

No you must replace every occurrence of the `\n` character with `~`. This will do the trick until this is fixed, ``` csharp [Fact] public void X12_204_Test() { var grammar...

@raholland79 glad you made it work. Issue #24 is still one of my top priorities. Thanks.

Hi @PGP-Protector, Unfortunately this is still an issue. The main reason is that I did not find the time. Changing the code to be able to treat `\n` (#24) was...

Hi @Qtemp123 and thank you for your interest in [EDI.Net](https://github.com/indice-co/EDI.Net) > question is, is this actually a proper solution? Based on all issue suggestions that I have read, I should...

Hi @Patrickyp thanks for your interest in the library. What you see is expected behavior. When writing values the format defined is clear that is used as a string format...

Dont worry about the format spec (pictures) because it will never mess the value so bad when reading. First worry about the binding structure. When deserializing the issue is 99%...