A proposal for standardizing TSV files
erack at redhat.com
Thu Nov 3 14:35:36 UTC 2016
On Thursday, 2016-11-03 08:08:23 -0400, Piotr Mitros wrote:
> I do a fair bit of work where I move data between LibreOffice, MySQL,
> Vertica, Google Docs, Hadoop, Python, and a few other systems. The
> formatting of TSV files is ad-hoc. Each system has little differences in
> how strings are escaped, and similar. In addition, there is no way to
> preserve metadata.
> I drafted a modest proposed spec for standardizing TSV files by
> standardizing types, and adding metadata, and was hoping to solicit
> feedback on that proposal:
It seems to me you're attempting to reinvent a wheel. I suggest you take
a look at https://www.w3.org/standards/techs/csv and maybe
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/
Care about Free Software, support the FSFE https://fsfe.org/support/?erack
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the LibreOffice