<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 8 September 2016 at 13:55, Ian Y. Choi <span dir="ltr"><<a href="mailto:ianyrchoi@gmail.com" target="_blank">ianyrchoi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Brian,<br>
<br>
After seeing the mail thread, I have a question on sphinxmark and building PDFs.<br>
<br>
Now I would like to generate PDF files using the same rst sources.<br>
Currently the spec <a href="https://review.openstack.org/#/c/364477/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/364477/</a> is under review,<br>
and at the same time, I am experiencing rst2pdf Sphinx extension on my local environment.<br>
<br>
Then, sphinxmark will also support watermarks for PDFs?<br>
Although I would leave watermarks in PDFs as out of scope in the spec,<br>
if the support of PDF watermarks is possible, then I would like to also consider to include watermarks in PDFs.<br>
<br></blockquote><div><br></div><div>Hi Ian,<br><br></div><div>I don't think that sphinxmark would currently work with rst2pdf, as it applies the watermark by adding a bit of custom CSS to the HTML theme. That said, rst2pdf has an option to add custom pdf stylesheets so I imagine sphinxmark could do something similar for PDFs.<br><br></div><div>As you can see from the thread, we still have some design work to do on the watermarks. When that gets finished we can look into adding PDF support so the HTML and PDF output match. It will probably be easier to do as well when you've implemented the spec.<br><br></div><div>Cheers,<br><br></div><div>Brian<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
With many thanks,<br>
<br>
/Ian<br>
<br>
<br>
Anne Gentle wrote on 9/8/2016 11:02 AM:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Wed, Sep 7, 2016 at 8:07 PM, Brian Moss <<a href="mailto:kallimachos@gmail.com" target="_blank">kallimachos@gmail.com</a> <mailto:<a href="mailto:kallimachos@gmail.com" target="_blank">kallimachos@gmail.com</a>><wbr>> wrote:<br>
<br>
On 7 September 2016 at 23:49, Anne Gentle<br>
<<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a><br></span><span class="">
<mailto:<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwritecl<wbr>ick.com</a>>> wrote:<br>
<br>
<br>
<br>
On Wed, Sep 7, 2016 at 1:51 AM, Brian Moss<br></span><span class="">
<<a href="mailto:kallimachos@gmail.com" target="_blank">kallimachos@gmail.com</a> <mailto:<a href="mailto:kallimachos@gmail.com" target="_blank">kallimachos@gmail.com</a>><wbr>> wrote:<br>
<br>
Hi Mahesh,<br>
<br>
Glad you like it! I think we want the image to repeat down<br>
the page so if someone links to the middle of a long page<br>
they still have an indication of which version they are<br>
looking at. However, perhaps the spacing between images<br>
can be increased so they do not appear as frequently.<br>
<br>
I've filed a couple of issues for sphinxmark to add these<br>
as config options so we can experiment and find the best<br>
look for the OpenStack docs.<br>
<br>
<a href="https://github.com/kallimachos/sphinxmark/issues/12" rel="noreferrer" target="_blank">https://github.com/kallimachos<wbr>/sphinxmark/issues/12</a><br></span>
<<a href="https://github.com/kallimachos/sphinxmark/issues/12" rel="noreferrer" target="_blank">https://github.com/kallimacho<wbr>s/sphinxmark/issues/12</a>><br>
<a href="https://github.com/kallimachos/sphinxmark/issues/13" rel="noreferrer" target="_blank">https://github.com/kallimachos<wbr>/sphinxmark/issues/13</a><span class=""><br>
<<a href="https://github.com/kallimachos/sphinxmark/issues/13" rel="noreferrer" target="_blank">https://github.com/kallimacho<wbr>s/sphinxmark/issues/13</a>><br>
<br>
<br>
<br>
If the solution is experimental, and the readability is poor,<br>
let's revert until we have a design we've all agreed to. Right<br>
now I find it really distracting and hard to read. Maybe I<br>
missed the design phase -- totally possible -- but the current<br>
overlay watermark makes the Mitaka install guide not readable.<br>
<br>
Can you come up with some next steps and let us know the plan?<br>
<br>
Anne<br>
<br>
<br>
A few options that are immediately available would be to reduce<br>
the opacity of the watermark, change its color, and/or reduce the<br>
font size. For example, the current opacity is 40. This is what it<br>
looks like set to 10:<br>
<br>
<a href="http://docs-draft.openstack.org/29/367029/1/check/gate-openstack-manuals-tox-doc-publish-checkbuild/4b8dd8c//publish-docs/draft/install-guide-ubuntu/index.html" rel="noreferrer" target="_blank">http://docs-draft.openstack.or<wbr>g/29/367029/1/check/gate-opens<wbr>tack-manuals-tox-doc-publish-<wbr>checkbuild/4b8dd8c//publish-<wbr>docs/draft/install-guide-<wbr>ubuntu/index.html</a><br>
<<a href="http://docs-draft.openstack.org/29/367029/1/check/gate-openstack-manuals-tox-doc-publish-checkbuild/4b8dd8c//publish-docs/draft/install-guide-ubuntu/index.html" rel="noreferrer" target="_blank">http://docs-draft.openstack.o<wbr>rg/29/367029/1/check/gate-open<wbr>stack-manuals-tox-doc-publish-<wbr>checkbuild/4b8dd8c//publish-<wbr>docs/draft/install-guide-<wbr>ubuntu/index.html</a>><br>
<br>
Alternatively, an image can be used in place of the text if we<br>
have one that is more suitable than the text-based solution.<br>
<br>
If the concern is with having the watermark behind the text and we<br>
want it somewhere else on the page, that will require a bit more<br>
effort to implement.<br>
<br>
If the above config options don't provide the desired result,<br>
watermarks can be turned off by setting 'sphinxmark_enable =<br>
False' in the conf.py files of the relevant books.<br>
<br>
If you have a particular look in mind, let me know and I'll see<br>
what I can do to make it happen. :)<br>
<br>
<br></span>
At the risk of sounding like I'm late to the party or simply being a grumpy cat, I need to point out that the bug you worked against doesn't talk about the design. <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1479166" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ope<wbr>nstack-manuals/+bug/1479166</a> <<a href="https://bugs.launchpad.net/openstack-manuals/+bug/1479166" rel="noreferrer" target="_blank">https://bugs.launchpad.net/op<wbr>enstack-manuals/+bug/1479166</a>><span class=""><br>
<br>
Ideally this solution would have been designed, gotten feedback, tested, then implemented. Right now you're getting feedback so there's still work to be done to get a design then do the right implementation.<br>
<br>
Ideas:<br></span>
* The versioning indicator designs I get the most positive response to are the ones on <a href="http://readthedocs.org" rel="noreferrer" target="_blank">readthedocs.org</a> <<a href="http://readthedocs.org" rel="noreferrer" target="_blank">http://readthedocs.org</a>>. It's in the corner, stays in the same place regardless of scroll point, and it provides links to other versions. Seems to address comment #3 in the bug above more than a background watermark does.<span class=""><br>
<br>
* The design for a watermark we had in the past was vertical rather than horizontal and did not overlap any text. <a href="http://docs.openstack.org/icehouse/install-guide/install/apt-debian/content/" rel="noreferrer" target="_blank">http://docs.openstack.org/iceh<wbr>ouse/install-guide/install/<wbr>apt-debian/content/</a> Your second iteration of more transparency helps but still overlaps the text.<br>
<br>
I'd like more design work up-front please, and more explanation in the bug of how the design addressed the concerns. We can get more use out of this beyond the install guide if it's designed based on input. Think of the CLI guides, they are not tied to a release name but a release number. Can your solution solve for more uses than a word-based release name?<br>
Anne<br>
<br>
<br>
<br>
Brian<br>
<br>
<br>
<br>
Cheers,<br>
<br>
Brian<br>
<br>
On 7 September 2016 at 15:12, venkata mahesh<br>
<<a href="mailto:venkatamaheshkotha@gmail.com" target="_blank">venkatamaheshkotha@gmail.com</a><br></span><span class="">
<mailto:<a href="mailto:venkatamaheshkotha@gmail.com" target="_blank">venkatamaheshkotha@gma<wbr>il.com</a>>> wrote:<br>
<br>
Hi team,<br>
<br>
The addition of release name (Mitaka) in the<br>
background is nice. My suggestion is make this version<br>
name Mitaka in the background only one in each page.<br>
Now it is having more than five ( Mitaka )images in<br>
background that will distract the reader.<br>
<br>
Thanks<br>
mahesh<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack<wbr>.org</a><br></span>
<mailto:<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.o<wbr>penstack.org</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-docs</a><span class=""><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-docs</a>><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack<wbr>.org</a><br></span>
<mailto:<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.o<wbr>penstack.org</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-docs</a><span class=""><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-docs</a>><br>
<br>
<br>
<br>
<br>
-- Anne Gentle<br></span>
<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
<br>
<br>
<br>
<br><span class="HOEnZb"><font color="#888888">
<br>
-- <br>
Anne Gentle<br>
<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>></font></span><span class=""><br>
<br>
<br>
______________________________<wbr>_________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack<wbr>.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-docs</a><br>
</span></blockquote>
<br>
<br>
</blockquote></div><br></div></div>