Chris I think that he is referring to the 2 different characters - CR and LF (Hex 0D and 0A)
The EDI standard specifies a SINGLE delimiter. In Unix, this is not a problem. In Windows, both characters usually appear at the end of the line. Technically, the Windows file (with 0D0A) would be rejected, and many translators do reject these files... When I have written translators, I usually convert the single Unix style delimiter into the dual Windows delimiter or make sure that I can read and parse both on the inbound side. On the Outbound side only a single delimiter is correct (hex 0A) or whatever... Henk-Jan - a single delimiter is technically correct. Both would be nice to have ;-) To: [email protected] From: Chris Johnson <[EMAIL PROTECTED]> Date sent: Wed, 12 Sep 2007 16:43:31 +0100 Subject: Re: [EDI-L] questions about X12 syntax (building ta X12 translator) > Quoted text is from <[EMAIL PROTECTED]>, by > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > >1. About using <CR/LF> in X12. > >It seems this can be used as a segment terminator. > >In edifact I sometimes see a 'blocked' (or 'wrapped') output format, > >where after (typically) 80 characters a <CR/LF> is inserted. > >In edifact, some (actually a lot of) senders append <CR/LF> after a > >segment terminator. > >How is this for X12? > > > CR/LF will appear as a single linefeed character if you read in text > mode. Since linefeed is valid as a syntax character in X12 (and EDIFACT > if you use a UNA) a fairly safe approach is to establish first if > linefeed is used as a syntax character, and if not just ignore linefeeds > in the input stream. Analysing an ISA which has been blocked is an > amusing coding exercise. > > In truth it has been a long time since I saw EDI which had been blocked > as such, although mauling by email system word-wrapping does happen > occasionally. In my experience inserting linefeed after each segment in > EDI for live transmission is also uncommon, although presentation > utilities (and it is also an option in Expedite Base) can do this. > > If linefeed *is* used as a syntax character then you cannot reasonably > be expected to cater for an external system which has inserted > extraneous examples in the EDI. > > Regards > Chris > -- > Chris Johnson mobile:+44 (0)7785 302122 Fax: +44 (0)870 0519 818 > EDI website http://www.edimatrix.co.uk > EDIMatrix Ltd work: 0845 126 0680 or +44 20 8778 1402 > Registered in UK no. 2777624 Reg.Office: 34 Sydenham Rd, London SE26 5QF > > > ... > 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 > > > > > __________ NOD32 2524 (20070912) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > Earl Wertheimer [EMAIL PROTECTED] http://www.spe-edi.com ... 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: mailto:[EMAIL PROTECTED] mailto:[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/
