#12 — Comma as delimiter in CSV format for subscribers is suboptimal
by
Dinu Gherman
—
last modified
Feb 09, 2011 04:23 PM
| State | Confirmed |
|---|---|
| Version: | |
| Area | Functionality |
| Issue type | Feature |
| Severity | Medium |
| Submitted by | Dinu Gherman |
| Submitted on | Feb 09, 2011 |
| Responsible |
—
|
| Target release: |
—
|
The currently used comma as a delimiter in the CSV format for subscribers is highly suboptimal since it can easily occur in names like "Joe Foo, Jr." or in company names including department descriptions, like "Siebens Healthcare".
I suggest using a semikolon, instead, which is much less likely to cause issues with such entries. Also, it would potentially allow to include multiple email addresses, seperated by commas, in a single entry, just in case.
I suggest using a semikolon, instead, which is much less likely to cause issues with such entries. Also, it would potentially allow to include multiple email addresses, seperated by commas, in a single entry, just in case.
Added by
Maik Derstappen
on
Feb 09, 2011 03:54 PM
why not using commas and quote the text?
Issue state:
Unconfirmed
→
Confirmed
like:
"Hans Meiser",hans.meiser@rtl.de
Im not sure if the import can handle this, but this can be changed.
Added by
Dinu Gherman
on
Feb 09, 2011 04:23 PM
If you use quotes, you must use them in all fields, I think, which adds quite a few characters the more fields and lines you have. Even if you don't have to type them, you might have to check them at some point. So, I'm still favouring semicola.
No responses can be added.
If you can, please log in before submitting a reaction.
