docutils-users Mailing List for Docutils: Documentation Utilities

> Sent: Saturday, September 29, 2012 12:14 AM
> Subject: [Docutils-users] rst2odt: anchoring figures/images as characters

> Hi,
> 
> I am very glad to use rst2odt to write and run R scripts. I thanks a
> lot Matti Pastell. It is super in order to allow readers to reuse
> figures in presentation for example. For those who are interested
> in, check:
> 
> http://mpastell.com/2010/03/25/create-odf-pdf-and-html-report-from-a-single-sweave-document/
> 
> http://eusebe.github.com/ascii/#_other_outputs
> http://eusebe.github.com/ascii/rest.html
> 
> Unfortunately, in documents larger than a few pages some
> figures/images are placed on the top of text. IMHO, one trick would
> to anchor figures and images as character. But I don't know where to
> change this behaviour. If somebody has clues...
> 
> Cheers.

Hello,

I work on and maintain rst2odt.py.  So, perhaps I can help with your
suggestion.

In a separate email, I have attached a zipped file containing:

1. a reST (test_image7.txt) file in which there are references to images
2. the test_image7.odt file I have generated from it
3. the images needed to generate the .odt file

In the output file (test_image7.odt), the images seem to be placed
reasonably close to the location where they are referenced.

Perhaps you could send me a reST file that generates images
incorrectly as you mentioned.  And, perhaps you could tell me how
those images should be placed or generated diffently.

Or, perhaps the ways that the images are referenced in the attached
test_image7.txt will give you a suggestion about how to get the
effect that you want.

One question -- Is it possible that an image in your document is
forcing a page break (in oowriter), and that is why the image is at
the top of the page?

Thanks for your help with rst2odt.py and the odf-odt writer.

By the way, the hawk in the image was one of a pair of hawks that
nested in a tree behind our house.  We watched their two babies grow
from small fuzzy chicks to young adults who climbed out farther and
farther on a branch before they finally left the nest for good.
Very cool, don't you think?

Dave K.



 
--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

Hi,

I am very glad to use rst2odt to write and run R scripts. I thanks a lot Matti Pastell. It is super in order to allow readers to reuse figures in presentation for example. For those who are interested in, check:

http://mpastell.com/2010/03/25/create-odf-pdf-and-html-report-from-a-single-sweave-document/

http://eusebe.github.com/ascii/#_other_outputs
http://eusebe.github.com/ascii/rest.html

Unfortunately, in documents larger than a few pages some figures/images are placed on the top of text. IMHO, one trick would to anchor figures and images as character. But I don't know where to change this behaviour. If somebody has clues...

Cheers.

On 2012-09-25, Tomi Pieviläinen wrote:
> On Tue, Sep 25, 2012 at 11:42:02AM +0200, Norman Jäckel wrote:
>> Hallo everybody,

>> does anybody know a smart way to leave out the whitespace before a
>> footnotemark in the main text?

> Text\ [1]_

> .. [1] foo

There is also a config setting to drop this space.

  trim_footnote_reference_space

    Remove spaces before footnote references.

    Default: don't (None); may be overriden by a writer-specific
    footnote_references default though. Options:
    --trim-footnote-reference-space, --leave-footnote-reference-space.

  -- http://docutils.sourceforge.net/docs/user/config.html
  
Günter  

On Tue, Sep 25, 2012 at 11:42:02AM +0200, Norman Jäckel wrote:
> Hallo everybody,
> 
> does anybody know a smart way to leave out the whitespace before a
> footnotemark in the main text?

Text\ [1]_

.. [1] foo

-- 
Tomi Pieviläinen, +358 400 487 504
A: Because it disrupts the natural way of thinking.
Q: Why is top posting frowned upon?

Hallo everybody,

does anybody know a smart way to leave out the whitespace before a
footnotemark in the main text?

>Text [1]_
>
>.. [1] foo

renders to

>Text 1

and in odt, the numeric character is superscripted. In German style,
there should not be a space before this superscripted footnotemark.

>Text[1]_
>
>.. [1] foo

does not work.

Thank you very much for your help.

Norman

You're describing a Sphinx-specific extension to reStructuredText that
is not supported by core Docutils. Somebody here may be able to help
you, but I cannot. I suggest you ask on the Sphinx mailing list.

-- David Goodger

