El 17/12/2015 a las 17:28, Ross Berteig escribió: > On 12/16/2015 6:42 PM, Ron W wrote:
>> Would be nice if there was a "fossil ticket export" command that would >> produce a "proper" CSV file. While "proper" is still something of a >> debate, most spread sheet apps (Excel, LibreCalc, GnomeCalc, etc) seem to >> adequately digest CSV files where fields that contain comas or newlines >> are enclosed in double quotes, with any contained double quote escaped (I >> think by doubling - ie. like "has ""quote"" inside"). > > A problem with CSV is that there really isn't a clear definition of it at > its edge cases other than testing what Excel will import correctly. Which is a sorry state of things, in itself. Reading an article about support of CSV files in PostgreSQL (at http://www.pg-versus-ms.com/), I learned that there is somewhat of a standard of CSV defined as a RFC at http://tools.ietf.org/html/rfc4180; I also learned that no Microsoft product (including MSSQL Server, Excel and Access) can import the standards-compliant file linked in the article. So apparently your use of JSON was the safest course of action. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
