Thanks. I hadn't given \r too much thought, as it hasn't ever bit me. We're on Unix, and most of our trading partners are Unix and Linux. (.?\r?\n?) is pretty cool, though. I'll have to remember that.

I do mainly banking files right now (820, 828, etc.). It's my wife who is in health care, though. She works at Foresight helping develop the HIPAA validator, among other things.

I haven't ever had to argue against the grep utility. My group knew not to use it long before I got there. A few of our TPs send data with no line breaks, and our version of Unix has a grep that can't handle > 2048 characters. Saying "grep says it can't handle the file" carries some weight, apparently.

In reply to Re: Re: Getting an ANSI X.12 file's delimiters by delirium
in thread Getting an ANSI X.12 file's delimiters by delirium

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.