docutils-users — General discussions, questions, help requests.

Re: [Docutils-users] screenplay markup (was Re: Nested, titled sections)

[David G. <go...@py...>]

On Apr 19, 2015 3:22 PM, "Guenter Milde" <mi...@us...> wrote:
>
> Dear Jeffrey and David,
>
> On 2015-04-14, David Goodger wrote:
> > On Tue, Apr 14, 2015 at 3:13 PM, Jeffrey C. Jacobs
> ><dar...@ti...> wrote:
> >> David Goodger <goodger <at> python.org> writes:
>
> >> Currently::
>
> >> :Character:
> >>    `(action)`:parenthetical:
> >>    Dialog
>
> > This seems perfectly reasonable to me. See below for my suggestions.
>
> ...
>
> >> Proposal with Definition Lists::
>
> ...
>
> > Character
> >   .. admonition:: parenthetical
>
> >      (action)
>
> >   Dialog
>
> >> I'm not sure if I'm able to embed adminitions in a topic or a
definition
> >> list
>
> > You can. At the block level, reST is completely orthogonal. Anywhere
> > that you can put a paragraph or a bullet list, you can also put any
> > other block-level element, including admonitions. With reST, you can
> > put a table inside an admonition inside a table cell inside... as
> > deeply as you like.
>
> > However, I don't think admonitions are the right thing for your
> > purposes here.
>
> The idea was to use a block element instead of a role. This could be a
> generic admonition, an (ab)used pre-defined admonition (note, hint, ...)
or
> a custom directive (whether the parentheses are added by the directive or
> required in the source is up to the implementation)::
>
>   Character
>     .. parenthetical:: action
>
>     Dialog

That does work. But I'd recommend a less verbose option.

> > I suspect that definition lists would be your best bet for dialog.
> > Field lists could work too, but they are typically formatted
> > side-by-side (e.g., by the current html4css1 writer) while definition
> > lists are often formatted term-on-top, definition-below. So it would
> > be easier to reconfigure a stylesheet to make definition lists look
> > like screenplay dialog.
>
> In addition, definition lists look more similar to a dialogue and are
easier
> to type also in the rST source.
>
> > Your "parentheticals" (AKA "personal direction" or "wrylies") may be
> > common enough to deserve their own special syntax. Lucky for you, reST
> > offers one customizable inline syntax mechanism: the default
> > interpreted text role:
>
> >     .. role:: parenthetical
> >     .. default-role:: parenthetical
>
> > After that, you can drop the text ":parenthetical:" from your markup:
>
> >     Character
> >         `(action)`
> >         Dialog
>
> > At this point, the only real issue is that the "(action)" text above
> > has to be on its own line. You could either process your document to
> > treat the "parenthetical" role specially, or you could use line
> > blocks:
>
> >     Character
> >         | Dialog
> >         | `(action)`
> >         | More dialog, that might
> >           wrap around. Note that
> >           the vertical bars aren't
> >           necessary on wrapped lines.
>
> Or you could simply put the `action` in a separate paragraph:
>
>     Character
>           `action`
>
>           Dialog

Yes, but I believe there should not be any blank lines between sections of
dialog and parentheticals (in the output). Of course, a transform could do
that too.

> Again, the parentheses might be added by the "parenthetical" role.

Probably better to require the parentheses in the source text, for the sake
of WYSIWYG (input matching output).

> Another, not very clean but concise option would be to (ab)use the
> "classifier" of a definition list term::
>
>     Character : action
>        Dialogue
>
> A custom transform could replace the classifier node in the definition
> term with a leading paragraph with class "parenthetical" in the defintion.

Unfortunately that won't work, because such parentheticals can occur in
arbitrary positions (not just at the beginning of dialog, but in the middle
or at the end), and there can be multiple instances. The pattern doesn't
match definition list classifiers at all.

DG

[Docutils-users] screenplay markup (was Re: Nested, titled sections)

[Guenter M. <mi...@us...>]

Dear Jeffrey and David,

On 2015-04-14, David Goodger wrote:
> On Tue, Apr 14, 2015 at 3:13 PM, Jeffrey C. Jacobs
><dar...@ti...> wrote:
>> David Goodger <goodger <at> python.org> writes:

>> Currently::

>> :Character:
>>    `(action)`:parenthetical:
>>    Dialog

> This seems perfectly reasonable to me. See below for my suggestions.

...

>> Proposal with Definition Lists::

...

> Character
>   .. admonition:: parenthetical

>      (action)

>   Dialog

>> I'm not sure if I'm able to embed adminitions in a topic or a definition
>> list

> You can. At the block level, reST is completely orthogonal. Anywhere
> that you can put a paragraph or a bullet list, you can also put any
> other block-level element, including admonitions. With reST, you can
> put a table inside an admonition inside a table cell inside... as
> deeply as you like.

> However, I don't think admonitions are the right thing for your
> purposes here.

The idea was to use a block element instead of a role. This could be a
generic admonition, an (ab)used pre-defined admonition (note, hint, ...) or
a custom directive (whether the parentheses are added by the directive or
required in the source is up to the implementation)::

  Character
    .. parenthetical:: action
 
    Dialog

> I suspect that definition lists would be your best bet for dialog.
> Field lists could work too, but they are typically formatted
> side-by-side (e.g., by the current html4css1 writer) while definition
> lists are often formatted term-on-top, definition-below. So it would
> be easier to reconfigure a stylesheet to make definition lists look
> like screenplay dialog.

In addition, definition lists look more similar to a dialogue and are easier
to type also in the rST source.

> Your "parentheticals" (AKA "personal direction" or "wrylies") may be
> common enough to deserve their own special syntax. Lucky for you, reST
> offers one customizable inline syntax mechanism: the default
> interpreted text role:

>     .. role:: parenthetical
>     .. default-role:: parenthetical

> After that, you can drop the text ":parenthetical:" from your markup:

>     Character
>         `(action)`
>         Dialog

