From: Vladimir Lomov <lomov.vl@yandex.ru>
To: emacs-orgmode@gnu.org
Subject: Re: Org can't export inline image link to PDF
Date: Sat, 23 Feb 2019 09:56:37 +0800 [thread overview]
Message-ID: <20190223015637.GA873@smoon.vl-lomov.ru> (raw)
In-Reply-To: <87h8cwmbd2.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
Hello,
** stardiviner [2019-02-22 17:16:41 +0800]:
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> stardiviner <numbchild@gmail.com> writes:
>>
>>> 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]]
>>
>> Would it be an issue with LaTeX? Does "23.bb" appear anywhere in the
>> LaTeX code generated by Org?
>>
>> Maybe LaTeX experts could chime in.
>
> I checked the =Resume.tex= file. The raw latex is this:
>
> #+begin_src latex
> \begin{center}
> \includegraphics[width=2.0in]{data/images/me_picture 23.jpg}
> \end{center}
> #+end_src
>
> No "23.bb", I search over the whole TeX file, nothing found. But the
> compiled PDF file still have "23.bb".
May be you find what '.bb' file is if you look into the 'graphics'
package documentation (assuming that you use TeX Live run 'texdoc
graphicx', in my local copy on page 13 there is example of .bb file,
search the document for .ps.bb).
As for spaces in file name, if you cannot avoid them use 'grffile'
package with 'graphicx' package.
>>
>> Regards,
>
>
> --
> [ 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
>
P.S. The question how the .bb file comes on scene completely related how
LaTeX works with graphic file. Look into documentation or ask question
on TeX.SO or on texhax mailing list.
---
WBR, Vladimir Lomov
--
Will this never-ending series of PLEASURABLE EVENTS never cease?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-02-23 1:56 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
2019-02-21 14:41 ` Nicolas Goaziou
2019-02-22 9:16 ` stardiviner
2019-02-23 1:56 ` Vladimir Lomov [this message]
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
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=20190223015637.GA873@smoon.vl-lomov.ru \
--to=lomov.vl@yandex.ru \
--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).