[chirp_devel] Files with CRLF vs. LF vs. CR?

[Tom Hayward]

On Sun, Nov 9, 2014 at 1:27 PM, Tyler Tidman <tyler.tidman at draak.ca> wrote:
>> Open the CSV in Chirp, edit something, and save it. That'll tell you
>> which line endings are appropriate for your system.
>
> I seem to always get DOS-formatted files output from Chirp on my Ubuntu
> system using the daily builds.  I shall start watching more carefully
> for this behaviour now.  So far, I've only used Chirp and generated csv
> files for Chirp on Linux systems.

That's Python's CSV module attempting to build files that are
compatible with as many systems as possible. Let that be your guide:
if you want to standardize CSV files to a specific line terminator, it
looks like DOS format is most appropriate.

>> People use Chirp CSV files in a lot of different editors. Chirp,
>> Notepad, Excel, LibreOffice, etc., all work fine now. That's a long
>> list of tests that would need to be done to accept a change.
>
> Hmm... I don't recall seeing a list of supported external CSV editors.
> Should this be added to the wiki?

If you test some third-party CSV editors and find them to work with
Chirp files, you can document this on the wiki. I wouldn't go so far
as to say they're "supported", just "known to work". If there are any
caveats with any of them, you could document this in the same place. I
seem to recall there being some issue with how Excel handled empty
fields, but I don't recall the details--this would be a perfect thing
to document.

Tom KD7LXL