> At this point, the only real issue is that the "(action)" text above
> has to be on its own line. You could either process your document to
> treat the "parenthetical" role specially, or you could use line
> blocks:

>     Character
>         | Dialog
>         | `(action)`
>         | More dialog, that might
>           wrap around. Note that
>           the vertical bars aren't
>           necessary on wrapped lines.

Or you could simply put the `action` in a separate paragraph:

    Character
          `action`
           
          Dialog

Again, the parentheses might be added by the "parenthetical" role.

Another, not very clean but concise option would be to (ab)use the
"classifier" of a definition list term::

    Character : action
       Dialogue
       
A custom transform could replace the classifier node in the definition
term with a leading paragraph with class "parenthetical" in the defintion.


Günter

Re: [Docutils-users] Class assigned to all titles or titled blocks of a given level

[Jeffrey C. J. <dar...@ti...>]

On Tue, Apr 14, 2015 at 5:29 PM, David Goodger <go...@py...> wrote:
> And then select for every section within a section with class "doctor".

Cool!  Cheers!

Jeffrey.

Re: [Docutils-users] Nested, titled sections

[Jeffrey C. J. <dar...@ti...>]

On Tue, Apr 14, 2015 at 5:19 PM, David Goodger <go...@py...> wrote:
> At this point, the only real issue is that the "(action)" text above
> has to be on its own line. You could either process your document to
> treat the "parenthetical" role specially, or you could use line
> blocks:
>
>     Character
>         | Dialog
>         | `(action)`
>         | More dialog, that might
>           wrap around. Note that
>           the vertical bars aren't
>           necessary on wrapped lines.

Thanks for drilling down into a more specific use case than dogs,
David.  I know the original question doesn't seem like its related but
I was trying to make a query in the most general case possible.  In
that sense, I think your title suggestion does make some sense as long
as it's rendered inline and not separate from the document which I
think was my main concern, how the writer would handle it.

I think the line-blocks are an interesting idea and I'll definitely
consider it as a way to spell how it should be rendered.  As you saw
in the developer's thread, I'm trying to look at all of Docutils for
rendering, which will likely mean modifying the doctree through a
custom transform before it hits the writer and then use the existing
writer with a custom stylesheet to render it properly.  I just wonder
if custom doctree transforms can be added to any of the publish
functions as I worry that styling may not be able to smooth over all
the bumps of the default generated document elements without a little
massaging beforehand.  A simple visitor transform could accomplish
this (seeing adding an XSLT parser is a bit much for such a thing).
But as transforms are more a developer issue, I'll move that
discussion there.

Thanks again!

Jeffrey.

Re: [Docutils-users] Class assigned to all titles or titled blocks of a given level

[David G. <go...@py...>]

On Tue, Apr 14, 2015 at 2:58 PM, Jeffrey C. Jacobs
<dar...@ti...> wrote:
> Is there a way to assign a class to every document element at a given
> title level,

No.

> or is this better at the xml transform level?

You'd need new code or a transform of some kind.

Alternatively:

"""
.. class:: doctor

Doctors
=======

Peter Davison
~~~~~~~~~~~~~

content...

Colin Baker
~~~~~~~~~~~

content...
"""

And then select for every section within a section with class "doctor".

-- 
David Goodger <http://python.net/~goodger>

Re: [Docutils-users] Nested, titled sections

[David G. <go...@py...>]

On Tue, Apr 14, 2015 at 3:13 PM, Jeffrey C. Jacobs
<dar...@ti...> wrote:
> David Goodger <goodger <at> python.org> writes:
>> > What's the right way to specify a limited-scope subsection?
>>
>> Use "topic" or "sidebar" directives. Probably topic:
>> http://docutils.sourceforge.net/docs/ref/rst/directives.html#topic
>
> Thank you David.  I looked over the documentation for topic and sidebar
> and I think maybe this way of specifying isn't ideal as these would be
> normal text elements in the flow.  It goes back to the formal definition
> of how one writes a screenplay using RST.

First off, I was answering your question about the dog essay. I'd
never suggest topics or sidebars for use in screenplays. If you want
to know about screenplays, don't ask about dog essays; ask about
screenplays, as you did in the other thread. Please don't bait &
switch.

Next, I have no idea what you mean by "normal text elements in the
flow". A document is nothing more than a series of text elements, no
matter what type (document, or elements).

> Right now I'm using Field Lists but that won't allow embedded
> admonitions so I'm looking for a better way.

Uh... yes they would. You can put admonitions inside field lists, no
problem. Try it. Not sure why you'd want to though. I don't see how
admonitions apply to screenplays.

> Currently::
>
> :Character:
>    `(action)`:parenthetical:
>    Dialog

This seems perfectly reasonable to me. See below for my suggestions.

> Proposal with topics::
>
> .. topic:: Character
>
>    .. admonition:: parenthetical
>
>       (action)
>
>    Dialog

Far too wordy and complex. In "An Introduction to reStructuredText", I
described reST as "an easy-to-read, what-you-see-is-what-you-get
plaintext markup syntax". The above is neither. You'll never get
perfect WYSIWYG, but you can get much closer.

> Proposal with Definition Lists::
>
> Character
>
>   .. admonition:: parenthetical
>
>      (action)
>
>   Dialog

While definition lists are a viable alternative to field lists for
screenplay dialog, the above is not a valid definition list item. This
would be:

Character
  .. admonition:: parenthetical

     (action)

  Dialog

> I'm not sure if I'm able to embed adminitions in a topic or a definition
> list

You can. At the block level, reST is completely orthogonal. Anywhere
that you can put a paragraph or a bullet list, you can also put any
other block-level element, including admonitions. With reST, you can
put a table inside an admonition inside a table cell inside... as
deeply as you like.

However, I don't think admonitions are the right thing for your purposes here.

> but as suggested in the developers list an admonition is a better
> document type than a role since parenthetical is typically on a line by
> itself.

That should be "element", not "document". A document is a much bigger
thing, with a title, section structure, multiple block-level elements,
etc.

"On a line by itself". Hmmm. Sounds like line blocks might be just the thing:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#line-blocks

