octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58374] print function creates path not readab


From: Folken
Subject: [Octave-bug-tracker] [bug #58374] print function creates path not readable by latex
Date: Mon, 18 May 2020 12:50:05 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36

Follow-up Comment #11, bug #58374 (project octave):

@Rik: I did place the code to the desctibed spot but it did not work (for me)

I also run the print command wthout a path but latex was not able to find the
picture from the \includegraphics command in the tex. file (this might be due
to my limited latex capabilities..)

If I understand the print.m code correctly, then the pdflatexstandalone almost
creates the same .tex file as pdflatex. Only without lines 979 and 981
(prepend and postpend)? Could that be used?

fid = fopen (latexfile, "w");
  if (fid >= 0)
    fprintf (fid, "%s\n", prepend{:});
    fprintf (fid, "%s", latex);
    fprintf (fid, "%s\n", postpend{:});
    status = fclose (fid);
    if (status != 0)

Still the problem occurs, that running the *strrep* in the print.m fiel gives
\ and only running it in the comand window gives the usable /? Why is there a
difference?

latex = strrep (latex, "\\includegraphics{}",
                  sprintf ("\\includegraphics{%s}", graphicsfile))



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58374>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]