#18292: Fix HTML output
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_info
Priority: major | Milestone: sage-6.7
Component: notebook | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Andrey Novoseltsev
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/fix_html_output | 1f75112c7b835b8c7cdfdde992d8b86e4e7ab73e
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by novoselt):
OK, I think a nice way to proceed here is:
- make `HTMLExpr` take strings (presumably with HTML code) and turn them
into `HTMLExpr` objects that can be sensibly printed/displayed depending
on the backend
- deprecate `html`: keep its current behaviour of displaying HTML code
that was passed to it, but recommend usage of
`pretty_print(HTMLExpr(...))` instead
- once the deprecation is over, `html` is a great name for the function
that will try to convert its input into `HTMLExpr` in a smart way, similar
to how `latex` produces `LatexExpr` and perhaps relying on `_html_`
methods which we may or may not have already.
Regarding tables:
- `html.table` should be gone
- `table` should have HTML pretty-printing.
Thoughts/objections?
--
Ticket URL: <http://trac.sagemath.org/ticket/18292#comment:38>
Sage <http://www.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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