> I do worry though about how wordy the admonitions are relative to how
> concise the current specification is, but I think processing of the
> generated doctree would be incorrect.

Correctness is a wonderful goal, but practicality beats purity.
Looking at screenplays, I see a set of conventions accumulated
organically over the years. In other words: evolved, not designed.
Evolution is messy, and I wouldn't expect screenplays to fit neatly
into any document model. Neither Docutils' document model nor reST's
set of constructs were designed with screenplays in mind, so you'll
have to shoehorn those conventions in as best you can.

> So thanks again for your help but
> if you have more suggestions on how to resolve this issue I'd greatly
> appreciate it.

I suspect that definition lists would be your best bet for dialog.
Field lists could work too, but they are typically formatted
side-by-side (e.g., by the current html4css1 writer) while definition
lists are often formatted term-on-top, definition-below. So it would
be easier to reconfigure a stylesheet to make definition lists look
like screenplay dialog.

Your "parentheticals" (AKA "personal direction" or "wrylies") may be
common enough to deserve their own special syntax. Lucky for you, reST
offers one customizable inline syntax mechanism: the default
interpreted text role:

    .. role:: parenthetical
    .. default-role:: parenthetical

After that, you can drop the text ":parenthetical:" from your markup:

    Character
        `(action)`
        Dialog

At this point, the only real issue is that the "(action)" text above
has to be on its own line. You could either process your document to
treat the "parenthetical" role specially, or you could use line
blocks:

    Character
        | Dialog
        | `(action)`
        | More dialog, that might
          wrap around. Note that
          the vertical bars aren't
          necessary on wrapped lines.

-- 
David Goodger <http://python.net/~goodger>

Re: [Docutils-users] Nested, titled sections

[Jeffrey C. J. <dar...@ti...>]

David Goodger <goodger <at> python.org> writes:
> > What's the right way to specify a limited-scope subsection?
> 
> Use "topic" or "sidebar" directives. Probably topic:
> http://docutils.sourceforge.net/docs/ref/rst/directives.html#topic

Thank you David.  I looked over the documentation for topic and sidebar 
and I think maybe this way of specifying isn't ideal as these would be 
normal text elements in the flow.  It goes back to the formal definition 
of how one writes a screenplay using RST.

Right now I'm using Field Lists but that won't allow embedded 
admonitions so I'm looking for a better way.

Currently::

:Character:
   `(action)`:parenthetical:
   Dialog

Proposal with topics::

.. topic:: Character

   .. admonition:: parenthetical

      (action)

   Dialog

Proposal with Definition Lists::

Character

  .. admonition:: parenthetical

     (action)

  Dialog


I'm not sure if I'm able to embed adminitions in a topic or a definition 
list but as suggested in the developers list an admonition is a better 
document type than a role since parenthetical is typically on a line by 
itself.

I do worry though about how wordy the admonitions are relative to how 
concise the current specification is, but I think processing of the 
generated doctree would be incorrect.  So thanks again for your help but 
if you have more suggestions on how to resolve this issue I'd greatly 
appreciate it.

Jeffrey.

[Docutils-users] Class assigned to all titles or titled blocks of a given level

[Jeffrey C. J. <dar...@ti...>]

Is there a way to assign a class to every document element at a given 
title level, or is this better at the xml transform level?  For 
instance,

.. class:: doctor

Peter Davison
~~~~~~~~~~~~~

Companion
---------

Adric

Nyssa

Tegan

Turlough

Peri

Colin Baker
~~~~~~~~~~~

Peri

Mel

----------------

Is there a way in other words of writing this such that Colin Baker is 
also doctor class without repeating ".. class:: doctor for every Doctor?

Jeffrey.

Re: [Docutils-users] Nested, titled sections

[David G. <go...@py...>]

On Tue, Apr 14, 2015 at 1:54 PM, Jeffrey C. Jacobs
<dar...@ti...> wrote:
> Is there a way to nest a titled section.

In the strictest sense, only in the normal way, via the normal
hierarchy of sections and subsections etc. But that doesn't do what
you want.

> For instance, say we have text::
>
> All About Dogs
> ~~~~~~~~~~~~~~
>
> Aren't Dogs great?  Let's talk about a breed.
>
>    Poodle
>    ------
>
>    Poodles are the smartest dog.  They come in full and toy sizes.
>
> So let's talk about a different dog.
>
>    Beagle
>    ------
>
>    Beagles are noisy.  Snoopy was a beagle.
>
> And how about another Dog.
>
> In this example, I've incorrectly indented the headings for the
> subsections to make it clear where each subsection ends but this isn't
> valid RST.

Exactly. There is no way apart from some mechanism like this. And the
output should also format such segments in a distinctive way,
otherwise the document will not make sense to the reader.

> What's the right way to specify a limited-scope subsection?

Use "topic" or "sidebar" directives. Probably topic:
http://docutils.sourceforge.net/docs/ref/rst/directives.html#topic

-- 
David Goodger <http://python.net/~goodger>

[Docutils-users] Nested, titled sections

[Jeffrey C. J. <dar...@ti...>]

Is there a way to nest a titled section.  For instance, say we have text::

All About Dogs
~~~~~~~~~~~~~~

Aren't Dogs great?  Let's talk about a breed.

   Poodle
   ------

   Poodles are the smartest dog.  They come in full and toy sizes.

So let's talk about a different dog.

   Beagle
   ------

   Beagles are noisy.  Snoopy was a beagle.

And how about another Dog.

In this example, I've incorrectly indented the headings for the 
subsections to make it clear where each subsection ends but this isn't 
valid RST.  What's the right way to specify a limited-scope subsection?

Jeffrey.

Re: [Docutils-users] Font Specification For rst2odt?

[Terry B. <ter...@ya...>]

On Mon, 6 Apr 2015 16:24:46 -0500
Terry Brown <ter...@ya...> wrote:

> Yes, make your odt file:
> 
>   (1) rst2odf myfile.txt >myfile.odt
[snip]
>    (4) rst2odf --stylesheet=myfile.styles.odt myfile.txt >myfile.odt

