Table filter: eimbedded line breaks are not treated properly when leading/trailing whitspace is excluded

[Former user]

Original [issue 155](https://code.google.com/p/okapi/issues/detail?id=155) created by frank.kuh... on 2010-12-19T12:17:13.000Z:

When I have a CSV record like

1,"""eins"" zwei"

extraction with "exclude leading/trailing whitspace" and "separate lines with line-feeds" options set creates the following:

<source xml:lang="en-us">"""eins"" zwei"</source>

extraction without the "exclude leading/trailing whitspace" option set creates the expected result:

<source xml:lang="en-us">"""eins"" zwei"</source>

I assume that the
n is eaten by the whitspace handling before it can be evaluated ....

This has been tested with the 10-12-16 snapshot

cheers,
frank

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=155#c1) originally posted by @ysavourel on 2010-12-19T17:07:30.000Z:

[Former user]

Comment [2.](https://code.google.com/p/okapi/issues/detail?id=155#c2) originally posted by @ysavourel on 2011-02-17T15:21:51.000Z:

I committed some tests and the filter behaves as expected:

testFileEvents4() testFileEvents5()

in /okapi-filter-table/src/test/java/net/sf/okapi/filters/table/CommaSeparatedValuesFilterTest.java

[Jim Hargrave (OLD)]

Fixed