From: stardiviner <numbchild@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org can't export inline image link to PDF
Date: Wed, 20 Feb 2019 23:44:34 +0800 [thread overview]
Message-ID: <8736oiwjkt.fsf@gmail.com> (raw)
In-Reply-To: <87tvgysf8f.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> stardiviner <numbchild@gmail.com> writes:
>
>> Now I figured out, because the filename contains a space, which Org auto
>> converted to `%20' when exit org-insert-link. That's why can't see the
>> inline image in exported PDF file. After I renamed image filename with
>> replace space with underline "_". Problem solved.
>>
>> But, if possible, I still hope Org can fix this problem.
>
> Fixed. Thank you.
>
> Regards,
Hi, Nicolas, as always, thanks for quick fix. Still a minor issue.
Here is the screenshot in attachment, you can see the characters 23.bb
left side of the inline image.
The original Org inline image format is:
```org
#+ATTR_ORG: :width 200
#+ATTR_LATEX: :width 2.0in
#+ATTR_HTML: :id avatar :width 200px :alt 那时23岁的我
[[file:data/images/me_picture%2023.jpg]]
```
[-- Attachment #2: ox-latex inline image minor issue.png --]
[-- Type: image/png, Size: 99260 bytes --]
[-- Attachment #3: Type: text/plain, Size: 255 bytes --]
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
next prev parent reply other threads:[~2019-02-20 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 4:03 Org can't export inline image link to PDF stardiviner
2019-02-20 7:25 ` stardiviner
2019-02-20 14:32 ` Nicolas Goaziou
2019-02-20 15:44 ` stardiviner [this message]
2019-02-21 14:41 ` Nicolas Goaziou
2019-02-22 9:16 ` stardiviner
2019-02-23 1:56 ` Vladimir Lomov
2019-02-23 10:19 ` stardiviner
2019-02-25 13:38 ` Vladimir Lomov
2019-02-26 4:35 ` stardiviner
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=8736oiwjkt.fsf@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.