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

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

[Octave-bug-tracker] [bug #44463] Print command for pdfstandalone device


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #44463] Print command for pdfstandalone device produces output that doesn't compile
Date: Sat, 07 Mar 2015 08:06:37 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15

URL:
  <http://savannah.gnu.org/bugs/?44463>

                 Summary: Print command for pdfstandalone device produces
output that doesn't compile
                 Project: GNU Octave
            Submitted by: sebald
            Submitted on: Sat 07 Mar 2015 08:06:36 AM GMT
                Category: Plotting with OpenGL
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Inaccurate Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

In the print command are these devices:


         `pslatexstandalone'
         `epslatexstandalone'
         `pdflatexstandalone'
                                                  ...In either case,
               the LaTeX file contains an `\includegraphics' command so
               that the generated graphics file is automatically
               included when the LaTeX file is processed...
                                 ...The `pdflatex' device, and any of the
               `standalone' formats, are not available with the Gnuplot
               toolkit.


gnuplot does have epslatexstandalone.  I will correct that with a changeset
from another bug fix at some point.  Aside from that, part of the reason
gnuplot doesn't have those is that, if I recall correctly, there really needs
to be a bounding box in the postscript file in order for LaTeX to properly
include the figure.  I've looked at the outputs for FLTK/OpenGL toolkit and
both the EPS and PS file have bounding boxes, so technically the PS file is an
encapsulated postscript file.  Although the files are quite different because
they are scaled slightly differently, in some sense it is really the extension
that differs...fine.

On the other hand, contrary to what the documentation suggests, including a
PDF file in a LaTeX document isn't possible, unless there is some kind package
to accomplish that, but I doubt that.  I've built a printing demo that sends
the results to a temporary file and processes.  This example shows that,
first, LaTeX can't find the file because it is by default looking for one with
extension .ps or .eps:


! LaTeX Error: File `/tmp/oct-wBFKA0-inc' not found.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

l.12 \includegraphics{/tmp/oct-wBFKA0-inc}


So I copied those temp files over to my account and modified the imported file
to include the full file name with extension.  The error then becomes:


! LaTeX Error: Cannot determine size of graphic in test-pdf.pdf (no
BoundingBox
).

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.12 \includegraphics{test-pdf.pdf}
                                   

The reason is a PDF file hasn't a bounding box.  (At least not in readable
ASCII.)  Really the only thing LaTeX does is look through the EPS file for the
"Bounding Box" size definition so that it knows how much space to leave for
the graphic and instruct DVI where to find the missing contents.  The DVI
processing then embeds the PostScript file in place.

To me, I've always thought of "pdflatex" as being a different flavor of LaTeX.
 I think it has a few extra commands and such and is geared for creating PDF
files directly from processing.  That way pdflatex can create links within the
created file (i.e., PDF viewer can click on links and jump to other parts of
the file, e.g., table of contents).  Type "pdflatex" at the command prompt of
your shell window and notice it is a "separate" program (both pdflatex and
latex may use the same engine on some systems).  I suppose I'd welcome an
actual pdflatex and associated standalone devices, but not at the moment.

So, the question is what to do with this.  pdflatexstandalone produces a
result that doesn't compile for reasons that are the fault of Octave code, so
that's at least a bug.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44463>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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