From: Markus Heiser <markus.heiser@darmarit.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: The downside of math::
Date: Thu, 20 Oct 2016 17:15:22 +0200 [thread overview]
Message-ID: <CF522109-3020-4E7D-A9F5-F7DFB61F9B65@darmarit.de> (raw)
In-Reply-To: <877f93qdd2.fsf@intel.com>
Am 20.10.2016 um 16:55 schrieb Jani Nikula <jani.nikula@linux.intel.com>:
>> So, I really prefer not removing math support.
>
> I wonder if we could cook up a nice way to make the math:: usage
> conditional on actually being able to render it.
>
> I would rather have the math:: directive produce just the preformatted
> indented block as-is in the html output, instead of failing, when latex
> is not available.
>
> Adapt to the environment, produce the prettiest thing when you can, but
> fallback to something uglier if all the dependencies are not there. See
> what I did with the sphinx_rtd_theme in conf.py - we use it if it's
> there, but it's not a hard dependency.
Hi Jani,
you are right. I will add this point to my TODO list. Give me just
a view days / ATM I'am working on a other project.
--Markus--
next prev parent reply other threads:[~2016-10-20 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 23:02 The downside of math:: Jonathan Corbet
2016-10-20 0:26 ` Mauro Carvalho Chehab
2016-10-20 0:48 ` Mauro Carvalho Chehab
2016-10-20 14:55 ` Jani Nikula
2016-10-20 15:15 ` Markus Heiser [this message]
2016-10-21 21:38 ` Jonathan Corbet
2016-10-23 10:58 ` Markus Heiser
2016-10-24 7:52 ` Johannes Berg
2016-10-24 8:22 ` Jani Nikula
2016-10-24 8:26 ` Johannes Berg
2016-10-24 9:06 ` Jani Nikula
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=CF522109-3020-4E7D-A9F5-F7DFB61F9B65@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.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 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.