-
-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug in conversion powers in to LaTeX #7406
Comments
This comment has been minimized.
This comment has been minimized.
Changed keywords from latex, power, jsmath to latex, power, jsmath, pynac |
comment:3
Perhaps close problem is
Note missing \left and \right at outside parentheses which makes the rendering of the expression far from perfect. Should look like
|
add doctests |
comment:4
Attachment: trac_7406-power_latex.patch.gz The new pynac package here http://sage.math.washington.edu/home/burcin/pynac/pynac-0.1.10.spkg contains fixes for both the problem in the description and the one in comment:3. attachment: trac_7406-power_latex.patch contains doctests for the fix. Note that the new pynac version also contains fixes for #7508 and #7264. Tests should be run with the patches from those tickets also applied in this order: |
Author: Burcin Erocal |
comment:5
Positive review - they look great in show()! Obviously pending #7264 or a rebase. |
Reviewer: Karl-Dieter Crisman |
Merged: sage-4.3.rc0 |
The LaTeX representation of (xpi)e is not valid TeX string and is not rendered by jsmath
Burcin suggested how to fix this and get output like
However a better fix would be to get
if the base is an atom (or not power) and
if the base is a power. This allows to distinguish easily between
and
A workaround is to remove powers of powers by simplification. For example radcan function from Maxima perfoms such simplifications
Component: symbolics
Keywords: latex, power, jsmath, pynac
Author: Burcin Erocal
Reviewer: Karl-Dieter Crisman
Merged: sage-4.3.rc0
Issue created by migration from https://trac.sagemath.org/ticket/7406
The text was updated successfully, but these errors were encountered: