From: Russel Winder <russel@winder.org.uk>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-media@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@intel.com>,
Keith Packard <keithp@keithp.com>,
Graham Whaley <graham.whaley@linux.intel.com>
Subject: Re: V4L docs and docbook
Date: Fri, 19 Feb 2016 08:28:13 +0000 [thread overview]
Message-ID: <1455870493.8834.8.camel@winder.org.uk> (raw)
In-Reply-To: <20160218072806.04484884@recife.lan>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
On Thu, 2016-02-18 at 07:28 -0200, Mauro Carvalho Chehab wrote:
> Em Thu, 18 Feb 2016 07:10:14 -0200
> […]
>
> Stupid me: it should be just:
> asciidoc book.asciidoc
>
> Still, there are lots of broken things there, and lots of errors when
> building it:
> https://mchehab.fedorapeople.org/media-kabi-docs-test/book.html
>
> Ok, I would expect the need to handling some things manually, but
> it worries that it broke the tables. For example, see
> "Table 1. Control IDs" at https://mchehab.fedorapeople.org/media-kabi
> -docs-test/book.html
>
> It was mapped as a 3 cols table, but this is how it should be,
> instead:
> https://linuxtv.org/downloads/v4l-dvb-apis/control.html
>
> As this table has actually 5 cols, because some controls have a list
> of multiple values (see V4L2_CID_COLORFX for example).
I will not be able to do anything to help with any of this today, but I
can try and take a look tomorrow.
Certainly an automated translation will not do all the complicated
bits, that will need manual intervention. I may well be able to assist
on this. I think the transform from DocBook/XML is worth a bit of up
front effort now, so as to make everything so much easier for all
concerned in the future. Obviously I do not have data relating to this
project, just experience and anecdotal evidence from others.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-02-19 8:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 21:52 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 [this message]
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
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=1455870493.8834.8.camel@winder.org.uk \
--to=russel@winder.org.uk \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=graham.whaley@linux.intel.com \
--cc=jani.nikula@intel.com \
--cc=keithp@keithp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®