All of lore.kernel.org
 help / color / mirror / Atom feed
From: CityK <cityk@rogers.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: V4L Mailing List <linux-media@vger.kernel.org>
Subject: Re: problem building v4l2-spec from docbook source
Date: Wed, 09 Sep 2009 00:07:05 -0400	[thread overview]
Message-ID: <4AA729E9.2080601@rogers.com> (raw)
In-Reply-To: <20090907040048.369308a1@caramujo.chehab.org>

Mauro Carvalho Chehab wrote:
> Em Sun, 6 Sep 2009 22:25:25 -0300
> Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
>
>   
>> Em Sat, 05 Sep 2009 18:54:27 +0100
>> Peter Brouwer <pb.maillists@googlemail.com> escreveu:
>>
>>     
>>> Is it possible to create a link on the linuxtv.org website to the latest dvb and 
>>> v4l spec in pdf?
>>> For dvb the v3 is still on the documentation page.
>>>       
>> The pdf version of V4L2 spec is currently broken: several tables and graphics
>> don't fit at the page size. If you (or someone else) is interested on fixing
>> it, I'll add a pointer at linuxtv.org  for the updated version, and improve the
>> script to auto-generate it.
>>
>> In the case of the DVB spec, the version of the current document is version 3.
>> Patrick's ISDB-T patch series are increasing version to 5.1, but there are
>> still some missing parts when comparing with the current API.
>>
>> In order to make easier for people to maintain the DVB API and to allow people
>> of just using just one language and document generation tools, I've converted the
>> DVB API specs to DocBook as well. I'll add it to the tree soon. It is yet a
>> work undergoing, but it would be nice if people could review it and improve.
>> After having some review and porting the ISDB-T changes to it, IMO, the better
>> is to deprecate the LaTex version using the DocBooc version one instead.
>>
>>     
>
> I've updated the Documentation page at linuxtv.org to warn people to not trust
> at V4L2 spec pdf file, while nobody fixes it. I also added there a link to the
> dvbapi spec generated via the newly DocBook port of the docs that I posted at:
> 	http://linuxtv.org/hg/~mchehab/dvb-specs
>
> This way, it will be easier for people to double check if nothing were lost
> during the format conversion. IMHO, one of the biggest advantage of the html
> generated from DocBook is that the chapter/section numbering is preserved,
> while, with the LaTex version, they are shown only at the pdf doc. It should be
> noticed that, as no styles are applied to the tables, that they are not
> nicely displayed at the DocBook version.
>   

We've got too many entry points/links to things -- which lends itself to
becoming a maintenance nightmare  (not blaming anyone, just pointing out
the obvious).  For example:  although the updated info was applied here:
http://www.linuxtv.org/docs.php, we have other avenues such as
http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/  (as linked
to by, for example,  from here
:http://www.linuxtv.org/wiki/index.php/Development:_Video4Linux_APIs)
that do not reflect those changes, and hence we have inconsistent info
across the board. 

Same goes with mailing lists and #irc channels -- we've got too many of
them! ... /trails off mumbling about this and that....mumble mumble
mumble grumble....

  reply	other threads:[~2009-09-09  4:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30  8:20 problem building v4l2-spec from docbook source Németh Márton
2009-08-31 12:42 ` William M. Brack
2009-08-31 16:52   ` Mauro Carvalho Chehab
2009-09-01  0:35     ` Mauro Carvalho Chehab
2009-09-01  6:59       ` Hans Verkuil
2009-09-01  8:49         ` Laurent Pinchart
2009-09-01  8:55           ` Hans Verkuil
2009-09-01 13:11             ` Mauro Carvalho Chehab
2009-09-03  5:23   ` Németh Márton
2009-09-03 11:54     ` Mauro Carvalho Chehab
2009-09-03 12:08       ` Mauro Carvalho Chehab
2009-09-04 14:43         ` Németh Márton
2009-09-05 17:54           ` Peter Brouwer
2009-09-07  1:25             ` Mauro Carvalho Chehab
2009-09-07  7:00               ` Mauro Carvalho Chehab
2009-09-09  4:07                 ` CityK [this message]
2009-09-12 16:19                   ` Mauro Carvalho Chehab

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=4AA729E9.2080601@rogers.com \
    --to=cityk@rogers.com \
    --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.