From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-usb@vger.kernel.org
Subject: Re: make xmldocs failed with error after 4.17 merge period
Date: Fri, 6 Apr 2018 13:51:39 +0300 [thread overview]
Message-ID: <20180406105139.GA28862@kuha.fi.intel.com> (raw)
In-Reply-To: <2A917B38-AFF6-44DC-A4A9-796B2BE560E2@darmarit.de>
Hi Markus,
On Fri, Apr 06, 2018 at 12:03:55PM +0200, Markus Heiser wrote:
> >> There are ways to do this, look at how the v4l2 and I think the drm
> >> subsystems handle ascii art such that "real" drawings end up being
> >> produced.
> >
> > Thanks. I did not actually find anything else except use of tables and
> > code-blocks in v4l documentation. Is that what you were referring?
>
> If it is about *figures*: we have a directive named 'kernel-figure',
> which is a full replacement of the 'figure' directive from Sphinx-Doc.
> In addition it supports *inline* SVG and DOT markups. Read:
>
> https://www.kernel.org/doc/html/latest/doc-guide/sphinx.html#figures-images
Thanks for the info.
I don't want to use for example dot language in kernel documentation.
I want to be able to clearly see the figure also from the plain text
file. That's why I prefer ascii art.
Isn't there a way we could render ascii art as svg diagram?
Br,
--
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-06 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 3:38 make xmldocs failed with error after 4.17 merge period Masanari Iida
2018-04-06 7:51 ` Heikki Krogerus
2018-04-06 7:57 ` Greg KH
2018-04-06 8:15 ` Heikki Krogerus
2018-04-06 8:30 ` Greg KH
2018-04-06 9:11 ` Heikki Krogerus
2018-04-06 10:03 ` Markus Heiser
2018-04-06 10:51 ` Heikki Krogerus [this message]
2018-04-06 11:38 ` Markus Heiser
2018-04-07 19:19 ` Johannes Berg
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=20180406105139.GA28862@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=standby24x7@gmail.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;
as well as URLs for NNTP newsgroup(s).