36 failures from alltests.py

Thanks for the report.
However, without an error log, we cannot tell whether this is a Docutils problem,
a false positive, or a problem on your site/installation.

cmd shell screen output from alltests.py

Sorry about not uploading this before. Here are the command lines. I will upload the error log.
C:\>cd "C:\1dnlds\Python modules\docutils-snapshot\docutils\test"

C:\1dnlds\Python modules\docutils-snapshot\docutils\test>python alltests.py > joeResults.txt

Thanks for the great work.
All the best,
Joe

This looks very much like a line-ending problem.
Unix uses LF for new lines, while DOS (and Windows) use CR LF.

Docutils is expected to use native line endings but can work with both conventions.

+ even if the tests fail you should get the expected results in real world tasks

- you must either enable or disable line-end conversion when downloading from the repository.
(I cannot check, as I don't have Windows.)

Maybe we need

Hi Gunter,

On [2010-06-14 19:20:51 UTC] you wrote:

>This looks very much like a line-ending problem.
>Unix uses LF for new lines, while DOS (and Windows) use CR LF.
>
>Docutils is expected to use native line endings but can work with both
>conventions.
>
>+ even if the tests fail you should get the expected results in real world
>tasks
>
>- you must either enable or disable line-end conversion when downloading
>from the repository.
>(I cannot check, as I don't have Windows.)
>
>Maybe we need

OK so regarding your 3 points [not in order]:

1.
>This looks very much like a line-ending problem.
>Unix uses LF for new lines, while DOS (and Windows) use CR LF.

I downloaded the docutils-snapshot.tgz file from
[http://docutils.sourceforge.net/docutils-snapshot.tgz]
I don't think WinZip is unpacking it incorrectly.

2.
>- you must either enable or disable line-end conversion when downloading
>from the repository.
>(I cannot check, as I don't have Windows.)

I got to the download link from README.[Releases & Snapshots]
[http://docutils.sourceforge.net/README.html#releases-snapshots]
I clicked on Snapshot of Docutils code, documentation, front-end tools, and tests:
[http://docutils.sf.net/docutils-snapshot.tgz]
There was no "enable or disable line-end conversion" option available.

3.
>+ even if the tests fail you should get the expected results in real world
>tasks
I had a lot of trouble getting a simple :: operator to work.
As a test, i tried to run against the demo.txt file which i got from
http://docutils.sourceforge.net/docs/user/rst/demo.txt

Here is the result:
C:\1d\ReStructuredTextPjs>python -m rst2html demo.txt demo.html
demo.txt:89: (ERROR/3) Undefined substitution referenced: "problematic".
demo.txt:547: (ERROR/3) Undefined substitution referenced: "*** Expect 6 errors (including this one). ***".
demo.txt:346: (ERROR/3) Unknown target name: "5".
demo.txt:355: (ERROR/3) Unknown target name: "nonexistent".
demo.txt:380: (ERROR/3) Unknown target name: "hyperlink reference without a target".
demo.txt:393: (ERROR/3) Duplicate target name, cannot be used as a unique reference: "duplicate target names".

Thanks for the help.

All the best,

Joe

> As a test, i tried to run against the demo.txt file which i got from
> http://docutils.sourceforge.net/docs/user/rst/demo.txt
>
> Here is the result:
...
> demo.txt:547: (ERROR/3) Undefined substitution referenced: "*** Expect 6
> errors (including this one). ***".

Note the content of the quoted error. To demonstrate Docutils' error-handling, demo.txt intentionally generates 6 errors. I count 6 errors in your example. They're expected, not a bug.

IOW, the "test" and the example output are invalid.

> I had a lot of trouble getting a simple :: operator to work.

What are you trying to do? Show us *your* input and output. Attach files, please -- the comment system corrupts indentation.

Joe's input file

Joe's output file

Dear David,

>> demo.txt:547: (ERROR/3) Undefined substitution referenced: "*** Expect 6
>> errors (including this one). ***".
>
>Note the content of the quoted error. To demonstrate Docutils'
>error-handling, demo.txt intentionally generates 6 errors. I count 6 errors
>in your example. They're expected, not a bug.

Well, sorry about that. Being a newbie I didn't know if i understood the text input requirements enough to be sure that i wasn't causing the errors in my case, so i looked around for a "known good" example to test against the docutils installation. When I saw errors, after having seen errors from the alltests, i thought i'd better report back. I could have looked more closely at the details.

I've uploaded myfirst.txt and myfirst.html. This is what i'm having trouble getting '::' to work in. As i say i'm a newbie, so it could be my fault.

Thanks for a great system.

All the best,

Joe

> I've uploaded myfirst.txt and myfirst.html. This is what i'm having
> trouble getting '::' to work in. As i say i'm a newbie, so it could
> be my fault.

The problem is the lack of blank lines separating the literal block from the preceding paragraph. IOW, after the "::", you have to have a blank line before the literal block starts. See https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3015675&group_id=38414 for more details.

Fixed in SVN r6380.