Is there a graceful way to deal with hard returns found in delimited text files? Some of our sources have long "description" fields, which seem to be large arbitrary text fields.
The text file export has kept these hard returns, and thus a new line in the text file is *not* a new record.
Does Kettle have a way to handle this? The file is delimited, so it might be able to know that it isn't done reading in a full record.