On Thu, Sep 20, 2012 at 9:29 AM, Boggess, Rod <rbo...@te...> wrote:
> First, I’m not subscribed to the mailing list. Per the FAQ, and to keep my
> email to a sane level, I’m asking to please CC me on replies.
>
> I’m http://sphinx.pocoo.org/markup/inline.html, and it says that you can
> create a reference:
>
> ..  _my-reference-label:
>
> Some document text goes here.
>
> And that a link can be created to this reference, even across documents.
>
>                 This links to the reference :ref:`my-reference-label`.
>
> The document shows a self-referencing paragraph, and since it resides in the
> same source document, it does work, but the document’s claim that this
> reference works across source documents appears to be an overstatement. At
> least, it doesn’t work for me when I copy it from one source document and
> paste it in another, rebuild, and test. Once I move it to another document,
> the link it italicized but dead.
>
> I’m trying to improve the TortoiseHg documentation, and know very little
> about Sphinx or Docutils, but I’m more than happy to answer any relevant
> questions, and I’m not afraid to dig through more documentation on how to
> create cross-document-references. It’s just that this document seems to be
> leading me on a snipe hunt.
>
>
>
> Rod Boggess
>
> Software Engineer
>
> Tenova Core
>
> Cherrington Corporate Center
>
> 100 Corporate Center Drive
>
> Coraopolis, PA 15108
>
> Phone:  412-262-2240 x2467
>
> Email:  rbo...@te...
>
> Website:  www.tenovacore.com

Hi Ben and all!

Yesterday Ben Finney wrote:
> In announcements like this, can you give the URL to this new release?

Good point. As always it's in the SVN main line at

	http://docutils.svn.sourceforge.net/svnroot/docutils/trunk/docutils/tools/editors/emacs/rst.el

or as a complete package at

	http://www.merten-home.de/FreeSoftware/rst_el/


						Grüße

						Stefan

On Fri, Sep 21, 2012 at 7:25 AM, Norman Jäckel
<doc...@no...> wrote:
> is it possible to set a document title or section title with more than
> one line in the source file?

No, it's not possible, sorry.

> I would like to know this, because I want to setup a document with about
> 120 characters in the title and it does not look very nice, when the
> editor wraps the lines.

Yes, that's a limitation of reStructuredText. Such a long title is a
bit excessive though...

Perhaps use a subtitle instead? Especially if your title is of the
form "Long Title: Long Subtitle", this will work:

============
 Long Title
============
---------------
 Long Subtitle
---------------

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

Hello everybody,

is it possible to set a document title or section title with more than
one line in the source file?

Something like

=======
 Lorem
 ipsum
=======

which should work in the same way as

=============
 Lorem ipsum
=============

In my example, docutils raises an error, because ' ipsum ' does not
match to '======='.

I would like to know this, because I want to setup a document with about
120 characters in the title and it does not look very nice, when the
editor wraps the lines.

Thank you very much for your help (if possible).

Norman

Hi!

I just committed version 1.4.0 of rst.el. Here are the user visible
changes:

  Add support for `imenu` and `which-func-mode`. Remember setting
  `which-func-modes` for this feature to work.

  Automated calculations of section title faces replaced by `defface`.

The latter replaces the calculated background colors of section titles
by explicit `defface`\s. This may break existing customizations
although these faces are not customizable really. I'm interested in
feedback on this.

This version - or may be a slightly refactored one - will be included
in Emacs 24.3. This will replace a very old version of `rst.el` up to
the Emacs 24.2 distribution.


						Grüße

						Stefan

First, I'm not subscribed to the mailing list. Per the FAQ, and to keep
my email to a sane level, I'm asking to please CC me on replies.

 

I'm http://sphinx.pocoo.org/markup/inline.html, and it says that you can
create a reference:

 

..  _my-reference-label:

                

Some document text goes here.

 

And that a link can be created to this reference, even across documents.

 

                This links to the reference :ref:`my-reference-label`.

 

The document shows a self-referencing paragraph, and since it resides in
the same source document, it does work, but the document's claim that
this reference works across source documents appears to be an
overstatement. At least, it doesn't work for me when I copy it from one
source document and paste it in another, rebuild, and test. Once I move
it to another document, the link it italicized but dead.

 

I'm trying to improve the TortoiseHg documentation, and know very little
about Sphinx or Docutils, but I'm more than happy to answer any relevant
questions, and I'm not afraid to dig through more documentation on how
to create cross-document-references. It's just that this document seems
to be leading me on a snipe hunt.

 

Rod Boggess

Software Engineer

Tenova Core

Cherrington Corporate Center

100 Corporate Center Drive

Coraopolis, PA 15108

Phone:  412-262-2240 x2467

Email:  rbo...@te...

Website:  www.tenovacore.com

 

