Note that you don't need to actually post much data. Strip it down to show the salient variations. Any text that isn't important for identifying records or data items or parameters can be omitted or abbreviated as appropriate. Background like how the original file is generated may be helpful to give us some idea of how much variation there may be in elements of the format. The smaller you can make the data and still be clear about the actual file format the easier it will be to figure out how to parse it.
If the sample we have already is representative of the actual data (exact naming format aside) we don't need large lumps of additional data. It is important that anything related to record breaks is accurately represented though.
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.