docutils-users Mailing List for Docutils: Documentation Utilities

On Fri, 12 Aug 2016 16:24:01 +0200, Brecht Machiels  
<bre...@mo...> wrote:

> I have tried rendering the Lizmap documentation [1]. I don't suppose it  
> is
> this project you tried to render using rinohtype, since it triggers a bug
> (#47) aborting the rendering process?
>
> In addition to this bug it revealed another bug (#45) and indeed
> illustrates the difference with LaTeX output (#46). I plan to deal with
> these issues in a bugfix release 0.2.1 [2]. Please subscribe to these
> issues if you wish to receive updates about them. You're also welcome to
> share your ideas about #46 by adding comments, of course.

Release 0.2.1 [1] fixes these issues. Just like the LaTeX builder, the  
rinohtype Sphinx builder now scales down images that are wider than the  
text width. However, it does not copy the strange handling of the image  
directive's :scale: option [2]. To obtain the same effect, you should pass  
a percentage to the :width: option.

Best regards,
Brecht

[1] https://pypi.python.org/pypi/RinohType/0.2.1
[2] https://github.com/sphinx-doc/sphinx/issues/2865

On 2016-08-14, Alan G. Isaac wrote:
>> On 2016-08-11, Alan Isaac wrote:
>>> 3. If styling is not a solution, should PRE elements be written
>>> with content following immediately (rather than with
>>> an initial EOL)?


> On 8/13/2016 6:29 AM, Guenter Milde wrote:>
>> I think so. This is what the "html5" writer does.


> I found this explanation:
> http://stackoverflow.com/questions/17722951/difference-in-display-between-html-and-xhtml
> It seems from this explanation that the XHTML writers
> should not write an extra EOL immediately after a PRE tag,
> but it should not matter for HTML 5.

Yes. However, to be on the safe side, the "html5-plain" writer writes
"polyglott" HTML that is also valid XML.

Günter

> On 2016-08-11, Alan Isaac wrote:
>> 3. If styling is not a solution, should PRE elements be written
>> with content following immediately (rather than with
>> an initial EOL)?


On 8/13/2016 6:29 AM, Guenter Milde wrote:>
> I think so. This is what the "html5" writer does.


I found this explanation:
http://stackoverflow.com/questions/17722951/difference-in-display-between-html-and-xhtml
It seems from this explanation that the XHTML writers
should not write an extra EOL immediately after a PRE tag,
but it should not matter for HTML 5.

fwiw,
Alan

On 2016-08-11, Alan Isaac wrote:
> There is a major docutils component to this question, but I also
> ask for CSS help.

> Default browser styling of a PRE element is something like this::

>    display: block;
>    font-family: monospace;
>    white-space: pre;

> The white-space appears to be interpreted by many browsers as
> including any EOL immediately following the tag. ::

>    <pre>
>    So this appears to be preceded by an empty line.
>    </pre>

> That seems to be typical handling, although not in Edge.

> If I am right, it conflicts with the spec:
> https://www.w3.org/TR/html4/appendix/notes.html#notes-line-breaks
> Finding a browser error admittedly seems unlikely ...

This is the "normal" rule. It conflicts with the definition of
``white-space:pre``: "don't ignore whitespace".

Also, the definition for XHTML may differ.

> But if I am wrong, it should be possible to style it away.

> 1. Is this a browser bug?

Unsure, see above.

> 2. If not, this behavior can be styled away.  How?
> And should this "fixed" styling be done by the writer.

Not that I know of. Maybe with some exoticly complicated rule...

> 3. If styling is not a solution, should PRE elements be written
> with content following immediately (rather than with
> an initial EOL)?

I think so. This is what the "html5" writer does.

Günter

Hi Brecht,

Il 12/08/2016 16:24, Brecht Machiels ha scritto:

> Rinohtype respects an image's embedded DPI setting. If no DPI value is  
> present in the image, a default of 72 DPI is used.

Thanks for the clarification.

> I have tried rendering the Lizmap documentation [1]. I don't suppose it is  
> this project you tried to render using rinohtype, since it triggers a bug  
> (#47) aborting the rendering process?

Not, I have a variety of docs that I compile often using Sphinx.

> In addition to this bug it revealed another bug (#45) and indeed  
> illustrates the difference with LaTeX output (#46). I plan to deal with  
> these issues in a bugfix release 0.2.1 [2]. Please subscribe to these  
> issues if you wish to receive updates about them. You're also welcome to  
> share your ideas about #46 by adding comments, of course.

> [1] https://github.com/3liz/lizmap-documentation
> [2] https://github.com/brechtm/rinohtype/milestone/3

Done, thanks.

All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Hi Paolo,

On Fri, 12 Aug 2016 09:03:16 +0200, Paolo Cavallini  
<cav...@fa...> wrote:

>> Did you set a size or scale option for the figures?
>
> I didn't. Just used the same settings as for the Latexpdf builder, with
> plain .. image:: directive
> Shouldn't rinoh have the same output as the latex one?
> What would be the suggested settings?

Rinohtype respects an image's embedded DPI setting. If no DPI value is  
present in the image, a default of 72 DPI is used.

I have tried rendering the Lizmap documentation [1]. I don't suppose it is  
this project you tried to render using rinohtype, since it triggers a bug  
(#47) aborting the rendering process?

In addition to this bug it revealed another bug (#45) and indeed  
illustrates the difference with LaTeX output (#46). I plan to deal with  
these issues in a bugfix release 0.2.1 [2]. Please subscribe to these  
issues if you wish to receive updates about them. You're also welcome to  
share your ideas about #46 by adding comments, of course.

Best regards,
Brecht

[1] https://github.com/3liz/lizmap-documentation
[2] https://github.com/brechtm/rinohtype/milestone/3

Hi Brecht,

Il 11/08/2016 18:20, Brecht Machiels ha scritto:

> Are you talking about rinoh or the Sphinx builder?

the rinoh Sphinx builder

> Did you set a size or scale option for the figures?

I didn't. Just used the same settings as for the Latexpdf builder, with
plain .. image:: directive
Shouldn't rinoh have the same output as the latex one?
What would be the suggested settings?

> Please create a bug report [1] and provide a small example that  
> illustrates the problem.
> [1] https://github.com/brechtm/rinohtype/issues

Will do, when I understand the above points.
Thanks.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Hi,

On Thu, 11 Aug 2016 17:47:57 +0200, Paolo Cavallini  
<cav...@fa...> wrote:

> Il 11/08/2016 10:08, Paolo Cavallini ha scritto:
>
>> Oh, I see. I'll set up a virtualenv with Py3 then.
>
> Done, it works reasonably well, but figures are not resized correctly,
> and sometimes flow over the borders of the page.
> Thanks.

Are you talking about rinoh or the Sphinx builder?
Did you set a size or scale option for the figures?

Please create a bug report [1] and provide a small example that  
illustrates the problem.

Best regards,
Brecht

[1] https://github.com/brechtm/rinohtype/issues

There is a major docutils component to this question, but I also
ask for CSS help.

Default browser styling of a PRE element is something like this::

   display: block;
   font-family: monospace;
   white-space: pre;

The white-space appears to be interpreted by many browsers as
including any EOL immediately following the tag. ::

   <pre>
   So this appears to be preceded by an empty line.
   </pre>

That seems to be typical handling, although not in Edge.
If I am right, it conflicts with the spec:
https://www.w3.org/TR/html4/appendix/notes.html#notes-line-breaks
Finding a browser error admittedly seems unlikely ...
But if I am wrong, it should be possible to style it away.

1. Is this a browser bug?

2. If not, this behavior can be styled away.  How?
And should this "fixed" styling be done by the writer.

3. If styling is not a solution, should PRE elements be written
with content following immediately (rather than with
an initial EOL)?

Cheers,
Alan

Il 11/08/2016 10:08, Paolo Cavallini ha scritto:

> Oh, I see. I'll set up a virtualenv with Py3 then.

Done, it works reasonably well, but figures are not resized correctly,
and sometimes flow over the borders of the page.
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Il 11/08/2016 09:49, Brecht Machiels ha scritto:
> Hi Paolo,
> 
> Thanks for giving rinohtype a spin.
> 
> Rinohtype only supports Python 3.3+. I see you are running it on Python  
> 2.7. I'll see if I can have pip (and easy_install) abort with a clear  
> error message when someone tries to install it on an unsupported Python  
> version.

Oh, I see. I'll set up a virtualenv with Py3 then.
Thanks.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Hi Paolo,

Thanks for giving rinohtype a spin.

Rinohtype only supports Python 3.3+. I see you are running it on Python  
2.7. I'll see if I can have pip (and easy_install) abort with a clear  
error message when someone tries to install it on an unsupported Python  
version.

Best regards,
Brecht

On Thu, 11 Aug 2016 09:07:12 +0200, Paolo Cavallini  
<cav...@fa...> wrote:

> Il 10/08/2016 19:08, Brecht Machiels ha scritto:
>>
>> Hi all,
>>
>> Rinohtype transforms structured text documents to PDF, styled based on a
>> document template and style sheet.
>
> Thanks Brecht,
> looking forward to see it integrated in sphinx. I tried to install it,
> but I get a long series of errors [0]
> All the best.
> ===
> [0]
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/stylesheets/matcher.py",
> line 25
>         / ... / StyledText.like('number'),
>           ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/font/opentype/parse.py",
> line 70
>         def context_array(reader, count_key, *indirect_args,  
> multiplier=1):
>                                                                       ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/font/__init__.py",
> line 95
>         def __new__(cls, name, *fonts, weight_order=FontWeight.values):
>                                                   ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/epub/__init__.py",
> line 33
>         class EPubNode(ElementTreeNode, metaclass=ElementTreeNodeMeta):
>                                                  ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/docbook/__init__.py",
> line 20
>         class DocBookNode(ElementTreeNode,  
> metaclass=ElementTreeNodeMeta):
>                                                     ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/rst/__init__.py",
> line 25
>         class DocutilsNode(TreeNode, metaclass=TreeNodeMeta):
>                                               ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/template.py",
> line 93
>         metaclass=TemplateConfigurationMeta):
>                  ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/paragraph.py",
> line 403
>         nonlocal state, saved_state, max_line_width, descender
>                      ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/backend/pdf/__init__.py",
> line 153
>         def print(self, string):
>                 ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/backend/pdf/cos.py",
> line 337
>         def __init__(self, *args, indirect=False, **items):
>                                          ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/flowable.py",
> line 662
>         def __init__(self, *args, align=None, width=None, **kwargs):
>                                       ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/attribute.py",
> line 62
>         class OptionSet(AttributeType, metaclass=OptionSetMeta):
>                                                 ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/strings.py",
> line 43
>         class Strings(dict, metaclass=WithNamedDescriptors):
>                                      ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/document.py",
> line 178
>         class DocumentPart(object, metaclass=DocumentLocationType):
>                                             ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/dimension.py",
> line 53
>         class DimensionBase(AcceptNoneAttributeType,
> metaclass=DimensionType):
>                                                               ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/text.py",
> line 497
>         print(self.ps, file=box_canvas.psg_canvas)
>                            ^
>     SyntaxError: invalid syntax
>
>       File
> "/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/style.py",
> line 404
>         class Styled(DocumentElement, metaclass=StyledMeta):
>                                                ^
>     SyntaxError: invalid syntax
>
>     Installing rinoh script to /usr/local/src/py_virtual_experimental/bin
>   Could not find .egg-info directory in install record for rinohtype

Il 10/08/2016 19:08, Brecht Machiels ha scritto:
> 
> Hi all,
> 
> Rinohtype transforms structured text documents to PDF, styled based on a  
> document template and style sheet.

Thanks Brecht,
looking forward to see it integrated in sphinx. I tried to install it,
but I get a long series of errors [0]
All the best.
===
[0]
      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/stylesheets/matcher.py",
line 25
        / ... / StyledText.like('number'),
          ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/font/opentype/parse.py",
line 70
        def context_array(reader, count_key, *indirect_args, multiplier=1):
                                                                      ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/font/__init__.py",
line 95
        def __new__(cls, name, *fonts, weight_order=FontWeight.values):
                                                  ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/epub/__init__.py",
line 33
        class EPubNode(ElementTreeNode, metaclass=ElementTreeNodeMeta):
                                                 ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/docbook/__init__.py",
line 20
        class DocBookNode(ElementTreeNode, metaclass=ElementTreeNodeMeta):
                                                    ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/frontend/rst/__init__.py",
line 25
        class DocutilsNode(TreeNode, metaclass=TreeNodeMeta):
                                              ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/template.py",
line 93
        metaclass=TemplateConfigurationMeta):
                 ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/paragraph.py",
line 403
        nonlocal state, saved_state, max_line_width, descender
                     ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/backend/pdf/__init__.py",
line 153
        def print(self, string):
                ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/backend/pdf/cos.py",
line 337
        def __init__(self, *args, indirect=False, **items):
                                         ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/flowable.py",
line 662
        def __init__(self, *args, align=None, width=None, **kwargs):
                                      ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/attribute.py",
line 62
        class OptionSet(AttributeType, metaclass=OptionSetMeta):
                                                ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/strings.py",
line 43
        class Strings(dict, metaclass=WithNamedDescriptors):
                                     ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/document.py",
line 178
        class DocumentPart(object, metaclass=DocumentLocationType):
                                            ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/dimension.py",
line 53
        class DimensionBase(AcceptNoneAttributeType,
metaclass=DimensionType):
                                                              ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/text.py",
line 497
        print(self.ps, file=box_canvas.psg_canvas)
                           ^
    SyntaxError: invalid syntax

      File
"/usr/local/src/py_virtual_experimental/lib/python2.7/site-packages/rinoh/style.py",
line 404
        class Styled(DocumentElement, metaclass=StyledMeta):
                                               ^
    SyntaxError: invalid syntax

    Installing rinoh script to /usr/local/src/py_virtual_experimental/bin
  Could not find .egg-info directory in install record for rinohtype

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html

Hi all,

Rinohtype transforms structured text documents to PDF, styled based on a  
document template and style sheet.

I have just released version 0.2.0. Along with many other changes [1], the  
included command line tool rinoh that renders reStructuredText documents  
has seen some improvements. It now allows specifying a document template  
and style sheet to use. It is relatively easy to write your own style  
sheet; see the documentation [2] for details.

Quickstart:

     pip install rinohtype
     rinoh my_document.rst

Please report any problems you may encounter at the project's GitHub page  
[3].

Besides the rinoh command-line tool rinohtype also includes a Sphinx  
builder which is a drop-in replacement for the LaTeX builder.

Best regards,
Brecht

[1]  
http://www.mos6581.org/rinohtype/changelog.html#release-0-2-0-2016-08-09
[2] http://www.mos6581.org/rinohtype/
[3] https://github.com/brechtm/rinohtype/issues

On 8/5/2016 2:13 AM, Deshpande, Vinita wrote:
> I have created a txt file,with some content, which is formatted using rst (for ex:, headings using “=”, table etc).  I would like to see, how this would look as an html page. Can I
> please know how to do this?


http://docutils.sourceforge.net/docs/user/tools.html#html-generating-tools

hth,
Alan Isaac

Hi Vinita!

Today Deshpande, Vinita wrote:
> I have created a txt file,with some content, which is formatted
> using rst (for ex:, headings using "=", table etc).  I would like to
> see, how this would look as an html page.

In Emacs the simplest solution would be to load the file into a
buffer, switch to `rst-mode` (which might be running already when
using ``.rst`` as an extension). Then hit C-c C-c C-c executing
compiling to HTML if you have the Docutils package installed (which
you of course should when using reStructuredText). This creates a HTML
file in parallel to your source you can pick up with your favorite
browser.



						HTH

						Stefan

On 2016-08-05, Deshpande, Vinita wrote:

> Hi, 

> I have created a txt file,with some content, which is formatted
> using rst (for ex:, headings using "=", table etc).  I would like to
> see, how this would look as an html page. 

> Can I please know how to do this? 

If you have Docutils installed, call

  rst2html.py INPUT.rst OUTPUT.html
  
on some linux distributions, it is "rst2html" (without the extension .py),
use

  rst2html --help
  
for command line options and the documentation at
http://docutils.sourceforge.net/docs/index.html

> Sample txt file content:

...

> I would like to know, how this would appear after formatting is applied.

See below for the output of the new rst2html5 converter (after indenting
the table).

Günter


<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta charset="utf-8"/>
<meta name="generator" content="Docutils 0.13: http://docutils.sourceforge.net/" />
<title>My heading</title>
<style type="text/css">

/* Minimal style sheet for the HTML output of Docutils.                    */
/*                                                                         */
/* :Author: Günter Milde, based on html4css1.css by David Goodger          */
/* :Id: $Id: minimal.css 7952 2016-07-26 18:15:59Z milde $               */
/* :Copyright: © 2015 Günter Milde.                                        */
/* :License: Released under the terms of the `2-Clause BSD license`_,      */
/*    in short:                                                            */
/*                                                                         */
/*    Copying and distribution of this file, with or without modification, */
/*    are permitted in any medium without royalty provided the copyright   */
/*    notice and this notice are preserved.                                */
/*                                                                         */
/*    This file is offered as-is, without any warranty.                    */
/*                                                                         */
/* .. _2-Clause BSD license: http://www.spdx.org/licenses/BSD-2-Clause     */

/* This CSS2.1_ stylesheet defines rules for Docutils elements without    */
/* HTML equivalent. It is required to make the document semantic visible. */
/*                                                                        */
/* .. _CSS2.1: http://www.w3.org/TR/CSS2                                  */
/* .. _validates: http://jigsaw.w3.org/css-validator/validator$link       */

/* alignment of text and inline objects inside block objects*/
.align-left   { text-align: left; }
.align-right  { text-align: right; }
.align-center { clear: both; text-align: center; }
.align-top    { vertical-align: top; }
.align-middle { vertical-align: middle; }
.align-bottom { vertical-align: bottom; }

/* titles */
h1.title, p.subtitle {
  text-align: center;
}
p.admonition-title,
p.topic-title,
p.sidebar-title,
p.rubric,
p.system-message-title {
  font-weight: bold;
}
h1 + p.subtitle,
h1 + p.section-subtitle {
  font-size: 1.6em;
}
h2 + p.section-subtitle { font-size: 1.28em; }
p.subtitle,
p.section-subtitle,
p.sidebar-subtitle {
  font-weight: bold;
  margin-top: -0.5em;
}
p.sidebar-title,
p.rubric {
  font-size: larger;
}
p.rubric { color: maroon; }
a.toc-backref {
  color: black;
  text-decoration: none; }

/* Warnings, Errors */
div.caution p.admonition-title,
div.attention p.admonition-title,
div.danger p.admonition-title,
div.error p.admonition-title,
div.warning p.admonition-title,
div.system-messages h1,
div.error,
span.problematic,
p.system-message-title {
  color: red;
}

/* inline literals */
span.docutils.literal {
  font-family: monospace;
  white-space: pre-wrap;
}
/* do not wraph at hyphens and similar: */
.literal > span.pre { white-space: nowrap; }

/* Lists */

/* compact and simple lists: no margin between items */
.simple  li, .compact li,
.simple  ul, .compact ul,
.simple  ol, .compact ol,
.simple > li p, .compact > li p,
dl.simple > dd, dl.compact > dd {
  margin-top: 0;
  margin-bottom: 0;
}

/* Table of Contents */
div.topic.contents { margin: 0; }
ul.auto-toc {
  list-style-type: none;
  padding-left: 1.5em; }

/* Enumerated Lists */
ol.arabic     { list-style: decimal }
ol.loweralpha { list-style: lower-alpha }
ol.upperalpha { list-style: upper-alpha }
ol.lowerroman { list-style: lower-roman }
ol.upperroman { list-style: upper-roman }

dt span.classifier { font-style: italic }
dt span.classifier:before {
  font-style: normal;
  margin: 0.5em;
  content: ":";
}

/* Field Lists and drivatives */
/* bold field name, content starts on the same line */
dl.field-list > dt,
dl.option-list > dt,
dl.docinfo > dt,
dl.footnote > dt,
dl.citation > dt {
  font-weight: bold;
  clear: left;
  float: left;
  margin: 0;
  padding: 0;
  padding-right: 0.5em;
}
/* Offset for field content (corresponds to the --field-name-limit option) */
dl.field-list > dd,
dl.option-list > dd,
dl.docinfo > dd {
  margin-left:  9em; /* ca. 14 chars in the test examples */
}
/* start field-body on a new line after long field names */
dl.field-list > dd > *:first-child,
dl.option-list > dd > *:first-child
{
  display: inline-block;
  width: 100%;
  margin: 0;
}
/* field names followed by a colon */
dl.field-list > dt:after,
dl.docinfo > dt:after {
  content: ":";
}

/* Bibliographic Fields (docinfo) */
pre.address { font: inherit; }
dd.authors > p { margin: 0; }

/* Option Lists */
dl.option-list { margin-left: 40px; }
dl.option-list > dt { font-weight: normal; }
span.option { white-space: nowrap; }

/* Footnotes and Citations  */
dl.footnote.superscript > dd {margin-left: 1em; }
dl.footnote.brackets > dd {margin-left: 2em; }
dl > dt.label { font-weight: normal; }
a.footnote-reference.brackets:before,
dt.label > span.brackets:before { content: "["; }
a.footnote-reference.brackets:after,
dt.label > span.brackets:after { content: "]"; }
a.footnote-reference.superscript,
dl.footnote.superscript > dt.label {
  vertical-align: super;
  font-size: smaller;
}
dt.label > span.fn-backref { margin-left: 0.2em; }
dt.label > span.fn-backref > a { font-style: italic; }

/* Line Blocks */
div.line-block { display: block; }
div.line-block div.line-block {
  margin-top: 0;
  margin-bottom: 0;
  margin-left: 40px;
}

/* Figures, Images, and Tables */
.figure.align-left,
img.align-left,
object.align-left,
table.align-left {
  margin-right: auto;
}
.figure.align-center,
img.align-center,
object.align-center {
  margin-left: auto;
  margin-right: auto;
  display: block;
}
table.align-center {
  margin-left: auto;
  margin-right: auto;
}
.figure.align-right,
img.align-right,
object.align-right,
table.align-right {
  margin-left: auto;
}
/* reset inner alignment in figures and tables */
div.align-left, div.align-center, div.align-right,
table.align-left, table.align-center, table.align-right
{ text-align: inherit }

/* Admonitions and System Messages */
div.admonition,
div.system-message,
div.sidebar{
  margin: 40px;
  border: medium outset;
  padding-right: 1em;
  padding-left: 1em;
}

/* Sidebar */
div.sidebar {
  width: 30%;
  max-width: 26em;
  float: right;
  clear: right;
}

/* Text Blocks */
div.topic,
pre.literal-block,
pre.doctest-block,
pre.math,
pre.code {
  margin-right: 40px;
  margin-left: 40px;
}
pre.code .ln { color: gray; } /* line numbers */

/* Tables */
table { border-collapse: collapse; }
td, th {
  border-style: solid;
  border-color: silver;
  padding: 0 1ex;
  border-width: thin;
}
td > p:first-child, th > p:first-child { margin-top: 0; }
td > p, th > p { margin-bottom: 0; }

table > caption {
  text-align: left;
  margin-bottom: 0.25em
}

table.borderless td, table.borderless th {
  border: 0;
  padding: 0;
  padding-right: 0.5em /* separate table cells */
}

</style>
<style type="text/css">

/* CSS31_ style sheet for the output of Docutils HTML writers.             */
/* Rules for easy reading and pre-defined style variants.		   */
/*                                                                         */
/* :Author: Günter Milde, based on html4css1.css by David Goodger          */
/* :Id: $Id: plain.css 7952 2016-07-26 18:15:59Z milde $               */
/* :Copyright: © 2015 Günter Milde.                                        */
/* :License: Released under the terms of the `2-Clause BSD license`_,      */
/*    in short:                                                            */
/*                                                                         */
/*    Copying and distribution of this file, with or without modification, */
/*    are permitted in any medium without royalty provided the copyright   */
/*    notice and this notice are preserved.                                */
/*    	     	      	     	 					   */
/*    This file is offered as-is, without any warranty.                    */
/*                                                                         */
/* .. _2-Clause BSD license: http://www.spdx.org/licenses/BSD-2-Clause     */
/* .. _CSS3: http://www.w3.org/TR/CSS3		        		   */


/* Document Structure */
/* ****************** */

/* "page layout" */
body {
  padding: 0 5%;
  margin: 8px 0;
}
div.document {
  line-height:1.3;
  counter-reset: table;
  /* counter-reset: figure; */
  /* avoid long lines --> better reading */
  /* OTOH: lines should not be too short because of missing hyphenation, */
  max-width: 50em;
  margin: auto;
}

/* Sections */

/* Transitions */

hr.docutils {
  width: 80%;
  margin-top: 1em;
  margin-bottom: 1em;
  clear: both;
}

/* Paragraphs               */
/* ==========               */

/* vertical space (parskip) */
p, ol, ul, dl,
div.line-block,
table{
  margin-top: 0.5em;
  margin-bottom: 0.5em;
}
h1, h2, h3, h4, h5, h6,
dl > dd {
  margin-bottom: 0.5em;
}

/* Lists                    */
/* ==========               */

/* Definition Lists         */

dl > dd p:first-child { margin-top: 0; }
/* :last-child is not part of CSS 2.1 (introduced in CSS 3) */
/* dl > dd p:last-child  { margin-bottom: 0; } */

/* lists nested in definition lists */
/* :only-child is not part of CSS 2.1 (introduced in CSS 3) */
dd > ul:only-child, dd > ol:only-child { padding-left: 1em; }

/* Description Lists */
/* styled like in most dictionaries, encyclopedias etc. */
dl.description > dt {
  font-weight: bold;
  clear: left;
  float: left;
  margin: 0;
  padding: 0;
  padding-right: 0.5em;
}

/* Field Lists */

/* example for custom field-name width */
dl.field-list.narrow > dd {
  margin-left: 5em;
}
/* run-in: start field-body on same line after long field names */
dl.field-list.run-in > dd p {
  display: block;
}

/* Bibliographic Fields */

/* generally, bibliographic fields use special definition list dl.docinfo */
/* but dedication and abstract are placed into "topic" divs */
div.abstract p.topic-title {
  text-align: center;
}
div.dedication {
  margin: 2em 5em;
  text-align: center;
  font-style: italic;
}
div.dedication p.topic-title {
  font-style: normal;
}

/* Citations */
dl.citation dt.label {
  font-weight: bold;
}
span.fn-backref {
  font-weight: normal;
}

/* Text Blocks           */
/* ============          */

/* Literal Blocks           */
pre.literal-block, pre.doctest-block,
pre.math, pre.code {
  margin-left: 1.5em;
  margin-right: 1.5em
}

/* Block Quotes             */

blockquote,
div.topic {
  margin-left: 1.5em;
  margin-right: 1.5em
}
blockquote > table,
div.topic > table {
  margin-top: 0;
  margin-bottom: 0;
}
blockquote p.attribution,
div.topic p.attribution {
  text-align: right;
  margin-left: 20%;
}

/* Tables                   */
/* ======                   */

/* th { vertical-align: bottom; } */

table tr { text-align: left; }

/* "booktabs" style (no vertical lines) */
table.booktabs {
  border: 0;
  border-top: 2px solid;
  border-bottom: 2px solid;
  border-collapse: collapse;
}
table.booktabs * {
  border: 0;
}
table.booktabs th {
  border-bottom: thin solid;
}

/* numbered tables (counter defined in div.document) */
table.numbered > caption:before {
  counter-increment: table;
  content: "Table " counter(table) ": ";
  font-weight: bold;
}

/* Explicit Markup Blocks   */
/* ======================   */

/* Footnotes and Citations  */
/* -----------------------  */

/* line on the left */
dl.footnote {
  padding-left: 1ex;
  border-left: solid;
  border-left-width: thin;
}

/* Directives               */
/* ----------               */

/* Body Elements            */
/* ~~~~~~~~~~~~~            */

/* Images and Figures */

/* let content flow to the side of aligned images and figures */
.figure.align-left,
img.align-left,
object.align-left {
  display: block;
  clear: left;
  float: left;
  margin-right: 1em
}
.figure.align-right,
img.align-right,
object.align-right {
  display: block;
  clear: right;
  float: right;
  margin-left: 1em
}
/* Stop floating sidebars, images and figures at section level 1,2,3 */
h1, h2, h3 { clear: both; }

/* Sidebar */

/* Move into the margin. In a layout with fixed margins, */
/* it can be moved into the margin completely.		 */
div.sidebar {
  width: 30%;
  max-width: 26em;
  margin-left: 1em;
  margin-right: -5.5%;
  background-color: #ffffee ;
}

/* Code                     */

pre.code, code { background-color: #eeeeee }
pre.code .ln { color: gray; } /* line numbers */
/* basic highlighting: for a complete scheme, see */
/* http://docutils.sourceforge.net/sandbox/stylesheets/ */
pre.code .comment, code .comment { color: #5C6576 }
pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
pre.code .literal.string, code .literal.string { color: #0C5404 }
pre.code .name.builtin, code .name.builtin { color: #352B84 }
pre.code .deleted, code .deleted { background-color: #DEB0A1}
pre.code .inserted, code .inserted { background-color: #A3D289}

/* Math                     */
/* styled separately (see math.css for math-output=HTML) */

/* Epigraph                 */
/* Highlights               */
/* Pull-Quote               */
/* Compound Paragraph       */
/* Container                */

/* can be styled in a custom stylesheet */

/* Document Header and Footer */

div.footer, div.header {
  clear: both;
  font-size: smaller;
}

/* Inline Markup            */
/* =============            */

/* Emphasis                 */
/*   em                     */
/* Strong Emphasis          */
/*   strong		    */
/* Interpreted Text         */
/*   span.interpreted  	    */
/* Title Reference 	    */
/*   cite		    */
/* Inline Literals          */
/* possible values: normal, nowrap, pre, pre-wrap, pre-line */
/*   span.docutils.literal { white-space: pre-wrap; } */

/* Hyperlink References     */
a { text-decoration: none; }

/* External Targets         */
/*   span.target.external   */
/* Internal Targets  	    */
/*   span.target.internal   */
/* Footnote References      */
/*   a.footnote-reference   */
/* Citation References      */
/*   a.citation-reference   */

</style>
</head>
<body>
<div class="document" id="my-heading">
<h1 class="title">My heading</h1>

<p class="subtitle" id="introduction">Introduction</p>
<p>My custome introduction</p>
<table>
<caption><strong>Default flavors</strong></caption>
<colgroup>
<col style="width: 24%" />
<col style="width: 18%" />
<col style="width: 30%" />
<col style="width: 28%" />
</colgroup>
<thead>
<tr><th class="head"><p>Flavor</p></th>
<th class="head"><p>VCPUs</p></th>
<th class="head"><p>Disk (in GB)</p></th>
<th class="head"><p>RAM (in MB)</p></th>
</tr>
</thead>
<tbody>
<tr><td><p>m1.tiny</p></td>
<td><p>1</p></td>
<td><p>1</p></td>
<td><p>512</p></td>
</tr>
<tr><td><p>m1.small</p></td>
<td><p>1</p></td>
<td><p>20</p></td>
<td><p>2048</p></td>
</tr>
<tr><td><p>m1.medium</p></td>
<td><p>2</p></td>
<td><p>40</p></td>
<td><p>4096</p></td>
</tr>
<tr><td><p>m1.large</p></td>
<td><p>4</p></td>
<td><p>80</p></td>
<td><p>8192</p></td>
</tr>
<tr><td><p>m1.xlarge</p></td>
<td><p>8</p></td>
<td><p>160</p></td>
<td><p>16384</p></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>

I use Sphinx, which (if you're interested in it) can output a tree view
if you build 'make pseudoxml'. 

--
Bram Geron
Doctoral researcher in computer science

On Fri, 5 Aug 2016, at 05:04 PM, Francesco Ariis wrote:
> On Fri, Aug 05, 2016 at 06:13:44AM +0000, Deshpande, Vinita wrote:
> > I have created a txt file,with some content, which is formatted using
> > rst (for ex:, headings using "=", table etc).  I would like to see, how
> > this would look as an html page. Can I please know how to do this?
> 
> Hello Vinita,
> I use pandoc to convert from/to .rst (and a bunch of other formats).
> 
>     pandoc -o file.html file.rst
> 
> Remember that you can add a .css stylesheet to modify the formatting
> as you see fit.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Docutils-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/docutils-users
> 
> Please use "Reply All" to reply to the list.

On Fri, Aug 05, 2016 at 06:13:44AM +0000, Deshpande, Vinita wrote:
> I have created a txt file,with some content, which is formatted using
> rst (for ex:, headings using "=", table etc).  I would like to see, how
> this would look as an html page. Can I please know how to do this?

Hello Vinita,
I use pandoc to convert from/to .rst (and a bunch of other formats).

    pandoc -o file.html file.rst

Remember that you can add a .css stylesheet to modify the formatting
as you see fit.

Hi,
I have created a txt file,with some content, which is formatted using rst (for ex:, headings using "=", table etc).  I would like to see, how this would look as an html page. Can I please know how to do this?
Sample txt file content:

==========
My heading
==========

Introduction
~~~~~~~~~~~~
My custome introduction

.. table:: **Default flavors**

============  =========  ===============  =============
  Flavor         VCPUs      Disk (in GB)     RAM (in MB)
============  =========  ===============  =============
  m1.tiny        1          1                512
  m1.small       1          20               2048
  m1.medium      2          40               4096
  m1.large       4          80               8192
  m1.xlarge      8          160              16384
============  =========  ===============  =============


I would like to know, how this would appear after formatting is applied.

Thanks,
Vinita

Hi Oleksandr!

Yesterday Oleksandr Gavenko wrote:
> Hi! I actively use rst.el (which come with official Emacs).

Over the time different versions of rst.el have been bundled with
official Emacs versions. In more recent versions of rst.el you could
try ``C-h v rst-version`` for the version you are using.

> Only one downside I have. For one long file (700 KiB, 20 kLOC).
> 
> When I open it I have 2-5 sec delay first time and when I mark line as header
> (C-c C-= / M-x rst-adjust) it take 1-2 sec to complete action.
> 
> File has near 660 headers (notes for future blog posts).

I guess you are using font locking. Some years ago with the help of
Emacs developers I spent some effort to enable using `jit-lock-mode`.
Please check ``C-h v font-lock-support-mode``. The value should be
`jit-lock-mode` (the default).

If that makes a difference then fine. If not you may send me your file
by private mail. You may want to use rot13 for privacy reasons.

You can also try loading your file without font locking switched on.
This should not result in any delay.

> I have not tried new version yet.

There should be no changes in this regard.


						Grüße

						Stefan

On 2016-07-31, Stefan Merten wrote:

> Today I uploaded a new version of `rst.el` - the reStructuredText
> major mode for Emacs. This is a very big patch which is basically a
> major refactoring introducing some abstractions reflecting
> reStructuredText concepts.

Hi! I actively use rst.el (which come with official Emacs).

Only one downside I have. For one long file (700 KiB, 20 kLOC).

When I open it I have 2-5 sec delay first time and when I mark line as header
(C-c C-= / M-x rst-adjust) it take 1-2 sec to complete action.

File has near 660 headers (notes for future blog posts).

I have not tried new version yet.

-- 
http://defun.work/