Support Comma-delimited Entries

[nojronatron]

Is your feature request related to a problem? Please describe.

Yes. It is possible to edit bib entries within the box where IN, OUT, and DROP buttons place the bib record data. If I make an error entering a bib record, I might decide to edit the data within that text box, but it is not easy to re-create tabs using just a keyboard (without using special techniques), and I'm likely to just add lots of spaces to make things line up.

If the Winlink Message recipient receives this poorly formatted data, they might not be able to easily import it to Excel (as the Form promises), and some data might be missed or incorrectly copied by the recipient.

Describe the solution you'd like

Allow the Form to support comma-delimited entries. If I must go in and update an error, I can easily re-create the comma(s), maintaining a useful data format.

The recipient will still be able to import the comma-delimited data and it will be less likely to cause a problem on their end.

Describe alternatives you've considered

• Blocking access to editing the text field: This is acceptable (for the recipient) but potentially troublesome for the remote operator. Everyone makes mistakes, why can't the remote operate fix a mistake before transmitting it elsewhere (pushing to problem to someone else)?
• Enable editing or removing "bad entries": This sounds easy but will require re-writing portions of data processing JavaScript and could clutter-up the user interface (even more than it already is), making it more difficult to use, especially on a small-screen device.

Additional context

BF Base will be provided the ability to process comma-delimited records, in addition to the current tab-delimited.

[nojronatron]

Note: BigFoot Base wants the Winlink Message body to remain in tab-delimited format, but this can be addressed in a future, linked issue.

[nojronatron]

This issue has been addressed by releases v2.1.x, PR #58, and includes tab-delimited bib-records output when submitted.