>
> > >> Would be nice if there was a "fossil ticket export" command that would
> > >> produce a "proper" CSV file. {snip}
> > > 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 {snip}
>
> If you want to get files with newlines etc into Excel, your best bet is
> always the libreoffice round. Alternatively, creating Office XML might
> also be an option.{snip}Maybe JSON is a better bet. Fossil could support a JSON ticket dump in some standard form. And hey, we can reuse someone's work who has already figured out a decent way to represent a ticket database in JSON: https://confluence.atlassian.com/jira/importing-data-from-json-495976468.html So if you follow that form, then you get your Jira export capability for free. :-) Eric
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
