#6089: [with patch, needs work] view command: don't always use jsMath
-------------------------+--------------------------------------------------
Reporter: jhpalmieri | Owner: jhpalmieri
Type: enhancement | Status: new
Priority: minor | Milestone: sage-4.0.1
Component: misc | Keywords:
-------------------------+--------------------------------------------------
Comment(by rbeezer):
I installed the latest patch on top of my own work on #5975, just to have
a few more examples to practice with.
With all the right programs installed (dvipng, convert, dvips, etc.) this
seems to work as advertised both at the command line and in the notebook.
The only oddity I noticed is the following: Let g and k be the graph
and knot examples, respectively, from the {{{latex_examples}}} class.
Then in the notebook execute {{{view([k,g])}}}. The graphic for the knot
is centered vertically relative to the comma, but the graphic for the
graph has its bottom edge aligned with the commas. More experimentation
with other objects, including other graphs, would indicate that it is the
graphs that are behaving differently, but perhaps it is just the graphics
format used, or converter applied? Since the graph example is big, the
left/right brackets are much longer than needed below the midline.
When moving dvipng and convert out of the way, I ran into more serious
problems.
Remove just dvipng, then in notebook run {{{view(k)}}} (with correct
preamble, jsmath-avoid, etc).[[BR]]
I get a "local unbound variable" e in line 401 of
{{{_run_latex_on_file}}}.[[BR]]
Chasing through the code by hand it seems that e never gets set when
{{{pdflatex}}} is not True and dvipng is missing.[[BR]]
This seems to happen on any of the examples.
Remove just convert, then run {{{view(g)}}} (with correct preamble,
jsmath-avoid, etc).[[BR]]
I get "An error occured", a latex log file, and "Latex error"[[BR]]
To my eye the latex log doesn't seem to present any errors.[[BR]]
I'm less certain just what is happening here.
I found {{{_run_latex_on_file()}}} and {{{png()}}} a bit hard to follow.
I know you've done a lot of rearrangement to accomodate all the cases and
scenarios, but maybe there is more that can be done? Maybe more along the
lines of the return "code" from {{{_run_latex_on_file()}}}, but related to
inputs, targets, processing of tex, etc. I'm still a bit uncomfortable
with all the possibilities, so I don't really have any well-formed ideas
at the moment.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6089#comment:16>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
