From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 04/35] DocBook: fix emphasis at the DVB documentation
Date: Tue, 2 Jun 2015 10:02:24 -0300 [thread overview]
Message-ID: <20150602100224.201e2e86@recife.lan> (raw)
In-Reply-To: <20150602085138.72d453e3@recife.lan>
Em Tue, 2 Jun 2015 08:51:38 -0300
Mauro Carvalho Chehab <mchehab@osg.samsung.com> escreveu:
> Em Tue, 02 Jun 2015 11:56:04 +0900
> Jonathan Corbet <corbet@lwn.net> escreveu:
>
> > On Thu, 28 May 2015 18:49:07 -0300
> > Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote:
> >
> > > Currently, it is using 'role="tt"', but this is not defined at
> > > the DocBook 4.5 spec. The net result is that no emphasis happens.
> > >
> > > So, replace them to bold emphasis.
> >
> > Nit: I suspect the intent of the "emphasis" here was to get the code in a
> > monospace font, which "bold" is unlikely to do. Isn't there a
> > role="code" or something useful like that to use? I'd have to go look.
>
> Good point! I think that emphasis only does italic (with is the default,
> and don't need role option) or bold on DocBook 4.5.
>
> We're using <constant> on the places where we want a monospace font.
> That's probably the right tag there.
>
> For the record: this document was produced by merging two different
> documents: the V4L docbook (that used a legacy DocBook version - 3.x or
> 2.x) and the DVB LaTex documentation, which was converted by some
> tool to docbook 3.x (or 2.x) to match the same DocBook spec that
> V4L were using. The 'role="tt"' came from such conversion. This
> were maintained together with the legacy Mercurial tree that was
> used to contain the media drivers.
>
> When we moved to git, the DocBook got merged in the Kernel and
> another conversion was taken to allow compiling it using DocBook 4.x.
> We only checked the tags that didn't compile, but options with
> invalid arguments like 'role="tt"' where xmllint doesn't complain
> weren't touched.
>
> One question: any plans to update the documentation to DocBook schema?
Gah, something got wrong on my edition on the above line...
I meant to say, instead:
"One question: any plans to update the DocBook schema on the documentation?"
>
> We're using either schema 4.1 or 4.2, with are both very old. The
> latest 4.x is 4.5, with was written back on 2006. So, except for historic
> reasons, are there any reason why keeping them at version 4.2?
> I did a quick look at the DocBook specs (for 4.3, 4.4 and 4.5),
> and they say that no backward compatible changes were done. So, using
> version 4.5 should be straightforward.
>
> I applied this patch here:
>
> --- a/Documentation/DocBook/media_api.tmpl
> +++ b/Documentation/DocBook/media_api.tmpl
> @@ -2,2 +2,2 @@
> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
>
> and compiled the media documentation with:
>
> make cleanmediadocs
> make DOCBOOKS=media_api.xml htmldocs 2>&1 | grep -v "element.*: validity error : ID
> .* already defined"
> xmllint --noent --postvalid "$PWD/Documentation/DocBook/media_api.xml" >/tmp/x.xml 2>/dev/null
> xmllint --noent --postvalid --noout /tmp/x.xml
> xmlto html-nochunks -m ./Documentation/DocBook/stylesheet.xsl -o Documentation/DocBook/media Documentation/DocBook/media_api.xml >/dev/null 2>&1
>
> In order to try to produce errors. Everything seemed to work. On a quick
> look, the documentation looked fine, and no errors (except for some
> crappy element validity errors, with seems to be due to a bug on recent
> versions of the xml tools present on Fedora 22).
I did a diff between what's produced with v4.2 and v4.5 using:
make cleanmediadocs
make DOCBOOKS=media_api.xml htmldocs 2>&1 | grep -v "element.*: validity error : ID .* already defined"
xmlto html-nochunks -m ./Documentation/DocBook/stylesheet.xsl -o Documentation/DocBook/media Documentation/DocBook/media_api.xml >/dev/null 2>&1
cat Documentation/DocBook/media/media_api.html |sed s,'>','>\n',g >v4.2
Then applying the patch and doing the same.
Except for auto-generated naming references:
--- v4.2 2015-06-02 09:51:14.867426792 -0300
+++ v4.5 2015-06-02 09:51:21.030553531 -0300
@@ -24 +24 @@ Copyright <A9> 2009-2014 LinuxTV Developers
-<a name="idm140503220604352">
+<a name="idm140423402024512">
@@ -45 +45 @@ Table of Contents</b>
-<a href="#idm140503221376592">
+<a href="#idm140423402329888">
The document looks the same.
So, I'll likely send on my next docbook patch series a patch
changing the DTD to DocBook schema 4.5, with is the latest 4.x
spec.
Still, the question remains: are there any value on changing it to
5.0?
Regards,
Mauro
next prev parent reply other threads:[~2015-06-02 13:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 21:49 [PATCH 00/35] Improve DVB frontend API documentation Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 01/35] DocBook: Update DVB supported standards at introduction Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 02/35] DocBook: add a note about the ALSA API Mauro Carvalho Chehab
2015-06-02 2:50 ` Jonathan Corbet
2015-05-28 21:49 ` [PATCH 03/35] DocBook: add drawing with a typical media device Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 04/35] DocBook: fix emphasis at the DVB documentation Mauro Carvalho Chehab
2015-06-02 2:56 ` Jonathan Corbet
2015-06-02 11:51 ` Mauro Carvalho Chehab
2015-06-02 13:02 ` Mauro Carvalho Chehab [this message]
2015-05-28 21:49 ` [PATCH 05/35] DocBook: Improve DVB frontend description Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 06/35] DocBook: move DVBv3 frontend bits to a separate section Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 07/35] dvb: split enum from typedefs at frontend.h Mauro Carvalho Chehab
2015-05-28 21:57 ` Hans Verkuil
2015-05-28 22:22 ` Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 08/35] DocBook: reformat FE_GET_INFO ioctl documentation Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 09/35] DocBook: move FE_GET_INFO to a separate xml file Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 10/35] DocBook: improve documentation for FE_READ_STATUS Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 11/35] DocBook: move DVB properties to happen earlier at the document Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 12/35] DocBook: rewrite FE_GET_PROPERTY/FE_SET_PROPERTY to use the std way Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 13/35] DocBook: fix xref to the FE open() function Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 14/35] DocBook: Merge FE_SET_PROPERTY/FE_GET_PROPERTY ioctl description Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 15/35] DocBook: Improve the description of the properties API Mauro Carvalho Chehab
2015-06-02 3:03 ` Jonathan Corbet
2015-05-28 21:49 ` [PATCH 16/35] DocBook: Add xref links for DTV propeties Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 17/35] DocBook: Improve xref check for undocumented ioctls Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 18/35] DocBook: remove duplicated ioctl from v4l2-subdev Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 19/35] DocBook: Fix false positive undefined ioctl references Mauro Carvalho Chehab
2015-05-30 12:20 ` Hans Verkuil
2015-05-28 21:49 ` [PATCH 20/35] DocBook: Rename ioctl xml files Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 21/35] DocBook: move FE_GET_PROPERTY to its own xml file Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 22/35] DocBook: reformat FE_SET_FRONTEND_TUNE_MODE ioctl Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 23/35] DocBook: reformat FE_ENABLE_HIGH_LNB_VOLTAGE ioctl Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 24/35] DocBook: better document FE_SET_VOLTAGE ioctl Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 25/35] DocBook: better document FE_SET_TONE ioctl Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 26/35] DocBook: better document FE_DISEQC_SEND_BURST ioctl Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 27/35] DocBook: better document FE_DISEQC_RECV_SLAVE_REPLY Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 28/35] DocBook: better document FE_DISEQC_SEND_MASTER_CMD Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 29/35] DocBook: better document FE_DISEQC_RESET_OVERLOAD Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 30/35] DocBook: better organize the function descriptions for frontend Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 31/35] DocBook: fix FE_READ_STATUS argument description Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 32/35] DocBook: Provide a high-level description for DVB frontend Mauro Carvalho Chehab
2015-06-02 3:08 ` Jonathan Corbet
2015-05-28 21:49 ` [PATCH 33/35] DocBook: add a proper description for dvb_frontend_info.fe_type Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 34/35] DocBook: Better document enum fe_modulation Mauro Carvalho Chehab
2015-05-28 21:49 ` [PATCH 35/35] DocBook: some fixes at FE_GET_INFO Mauro Carvalho Chehab
2015-06-02 3:12 ` [PATCH 00/35] Improve DVB frontend API documentation Jonathan Corbet
2015-06-02 9:26 ` Mauro Carvalho Chehab
2015-06-02 9:33 ` Jonathan Corbet
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=20150602100224.201e2e86@recife.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox