> The foolproof method would be to look two characters beyond the final > element delimiter for the segment terminator. Count delimiters, not > characters and especially don't look to the end of a line.
Not quite so foolproof, Art. I have been working with a user of EDICLEAN to handle additional data conditions (yes, I do do that!). Seems he has files which use LF as a segment terminator AND are blocked. Trying to figure out which LFs are segment terminators and which are blocking characters was driving me nuts until I figured out that I could only do it *IF* the data are blocked with CRLF and not only LF, which was an early 'test file' supplied. (I want to continue handling 'nix/PC newline 0x0A vs 0x0D0A transparently but that is not possible in this case). I wrote my scan engine about ten years ago. Since then about 75% of the updates I have made have been to accommodate new and imaginative ways to submit corrupt or otherwise "weird" data. (most often the product of EBCDIC/ASCII conversions and/or "FTP'd" files). Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
