From: Vladimir Lomov <v.p.lomov@yandex.ru>
To: stardiviner <numbchild@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org can't export inline image link to PDF
Date: Mon, 25 Feb 2019 21:38:38 +0800 [thread overview]
Message-ID: <20190225133838.GE904@smoon.vl-lomov.ru> (raw)
In-Reply-To: <87va1au7s6.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]
Hello,
** stardiviner [2019-02-23 18:19:05 +0800]:
[...]
>>> 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.
>
> I have not found '.bb' files. Neither '.ps.bb' files. I checked out variable
> ~org-latex-packages-alist~, it have 'grffile' and 'graphicx' packages.
>> 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.
The LaTeX cannot work directly with graphic files. In past when only
latex and dvips were existed a user was able to use only PS/EPS graphic
files. latex can work with any graphic files using graphics/graphicx
package. One of the purpose of the package is to provide to latex
information about the size of a figure (Bounding Box) what is found in
EPS file. Sometimes EPS files were gzipped but latex was unable on-fly
decompress them and extract BB information. The workaround for this
situation is to either provide bb keyword for '\includegraphics' command
or create file with extension .eps.bb which will hold necessary
information. Actual inclusion of graphic file was done by dvips program.
Nowadays almost everyone uses pdflatex/xelatex/luatex engines. They use
graphic files in format PDF (native), PNG, JPEG. In most situations the
engine could determine the size of a figure but when it fails it will
include the figure with wrong size.
The problem that you faced is a bit another, while it is looked as being
related to missing BB (bounding box): the latex engine don't like the
space in file name. pdflatex engine being run in special mode don't stop
on missing file but show you information about missing .bb file. A
workaround to use graphic files with spaces in file name is to use
package 'grffile'. Note, however, this workaround is only for graphic
files and don't work to input other LaTeX files with spaces in they
filenames into current one.
---
WBR, Vladimir Lomov
--
Sales tax applies.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-02-25 13:38 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
2019-02-23 10:19 ` stardiviner
2019-02-25 13:38 ` Vladimir Lomov [this message]
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=20190225133838.GE904@smoon.vl-lomov.ru \
--to=v.p.lomov@yandex.ru \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.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.
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).