All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Jani Nikula <jani.nikula@intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-doc@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
	Graham Whaley <graham.whaley@linux.intel.com>
Subject: Re: V4L docs and docbook
Date: Thu, 18 Feb 2016 22:00:14 -0700	[thread overview]
Message-ID: <861t89l2g1.fsf@hiro.keithp.com> (raw)
In-Reply-To: <56C5A248.8080902@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 5771 bytes --]

Hans Verkuil <hverkuil@xs4all.nl> writes:

> But good table handling is a prerequisite for us since we rely heavily on that.

I converted an asciidoc document that included some tables to sphinx via
docbook using pandoc; that seemed to generate workable results for me,
but my needs are pretty simple.

Asciidoc has more sophisticated table support, providing the ability to
align text within cells and paint different kinds of borders. Sphinx
provides for spanning rows and columns, and multi-line auto-wrapped cell
contents. The rst docs say there's an emacs mode that can help paint the
source format, but I haven't tried that yet.

In any case, here's some tables from the document I converted:

asciidoc via docbook:

http://altusmetrum.org/AltOS/doc/altusmetrum.html#_altus_metrum_hardware_specifications

sphinx:

http://keithp.com/~keithp/altusmetrum-sphinx/hardwarespecs.html#altus-metrum-hardware-specifications

While completely unconfigurable, rst tables do at least benefit from an
easier to read input syntax; asciidoc tables are about as readable in
source form as troff or latex...

asciidoc:

	.Altus Metrum Flight Computer Electronics
	[options="header"]
	|================================
	|Device | Barometer | Z-axis accel | GPS | 3D sensors | Storage | RF Output | Battery

	|TeleMetrum v1.0
	|MP3H6115 10km (33k')
	|MMA2202 50g
	|SkyTraq
	|-
	|1MB
	|10mW
	|3.7V

	|TeleMetrum v1.1
	|MP3H6115 10km (33k')
	|MMA2202 50g
	|SkyTraq
	|-
	|2MB
	|10mW
	|3.7V

	|TeleMetrum v1.2
	|MP3H6115 10km (33k')
	|ADXL78 70g
	|SkyTraq
	|-
	|2MB
	|10mW
	|3.7V

	|TeleMetrum v2.0
	|MS5607 30km (100k')
	|MMA6555 102g
	|uBlox Max-7Q
	|-
	|8MB
	|40mW
	|3.7V

	|TeleMini v1.0
	|MP3H6115 10km (33k')
	|-
	|-
	|-
	|5kB
	|10mW
	|3.7V

	|EasyMini v1.0
	|MS5607 30km (100k')
	|-
	|-
	|-
	|1MB
	|-
	|3.7-12V

	|TeleMega v1.0
	|MS5607 30km (100k')
	|MMA6555 102g
	|uBlox Max-7Q
	|MPU6000 HMC5883
	|8MB
	|40mW
	|3.7V

	|EasyMega v1.0
	|MS5607 30km (100k')
	|MMA6555 102g
	|-
	|MPU6000 HMC5883
	|8MB
	|-
	|3.7V

	|==============================

rst:

	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| Device    | Barometer | Z-axis    | GPS       | 3D        | Storage   | RF Output | Battery   |
	|           |           | accel     |           | sensors   |           |           |           |
	+===========+===========+===========+===========+===========+===========+===========+===========+
	| TeleMetru | MP3H6115  | MMA2202   | SkyTraq   | -         | 1MB       | 10mW      | 3.7V      |
	| m         | 10km      | 50g       |           |           |           |           |           |
	| v1.0      | (33k')    |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| TeleMetru | MP3H6115  | MMA2202   | SkyTraq   | -         | 2MB       | 10mW      | 3.7V      |
	| m         | 10km      | 50g       |           |           |           |           |           |
	| v1.1      | (33k')    |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| TeleMetru | MP3H6115  | ADXL78    | SkyTraq   | -         | 2MB       | 10mW      | 3.7V      |
	| m         | 10km      | 70g       |           |           |           |           |           |
	| v1.2      | (33k')    |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| TeleMetru | MS5607    | MMA6555   | uBlox     | -         | 8MB       | 40mW      | 3.7V      |
	| m         | 30km      | 102g      | Max-7Q    |           |           |           |           |
	| v2.0      | (100k')   |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| TeleMini  | MP3H6115  | -         | -         | -         | 5kB       | 10mW      | 3.7V      |
	| v1.0      | 10km      |           |           |           |           |           |           |
	|           | (33k')    |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| EasyMini  | MS5607    | -         | -         | -         | 1MB       | -         | 3.7-12V   |
	| v1.0      | 30km      |           |           |           |           |           |           |
	|           | (100k')   |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| TeleMega  | MS5607    | MMA6555   | uBlox     | MPU6000   | 8MB       | 40mW      | 3.7V      |
	| v1.0      | 30km      | 102g      | Max-7Q    | HMC5883   |           |           |           |
	|           | (100k')   |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+
	| EasyMega  | MS5607    | MMA6555   | -         | MPU6000   | 8MB       | -         | 3.7V      |
	| v1.0      | 30km      | 102g      |           | HMC5883   |           |           |           |
	|           | (100k')   |           |           |           |           |           |           |
	+-----------+-----------+-----------+-----------+-----------+-----------+-----------+-----------+


-- 
-keith

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]

      reply	other threads:[~2016-02-20  7:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 21:52 V4L docs and docbook Jonathan Corbet
2016-02-17 23:51 ` Mauro Carvalho Chehab
2016-02-18  8:17   ` Russel Winder
2016-02-18  8:31     ` Mauro Carvalho Chehab
2016-02-18  9:10       ` Mauro Carvalho Chehab
2016-02-18  9:28         ` Mauro Carvalho Chehab
2016-02-19  8:28           ` Russel Winder
2016-02-19 12:34             ` Mauro Carvalho Chehab
2016-02-18  9:37       ` Jani Nikula
2016-02-18 10:03         ` Mauro Carvalho Chehab
2016-02-18  9:33     ` Jani Nikula
2016-02-18  6:53 ` Hans Verkuil
2016-02-18 10:19   ` Jani Nikula
2016-02-18 10:51     ` Hans Verkuil
2016-02-19  5:00       ` Keith Packard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861t89l2g1.fsf@hiro.keithp.com \
    --to=keithp@keithp.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=graham.whaley@linux.intel.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jani.nikula@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.