#10637: Implement sage -sws2rst
------------------------------------------------------------+---------------
Reporter: nthiery | Owner:
jason, mpatel, was
Type: enhancement | Status:
needs_work
Priority: major | Milestone:
sage-5.4
Component: notebook | Resolution:
Keywords: ReST, worksheet | Work issues:
answer questions, math formatting, lists, maybe absolute paths?
Report Upstream: Workaround found; Bug reported upstream. | Reviewers:
Nicolas Thiéry, Jason Grout, Karl-Dieter Crisman, Jason Bandlow, John Palmieri
Authors: Pablo Angulo, Karl-Dieter Crisman | Merged in:
Dependencies: #11080, #11459 | Stopgaps:
------------------------------------------------------------+---------------
Comment (by kcrisman):
> > * The way you replace a span by a `\n` means that sometimes TinyMCE
stuff left over from trying to unformat things gets in a new line.
TinyMCE is annoying that way - sometimes to unitalicize you have to do a
few things. Anyway, users will have to expect lots of newlines because of
that. In one case, I ''intentionally'' had used a lot of different ones,
and since bold isn't a span, but everything else you can do is, the doc
looked kind of weird, lots of new lines. In another case, the text was
colored on purpose.
> > {{{
> > Plot a green <span style="color: #008000;">$y=\sin(x)$</span> together
with...
> > }}}
> > and then it made a new line there. I'm wondering why you chose to
make {{{\n}}} instead of just a space - surely you encountered some "real-
life" examples where that was the better option. I'm assuming we can't
easily take the color info in, if that's the only info.
>
> I don't really remember why I did that, but it also screwed html tables
in some situations, so it's best, and more naturally, made into a space.
Is this the change in `visit_inline_no_tag`? Sorry, I just can't figure
that one out.
> > * Dumb question; is there a way to have an empty cell? Currently you
remove them, but if the input ''and'' output are empty, then maybe it's
supposed to be an empty cell in the "live" documentation... that's
obviously very low priority.
>
> forgot that one too
>
I can't find where you did this.
> > * I found one thing that doesn't show up properly because of the html
blocks being removed - documentation! If one evaluates a cell like
{{{binomial??}}} then that is all html, and just disappears. Maybe just
making it plain text? I'm not sure either, you are right about that being
a pain in the neck to do anything intelligent with.
>
> Regarding docstring like in binomial??, how about we change the sage
code that turns the doctring into html and displays the result, so that it
also leaves a comment with the plain rst? The we could simply catch the
comment...
Well, maybe. That should be a different patch; we should really get this
in.
> > * There isn't much you can do about this, but since "the order
enforced will be the order as encountered" with section heading markup,
one can pretty easily get a lot of {{{SEVERE: Title level inconsistent:}}}
warnings. This is because we have a WYSIWYG editor which doesn't remember
state between cells.
>
> The use case that I find more likely is a worksheet with no heading at
all. I could catch those ones and use the file name as a title: what do
you think?
That's not a bad idea. And I like your catching of the identical heading
thing - that may have been a little of the problem. That said, if only we
could catch this thing... anyway, fixing the no heading worksheet is a
good idea.
Finally, I'm just wondering about a few changes - surely it's obvious what
they do, but I'm lazy.
* The change to `ALL_ENTITIES` in `soup`.
* The `images_dir` stuff - was that in response to anything I said?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10637#comment:85>
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 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.
