The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
On Wed, Feb 15, 2023 at 4:59 PM Don Brown via MIDRANGE-L
Our current solution of checking and replacing the EOL character(s) is
working but is realy a brute force and ignorance solution.
It doesn't feel particularly brutish or ignorant to me. It's easy to
understand, straightforward to implement, and it works. I don't see
why you couldn't just keep using that approach for future downloads.
I don't know what code was added where, but if you are worried that
it's ugly, put it in a separate and reusable procedure or program if
you haven't done so already.
I am sure others have had this issue or will have so hopefully there is a
simple process providing the solution..
In my opinion, what you're already doing is simple and effective, and
doesn't really need to be replaced by something "better".
But if you *were* to replace it, my recommendation would be to go
whole hog and rewrite a lot of the larger process in Python or
By "larger process" I mean the downloading, the handling of line
endings if needed, and whatever it is that is reading the CSV. All of
that can be replaced by a single, relatively short Python script.
As an Amazon Associate we earn from qualifying purchases.