Re: [O] LaTeX > PDF blocked by extender chars in filename

You're welcome! :) Eduardo Mercovich writes: > Aló Felipe. > > > I usually do it from the export menu: C-c C-e l p (export, latex, > pdf). > > > I still never customized that export, thanks a lot for the information > (emacs and orgmode depth and power never cease to

Re: [O] LaTeX > PDF blocked by extender chars in filename

Aló Felipe. To tell Emacs Org mode that you want a .pdf, customize the "org-latex-pdf-process" variable. I usually do it from the export menu: C-c C-e l p (export, latex, pdf). To do so, do, visit: [[help:org-latex-pdf-process]] and click the "customize" link. Near the name, you will see

Re: [O] LaTeX > PDF blocked by extender chars in filename

I forgot to mention... To tell Emacs Org mode that you want a .pdf, customize the "org-latex-pdf-process" variable. To do so, do, visit: [[help:org-latex-pdf-process]] and click the "customize" link. Near the name, you will see a "Value Menu" buttom, it has latexmk there.

Re: [O] LaTeX > PDF blocked by extender chars in filename

Oh... Are you generating .dvi or .pdf? Commonly, .dvi is generated by running: `latex [File path.]' or `latexmk [File path.]'. And, .pdf is commonly generated by running: `pdflatex [File path.]' or `latexmk -pdf [File path.]'. If generating .dvi, the "space" option won't work.

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hi Adonay, Adonay Felipe Nogueira writes: > Also, as a final note, the default grffile inclusion in the Org-to-LaTeX > (and to PDF also) doesn't include the necessary options to make LaTeX > accept spaces and accents in file names. That's OK for compatibility > reasons,

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hello Nicolas. [...] Nicolas, does this means we should modify these little things in Org? Unfortunately these are not "little things". Sorry, it was my ignorance of the infrastructure on which this depends... First, I assume "filenameencoding" is not necessarily utf8, so it cannot be

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hello, Eduardo Mercovich writes: > Rounding up: > + if we include the grffilesetup options "{filenameencoding = utf8, > space}", and > + insert the filename as it is, > + the pdf is exported and the referenced file is correctly included. > > Nicolas, does this means we

Re: [O] LaTeX > PDF blocked by extender chars in filename

Aló Felipe. The grffile package is already included, in: [[help:org-latex-default-packages-alist]] The text above is an Org hyperlink describing the "org-latex-default-packages-alist" variable. Beautiful, loved the link inclusion in the mail, thanks. :) However, grffile, as it is included,

Re: [O] LaTeX > PDF blocked by extender chars in filename

The grffile package is already included, in: [[help:org-latex-default-packages-alist]] The text above is an Org hyperlink describing the "org-latex-default-packages-alist" variable. However, grffile, as it is included, doesn't have any options (this is indicated with the empty quote-unquote

Re: [O] LaTeX > PDF blocked by extender chars in filename

Dear Felipe. This somehow happens to be problematic to me too [...] However, hyperlinks (that is: those between "[[" and "]]") demand percent encoding/escaping. But, it seems that the Org-to-LaTeX exporter isn't translating the hyperlinks to something LaTeX understands (LaTeX expects literal

Re: [O] LaTeX > PDF blocked by extender chars in filename

This somehow happens to be problematic to me too, if for some reason the inclusion of the file isn't made by Org mode itself. For example, we know that "#+INCLUDE:" keywords at the start of the line are Org mode specific includes, and you can place the file references in the first argument with

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hello Nicolas. Repeating the same experiment now results in: 1. Org inserts the same string (file:img/ProcesoDeDise%C3%B1oDeInteraccion.pdf) 2. But export is not blocked! :) Great. 3. The linked file is not present on the exported pdf (may not be an org issue, but about other latex to

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hello, Eduardo Mercovich writes: > Repeating the same experiment now results in: > > 1. Org inserts the same string > (file:img/ProcesoDeDise%C3%B1oDeInteraccion.pdf) > > 2. But export is not blocked! :) Great. > 3. The linked file is not present on the exported pdf

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hi Thomas. In my experience, having both org and org-plus-contrib installed is a problem. You might want to settle on the one or the other, then see if your problem persists. I didn't knew that, thanks a lot for the recommendation. :) Based on my (lack of) use of the contributions I

Re: [O] LaTeX > PDF blocked by extender chars in filename

Aloha Eduardo, In my experience, having both org and org-plus-contrib installed is a problem. You might want to settle on the one or the other, then see if your problem persists. hth, Tom Eduardo Mercovich writes: > Hola Nicolas. > >>> The file > img/ProcesoDeDiseñoDeInteraccion.pdf >>> was

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hola Nicolas. The file > img/ProcesoDeDiseñoDeInteraccion.pdf was translated/inserted on the org buffer as > img/ProcesoDeDise%C3%B1oDeInteraccion.pdf What command did you use to "translate/insert" the filename? C-c C-l with keyboard and tab completion. + Org-mode: Org-mode version

Re: [O] LaTeX > PDF blocked by extender chars in filename

Hello, Eduardo Mercovich writes: > The file > img/ProcesoDeDiseñoDeInteraccion.pdf > > was translated/inserted on the org buffer as > > img/ProcesoDeDise%C3%B1oDeInteraccion.pdf What command did you use to "translate/insert" the filename? > > + Org-mode: Org-mode