On Tue, Sep 11, 2012 at 12:25 AM, Dave Kuhlman <dku...@pa...> wrote:
>> From: Paolo Corti
>  > Sent: Friday, August 24, 2012 2:47 AM
>  >
>
>
>> I am afraid I have found a little bug in the rendering of the footer
>> (and header) in the rst2odt command.
>> When I am exporting the .rst file to .odt::
>>
>>     rst2odt.py --custom-odt-footer="Page %p% of %P%" f1.txt f1.odt
>>
>> the footer is correctly displayed in the odt document, but the field
>> specifiers are not recognized and the resulting label is "Page ".
>>
>> Any hints?
>> thanks in advance for the support
>
> Paolo -
>
> I finally found some time to work on this.  I believe I've fixed it
> and have checked the change into SVN.
>
> When you get a chance to try it, could you please let me know
> whether it works for you.  I'm worried that we might be dealing here
> with differences between versions of Open Office or Libre Office.
> It's possible that there are differences in the internal structure
> of the .odt files that they produce.
>
> Thanks again for helping with this.
>
> - Dave
>

Dave,
now it works well :)
thanks so much for the fix!
(and sorry for editing the subject, there way an error in the command name)

regards
p

-- 
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti

On 2012-09-11, Dave Kuhlman wrote:
>> From: Mark Wainwright
>  > Sent: Tuesday, September 11, 2012 8:04 AM
>  > 

>> >>> print type(PIL)
>> <type 'module'>
>> >>> print type(PIL.Image)
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>> AttributeError: 'module' object has no attribute 'Image'

>> (However, running 'import Image' does succeed.)


> And, the documentation here:

>         http://effbot.org/imagingbook/introduction.htm

> seems to be saying that "import Image" is the way to do it.

This documentation is outdated. 

> Günter, is there some specific version of PIL or Python that
> requires the "import PIL" etc way?

We had a bug report about this:

  - Fix [ 2993756 ]: import Python Imaging Library's Image module
    via ``import PIL`` as starting with PIL 1.2,
    "PIL lives in the PIL namespace only" (announcement__).

__ http://mail.python.org/pipermail/image-sig/2011-January/006650.html

> And, I'll have to admit that I over-wrote your change to
> odf_odt/__init__.py in the SVN repository.  I needed it to work on
> my machine.

No problem with overwriting changes that do not work (the strange thing is
that I did not have failures here). I hope the new version of the import
code fixes the problem "once and for all".

> Is there some way or place where we can find the correct way to
> import and use PIL?

(the bug tracker item 2993756 has the discussion that preceded the change.)

Thanks,

Günter

On 2012-09-11, Mark Wainwright wrote:
> Hi,

> On 11 September 2012 13:51, Guenter Milde <mi...@us...> wrote:
>> On 2012-09-11, Mark Wainwright wrote:
>>> Thanks. I tried again with a fresh snapshot as Guenter requested,
>>> though for what it's worth I still get the same four test failures. (I
>>> suspect the snapshot was the same as the one I originally used.)

>> OK. So we have to try to debug this. The tests run fine here.

>> * Do you have the Python Imaging Library installed?

>>   if yes: * from Ubuntu (package python-imaging)
>>           * local
>>           * both

> Yes, the python-imaging package is installed and up to date. (I'm not
> sure what 'local' would mean.)

Local would mean installing from separately downloaded source (instead of
Ubuntu package), usually put under /usr/local/.

...

>>   under Python 2.x and report the result?

>>>> print type(PIL)
><type 'module'>
>>>> print type(PIL.Image)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> AttributeError: 'module' object has no attribute 'Image'

> (However, running 'import Image' does succeed.)

You found a bug, which should be fixed now. 
(See http://docutils.svn.sourceforge.net/viewvc/docutils?view=revision&revision=7510
for details.)
The strange thing is, that when running this example, I get the same error
as you, but when running the test suite I get no error!

Try with a new snapshot (should be ready in about one hour).

Thanks for reporting,

Günter

> From: Mark Wainwright
 > Sent: Tuesday, September 11, 2012 8:04 AM
 > 

> >>> print type(PIL)
> <type 'module'>
> >>> print type(PIL.Image)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> AttributeError: 'module' object has no attribute 'Image'
> 
> (However, running 'import Image' does succeed.)
> 

And, the documentation here:

        http://effbot.org/imagingbook/introduction.htm

seems to be saying that "import Image" is the way to do it.

Günter, is there some specific version of PIL or Python that
requires the "import PIL" etc way?

And, I'll have to admit that I over-wrote your change to
odf_odt/__init__.py in the SVN repository.  I needed it to work on
my machine.

Is there some way or place where we can find the correct way to
import and use PIL?

- Dave


 
--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