Blah, `rst2odt`, obviously, not rst2odf.

Cheers -Terry

Re: [Docutils-users] Font Specification For rst2odt?

[Tim D. <tu...@tu...>]

On 04/06/2015 02:24 PM, Tim Daneliuk wrote:
> Is there a way to specify what default fonts to use for various portions of an
> rst document when converting to odt?  I am using libreoffice in headless mode
> to emit .doc files from a makefile  I would like better control of font
> selection in the makefile so as to produce output that renders a bit prettier
> in Word.
> 
> Thanks,
> 

Thanks Terry & David.  I shall try this.
-- 
----------------------------------------------------------------------------
Tim Daneliuk     tu...@tu...
PGP Key:         http://www.tundraware.com/PGP/

Re: [Docutils-users] Font Specification For rst2odt?

[Terry B. <ter...@ya...>]

[replied to OP only by mistake]

On Mon, 06 Apr 2015 14:24:16 -0500
Tim Daneliuk <tu...@tu...> wrote:

> Is there a way to specify what default fonts to use for various
> portions of an rst document when converting to odt?  I am using

Yes, make your odt file:

  (1) rst2odf myfile.txt >myfile.odt

make a copy

  (2) cp myfile.odt myfile.styles.odt

edit the copy and change the styles to be the way you want

  (3) libreoffice myfile.styles.odt

  (F11 the style manager thing, modify the styles in the document, not
  just the text on the page)

after that you can do

   (4) rst2odf --stylesheet=myfile.styles.odt myfile.txt >myfile.odt

It doesn't matter if myfile.styles.odt gets out of date content wise,
it's just being used to look up styles.  I.e. you only need to do
steps 1-3 once.  Unless... if your changes to myfile.txt cause the use
of a new style in myfile.odt, e.g. a figure caption style
after the first time you add a figure, just do steps 2 and 3 again -
you'll only need to edit the new style, the previous style edits get
copied at step 2.

Hope that helps.

Cheers -Terry



> libreoffice in headless mode to emit .doc files from a makefile  I
> would like better control of font selection in the makefile so as to
> produce output that renders a bit prettier in Word.
> 
> Thanks,

Re: [Docutils-users] Font Specification For rst2odt?

[David G. <go...@py...>]

On Mon, Apr 6, 2015 at 2:24 PM, Tim Daneliuk <tu...@tu...> wrote:
> Is there a way to specify what default fonts to use for various portions of an
> rst document when converting to odt?  I am using libreoffice in headless mode
> to emit .doc files from a makefile  I would like better control of font
> selection in the makefile so as to produce output that renders a bit prettier
> in Word.

I don't think any font information is generated by Docutils for ODT. I
believe the answer is to make and use a custom stylesheet.
Instructions here:
http://docutils.sourceforge.net/docs/user/odt.html#defining-and-using-a-custom-stylesheet

-- 
David Goodger <http://python.net/~goodger>

[Docutils-users] Font Specification For rst2odt?

[Tim D. <tu...@tu...>]

Is there a way to specify what default fonts to use for various portions of an
rst document when converting to odt?  I am using libreoffice in headless mode
to emit .doc files from a makefile  I would like better control of font
selection in the makefile so as to produce output that renders a bit prettier
in Word.

Thanks,
-- 
----------------------------------------------------------------------------
Tim Daneliuk     tu...@tu...
PGP Key:         http://www.tundraware.com/PGP/

Re: [Docutils-users] rst-mode broken indentation with emacs 24.4

[Stefan M. <st...@me...>]

Hi Yuri!

2 days ago Yuri D'Elia wrote:
> Hi everyone, hopefully this is the right place to post issues with
> `rst-mode'.

It is one of the options :-) .

> With emacs 24.4 `electric-indent-mode' is now globally on by default.
> This seems to have broken rst-mode's indentation behavior, since <RET>
> will also *cycle* the indentation of the current line; usually breaking
> it in frustrating ways.
> 
> To have an example, consider:
> 
> .. code::<RET>
>    type anything here<RET>
> 
> will result in:
> 
> .. code::
> type anything here
> 
> I currently fixed this by manually changing <RET> in rst-mode-map to
> `newline-and-indent', but it would be nicer to actually make rst-mode
> cooperate with electric-indent-mode.

Thanks for the report. I'll look into this.


						Grüße

						Stefan

[Docutils-users] rst-mode broken indentation with emacs 24.4

[Yuri D'E. <wa...@th...>]

Hi everyone, hopefully this is the right place to post issues with
`rst-mode'.

With emacs 24.4 `electric-indent-mode' is now globally on by default.
This seems to have broken rst-mode's indentation behavior, since <RET>
will also *cycle* the indentation of the current line; usually breaking
it in frustrating ways.

To have an example, consider:

.. code::<RET>
   type anything here<RET>

will result in:

.. code::
type anything here

I currently fixed this by manually changing <RET> in rst-mode-map to
`newline-and-indent', but it would be nicer to actually make rst-mode
cooperate with electric-indent-mode.

Re: [Docutils-users] Test suite failure

[Guenter M. <mi...@us...>]

Dear John,

> I'm getting 4 test failures.  Here is the info you request in 
> the order listed in the README:

Thank you for the report. The problem (a false positive) is fixed in the
repository. See http://sourceforge.net/p/docutils/bugs/256/

Günter

[Docutils-users] Test suite failure

[John C. <Joh...@gm...>]

If any of the tests fail, please open a bug report, send email, 
or post a message via the web interface (see Bugs). Please 
include all relevant output, information about your operating 
system, Python version, and Docutils version.

I'm getting 4 test failures.  Here is the info you request in 
the order listed in the README:

