From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Lomov Subject: Re: Org can't export inline image link to PDF Date: Sat, 23 Feb 2019 09:56:37 +0800 Message-ID: <20190223015637.GA873@smoon.vl-lomov.ru> References: <87bm37cdic.fsf@gmail.com> <877edudipw.fsf@gmail.com> <87tvgysf8f.fsf@nicolasgoaziou.fr> <8736oiwjkt.fsf@gmail.com> <87bm352oh8.fsf@nicolasgoaziou.fr> <87h8cwmbd2.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:40949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gxMYc-0005DU-0N for emacs-orgmode@gnu.org; Fri, 22 Feb 2019 20:56:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gxMYa-0006Ig-2V for emacs-orgmode@gnu.org; Fri, 22 Feb 2019 20:56:49 -0500 Received: from forward105o.mail.yandex.net ([37.140.190.183]:53275) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gxMYW-00067J-36 for emacs-orgmode@gnu.org; Fri, 22 Feb 2019 20:56:46 -0500 Received: from mxback16o.mail.yandex.net (mxback16o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::67]) by forward105o.mail.yandex.net (Yandex) with ESMTP id 334694200657 for ; Sat, 23 Feb 2019 04:56:39 +0300 (MSK) Content-Disposition: inline In-Reply-To: <87h8cwmbd2.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, ** stardiviner [2019-02-22 17:16:41 +0800]: >=20 > Nicolas Goaziou writes: >=20 >> Hello, >> >> stardiviner 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 =E9=82=A3=E6=97=B623=E5=B2=81= =E7=9A=84=E6=88=91 >>> [[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. >=20 > I checked the =3DResume.tex=3D file. The raw latex is this: >=20 > #+begin_src latex > \begin{center} > \includegraphics[width=3D2.0in]{data/images/me_picture 23.jpg} > \end{center} > #+end_src >=20 > 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, >=20 >=20 > -- > [ stardiviner ] > I try to make every word tell the meaning what I want to express. >=20 > Blog: https://stardiviner.github.io/ > IRC(freenode): stardiviner, Matrix: stardiviner > GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 >=20 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 --=20 Will this never-ending series of PLEASURABLE EVENTS never cease? --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQaopaKwcQWyz7yQfAHGfInzJc4BQUCXHCoVQAKCRAHGfInzJc4 BaRhAP9IoJDfbiHMo8WXvfRprKk3nTpHf32+RjUMe+rLd+5oAAD/T13QCbu2oMek BZ+A6iD50EYUN9jRKgZjKNhSU8NIAwo= =VVi+ -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs--