From: Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Bug: Texinfo export: Inline images are NOT rendered in INFO viewer [9.4.5 (release_9.4.5-354-g40b70c @ /home/rameshnedunchezian/src/org-mode/lisp/)]
Date: Fri, 30 Apr 2021 15:34:14 +0530 [thread overview]
Message-ID: <TY2PR0101MB3693187B93665E208637F6C8DA5E9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Bug: Texinfo export: Inline images are NOT rendered in INFO viewer
[9.4.5 (release_9.4.5-354-g40b70c @ /home/rameshnedunchezian/src/org-mode/lisp/)]
1. Unzip the attached zip file.
2. C-x C-f doc/helm.org. Note that it has inline image.
3. C-u C-h i doc/helm.info and rename the buffer. Note that it doesn't
display the inline image.
4. C-u C-h i doc/helm-1.info and rename the buffer. Note that it DOES
display the inline image.
See the attached screenshot for what the above steps looks like.
(3) above is a bug. (4) above is after applying the remedy.
You can do a
./helm.sh
to recreate the above texi files. This file also has additional
observations.
TLDR: The presence of leading "./" in texi file's `@image ...'
creates the problem.
[-- Attachment #2: helm.zip --]
[-- Type: application/zip, Size: 243844 bytes --]
[-- Attachment #3: Screenshot from 2021-04-30 15-23-46.png --]
[-- Type: image/png, Size: 183146 bytes --]
next reply other threads:[~2021-04-30 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 10:04 Ramesh Nedunchezian [this message]
2022-10-19 2:14 ` Bug: Texinfo export: Inline images are NOT rendered in INFO viewer [9.4.5 (release_9.4.5-354-g40b70c @ /home/rameshnedunchezian/src/org-mode/lisp/)] Ihor Radchenko
[not found] <4a08cf5b-b78f-7250-bdae-71753dacc809@outlook.com>
2021-04-30 10:26 ` Ramesh Nedunchezian
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TY2PR0101MB3693187B93665E208637F6C8DA5E9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com \
--to=rameshnedunchezian@outlook.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).