No matter which plugin I select under the "Plugins" menu, I see the following errors in the "Default cascading style sheet for the HTML output of Docutils." following plugin X's help text with all its formatting directives. Am I the only one seeing this problem?
Leo-Editor Version: revision 4424 OS: Ubuntu Studio 11.04 (natty) <?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.7: http://docutils.sourceforge.net/" /> <title></ title> <style type="text/css"> /* :Author: David Goodger ([email protected]) :Id: $Id: html4css1.css 6253 2010-03-02 00:24:53Z milde $ :Copyright: This stylesheet has been placed in the public domain. Default cascading style sheet for the HTML output of Docutils. See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to customize this style sheet. */ System Message: WARNING/2 (<string>, line 17); backlink Inline emphasis start-string without end-string. /* used to remove borders from tables and images */ .borderless, table.borderless td, table.borderless th { System Message: WARNING/2 (<string>, line 21); backlink Inline emphasis start-string without end-string. System Message: ERROR/3 (<string>, line 23) Unexpected indentation. border: 0 } table.borderless td, table.borderless th { /* Override padding for "table.docutils td" with "! important". The right padding separates the table cells. */ System Message: WARNING/2 (<string>, line 27); backlink Inline emphasis start-string without end-string. System Message: WARNING/2 (<string>, line 28) Definition list ends without a blank line; unexpected unindent. padding: 0 0.5em 0 0 ! important } .first { /* Override more specific margin styles with "! important". */ margin- top: 0 ! important } System Message: WARNING/2 (<string>, line 31); backlink Inline emphasis start-string without end-string. .last, .with-subtitle { margin-bottom: 0 ! important } .hidden { display: none } a.toc-backref { text-decoration: none ; color: black } blockquote.epigraph { margin: 2em 5em ; } dl.docutils dd { margin-bottom: 0.5em } /* Uncomment (and remove this text!) to get bold-faced definition list terms dl.docutils dt { System Message: ERROR/3 (<string>, line 52) Unexpected indentation. font-weight: bold } System Message: WARNING/2 (<string>, line 53) Block quote ends without a blank line; unexpected unindent. */ System Message: WARNING/2 (<string>, line 53); backlink Inline emphasis start-string without end-string. div.abstract { margin: 2em 5em } div.abstract p.topic-title { font-weight: bold ; text-align: center } div.admonition, div.attention, div.caution, div.danger, div.error, div.hint, div.important, div.note, div.tip, div.warning { System Message: ERROR/3 (<string>, line 64) Unexpected indentation. margin: 2em ; border: medium outset ; padding: 1em } div.admonition p.admonition-title, div.hint p.admonition-title, div.important p.admonition-title, div.note p.admonition-title, div.tip p.admonition-title { System Message: ERROR/3 (<string>, line 71) Unexpected indentation. font-weight: bold ; font-family: sans-serif } div.attention p.admonition-title, div.caution p.admonition-title, div.danger p.admonition-title, div.error p.admonition-title, div.warning p.admonition-title { System Message: ERROR/3 (<string>, line 77) Unexpected indentation. color: red ; font-weight: bold ; font-family: sans-serif } /* Uncomment (and remove this text!) to get reduced vertical space in compound paragraphs. div.compound .compound-first, div.compound .compound-middle { margin-bottom: 0.5em } div.compound .compound-last, div.compound .compound-middle { margin-top: 0.5em } System Message: WARNING/2 (<string>, line 88) Definition list ends without a blank line; unexpected unindent. */ System Message: WARNING/2 (<string>, line 88); backlink Inline emphasis start-string without end-string. div.dedication { margin: 2em 5em ; text-align: center ; font-style: italic } div.dedication p.topic-title { font-weight: bold ; font-style: normal } div.figure { margin-left: 2em ; margin-right: 2em } div.footer, div.header { clear: both; font-size: smaller } div.line-block { display: block ; margin-top: 1em ; margin-bottom: 1em } div.line-block div.line-block { margin-top: 0 ; margin-bottom: 0 ; margin-left: 1.5em } div.sidebar { margin: 0 0 0.5em 1em ; border: medium outset ; padding: 1em ; background-color: #ffffee ; width: 40% ; float: right ; clear: right } div.sidebar p.rubric { font-family: sans-serif ; font-size: medium } div.system-messages { margin: 5em } div.system-messages h1 { color: red } div.system-message { border: medium outset ; padding: 1em } div.system-message p.system-message-title { color: red ; font-weight: bold } div.topic { margin: 2em } h1.section-subtitle, h2.section-subtitle, h3.section-subtitle, h4.section-subtitle, h5.section-subtitle, h6.section-subtitle { System Message: ERROR/3 (<string>, line 149) Unexpected indentation. margin-top: 0.4em } h1.title { text-align: center } h2.subtitle { text-align: center } hr.docutils { width: 75% } img.align-left, .figure.align-left, object.align-left { clear: left ; float: left ; margin-right: 1em } img.align-right, .figure.align-right, object.align-right { clear: right ; float: right ; margin-left: 1em } img.align-center, .figure.align-center, object.align-center { display: block; margin-left: auto; margin-right: auto; System Message: WARNING/2 (<string>, line 174) Definition list ends without a blank line; unexpected unindent. } .align-left { text-align: left } .align-center { clear: both ; text-align: center } .align-right { text-align: right } /* reset inner alignment in figures */ div.align-right { System Message: WARNING/2 (<string>, line 186); backlink Inline emphasis start-string without end-string. System Message: ERROR/3 (<string>, line 188) Unexpected indentation. text-align: left } /* div.align-center * { / / text-align: left } */ System Message: WARNING/2 (<string>, line 190); backlink Inline emphasis start-string without end-string. ol.simple, ul.simple { margin-bottom: 1em } ol.arabic { list-style: decimal } ol.loweralpha { list-style: lower-alpha } ol.upperalpha { list-style: upper-alpha } ol.lowerroman { list-style: lower-roman } ol.upperroman { list-style: upper-roman } p.attribution { text-align: right ; margin-left: 50% } p.caption { font-style: italic } p.credits { font-style: italic ; font-size: smaller } p.label { white-space: nowrap } p.rubric { font-weight: bold ; font-size: larger ; color: maroon ; text-align: center } p.sidebar-title { font-family: sans-serif ; font-weight: bold ; font-size: larger } p.sidebar-subtitle { font-family: sans-serif ; font-weight: bold } p.topic-title { font-weight: bold } pre.address { margin-bottom: 0 ; margin-top: 0 ; font: inherit } pre.literal-block, pre.doctest-block { margin-left: 2em ; margin-right: 2em } span.classifier { font-family: sans-serif ; font-style: oblique } span.classifier-delimiter { font-family: sans-serif ; font-weight: bold } span.interpreted { font-family: sans-serif } span.option { white-space: nowrap } span.pre { white-space: pre } span.problematic { color: red } span.section-subtitle { /* font-size relative to parent (h1..h6 element) */ font-size: 80% } System Message: WARNING/2 (<string>, line 273); backlink Inline emphasis start-string without end-string. table.citation { border-left: solid 1px gray; margin-left: 1px } table.docinfo { margin: 2em 4em } table.docutils { margin-top: 0.5em ; margin-bottom: 0.5em } table.footnote { border-left: solid 1px black; margin-left: 1px } table.docutils td, table.docutils th, table.docinfo td, table.docinfo th { System Message: ERROR/3 (<string>, line 293) Unexpected indentation. padding-left: 0.5em ; padding-right: 0.5em ; vertical-align: top } table.docutils th.field-name, table.docinfo th.docinfo-name { font-weight: bold ; text-align: left ; white-space: nowrap ; padding- left: 0 } h1 tt.docutils, h2 tt.docutils, h3 tt.docutils, h4 tt.docutils, h5 tt.docutils, h6 tt.docutils { System Message: ERROR/3 (<string>, line 305) Unexpected indentation. font-size: 100% } ul.auto-toc { list-style-type: none } </style> </head> <body> <div class="document"> <p>Creates a Plugins menu and adds all actives plugins to it.</p> <p>Selecting these menu items will bring up a short <strong>About Plugin</strong> dialog with the details of the plugin. In some circumstances a submenu will be created instead and an 'About' menu entry will be created in this.</p> <p><strong>INI files and the Properties Dialog</strong></p> <p>If a file exists in the plugins directory with the same file name as the plugin but with a .ini extension instead of .py, then a <strong>Properties</strong> item will be created in a submenu. Selecting this item will pop up a Properties Dialog which will allow the contents of this file to be edited.</p> <p>The .ini file should be formated for use by the python ConfigParser class.</p> <p><strong>Special Methods</strong></p> <p>Certain methods defined at the top level are considered special.</p> <dl class="docutils"> <dt>cmd_XZY</dt> <dd>If a method is defined at the module level with a name of the form <strong>cmd_XZY</strong> then a menu item <strong>XZY</strong> will be created which will invoke <strong>cmd_XZY</strong> when it is selected. These menus will appear in a sub menu.</dd> </dl> <p>applyConfiguration</p> <dl class="docutils"> <dt>topLevelMenu</dt> <dd>This method, if it exists, will be called when the user clicks on the plugin name in the plugins menu (or the <strong>About</strong> item in its submenu), but only if the plugin was loaded properly and registered with g.plugin_signon.</ dd> </dl> <p><strong>Special Variable Names</strong></p> <p>Some names defined at the top level have special significance.</p> <dl class="docutils"> <dt>__plugin_name__</dt> <dd>This will be used to define the name of the plugin and will be used as a label for its menu entry.</dd> <dt>__plugin_priority__</dt> <dd>Plugins can also attempt to select the order they will appear in the menu by defining a __plugin_prioriy__. The menu will be created with the highest priority items first. This behavior is not guaranteed since other plugins can define any priority. This priority does not affect the order of calling handlers. To change the order select a number outside the range 0-200 since this range is used internally for sorting alphabetically. Properties and INI files.</dd> </dl> </div> </body> </ html> -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
