8/13/06
> However there is a nasty gap between what should happen and what does happen.
Truer words ne'er were spoken.
>The transmission method may not be neutral. In the real world a
> translator may be faced with interchange files which have been blocked
> and padded to fixed length records, contain mail header or routing
> records, and have been arbitrarily word wrapped by a mail system.
And let's not forget another source of both "creative" (?) formatting and
syntax interpretation: home-grown systems created by
"Sure, I know how to do that" types. Sometimes I have to wonder who let these
people out on work-release programs.
> Our translator can handle these cases, except for a word wrapped
> interchange which also uses newline as a segment delimiter!
Hmm, my scanner will handle that. Of course, I don't do translation the way you
do. Plus I had to find some way to deal with a
specific brand-name translator's output format. (Trading Partner PC).
Fortunately this control character choice is not made much any
more, what with all the Internet-based transmission and the "help"
automatically supplied (whether you want it or not) by VAN and
VAN-like services which believe a carriage return or line feed is always,
always, always an 'end of record' marker even when it
isn't.
(I've seen carriage return (0x0D) as the ANSI ASC X12 element delimiter. Let's
see one of those VAN-like services handle that
correctly!)
MCM
...
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/
<*> 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/
