headers
David Goodger | 1 May 2009 01:28
Favicon

Re: error reporting: physical lines not reported when files included

On Thu, Apr 30, 2009 at 17:47, Alan G Isaac <alan.isaac <at> gmail.com> wrote:
> I use lots of ``include`` directives.
> Currently this renders the line numbers in error
> reports pretty useless.  Is it possible to get
> the file and physical line number?

It's a known bug:
http://docutils.sourceforge.net/BUGS.html#known-bugs

--

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

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Docutils-users mailing list
Docutils-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
Permalink | Reply | 1 comment |
headers
Alan G Isaac | 1 May 2009 02:43
Picon
Favicon

Re: error reporting: physical lines not reported when files included

> On Thu, Apr 30, 2009 at 17:47, Alan G Isaac <alan.isaac <at> gmail.com> wrote:
>> I use lots of ``include`` directives.
>> Currently this renders the line numbers in error
>> reports pretty useless.  Is it possible to get
>> the file and physical line number?

On 4/30/2009 7:28 PM David Goodger apparently wrote:
> It's a known bug:
> http://docutils.sourceforge.net/BUGS.html#known-bugs

I see. Well ...
I don't know if this would be any easier
than really fixing it, but it would work
much better for me if the line of
an ``include`` directive counted just as a
single line.  The idea being that line numbers for
errors in the main file would be correct, and when
errors come from an included file, that
would again be correctly indicated
(by attributing all errors to the line
of the ``include`` directive.

Thanks,
Alan

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul van Gelder | 5 May 2009 09:03
Picon

Test suite failure

Hello, a colleague recommended docutils to me. So, I was following the install
procedure and after successful installation, I ran the test suite and got one
failure. Since the install doc asked me to submit a bug report, here it is :-).

Good luck!

OS:

Mac OS X Version 10.5.6

docutils version:

ganymede:tools paul$ ./quicktest.py --version
quicktest.py (Docutils 0.6 [snapshot 2009-05-05, r5933])

test output:

ganymede:test paul$ ./alltests.py 
Testing Docutils 0.6 [snapshot 2009-05-05, r5933] with Python 2.5.1 on
2009-05-05 at 08:52:58
Working directory: /Users/paul/Desktop/tmp/docutils/test
Docutils package: /Users/paul/Desktop/tmp/docutils/docutils
.................................................................... [snip]
test_parsers/test_rst/test_directives/test_tables.py: totest['csv-table'][20];
test_parser (DocutilsTestSupport.ParserTestCase)
input:
.. csv-table:: bad encoding
   :file: test_parsers/test_rst/test_directives/utf-16.csv
   :encoding: latin-1
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Foord | 7 May 2009 00:53
Picon
Favicon
Gravatar

Re: Status of S5 Support

David Goodger wrote:
> On Sat, Mar 14, 2009 at 17:44, Michael Foord <fuzzyman <at> voidspace.org.uk> wrote:
>   
>> Hmmm... I've been having some issues with a vanilla 1.1 from the meyer site.
>> I have the right css but must be doing something else wrong. I'll
>> investigate further.
>>     
>
> Why not use the S5 1.1 that comes with (and is installed by) Docutils? It works.
>
>   

I was trying to use the default theme that comes with 1.1 which I think 
looks slightly nicer.

I can see now that S5 includes a mechanism for specifying the theme 
without having to replace all the libraries so I'll try that.

All the best,

Michael Foord

> I made some changes (beyond cosmetic) to the S5 stylesheets to work
> with Docutils. I don't think I made any chances to the JavaScript, but
> I'm not certain. You can use diff to see.
>
>   

--

-- 
http://www.ironpythoninaction.com/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Watkins | 12 May 2009 02:47
Picon
Favicon

docutils 0.6/trunk - TypeError: write() argument 1 must be str, not bytes

Greetings list - the following occurs in 0.6/trunk on Python 3.1b1 trunk.

$ rst2html.py README.txt
TypeError: write() argument 1 must be str, not bytes
Exiting due to error.  Use "--traceback" to diagnose.
Please report errors to <docutils-users <at> lists.sf.net>.
Include "--traceback" output, Docutils version (0.6 [repository]),
Python version (3.1b1+), your OS type & version, and the
command line used.

[me <at> test:/data/src/python/docutils/test/functional]$ rst2html.py
--traceback README.txt
Traceback (most recent call last):
  File "/usr/local/bin/rst2html.py", line 23, in <module>
    publish_cmdline(writer_name='html', description=description)
  File "/usr/local/lib/python3.1/site-packages/docutils/core.py", line
336, in publish_cmdline
    config_section=config_section, enable_exit_status=enable_exit_status)
  File "/usr/local/lib/python3.1/site-packages/docutils/core.py", line
205, in publish
    output = self.writer.write(self.document, self.destination)
  File
"/usr/local/lib/python3.1/site-packages/docutils/writers/__init__.py",
line 77, in write
    output = self.destination.write(self.output)
  File "/usr/local/lib/python3.1/site-packages/docutils/io.py", line 317,
in write
    self.destination.write(output)
TypeError: write() argument 1 must be str, not bytes
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael P. Soulier | 12 May 2009 19:52
Picon
Gravatar

starred notes in a table

Hi,

I'm trying to link some starred items in a table to notes put after the table.

Like, this is a starred item*, and you look for the * beneath the
table for the note.

* Here is the note contents

Now, I'm currently using the footnote mechanism, but I do have to
explicitely use a number in the footnote, so that multiple items can
be linked to the same note.

Item one [7]_
Item two [7]_

.. [7] This is the footnote

The only problem with this approach is that I have to keep track of
the last number used in the document, and I was wondering if there is
a better way. If I create footnotes with just a pound sign, then my
number is incremented automagickally, which is great, but then I can't
link multiple items to the same note.

Is the explicit footnote the best mechanism for this?

Thanks,
Mike
--

-- 
Michael P. Soulier <msoulier <at> digitaltorque.ca>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Alan G Isaac | 12 May 2009 21:32
Picon
Favicon

Re: starred notes in a table

I think you want autonumbered labels:
http://docutils.sourceforge.net/docs/user/rst/quickref.html#footnotes

Cheers,
Alan Isaac

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 1 comment |
headers
Michael P. Soulier | 12 May 2009 22:10
Picon
Gravatar

Re: starred notes in a table

On Tue, May 12, 2009 at 3:32 PM, Alan G Isaac <aisaac <at> american.edu> wrote:
> I think you want autonumbered labels:
> http://docutils.sourceforge.net/docs/user/rst/quickref.html#footnotes

I'll try that, thanks.

Mike
--

-- 
Michael P. Soulier <msoulier <at> digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 0 comments |
headers
Michael P. Soulier | 12 May 2009 22:12
Picon
Gravatar

arrows

Hi,

I'm using ASCII arrows at the moment in a table, like

->
=>

etc.

Now, for HTML there's an arrow entity, but that's only good for HTML output.

What would you use to do

<-
->
<->

etc?

Thanks,
Mike
--

-- 
Michael P. Soulier <msoulier <at> digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
(Continue reading)

Permalink | Reply | 7 comments |
headers
David Goodger | 12 May 2009 22:27
Favicon

Re: arrows

Unicode U+2190 ... U+21FF are arrows going in all directions.
More mostly right-pointing arrows are U+2794 ... U+27BF.

See http://docutils.sourceforge.net/docs/ref/rst/directives.html#unicode-character-codes

I used this:

.. |==>| unicode:: U+02794 .. thick rightwards arrow

To remind me to advance the slide in
http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
(search for "defaultdict").

--

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

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 6 comments |

Gmane