> From: Mark Wainwright
 > Sent: Tuesday, September 11, 2012 1:04 AM
 > 

> Thanks. I tried again with a fresh snapshot as Guenter requested,
> though for what it's worth I still get the same four test failures. (I
> suspect the snapshot was the same as the one I originally used.)
> 
> > below.  His message describes how to specify the page size; and that
> 
> Yup, that works! So as not to have to use --stylesheet every time I
> invoke it, I'd like to edit the installed version of the stylesheet.
> Is there any problem with doing that? If not, where will I find it?

Mark -

You can do that (replace styles.odt with your modified copy), but if
you do, you will need to make a copy of your version, and then, each
time you update Docutils with the latest version, you will need to
remember to replace the installed version of styles.odt with your
copy.

An alternative is to use a batch file.  You are on Linux, so a
simple script file something like the following might be convenient
(named run_rst2odt, for example)::

        #!/bin/bash
        rst2odt.py --stylesheet=/path/to/my/styles.odt $1.txt $1.odt

Make it executable::

        $ chmod u+x run_rst2odt

Then, for example, call it from the command line with::

        $ ./run_rst2odt my_doc

That would read my_doc.txt and write out my_doc.odt.

The nice thing about using a batch file is that you can add other
command line options that you commonly use to it.  Also, using a
batch file will help you convert your documents in a consistent way.
I find that it is difficult after several months to remember which
command line options I used to produce a document that I want to
update.

If you decide to modify the installed version, on my machine, it's
here::

        /usr/local/lib/python2.7/site-packages/docutils/writers/odf_odt/styles.odt

Hope this helps.

And, I suspect that that we need yet another command line option
that enables us to specify page properties like page size, margin
sizes, etc.  But, that's an enhancement, and is a task for another
day.

- Dave



 
--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

Hi,

On 11 September 2012 13:51, Guenter Milde <mi...@us...> wrote:
> On 2012-09-11, Mark Wainwright wrote:
>> Thanks. I tried again with a fresh snapshot as Guenter requested,
>> though for what it's worth I still get the same four test failures. (I
>> suspect the snapshot was the same as the one I originally used.)
>
> OK. So we have to try to debug this. The tests run fine here.
>
> * Do you have the Python Imaging Library installed?
>
>   if yes: * from Ubuntu (package python-imaging)
>           * local
>           * both

Yes, the python-imaging package is installed and up to date. (I'm not
sure what 'local' would mean.)

> * could you run the Python code::
>
>    try: # check for the Python Imaging Library
>        import PIL
>    except ImportError:
>        try:  # sometimes PIL modules are put in PYTHONPATH's root
>            import Image
>            class PIL(object): pass  # dummy wrapper
>            PIL.Image = Image
>        except ImportError:
>            PIL = None
>
>    print type(PIL)
>    print type(PIL.Image)
>
>   under Python 2.x and report the result?

>>> print type(PIL)
<type 'module'>
>>> print type(PIL.Image)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'Image'

(However, running 'import Image' does succeed.)

> * could you find out whether the PIL sub-modules are installed in the
>   PYTHONPATH's root at your system?

Hmm - sorry, not being a programmer I'll need some guidance on how to
check this?

Mark

>
> Günter
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Docutils-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/docutils-users
>
> Please use "Reply All" to reply to the list.



-- 
Mark Wainwright, CKAN Community Co-ordinator
Open Knowledge Foundation http://okfn.org/
CKAN on Twitter: @CKANproject

On 2012-09-11, Mark Wainwright wrote:
> Thanks. I tried again with a fresh snapshot as Guenter requested,
> though for what it's worth I still get the same four test failures. (I
> suspect the snapshot was the same as the one I originally used.)

OK. So we have to try to debug this. The tests run fine here.

* Do you have the Python Imaging Library installed?

  if yes: * from Ubuntu (package python-imaging)
          * local
	  * both
	  
* could you run the Python code::

   try: # check for the Python Imaging Library
       import PIL
   except ImportError:
       try:  # sometimes PIL modules are put in PYTHONPATH's root
           import Image
           class PIL(object): pass  # dummy wrapper
           PIL.Image = Image
       except ImportError:
           PIL = None
	   
   print type(PIL)	   
   print type(PIL.Image)   

  under Python 2.x and report the result?
  
* could you find out whether the PIL sub-modules are installed in the
  PYTHONPATH's root at your system?
  	  
Günter	  

Thanks. I tried again with a fresh snapshot as Guenter requested,
though for what it's worth I still get the same four test failures. (I
suspect the snapshot was the same as the one I originally used.)

> below.  His message describes how to specify the page size; and that

