Tickets :: Comment on [#7237] Replace TSV parser with extended CSV parser

Search Results: 74 of 151 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: __ .__ . ..__.. . / `[__)\|\ \|\| \|\|__\| \__.[__)\| \\|\|__\|\| \|
Comment	> While trying to import a TSV file created by Outlook I found that > Horde was calculating an incorrect number of rows. Closer inspection > of the exported data and Horde's Data/tsv.php showed that the parser > simply splits the files on line endings. The data I exported from > Outlook contained numerous fields that contained newlines embedded in > quotation marks. To make matters worse Outlook did not consistently > quote each field. It appears to only have quoted fields which > contained quotes, the delimeter or the newline. > > > > Example of a single field: > > <tab>"""John's Barbeque"" > > Good food here."<tab> > > > > Outlook intended for this to be the string > > "John's Barbeque"\nGoodfoodhere. > > > > but the Horde Framework parser sees the newline and assumes it's the > next record. > > > > I've experimented with different ways of writing the parser to look > for newlines but each time I find new corner cases. Rather than spin > our wheels on this it might make sense to look at the PEAR library > (which seems only to operate on files rather than strings) or find a > reference implementation. I haven't yet read the RFC to determine > whether Outlook violates the standard or not by not consistently > quoting, but regardless its how the file was generated. > > > >
Attachment
Watch this ticket