From: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
To: Graham Whaley <graham.whaley@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, corbet@lwn.net
Subject: Re: [Intel-gfx] [PATCH 4/5] Documentation: drm: Convert KMS Properties HTML table to CALS
Date: Tue, 1 Sep 2015 14:56:52 -0300 [thread overview]
Message-ID: <55E5E6E4.3070509@collabora.co.uk> (raw)
In-Reply-To: <1440519054.4414.14.camel@linux.intel.com>
On 08/25/2015 01:10 PM, Graham Whaley wrote:
> On Tue, 2015-08-25 at 16:29 +0200, Daniel Vetter wrote:
>> On Tue, Aug 25, 2015 at 10:26:44AM +0100, Graham Whaley wrote:
>>> The KMS Properties table is in HTML format, which is not supported
>>> for building pdfdocs, resulting in the following types of errors:
>>>
>>> jade:/Documentation/DocBook/drm.xml:34413:15:E: there is no
>>> attribute
>>> "border"
>>> jade:/Documentation/DocBook/drm.xml:34413:31:E: there is no
>>> attribute
>>> "cellpadding"
>>> jade:/Documentation/DocBook/drm.xml:34413:47:E: there is no
>>> attribute
>>> "cellspacing"
>>> jade:/Documentation/DocBook/drm.xml:34414:7:E: document type does
>>> not
>>> allow element "tbody" here
>>>
>>> Convert the table over to a CALS format table
>>
>> Hm, long-term plan was to move this table into DOC: comments in the
>> source-code using markdown, which we now have (at least in
>> drm-intel-nightly and also planned to be merged into 4.4). Since this
>> is
>> both a lot of churn I'd like to get there in just 1 step ...
>> -Daniel
> First - I've just noted an erroneous debug comment (or two) left in
> this patch as well, so looks like I will have to re-issue the series
> anyway.
>
> OK. I guess this comes down to a matter of timing...
> From Danilos patch of: f6d6913 (drm/doc: Convert to markdown)
> we can see markdown does not natively support tables, and we'd have to
> make this a fixed width layout like the one in that patch I suspect.
> Danilo - any advice on how you did that other table conversion? I just
> did a pandoc docbook->markdown_github and it looks some way there - but
> of course seems to have not honored the multi-column items, of which
> there are a few. It's probably not too bad to fix up by hand - I'll see
> if I can get that to work...
Hi Graham,
To be honest I didn't have to do any conversion as that table was
already in the header file. I just added 4 spaces so it would be
transformed into fixed width.
However, there's tool you can use to help you: http://pandoc.org/try/
I did a lot of translation there. If your table doesn't have any
spancells, you can put the HTML code there and get the Markdown for free.
Danilo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-09-01 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:26 [PATCH 0/5] Documentation: drm: Make drm.tmpl build as pdfdoc Graham Whaley
2015-08-25 9:26 ` [PATCH 1/5] Documentation: drm: Fix pdfdocs sect/title tags Graham Whaley
2015-08-25 11:34 ` Daniel Vetter
2015-08-25 14:42 ` Graham Whaley
2015-08-25 9:26 ` [PATCH 2/5] Documentation: drm: Fix pdfdocs listitem and abstract <para>s Graham Whaley
2015-08-25 9:26 ` [PATCH 3/5] Documentation: drm: Change <code> to <literal> Graham Whaley
2015-08-25 9:26 ` [PATCH 4/5] Documentation: drm: Convert KMS Properties HTML table to CALS Graham Whaley
2015-08-25 14:29 ` Daniel Vetter
2015-08-25 16:10 ` Graham Whaley
2015-08-26 9:32 ` [Intel-gfx] " Daniel Vetter
2015-09-01 17:56 ` Danilo Cesar Lemes de Paula [this message]
2015-09-02 9:22 ` Graham Whaley
2015-09-02 13:50 ` Graham Whaley
2015-08-25 9:26 ` [PATCH 5/5] Documentation: drm: Unify quoting methods Graham Whaley
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=55E5E6E4.3070509@collabora.co.uk \
--to=danilo.cesar@collabora.co.uk \
--cc=corbet@lwn.net \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=graham.whaley@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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