<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">El 04/07/13 13:10, Jacob Vanderplas
escribió:<br>
</div>
<blockquote
cite="mid:CACpqBg265CxVfLBjzamLu6EHPGfG3ejPaR7iPMDXx0Bc3tGGSQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div style="">I've been working on adapting the recently-merged
nbconvert refactor to work with my Pelican blogging plugin,
and am having a really difficult time. In particular, the
header content produced by the new nbconvert (via
CSSHTMLHeaderTransformer) contains a lot of extra stuff
compared to the old version. This is conflicting with the
default blog theme, and leading to some results which are not
very pretty.</div>
<div style=""><br>
</div>
<div style="">In the old iteration of the notebook plugin, I
used about half a dozen regular expression replace statements
to modify the stylesheet & content and make it play well
with the blog style. My hope was that the new nbconvert would
be flexible enough to obviate the need for this sort of
text-mangling; in reality the required text-mangling in the
new version is much more extensive. I've been working at it
for several hours, and still don't have a suitable solution
that leads to nicely-formatted notebooks within blog posts.</div>
<div style=""><br>
</div>
<div style="">For those of you familiar with the new nbconvert:
what is the reason for the changes in the default CSS styles
between nbconvert 1 and 2? Is there a good way to recover the
old style sheet within the new codebase?</div>
<div style=""><br>
</div>
<div style="">Thanks,</div>
<div style=""> Jake</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
IPython-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a>
<a class="moz-txt-link-freetext" href="http://mail.scipy.org/mailman/listinfo/ipython-dev">http://mail.scipy.org/mailman/listinfo/ipython-dev</a>
</pre>
</blockquote>
<br>
Hi Jake, <br>
<br>
As far as I know, the changes in css are derived by the
incorporation of the less machinery to get the final css.<br>
The changes were done in the general IPython css styling, and
nbconvert is just reading the new style contained in style.min.css.<br>
Probably Mathias can go deeper in the explanation because he PRed
the changes involving less.<br>
<br>
You can always get the old style sheet from previous versions of
IPython, make an old_ipython.css file and include it in your head
instead of the new styling.<br>
This is the way I used to do it in my plugin for Nikola,
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<span style="color: rgb(0, 0, 0); font-family: arial, sans-serif;
font-size: 13px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: left; text-indent: 0px; text-transform:
none; white-space: nowrap; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration: underline;
display: inline !important; float: none;"></span> although I am
migrating to the new styling very soon.<br>
<br>
Hope it helps.<br>
<br>
Damián.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>