From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4 of 4 for 2014.08] manual-text: hide image representations
Date: Sun, 10 Aug 2014 20:35:11 +0200 [thread overview]
Message-ID: <d17274964babdd0b24ad.1407695711@localhost> (raw)
In-Reply-To: <patchbomb.1407695707@localhost>
Images specified in the asciidoc sources (currently only the logo) are
displayed as the file name in the text version of the manual. This causes an
odd line to appear:
logo.png
Avoid this by setting the image representation macros to {empty} in
manual-text.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/asciidoc-text.conf | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff -r a891fa8b7ca9 -r d17274964bab docs/manual/asciidoc-text.conf
--- a/docs/manual/asciidoc-text.conf Sat Aug 09 19:42:30 2014 +0200
+++ b/docs/manual/asciidoc-text.conf Sun Aug 10 17:55:54 2014 +0200
@@ -11,3 +11,9 @@
{0=} [{name}:{target}]
[mailto-inlinemacro]
{0=} [{name}:{target}]
+
+# Hide image representation from text manual
+[image-inlinemacro]
+{empty}
+[image-blockmacro]
+{empty}
prev parent reply other threads:[~2014-08-10 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 18:35 [Buildroot] [PATCH 0 of 4 for 2014.08] manual-text generation improvements Thomas De Schampheleire
2014-08-10 18:35 ` [Buildroot] [PATCH 1 of 4 for 2014.08] gendoc infra: use $(pkgname) instead of explicitly passing 'manual' Thomas De Schampheleire
2014-08-10 18:35 ` [Buildroot] [PATCH 2 of 4 for 2014.08] gendoc infra: add support for asciidoc configuration files Thomas De Schampheleire
2014-08-10 18:35 ` [Buildroot] [PATCH 3 of 4 for 2014.08] manual-text: make sure URLs are displayed if a link text was provided Thomas De Schampheleire
2014-08-12 10:56 ` Thomas De Schampheleire
2014-08-10 18:35 ` Thomas De Schampheleire [this message]
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=d17274964babdd0b24ad.1407695711@localhost \
--to=patrickdepinguin@gmail.com \
--cc=buildroot@busybox.net \
/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