r21266 - gnucash/trunk/src/plugins/bi_import - Business import: add a note about the quoting differences

[Geert Janssens]

Author: gjanssens
Date: 2011-09-17 13:20:01 -0400 (Sat, 17 Sep 2011)
New Revision: 21266
Trac: http://svn.gnucash.org/trac/changeset/21266

Modified:
   gnucash/trunk/src/plugins/bi_import/README
Log:
Business import: add a note about the quoting differences

Modified: gnucash/trunk/src/plugins/bi_import/README
===================================================================
--- gnucash/trunk/src/plugins/bi_import/README	2011-09-17 17:19:52 UTC (rev 21265)
+++ gnucash/trunk/src/plugins/bi_import/README	2011-09-17 17:20:01 UTC (rev 21266)
@@ -1,5 +1,20 @@
-Things and thoughs AKA the TODO and README pages.
+Things and thoughts AKA the TODO and README pages.
 
 BAD THINGS BAOUT THE IMPORTER
-The importer should be limited to a singe invoice per file, perhaps creating a new invoice number each time.
+The importer should be limited to a single invoice per file, perhaps creating a new invoice number each time.
 Too many fields, and too inflexible field format.
+
+QUOTING
+Depending on the source of the CSV file, different quoting rules are used.
+For example Calc quotes everything that looks like a string, ie
+is not a number or a date.
+Excel, on the other hand is quoting only those fields that contain a field
+separator, therefore in a typical file most strings would not be quoted.
+pgAdminIII is yet another CSV source. The SQL window has an option for
+exporting query results to a CSV file with the following quoting options:
+all fields, only strings, none. When I select 'only
+strings', date fields get quoted, probably because the actual value that goes
+to the file is the result of implicit to_char(date_value) function call.
+The importer tries its best to work in all circumstances, by allowing quotes
+on all fields, but not requiring them.
+See bug https://bugzilla.gnome.org/show_bug.cgi?id=658738 for more details.
\ No newline at end of file