|
From: John H. <jo...@zo...> - 2004-04-14 15:46:52
|
Seperators can come from the basic or extended control sets. Using the characters 0x1C, 0x1D, and 0x1E as seperators passed unit and functional tests. On Wed, Apr 14, 2004 at 09:50:33AM -0400, John Holland wrote: > Darren, > > The code dynamically identifies the seperators used in the source > data file. Specifically, it gets the element seperator from the > fourth character, the segment seperator from the 106th character, > and the sub-element seperator from the 105th character. > > I have assumed that a x12 document creator will use seperators from > the basic or extended character sets, but it may be possible to use > seperators from the basic or extended control sets. I will have to > test that. > > On Wed, Apr 14, 2004 at 08:51:34AM -0400, Darren Hartford wrote: > > Just an FYI, changing the special element seperator characters to "*",":", and "~" seemed to have corrected the issue. However, my data normally contains these characters (which I had to change for this test case), so I would like to add these as element seperators. Where should I look in the code for these seperator identifiers? -- John Holland jo...@zo... http://www.zoner.org |