Yup, that works! So as not to have to use --stylesheet every time I
invoke it, I'd like to edit the installed version of the stylesheet.
Is there any problem with doing that? If not, where will I find it?

Mark


On 10 September 2012 23:55, Dave Kuhlman <dku...@pa...> wrote:
>> From: Mark Wainwright
>  > Sent: Monday, September 10, 2012 2:33 PM
>  >
>
>> Thanks Guenter,
>>
>> > Could you try with a fresh snapshot from
>> > http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar
>>
>> Sure. Do I just follow the same install directions or do I need to
>> somehow uninstall the old version first (I don't see any kind of
>> uninstall option ...)
>
> Mark -
>
> You should be able to install the new version of Docutils over the
> top of (and replacing) the existing installed version by unpacking
> the distribution file::
>
> $ tar xf docutils-whateveritscalled.tar.gz
>
> and then cd to that new directory and type the following at the
> command line::
>
> $ python setup.py build
> $ sudo python setup.py install
>
> Back to your original question about paper size.  This issue was
> raised recently on this list by Paolo Corti.  See his message dated
> Aug. 10, 2012.  In case you can't find his message, I've pasted it
> below.  His message describes how to specify the page size; and that
> is working now that I've made a fix in response to his message.
> Note, especially, the link to the relevant documentation in Paolo's
> message.
>
>>
>> >> Unfortunately it gives me an ImportError ('ImportError: No module
>> >> named lxml').
>> >
>> > `apt-file lxml` revealed, that there is a python-lxml package for my debian
>> > system. Should be similar with Ubuntu.
>>
>> I don't know what that means, but I tried typing this (after apt-get
>> install'ing apt-file):
>>
>> `apt-file lxml`
>> D: this is a .deb file, calling dpkg-deb to get contents
>> dpkg-deb: error: failed to read archive `action': No such file or directory
>> E: Couldn't get contents from action
>
> I believe that Guenther is suggesting that you install python-lxml
> by doing the following at the command line::
>
> $ sudo apt-get install python-lxml
>
> *But,* you do not need to use rst2odt_prep.py in order to control
> the page size as you requested.
>
> Here is the message from Paolo:
>
>> I am trying to use rst2odt to generate an odt document from a rst source.
>>
>> I would like the document to have an "A4" page size, but when it is
>> being generated it is with "Letter" page size.
>>
>> According to this documentation [1], this is what I am doing:
>>
>> * cp ../my-virtual-env/lib/python2.7/site-packages/docutils/writers/odf_odt/styles.odt
>> .
>> * open the styles.odt document
>> * open the Format > Page menu
>> * set Format to A4, save the styles.odt and close it
>> * rst2odt --stylesheet-path=styles.odt  path/to/doc.rst path/to/doc.odt
>>
>> nothing happens (page size of doc.odt is still "Letter")...
>> Am I doing anything wront? Any suggestion?
>>
>> regards
>> p
>>
>> [1] http://docutils.sourceforge.net/docs/user/odt.html#defining-and-using-a-custom-stylesheet
>
> - Dave
>
>
> --
>
>
> Dave Kuhlman
> http://www.rexx.com/~dkuhlman



-- 
Mark Wainwright, CKAN Community Co-ordinator
Open Knowledge Foundation http://okfn.org/
CKAN on Twitter: @CKANproject

> From: Mark Wainwright
 > Sent: Monday, September 10, 2012 2:33 PM
 > 

> Thanks Guenter,
> 
> > Could you try with a fresh snapshot from
> > http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar
> 
> Sure. Do I just follow the same install directions or do I need to
> somehow uninstall the old version first (I don't see any kind of
> uninstall option ...)

Mark -

You should be able to install the new version of Docutils over the
top of (and replacing) the existing installed version by unpacking
the distribution file::

$ tar xf docutils-whateveritscalled.tar.gz

and then cd to that new directory and type the following at the
command line::

$ python setup.py build
$ sudo python setup.py install

Back to your original question about paper size.  This issue was
raised recently on this list by Paolo Corti.  See his message dated
Aug. 10, 2012.  In case you can't find his message, I've pasted it
below.  His message describes how to specify the page size; and that
is working now that I've made a fix in response to his message.
Note, especially, the link to the relevant documentation in Paolo's
message.

> 
> >> Unfortunately it gives me an ImportError ('ImportError: No module
> >> named lxml').
> >
> > `apt-file lxml` revealed, that there is a python-lxml package for my debian
> > system. Should be similar with Ubuntu.
> 
> I don't know what that means, but I tried typing this (after apt-get
> install'ing apt-file):
> 
> `apt-file lxml`
> D: this is a .deb file, calling dpkg-deb to get contents
> dpkg-deb: error: failed to read archive `action': No such file or directory
> E: Couldn't get contents from action

I believe that Guenther is suggesting that you install python-lxml
by doing the following at the command line::

$ sudo apt-get install python-lxml

*But,* you do not need to use rst2odt_prep.py in order to control
the page size as you requested.

Here is the message from Paolo:

> I am trying to use rst2odt to generate an odt document from a rst source.
> 
> I would like the document to have an "A4" page size, but when it is
> being generated it is with "Letter" page size.
> 
> According to this documentation [1], this is what I am doing:
> 
> * cp ../my-virtual-env/lib/python2.7/site-packages/docutils/writers/odf_odt/styles.odt
> .
> * open the styles.odt document
> * open the Format > Page menu
> * set Format to A4, save the styles.odt and close it
> * rst2odt --stylesheet-path=styles.odt  path/to/doc.rst path/to/doc.odt
> 
> nothing happens (page size of doc.odt is still "Letter")...
> Am I doing anything wront? Any suggestion?
> 
> regards
> p
> 
> [1] http://docutils.sourceforge.net/docs/user/odt.html#defining-and-using-a-custom-stylesheet

- Dave

 
--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

> From: Paolo Corti
 > Sent: Friday, August 24, 2012 2:47 AM
 > 


> I am afraid I have found a little bug in the rendering of the footer
> (and header) in the rst2odt command.
> When I am exporting the .rst file to .odt::
>
>     rst2odt.py --custom-odt-footer="Page %p% of %P%" f1.txt f1.odt
>
> the footer is correctly displayed in the odt document, but the field
> specifiers are not recognized and the resulting label is "Page ".
>
> Any hints?
> thanks in advance for the support

Paolo -

I finally found some time to work on this.  I believe I've fixed it
and have checked the change into SVN.

When you get a chance to try it, could you please let me know
whether it works for you.  I'm worried that we might be dealing here
with differences between versions of Open Office or Libre Office.
It's possible that there are differences in the internal structure
of the .odt files that they produce.

Thanks again for helping with this.

- Dave

 
--


Dave Kuhlman
http://www.rexx.com/~dkuhlman

Thanks Guenter,

> Could you try with a fresh snapshot from
> http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar

Sure. Do I just follow the same install directions or do I need to
somehow uninstall the old version first (I don't see any kind of
uninstall option ...)

>> Unfortunately it gives me an ImportError ('ImportError: No module
>> named lxml').
>
> `apt-file lxml` revealed, that there is a python-lxml package for my debian
> system. Should be similar with Ubuntu.

I don't know what that means, but I tried typing this (after apt-get
install'ing apt-file):

`apt-file lxml`
D: this is a .deb file, calling dpkg-deb to get contents
dpkg-deb: error: failed to read archive `action': No such file or directory
E: Couldn't get contents from action

Mark


On 10 September 2012 22:14, Guenter Milde <mi...@us...> wrote:
> On 2012-09-10, Mark Wainwright wrote:
>> Hi all,
>
>> I'm new to docutils; I've just installed it using the snapshot and
>> instructions at
>><http://docutils.sourceforge.net/README.html#running-the-test-suite>
>> and obediently ran the test suite, which yielded some errors. I'm
>> running Ubuntu 12.04 and 'python' seems to invoke Python 2.7.3. The
>> output is below. I'm not sure how to work out exactly which version
>> this docutils snapshot is of, but from the 'release notes' it seems as
>> if it might be slightly after 0.9.1.
>
> There has been work recently on PIL support.
> Could you try with a fresh snapshot from
> http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar
> ? (Also, you may compare your snapshots "HISTORY.txt" file to the one on the
> SVN repository
> http://docutils.svn.sourceforge.net/viewvc/docutils/
>
>> I also had a different problem: I ran rst2odt.py, and the output
>> appeared to have US Letter format for some reason ('paperconf' gives
>> the output 'a4'). Some googling suggested this might somehow be fixed
>> using rst2odt_prepstyles.py, so I tried to work out how to use that.
>> Unfortunately it gives me an ImportError ('ImportError: No module
>> named lxml').
>
> `apt-file lxml` revealed, that there is a python-lxml package for my debian
> system. Should be similar with Ubuntu.
>
> Günter
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Docutils-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/docutils-users
>
> Please use "Reply All" to reply to the list.



-- 
Mark Wainwright, CKAN Community Co-ordinator
Open Knowledge Foundation http://okfn.org/
CKAN on Twitter: @CKANproject

On 2012-09-10, Mark Wainwright wrote:
> Hi all,

> I'm new to docutils; I've just installed it using the snapshot and
> instructions at
><http://docutils.sourceforge.net/README.html#running-the-test-suite>
> and obediently ran the test suite, which yielded some errors. I'm
> running Ubuntu 12.04 and 'python' seems to invoke Python 2.7.3. The
> output is below. I'm not sure how to work out exactly which version
> this docutils snapshot is of, but from the 'release notes' it seems as
> if it might be slightly after 0.9.1.

There has been work recently on PIL support.
Could you try with a fresh snapshot from
http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar
? (Also, you may compare your snapshots "HISTORY.txt" file to the one on the
SVN repository 
http://docutils.svn.sourceforge.net/viewvc/docutils/

> I also had a different problem: I ran rst2odt.py, and the output
> appeared to have US Letter format for some reason ('paperconf' gives
> the output 'a4'). Some googling suggested this might somehow be fixed
> using rst2odt_prepstyles.py, so I tried to work out how to use that.
> Unfortunately it gives me an ImportError ('ImportError: No module
> named lxml').

`apt-file lxml` revealed, that there is a python-lxml package for my debian
system. Should be similar with Ubuntu.

Günter

Hi all,

I'm new to docutils; I've just installed it using the snapshot and
instructions at
<http://docutils.sourceforge.net/README.html#running-the-test-suite>
and obediently ran the test suite, which yielded some errors. I'm
running Ubuntu 12.04 and 'python' seems to invoke Python 2.7.3. The
output is below. I'm not sure how to work out exactly which version
this docutils snapshot is of, but from the 'release notes' it seems as
if it might be slightly after 0.9.1.

I also had a different problem: I ran rst2odt.py, and the output
appeared to have US Letter format for some reason ('paperconf' gives
the output 'a4'). Some googling suggested this might somehow be fixed
using rst2odt_prepstyles.py, so I tried to work out how to use that.
Unfortunately it gives me an ImportError ('ImportError: No module
named lxml').

Regards,

Mark Wainwright


======================================================================
ERROR: test_dependencies (test_dependencies.RecordDependenciesTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 57,
in test_dependencies
    record = self.get_record(writer_name='xml')
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 42,
in get_record
    **settings)
  File "/home/mark/okf/docutils/docutils/core.py", line 378, in publish_file
    enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 662, in
publish_programmatically
    output = pub.publish(enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 217, in publish
    self.settings)
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 72, in read
    self.parse()
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/mark/okf/docutils/docutils/parsers/rst/__init__.py",
line 162, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
174, in run
    input_source=document['source'])
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2281, in explicit_markup
    self.explicit_list(blank_finish)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2311, in explicit_list
    match_titles=self.state_machine.match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
323, in nested_list_parse
    node=node, match_titles=match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
199, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2584, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2291, in explicit_construct
    return method(self, expmatch)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2034, in directive
    directive_class, match, type_name, option_presets)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2083, in run_directive
    result = directive_instance.run()
  File "/home/mark/okf/docutils/docutils/parsers/rst/directives/images.py",
line 130, in run
    img = PIL.Image.open(
AttributeError: 'module' object has no attribute 'Image'

======================================================================
ERROR: test_dependencies_html (test_dependencies.RecordDependenciesTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 70,
in test_dependencies_html
    record = self.get_record(writer_name='html', settings_overrides=so)
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 42,
in get_record
    **settings)
  File "/home/mark/okf/docutils/docutils/core.py", line 378, in publish_file
    enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 662, in
publish_programmatically
    output = pub.publish(enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 217, in publish
    self.settings)
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 72, in read
    self.parse()
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/mark/okf/docutils/docutils/parsers/rst/__init__.py",
line 162, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
174, in run
    input_source=document['source'])
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2281, in explicit_markup
    self.explicit_list(blank_finish)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2311, in explicit_list
    match_titles=self.state_machine.match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
323, in nested_list_parse
    node=node, match_titles=match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
199, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2584, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2291, in explicit_construct
    return method(self, expmatch)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2034, in directive
    directive_class, match, type_name, option_presets)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2083, in run_directive
    result = directive_instance.run()
  File "/home/mark/okf/docutils/docutils/parsers/rst/directives/images.py",
line 130, in run
    img = PIL.Image.open(
AttributeError: 'module' object has no attribute 'Image'

======================================================================
ERROR: test_dependencies_latex (test_dependencies.RecordDependenciesTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 85,
in test_dependencies_latex
    record = self.get_record(writer_name='latex')
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 42,
in get_record
    **settings)
  File "/home/mark/okf/docutils/docutils/core.py", line 378, in publish_file
    enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 662, in
publish_programmatically
    output = pub.publish(enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 217, in publish
    self.settings)
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 72, in read
    self.parse()
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/mark/okf/docutils/docutils/parsers/rst/__init__.py",
line 162, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
174, in run
    input_source=document['source'])
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2281, in explicit_markup
    self.explicit_list(blank_finish)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2311, in explicit_list
    match_titles=self.state_machine.match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
323, in nested_list_parse
    node=node, match_titles=match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
199, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2584, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2291, in explicit_construct
    return method(self, expmatch)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2034, in directive
    directive_class, match, type_name, option_presets)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2083, in run_directive
    result = directive_instance.run()
  File "/home/mark/okf/docutils/docutils/parsers/rst/directives/images.py",
line 130, in run
    img = PIL.Image.open(
AttributeError: 'module' object has no attribute 'Image'

======================================================================
ERROR: test_stylesheet_dependencies (test_dependencies.RecordDependenciesTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 106,
in test_stylesheet_dependencies
    record = self.get_record(writer_name='html', settings_overrides=so)
  File "/home/mark/okf/docutils/test/test_dependencies.py", line 42,
in get_record
    **settings)
  File "/home/mark/okf/docutils/docutils/core.py", line 378, in publish_file
    enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 662, in
publish_programmatically
    output = pub.publish(enable_exit_status=enable_exit_status)
  File "/home/mark/okf/docutils/docutils/core.py", line 217, in publish
    self.settings)
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 72, in read
    self.parse()
  File "/home/mark/okf/docutils/docutils/readers/__init__.py", line 78, in parse
    self.parser.parse(self.input, document)
  File "/home/mark/okf/docutils/docutils/parsers/rst/__init__.py",
line 162, in parse
    self.statemachine.run(inputlines, document, inliner=self.inliner)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
174, in run
    input_source=document['source'])
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2281, in explicit_markup
    self.explicit_list(blank_finish)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2311, in explicit_list
    match_titles=self.state_machine.match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
323, in nested_list_parse
    node=node, match_titles=match_titles)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
199, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 239, in run
    context, state, transitions)
  File "/home/mark/okf/docutils/docutils/statemachine.py", line 460,
in check_line
    return method(match, context, next_state)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2584, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2291, in explicit_construct
    return method(self, expmatch)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2034, in directive
    directive_class, match, type_name, option_presets)
  File "/home/mark/okf/docutils/docutils/parsers/rst/states.py", line
2083, in run_directive
    result = directive_instance.run()
  File "/home/mark/okf/docutils/docutils/parsers/rst/directives/images.py",
line 130, in run
    img = PIL.Image.open(
AttributeError: 'module' object has no attribute 'Image'

----------------------------------------------------------------------
Ran 1194 tests in 8.415s

FAILED (errors=4)
Elapsed time: 10.499 seconds

On 2012-08-27, Angel J. Rivera wrote:

> I just installed docutils and I am having the error below when building
> an html from an rst file. The file cheatsheet.txt is from the
> restructured text website and I tested it using the online rst2html
> webpage with no problems.

> I am using:
> Python 3.2. on Windows XP.

> Output:

> C:\>rst2html.py cheatsheet.txt --traceback >cheatsheet.html
> Traceback (most recent call last):
>   File "c:\python32\scripts\rst2html.py", line 23, in <module>
>     publish_cmdline(writer_name='html', description=description)
>   File "C:\Python32\lib\site-packages\docutils\core.py", line 356, in publish_cm
> dline
>     config_section=config_section, enable_exit_status=enable_exit_status)
>   File "C:\Python32\lib\site-packages\docutils\core.py", line 223, in publish
>     output = self.writer.write(self.document, self.destination)
>   File "C:\Python32\lib\site-packages\docutils\writers\__init__.py", line 78, in
>  write
>     output = self.destination.write(self.output)
>   File "C:\Python32\lib\site-packages\docutils\io.py", line 406, in write
>     self.destination.write(data)
> TypeError: 'str' does not support the buffer interface
> Exception ValueError: 'I/O operation on closed file.' in <_io.TextIOWrapper name
>='<stdout>' mode='w' encoding='cp1252'> ignored

A similar error was reported in the docutils bug tracker when using Docutils
with Python 3.3b and fixed in the development version.

(The reported error is somewhat misleading - the real problem in this case
was not a missing "buffer interface" but mixing of "bytes" and (unicode)
"str" data types.)

Could you please try, if this is already solved with a current snapshot__?
__ http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/docutils/?view=tar

If not, could you please try to create a minimal example (i.e. the smallest
possible input file that still leads to the abovementioned error)?

Günter