C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-0.12\test
λ python alltests.py
Testing Docutils 0.12 [release] with Python 2.7.9 on 2015-03-20 
at 13:48:16
Working directory: 
C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-0.12\test
Docutils package: 
C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-0.12\docutils
...................................................................
................................................
.....................................................F.............
................................................
...................................................................
...........
test_writers\test_html4css1_template.py: totest['template'][0]; 
test_publish (DocutilsTestSupport.WriterPublishTest
input:
================
 Document Title
================
----------
 Subtitle
----------

:Author: Me

.. footer:: footer text

Section
=======

Some text.

-: expected
+: output
  head_prefix = """\
  <?xml version="1.0" encoding="utf-8" ?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition
  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>"""


  head = """\
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="generator" 
content="Docutils 0.12: http://docutils.sourceforge.net/" />
  <title>Document Title</title>
  <meta name="author" content="Me" />"""


  stylesheet = """\
- <link rel="stylesheet" href="/test.css" type="text/css" />"""
+ <link rel="stylesheet" href="C:/test.css" type="text/css" />"""
?                              ++


  body_prefix = """\
  </head>
  <body>
  <div class="document" id="document-title">"""


  body_pre_docinfo = """\
  <h1 class="title">Document Title</h1>
  <h2 class="subtitle" id="subtitle">Subtitle</h2>"""


  docinfo = """\
  <table class="docinfo" frame="void" rules="none">
  <col class="docinfo-name" />
  <col class="docinfo-content" />
  <tbody valign="top">
  <tr><th class="docinfo-name">Author:</th>
  <td>Me</td></tr>
  </tbody>
  </table>"""


  body = """\
  <div class="section" id="section">
  <h1>Section</h1>
  <p>Some text.</p>
  </div>"""


  body_suffix = """\
  </div>
  <div class="footer">
  <hr class="footer" />
  footer text
  </div>
  </body>
  </html>"""


  head_prefix = """\
  <?xml version="1.0" encoding="utf-8" ?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition
  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>"""


  head = """\
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
  <title>Document Title</title>
  <meta name="author" content="Me" />"""


  stylesheet = """\
- <link rel="stylesheet" href="/test.css" type="text/css" />"""
+ <link rel="stylesheet" href="C:/test.css" type="text/css" />"""
?                              ++


  body_prefix = """\
  </head>
  <body>
  <div class="document" id="document-title">"""


  body_pre_docinfo = """\
  <h1 class="title">Document Title</h1>
  <h2 class="subtitle" id="subtitle">Subtitle</h2>"""


  docinfo = """\
  <table class="docinfo" frame="void" rules="none">
  <col class="docinfo-name" />
  <col class="docinfo-content" />
  <tbody valign="top">
  <tr><th class="docinfo-name">Author:</th>
  <td>Me</td></tr>
  </tbody>
  </table>"""


  body = """\
  <div class="section" id="section">
  <h1>Section</h1>
  <p>Some text.</p>
  </div>"""


  body_suffix = """\
  </div>
  <div class="footer">
  <hr class="footer" />
  footer text
  </div>
  </body>
  </html>"""


  title = """\
  Document Title"""


  subtitle = """\
  Subtitle"""


  header = """\
  """


  footer = """\
  <div class="footer">
  <hr class="footer" />
  footer text
  </div>"""


  meta = """\
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
  <meta name="author" content="Me" />"""


  fragment = """\
  <div class="section" id="section">
  <h1>Section</h1>
  <p>Some text.</p>
  </div>"""


  html_prolog = """\
  <?xml version="1.0" encoding="%s" ?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition


  html_head = """\
  <meta http-equiv="Content-Type" content="text/html; charset=%s" />
  <meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
  <title>Document Title</title>
  <meta name="author" content="Me" />"""


  html_title = """\
  <h1 class="title">Document Title</h1>"""


  html_subtitle = """\
  <h2 class="subtitle" id="subtitle">Subtitle</h2>"""


  html_body = """\
  <div class="document" id="document-title">
  <h1 class="title">Document Title</h1>
  <h2 class="subtitle" id="subtitle">Subtitle</h2>
  <table class="docinfo" frame="void" rules="none">
  <col class="docinfo-name" />
  <col class="docinfo-content" />
  <tbody valign="top">
  <tr><th class="docinfo-name">Author:</th>
  <td>Me</td></tr>
  </tbody>
  </table>
  <div class="section" id="section">
  <h1>Section</h1>
  <p>Some text.</p>
  </div>
  </div>
  <div class="footer">
  <hr class="footer" />
  footer text
  </div>"""
F..............................
test_writers\test_s5.py: totest['basics'][0]; test_publish 
(DocutilsTestSupport.WriterPublishTestCase)
input:
============
 Show Title
============

Title slide

First Slide
===========

Slide text.

-: expected
+: output
  <?xml version="1.0" encoding="utf-8" ?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition
al.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
  <meta name="version" content="S5 1.1" />
  <title>Show Title</title>
- <link rel="stylesheet" href="/test.css" type="text/css" />
+ <link rel="stylesheet" href="C:/test.css" type="text/css" />
?                              ++
  <!-- configuration parameters -->
  <meta name="defaultView" content="slideshow" />
  <meta name="controlVis" content="hidden" />
  <!-- style sheet links -->
  <script src="ui/default/slides.js" type="text/javascript"></script>
  <link rel="stylesheet" href="ui/default/slides.css"
        type="text/css" media="projection" id="slideProj" />
  <link rel="stylesheet" href="ui/default/outline.css"
        type="text/css" media="screen" id="outlineStyle" />
  <link rel="stylesheet" href="ui/default/print.css"
        type="text/css" media="print" id="slidePrint" />
  <link rel="stylesheet" href="ui/default/opera.css"
        type="text/css" media="projection" id="operaFix" />

  <style type="text/css">
  #currentSlide {display: none;}
  </style>
  </head>
  <body>
  <div class="layout">
  <div id="controls"></div>
  <div id="currentSlide"></div>
  <div id="header">

  </div>
  <div id="footer">
  <h1>Show Title</h1>

  </div>
  </div>
  <div class="presentation">
  <div class="slide" id="slide0">
  <h1 class="title">Show Title</h1>

  <p>Title slide</p>

  </div>
  <div class="slide" id="first-slide">
  <h1>First Slide</h1>
  <p>Slide text.</p>
  </div>
  </div>
  </body>
  </html>
F
test_writers\test_s5.py: totest['settings'][0]; test_publish 
(DocutilsTestSupport.WriterPublishTestCase)
input:
==================
 Bogus Slide Show
==================

We're just checking the settings

-: expected
+: output
  <?xml version="1.0" encoding="utf-8" ?>
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transition
al.dtd">
  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
  <meta name="version" content="S5 1.1" />
  <title>Bogus Slide Show</title>
- <link rel="stylesheet" href="/test.css" type="text/css" />
+ <link rel="stylesheet" href="C:/test.css" type="text/css" />
?                              ++
  <!-- configuration parameters -->
  <meta name="defaultView" content="outline" />
  <meta name="controlVis" content="visible" />
  <!-- style sheet links -->
  <script src="ui/default/slides.js" type="text/javascript"></script>
  <link rel="stylesheet" href="ui/default/slides.css"
        type="text/css" media="projection" id="slideProj" />
  <link rel="stylesheet" href="ui/default/outline.css"
        type="text/css" media="screen" id="outlineStyle" />
  <link rel="stylesheet" href="ui/default/print.css"
        type="text/css" media="print" id="slidePrint" />
  <link rel="stylesheet" href="ui/default/opera.css"
        type="text/css" media="projection" id="operaFix" />

  <style type="text/css">
  #currentSlide {display: none;}
  </style>
  </head>
  <body>
  <div class="layout">
  <div id="controls"></div>
  <div id="currentSlide"></div>
  <div id="header">

  </div>
  <div id="footer">
  <h1>Bogus Slide Show</h1>

  </div>
  </div>
  <div class="presentation">
  <div class="slide" id="slide0">
  <h1 class="title">Bogus Slide Show</h1>

  <p>We're just checking the settings</p>
  </div>
  </div>
  </body>
  </html>
F....................................................................
..............................................
.....................................................................
..............................................
....................................................................
...............................................
....................................................................
...........................................................
.....................................................................
..........................................................
.....................................................................
..........................................................
..........
======================================================================
FAIL: test_find_file_in_dirs (test_utils.HelperFunctionsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\test_utils.py", line 295, in test_find_file_in_dirs
    '../HISTORY.txt')
AssertionError: '..\\HISTORY.txt' != '../HISTORY.txt'

======================================================================
FAIL: test_writers\test_html4css1_template.py: totest['template'][0]; 
test_publish (DocutilsTestSupport.WriterPublishTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 729, in test_publish
    self.compare_output(self.input, output, self.expected)
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 244, in compare_output
    raise error
AssertionError: '''\
head_prefix = """\\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>"""


head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


stylesheet = """\\
<link rel="stylesheet" href="C:/test.css" type="text/css" />"""


body_prefix = """\\
</head>
<body>
<div class="document" id="document-title">"""


body_pre_docinfo = """\\
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


docinfo = """\\
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>"""


body = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


body_suffix = """\\
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>
</body>
</html>"""


head_prefix = """\\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>"""


head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


stylesheet = """\\
<link rel="stylesheet" href="C:/test.css" type="text/css" />"""


body_prefix = """\\
</head>
<body>
<div class="document" id="document-title">"""


body_pre_docinfo = """\\
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


docinfo = """\\
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>"""


body = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


body_suffix = """\\
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>
</body>
</html>"""


title = """\\
Document Title"""


subtitle = """\\
Subtitle"""


header = """\\
"""


footer = """\\
<div class="footer">
<hr class="footer" />
footer text
</div>"""


meta = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="author" content="Me" />"""


fragment = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


html_prolog = """\\
<?xml version="1.0" encoding="%s" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">"""


html_head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=%s" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


html_title = """\\
<h1 class="title">Document Title</h1>"""


html_subtitle = """\\
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


html_body = """\\
<div class="document" id="document-title">
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>"""''' != '''\
head_prefix = """\\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>"""


head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


stylesheet = """\\
<link rel="stylesheet" href="/test.css" type="text/css" />"""


body_prefix = """\\
</head>
<body>
<div class="document" id="document-title">"""


body_pre_docinfo = """\\
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


docinfo = """\\
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>"""


body = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


body_suffix = """\\
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>
</body>
</html>"""


head_prefix = """\\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>"""


head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


stylesheet = """\\
<link rel="stylesheet" href="/test.css" type="text/css" />"""


body_prefix = """\\
</head>
<body>
<div class="document" id="document-title">"""


body_pre_docinfo = """\\
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


docinfo = """\\
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>"""


body = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


body_suffix = """\\
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>
</body>
</html>"""


title = """\\
Document Title"""


subtitle = """\\
Subtitle"""


header = """\\
"""


footer = """\\
<div class="footer">
<hr class="footer" />
footer text
</div>"""


meta = """\\
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="author" content="Me" />"""


fragment = """\\
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>"""


html_prolog = """\\
<?xml version="1.0" encoding="%s" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">"""


html_head = """\\
<meta http-equiv="Content-Type" content="text/html; charset=%s" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<title>Document Title</title>
<meta name="author" content="Me" />"""


html_title = """\\
<h1 class="title">Document Title</h1>"""


html_subtitle = """\\
<h2 class="subtitle" id="subtitle">Subtitle</h2>"""


html_body = """\\
<div class="document" id="document-title">
<h1 class="title">Document Title</h1>
<h2 class="subtitle" id="subtitle">Subtitle</h2>
<table class="docinfo" frame="void" rules="none">
<col class="docinfo-name" />
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
<td>Me</td></tr>
</tbody>
</table>
<div class="section" id="section">
<h1>Section</h1>
<p>Some text.</p>
</div>
</div>
<div class="footer">
<hr class="footer" />
footer text
</div>"""'''

======================================================================
FAIL: test_writers\test_s5.py: totest['basics'][0]; test_publish 
(DocutilsTestSupport.WriterPublishTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 729, in test_publish
    self.compare_output(self.input, output, self.expected)
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 244, in compare_output
    raise error
AssertionError: '''\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="version" content="S5 1.1" />
<title>Show Title</title>
<link rel="stylesheet" href="C:/test.css" type="text/css" />
<!-- configuration parameters -->
<meta name="defaultView" content="slideshow" />
<meta name="controlVis" content="hidden" />
<!-- style sheet links -->
<script src="ui/default/slides.js" type="text/javascript"></script>
<link rel="stylesheet" href="ui/default/slides.css"
      type="text/css" media="projection" id="slideProj" />
<link rel="stylesheet" href="ui/default/outline.css"
      type="text/css" media="screen" id="outlineStyle" />
<link rel="stylesheet" href="ui/default/print.css"
      type="text/css" media="print" id="slidePrint" />
<link rel="stylesheet" href="ui/default/opera.css"
      type="text/css" media="projection" id="operaFix" />

<style type="text/css">
#currentSlide {display: none;}
</style>
</head>
<body>
<div class="layout">
<div id="controls"></div>
<div id="currentSlide"></div>
<div id="header">

</div>
<div id="footer">
<h1>Show Title</h1>

</div>
</div>
<div class="presentation">
<div class="slide" id="slide0">
<h1 class="title">Show Title</h1>

<p>Title slide</p>

</div>
<div class="slide" id="first-slide">
<h1>First Slide</h1>
<p>Slide text.</p>
</div>
</div>
</body>
</html>''' != '''\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="version" content="S5 1.1" />
<title>Show Title</title>
<link rel="stylesheet" href="/test.css" type="text/css" />
<!-- configuration parameters -->
<meta name="defaultView" content="slideshow" />
<meta name="controlVis" content="hidden" />
<!-- style sheet links -->
<script src="ui/default/slides.js" type="text/javascript"></script>
<link rel="stylesheet" href="ui/default/slides.css"
      type="text/css" media="projection" id="slideProj" />
<link rel="stylesheet" href="ui/default/outline.css"
      type="text/css" media="screen" id="outlineStyle" />
<link rel="stylesheet" href="ui/default/print.css"
      type="text/css" media="print" id="slidePrint" />
<link rel="stylesheet" href="ui/default/opera.css"
      type="text/css" media="projection" id="operaFix" />

<style type="text/css">
#currentSlide {display: none;}
</style>
</head>
<body>
<div class="layout">
<div id="controls"></div>
<div id="currentSlide"></div>
<div id="header">

</div>
<div id="footer">
<h1>Show Title</h1>

</div>
</div>
<div class="presentation">
<div class="slide" id="slide0">
<h1 class="title">Show Title</h1>

<p>Title slide</p>

</div>
<div class="slide" id="first-slide">
<h1>First Slide</h1>
<p>Slide text.</p>
</div>
</div>
</body>
</html>'''

======================================================================
FAIL: test_writers\test_s5.py: totest['settings'][0]; test_publish 
(DocutilsTestSupport.WriterPublishTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 729, in test_publish
    self.compare_output(self.input, output, self.expected)
  File "C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-
0.12\test\DocutilsTestSupport.py", line 244, in compare_output
    raise error
AssertionError: '''\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="version" content="S5 1.1" />
<title>Bogus Slide Show</title>
<link rel="stylesheet" href="C:/test.css" type="text/css" />
<!-- configuration parameters -->
<meta name="defaultView" content="outline" />
<meta name="controlVis" content="visible" />
<!-- style sheet links -->
<script src="ui/default/slides.js" type="text/javascript"></script>
<link rel="stylesheet" href="ui/default/slides.css"
      type="text/css" media="projection" id="slideProj" />
<link rel="stylesheet" href="ui/default/outline.css"
      type="text/css" media="screen" id="outlineStyle" />
<link rel="stylesheet" href="ui/default/print.css"
      type="text/css" media="print" id="slidePrint" />
<link rel="stylesheet" href="ui/default/opera.css"
      type="text/css" media="projection" id="operaFix" />

<style type="text/css">
#currentSlide {display: none;}
</style>
</head>
<body>
<div class="layout">
<div id="controls"></div>
<div id="currentSlide"></div>
<div id="header">

</div>
<div id="footer">
<h1>Bogus Slide Show</h1>

</div>
</div>
<div class="presentation">
<div class="slide" id="slide0">
<h1 class="title">Bogus Slide Show</h1>

<p>We\'re just checking the settings</p>
</div>
</div>
</body>
</html>''' != '''\
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Docutils 0.12: 
http://docutils.sourceforge.net/" />
<meta name="version" content="S5 1.1" />
<title>Bogus Slide Show</title>
<link rel="stylesheet" href="/test.css" type="text/css" />
<!-- configuration parameters -->
<meta name="defaultView" content="outline" />
<meta name="controlVis" content="visible" />
<!-- style sheet links -->
<script src="ui/default/slides.js" type="text/javascript"></script>
<link rel="stylesheet" href="ui/default/slides.css"
      type="text/css" media="projection" id="slideProj" />
<link rel="stylesheet" href="ui/default/outline.css"
      type="text/css" media="screen" id="outlineStyle" />
<link rel="stylesheet" href="ui/default/print.css"
      type="text/css" media="print" id="slidePrint" />
<link rel="stylesheet" href="ui/default/opera.css"
      type="text/css" media="projection" id="operaFix" />

<style type="text/css">
#currentSlide {display: none;}
</style>
</head>
<body>
<div class="layout">
<div id="controls"></div>
<div id="currentSlide"></div>
<div id="header">

</div>
<div id="footer">
<h1>Bogus Slide Show</h1>

</div>
</div>
<div class="presentation">
<div class="slide" id="slide0">
<h1 class="title">Bogus Slide Show</h1>

<p>We\'re just checking the settings</p>
</div>
</div>
</body>
</html>'''

----------------------------------------------------------------------
Ran 1238 tests in 38.785s

FAILED (failures=4)
Elapsed time: 48.971 seconds

C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-0.12\test

λ msinfo32
OS Name	Microsoft Windows 7 Home Premium
Version	6.1.7601 Service Pack 1 Build 7601
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	JJC
System Manufacturer	Hewlett-Packard
System Model	Compaq Presario CQ60 Notebook PC
System Type	X86-based PC
Processor	Pentium(R) Dual-Core CPU       
T4200  @ 2.00GHz, 2000 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date	Hewlett-Packard F.52, 8/26/2009
SMBIOS Version	2.4
Windows Directory	C:\Windows
System Directory	C:\Windows\system32
Boot Device	\Device\HarddiskVolume1
Locale	United States
Hardware Abstraction Layer	Version = "6.1.7601.17514"
User Name	JJC\fred
Time Zone	Pacific Daylight Time
Installed Physical Memory (RAM)	3.00 GB
Total Physical Memory	2.93 GB
Available Physical Memory	1.04 GB
Total Virtual Memory	8.79 GB
Available Virtual Memory	3.93 GB
Page File Space	5.86 GB
Page File	C:\pagefile.sys

λ python
Python 2.7.9 (default, Dec 10 2014, 12:24:55) 
[MSC v.1500 32 bit (Intel)] on win32

C:\Users\fred\Downloads\burp\dist\docutils-0.12\docutils-0.12\tools
λ python quicktest.py --version
quicktest.py (Docutils 0.12 [release])

Re: [Docutils-users] Good ReStructuredText editors

[TP <wi...@gm...>]

On Sat, Mar 7, 2015 at 12:11 AM, Ben Finney <ben...@be...> wrote:
> Virgil Arrington <cuy...@ho...> writes:
>
>> But some of my documents are longer with ten or more section headings.
>> I'd like to be able to quickly jump from one section to the next, but
>> I don't see any type of navigator panel in Gedit geared to
>> ReStructuredText headings.
>
> In Emacs's ‘rst-mode’, I have the usual bindings for ‘rst-forward-section’
> and ‘rst-backward-section’.
>
> I find Emacs a very good tool for editing reST documents.

And the rst-toc command (normally bound to C-c C-t C-t), displays a
table of contents buffer that can be used to navigate quickly to any
section.

Re: [Docutils-users] Good ReStructuredText editors

[Guenter M. <mi...@us...>]

On 2015-03-07, Ben Finney wrote:
> Virgil Arrington <cuy...@ho...> writes:

>> But some of my documents are longer with ten or more section headings.
>> I'd like to be able to quickly jump from one section to the next, but
>> I don't see any type of navigator panel in Gedit geared to
>> ReStructuredText headings.

> In Emacs's ‘rst-mode’, I have the usual bindings for ‘rst-forward-section’
> and ‘rst-backward-section’.

> I find Emacs a very good tool for editing reST documents.

In Jed's rst-mode, there are navigating-by-section functions, too. 
Besides this, there is also the "navigator": a buffer that lists the
sections headings and links them to the section headings in the document.

Günter

Re: [Docutils-users] Good ReStructuredText editors

[Ben F. <ben...@be...>]

Virgil Arrington <cuy...@ho...> writes:

> But some of my documents are longer with ten or more section headings.
> I'd like to be able to quickly jump from one section to the next, but
> I don't see any type of navigator panel in Gedit geared to
> ReStructuredText headings.

In Emacs's ‘rst-mode’, I have the usual bindings for ‘rst-forward-section’
and ‘rst-backward-section’.

I find Emacs a very good tool for editing reST documents.

-- 
 \        “Your [government] representative owes you, not his industry |
  `\   only, but his judgment; and he betrays, instead of serving you, |
_o__)        if he sacrifices it to your opinion.” —Edmund Burke, 1774 |
Ben Finney

Re: [Docutils-users] Good ReStructuredText editors

[Matěj C. <mc...@ce...>]

On 2014-12-11, 23:00 GMT, Virgil Arrington wrote:
> But some of my documents are longer with ten or more section 
> headings. I'd like to be able to quickly jump from one section 
> to the next, but I don't see any type of navigator panel in 
> Gedit geared to ReStructuredText headings.

BTW, just to note that the screenshot on 
https://github.com/bittner/gedit-reST-plugin sports a chapter 
navigation panel.

Matěj

Re: [Docutils-users] Links in Chinese

[Dariusz S. <dsuch-docutils@m.zato.io>]

On 06/03/15 16:41, David Goodger wrote:

>     `Zato 是ESB，并且服务都是用Python写的。 <https://zato.io>`_
> 
> It may look like there was a space there already, but that's because
> of the small Chinese period offset to the left in a full-width glyph.

Oh, that's a great catch, David.

Yes, that was it - works perfectly now!

thanks a lot again,

-- 
Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and Cloud Integrations in Python

Re: [Docutils-users] Links in Chinese

[David G. <go...@py...>]

On Fri, Mar 6, 2015 at 7:18 AM, Dariusz Suchojad
<dsuch-docutils@m.zato.io> wrote:
>
> Hello,
>
> I'm on docutils 0.12 and I'm having a bit of difficulties with making
> links containing characters in Chinese to work.
>
> Consider the example over here converted to HTML using rst2html ..
>
> https://zato.io/support/docutils/link-cn.txt
> https://zato.io/support/docutils/link-cn.html
>
> .. which works as expected as long as the contents in ``_ is within
> ASCII but fails as soon as Chinese copy is included.
>
> Will appreciate any assistance on that front - it's difficult to use
> Chinese texts and docutils without the feature.

The problem has nothing to do with ASCII vs. Chinese text (UTF-8 or
any encoding). The link with Chinese text simply lacks whitespace
between the end of the link text and the <URL>. Just add a space (or a
newline, etc.) after the "。" and before the "<":

    `Zato 是ESB，并且服务都是用Python写的。 <https://zato.io>`_

It may look like there was a space there already, but that's because
of the small Chinese period offset to the left in a full-width glyph.

The space is necessary to allow for link text that contains "<" and
">" characters.

-- 
David Goodger <http://python.net/~goodger>