#48 buildhtml fails with demo


Using the snapshot, all files build OK except demo.txt.

::: Processing: demo.txt
D:\TEMP\docutils\docs\user\rst\demo.txt:89: (ERROR/3)
Undefined substitution referenced: "probl
D:\TEMP\docutils\docs\user\rst\demo.txt:346: (ERROR/3)
Unknown target name: "5".
D:\TEMP\docutils\docs\user\rst\demo.txt:355: (ERROR/3)
Unknown target name: "nonexistent".
D:\TEMP\docutils\docs\user\rst\demo.txt:380: (ERROR/3)
Unknown target name: "hyperlink referenc
e without a target".
D:\TEMP\docutils\docs\user\rst\demo.txt:393: (ERROR/3)
Duplicate target name, cannot be used as
a unique reference: "duplicate target names".


  • David Goodger

    David Goodger - 2005-07-15

    Logged In: YES

    Those 5 errors are testing the error-handling of Docutils,
    and are expected. The text of demo.txt describes the situation:

    There should be five messages in the following,
    auto-generated section,
    "Docutils System Messages":

    Closing bug report as invalid.

  • David Goodger

    David Goodger - 2005-07-15
    • assigned_to: nobody --> goodger
    • status: open --> closed-invalid
  • David Goodger

    David Goodger - 2005-07-15

    Logged In: YES

    But thanks for the bug report. I have modified the demo.txt
    file to insert a reminder (in the form of an error message,
    the first) that errors are expected.

  • Colin J. Williams

    Logged In: YES


    A suggestion: leave out anything which does not build cleanly.

    At this stage of the game the user is just trying to get
    some documentation he can read. He can explore peculiar
    cases later.

    This is a snapshot version and one expects an element of
    risk and doesn't need trip wires. Yes, I now see that there
    is a note in the readme file but this would be better ahead
    of the action step.

    Colin W.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks