Attempt to standardize table formats

[jgvictores]

Attempt to standardize csv as table format:

• Nice render by github
• Non-binary
• Good export/import via Calc and Excel (when editing plain text becomes unmanagable)

Related: https://github.com/roboticslab-uc3m/teo-hardware-manual/issues/26, roboticslab-uc3m/yarp-devices#161
ToDo: See how this affects https://github.com/roboticslab-uc3m/teo-hardware-manual and https://github.com/roboticslab-uc3m/teo-software-manual

[jgvictores]

@David-Estevez In the specific case of spreadsheets containing formulas, such as https://github.com/roboticslab-uc3m/teo-hardware-manual/issues/26, would it make sense to maintain duplicates?
Maybe append an extra line pointing to source?

[David-Estevez]

The key questions here are:

• Do you need to visualize the data from GitHub? Which format looks better on GitHub for that particular table?
• In the case of needing to visualize the data:
  • Do you want to generate the markdown table each time the .ods is updated by hand/with a script? Or do you prefer to export it directly with Libreoffice?

[jgvictores]

Studying Google Sheets as an option.

cc: @PeterBowman

[jgvictores]

Subtask of #26, check for more related in description, as well as:

• Provide rendered view of tables in gitbook teo-developer-manual#32
• Migrate tables to csv yarp-devices#161 (note that closed selecting csv as format)

[jgvictores]

It seems it would be easy to render the .csv files in gitbook. From https://plugins.gitbook.com/browse?q=csv we see:

• https://plugins.gitbook.com/plugin/include-csv 0.3.0 updated 1 year ago, maintained by TakuroFukamizu
• https://plugins.gitbook.com/plugin/csv-render 0.3.1 updated 7 months ago, maintained by wacdeben (erased github user), says "This is the little bug fix version from the raw gitbook-plugin-include-csv"

Instructions are identical, and both point to https://github.com/TakuroFukamizu/gitbook-plugin-include-csv