diff options
| author | Arnold D. Robbins <arnold@skeeve.com> | 2014-11-19 17:33:21 +0200 |
|---|---|---|
| committer | Arnold D. Robbins <arnold@skeeve.com> | 2014-11-19 17:37:42 +0200 |
| commit | f862e8fe648ed66662417bc37b20980fe7780eec (patch) | |
| tree | f1f49b6e5e7c949ddafc245cba1cece64e6d34dc /doc/gawktexi.in | |
| parent | 46fb38d70fe250f318fb95a6083beaceaaf5155d (diff) | |
| download | egawk-f862e8fe648ed66662417bc37b20980fe7780eec.tar.gz egawk-f862e8fe648ed66662417bc37b20980fe7780eec.tar.bz2 egawk-f862e8fe648ed66662417bc37b20980fe7780eec.zip | |
Document that RFC 4180 describes CSV data.
Diffstat (limited to 'doc/gawktexi.in')
| -rw-r--r-- | doc/gawktexi.in | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/gawktexi.in b/doc/gawktexi.in index 1ea028d4..7979b0ad 100644 --- a/doc/gawktexi.in +++ b/doc/gawktexi.in @@ -7402,10 +7402,12 @@ is so-called @dfn{comma-separated values} (CSV) data. Many spreadsheet programs, for example, can export their data into text files, where each record is terminated with a newline, and fields are separated by commas. If only commas separated the data, there wouldn't be an issue. The problem comes when -one of the fields contains an @emph{embedded} comma. Although there is no -formal standard specification for CSV data,@footnote{At least, we don't know of one.} -in such cases, most programs embed the field in double quotes. So we might -have data like this: +one of the fields contains an @emph{embedded} comma. +In such cases, most programs embed the field in double quotes.@footnote{The +CSV format lacked a formal standard definition for many years. +@uref{http://www.ietf.org/rfc/rfc4180.txt, RFC 4180} +standardizes the most common practices.} +So we might have data like this: @example @c file eg/misc/addresses.csv |