This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
No problem. As originally implemented, the parser was treating each individual character in a multicharacter separator string as a separator, rather than using the entire string as a single separator. Subtle, but easily rectified. -Lansing > I was unaware of this. Thanks for apprising me! > c > > Le 19/12/2013 09:12, Unidata netCDF Java Support a écrit : > > Hi Charlie, > > > > I'm not sure if word got back to you, but I implemented a solution for your > > *|* separator (and any other multicharacter separator, for that matter). > > It's in our 4.4.1 branch. > > > > -Lansing > > > > Ticket Details > > =================== > > Ticket ID: VKJ-807633 > > Department: Support netCDF Java > > Priority: Critical > > Status: Open > > > > -- > Charlie Zender, Earth System Sci. & Computer Sci. > University of California, Irvine 949-891-2429 )'( > > Ticket Details =================== Ticket ID: VKJ-807633 Department: Support netCDF Java Priority: Critical Status: Open