gmane.text.docutils.devel

[ docutils-Patches-3527397 ] Add indentation toliteral blocks in manpage writer

SourceForge.net — 2012-05-25T04:23:30

Patches item #3527397, was opened at 2012-05-16 13:42
Message generated for change (Settings changed) made by grubert
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3527397&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joshua Graff (joshuagraff)
Summary: Add indentation to literal blocks in manpage writer

Initial Comment:
The current manpage writer does not add or maintain any type of indentation on literal blocks. 

Example: 

$ cat example.rst
=====
Title
=====
  
:Version: 1.1
:Author: joe.user< at >example.com
  
  
Example
=======
  
Example::
  
  $ man ls

$ rst2man.py example.rst > example.man
$ man ./example.man
NAME
       Title -

EXAMPLE
       Example:

       $ man ls

AUTHOR
       joe.user< at >example.com



In the above example '$

[ docutils-Patches-3527401 ] manpage writeraddmonition's don't preserve indentation

SourceForge.net — 2012-05-25T04:22:57

Patches item #3527401, was opened at 2012-05-16 14:12
Message generated for change (Comment added) made by grubert
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3527401&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joshua Graff (joshuagraff)
Summary: manpage writer addmonition's don't preserve indentation

Initial Comment:
In the manpage writer admonitions use troff's ``.IP``/``.RE`` for paragraph 
indentation. This unfortunately does not appear to preserve indentation for 
bullets and other block types (literal) that might be contained within an 
admonition.

Example:

$ cat example.rst
=====
Title
=====
  
:Version: 1.1
:Author: joe.user< at >example.com
  
  
Example
=======
  
This is an example.
  
.. NOTE::
   This is an important note.

Re: C reStructuredText parser

Marvin Humphrey — 2012-05-18T22:30:59

FWIW, I'm not wedded to Lemon, only to C.  Lemon is convenient because it's
easy to add as a bundled dependency: tiny (2 C files), compiles everywhere,
and public domain so no licensing restrictions.

But one of the questions I'd have here is whether it makes more sense to
approach parsing RST from the top down (LL, recursive descent) or from the
bottom up (LR, LALR).  If the reference parser for RST uses something like an
extremely complex regular expression, maybe it makes sense to hand-code a
recursive descent parser?

    http://en.wikipedia.org/wiki/Recursive_descent_parser#C_implementation

It might be worthwhile to collect some opinions on stackoverflow.com.  And
maybe it's time I bought the Dragon book and read the chapter on parsing. :)


Agreed.

Marvin Humphrey

------------------------------------------------------------------------------
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 respon

Re: C reStructuredText parser

Marvin Humphrey — 2012-05-18T22:07:12

:)

The project is Apache Lucy.  Our portability and dependency goals are to build
on all common operating systems and to require only a C compiler environment
(C99/C++ compiler, Make, linker, etc.) in addition to the dynamic language
"host" which the Lucy C core gets bound to.  These requirements are very
unlikely to be relaxed -- if it came down to choosing between a different
lightweight markup language and adding Python as a mandatory dependency, we
would go with a different lightweight markup language.


It's not essential that this task consume an absolute minimum of
engineering hours.  So long as it looks like the parser I write will
ultimately be used by Lucy, I'm happy to at least spend a few days getting
something up and running -- I'd do it partly for work, partly for fun, partly
to learn more about parsing, and partly for the public good.

Besides, the hard work you've put in building consensus and writing a
canonical spec may benefit us:

    http://markmail.org/message/s5bs5ik5gusga3ws

    In

[ docutils-Bugs-3527842 ] Extra directories forpython 3

SourceForge.net — 2012-05-18T11:40:39

Bugs item #3527842, was opened at 2012-05-18 04:40
Message generated for change (Tracker Item Submitted) made by toddrme2178
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3527842&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Todd Rme (toddrme2178)
Assigned to: Nobody/Anonymous (nobody)
Summary: Extra directories for python 3

Initial Comment:
 When compiling docutils 9 for python 3 I get the same directories I get with python 2:

{root}/{prefix}/bin/
{root}/{prefix}/{site-packages}/docutils/

However, I also extra directories that are not present in the python 2 version. These are:

{root}/{prefix}/{site-packages}/test/
{root}/{prefix}/{site-packages}/tools/

I was told that these directories are not supposed to be there.

----------------

Re: C reStructuredText parser

Stefan Merten — 2012-05-17T14:03:32

Hi Marvin!

38 minutes ago Stefan Merten wrote:

Normally you start with the tokens for a grammar. I wrote a good part
of `rst.el` and there is `rst-re-alist-def` which defines a lot of
regular expressions for matching reStructuredText stuff. May be this
could be used for a start.

You find `rst.el` at

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


Grüße

Stefan
------------------------------------------------------------------------------
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/

Re: C reStructuredText parser

Stefan Merten — 2012-05-17T13:22:47

Hi Marvin!

Yesterday Marvin Humphrey wrote:

The main question is whether you can squeeze reStructuredText syntax
into a LALR(1) (or any other recursive) grammar. Frankly I doubt this.
One of the beauties of reStructuredText is that it is very readable /
writable for humans - which more or less implies that it is difficult
to parse.

However, it could be worth a try to at least cover a significant
subset of reStructuredText by a formal grammar. This would open the
door for reStructuredText parsers in other programming languages, too.
IMHO this would be a worthwhile goal.

In the past I worked with formal grammars a couple of times. May be I
can help a bit here. However, don't hold your breath for a reaction
from me ;-) .


Grüße

Stefan
------------------------------------------------------------------------------
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 in

Re: C reStructuredText parser

David Goodger — 2012-05-17T00:57:21

Seems short-sighted. Perhaps it would be easier to push for an exception.


I don't know of anything. The most up-to-date resource I know of for
tools using and implementing reST is
http://stackoverflow.com/questions/2746692/restructuredtext-tool-support


No idea. The reST parser is completely home-grown, and doesn't use any
kind of parser generator.

Be warned: reST is a two-dimensional markup language. Indentation is
significant, as well as specific amounts of relative indentation
(e.g., things that line up belong at the same level). Like the Python
language, but sometimes more exacting. The most extreme example is
tables. The table parser is implemented like a graphic edge-detecting
algorithm.

IOW, it would be a significant task to reimplement the reST parser.
You may want to look for tools that already exist in the C world, even
if you have to settle for what you may think is an inferior markup
language.

Re: C reStructuredText parser

David Goodger — 2012-05-17T00:46:06

This is just FUD. The standard is as solid as anything in software,
short of an ISO/IEEE standard. The basic syntax has been established
and has been used for over 10 years. I don't foresee any significant
incompatible changes to the syntax. There will undoubtedly be
additions, as there is in any evolving project.

Please avoid spreading FUD.

Re: C reStructuredText parser

Paul Tremblay — 2012-05-17T00:08:43

A c parser strikes me as useful. However, one problem with restructured 
text is the lack of a solid standard (no?). I believe the syntax is 
still being developed.

Paul

On 5/16/12 9:40 AM, Marvin Humphrey wrote:


------------------------------------------------------------------------------
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-Patches-3527401 ] manpage writeraddmonition's don't preserve indentation

SourceForge.net — 2012-05-16T21:12:28

Patches item #3527401, was opened at 2012-05-16 14:12
Message generated for change (Tracker Item Submitted) made by joshuagraff
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3527401&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joshua Graff (joshuagraff)
Assigned to: Nobody/Anonymous (nobody)
Summary: manpage writer addmonition's don't preserve indentation

Initial Comment:
In the manpage writer admonitions use troff's ``.IP``/``.RE`` for paragraph 
indentation. This unfortunately does not appear to preserve indentation for 
bullets and other block types (literal) that might be contained within an 
admonition.

Example:

$ cat example.rst
=====
Title
=====
  
:Version: 1.1
:Author: joe.user< at >example.com
  
  
Example
=======
  
This is an e

[ docutils-Patches-3527397 ] Add indentation toliteral blocks in manpage writer

SourceForge.net — 2012-05-16T20:42:49

Patches item #3527397, was opened at 2012-05-16 13:42
Message generated for change (Tracker Item Submitted) made by joshuagraff
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3527397&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joshua Graff (joshuagraff)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add indentation to literal blocks in manpage writer

Initial Comment:
The current manpage writer does not add or maintain any type of indentation on literal blocks. 

Example: 

$ cat example.rst
=====
Title
=====
  
:Version: 1.1
:Author: joe.user< at >example.com
  
  
Example
=======
  
Example::
  
  $ man ls

$ rst2man.py example.rst > example.man
$ man ./example.man
NAME
       Title -

EXAMPLE
       Example:

       $ man ls

AUTHOR

C reStructuredText parser

Marvin Humphrey — 2012-05-16T13:40:57

Hello,

There's a C project I'm involved with where it might make sense to use the
reStructuredText format, but the portability and dependency policies mandate
only C dependencies, so we can't use docutils.

I looked around for a reStructuredText parser implemented in C, but came up
empty.  Anybody know of one?

If not, would it be realistic to attempt a parser based on the Lemon
parser generator, which is an LALR(1) parser generator similar to yacc?  I'm
not a parsing guru, but I've had some success writing parsers with Lemon
in the past.

    http://www.hwaci.com/sw/lemon/

Cheers,

Marvin Humphrey

------------------------------------------------------------------------------
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/

Re: [Latex support in docutils] Problem with the restructuredtext reference.

Guenter Milde — 2012-05-14T14:13:45





There can be several reasons for the problems.

A detailled description of the used programs (and versions) and the
warnings/errors is welcome, as are suggestions for improvement.
(Patches will need revision/discussion before application, so instead of
preparing the perfect patch start in pieces.)

Thanks,

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-develop mailing list
Docutils-develop< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-develop

Please use "Reply All" to reply to the list.

[Latex support in docutils] Problem with therestructuredtext reference.

David Kremer — 2012-05-14T13:24:51

Hello,

I tried to compile the restructured text reference manual with 
rst2latex, and I had several warnings in doing so :

#!/bin/bash

mkdir tmp && cd tmp
wget http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.txt
rst2latex2 restructuredtext.txt rst.tex
pdflatex rst.tex

We have problems with references, and some chars are not translated 
properly. However it works rather well. But do you think it would be a 
good idea to propose a fix for perfectionnists ?

Cheers,

David

------------------------------------------------------------------------------
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-Bugs-3525847 ]test_directives/test_include.py: UnicodeEncodeError

SourceForge.net — 2012-05-11T20:59:10

Bugs item #3525847, was opened at 2012-05-11 07:18
Message generated for change (Comment added) made by milde
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3525847&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Priority: 5
Private: No
Submitted By: Jakub Wilk (jakub-wilk)
Assigned to: Nobody/Anonymous (nobody)
Summary: test_directives/test_include.py: UnicodeEncodeError

Initial Comment:
If LC_ALL=C is set to C, test_directives/test_include.py fails with UnicodeEncodeError:

$ LC_ALL=C python test/test_parsers/test_rst/test_directives/test_include.py
................E.............
======================================================================
ERROR: test/test_parsers/test_rst/test_directives/test_include.py: totest['include'][14]; test_parser (DocutilsTestSupport.ParserTestCase)
--------------

[ docutils-Bugs-3525847 ]test_directives/test_include.py: UnicodeEncodeError

SourceForge.net — 2012-05-11T14:18:23

Bugs item #3525847, was opened at 2012-05-11 07:18
Message generated for change (Tracker Item Submitted) made by jakub-wilk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3525847&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jakub Wilk (jakub-wilk)
Assigned to: Nobody/Anonymous (nobody)
Summary: test_directives/test_include.py: UnicodeEncodeError

Initial Comment:
If LC_ALL=C is set to C, test_directives/test_include.py fails with UnicodeEncodeError:

$ LC_ALL=C python test/test_parsers/test_rst/test_directives/test_include.py
................E.............
======================================================================
ERROR: test/test_parsers/test_rst/test_directives/test_include.py: totest['include'][14]; test_parser (DocutilsTest

[ docutils-Bugs-3495454 ]http://diveintopython.org/ is gone

SourceForge.net — 2012-05-03T11:50:49

Bugs item #3495454, was opened at 2012-02-28 15:39
Message generated for change (Settings changed) made by milde
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3495454&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Jakub Wilk (jakub-wilk)
Assigned to: Nobody/Anonymous (nobody)
Summary: http://diveintopython.org/ is gone 

Initial Comment:
roman.py contains the following text:

  This program is part of "Dive Into Python", a free Python tutorial for
  experienced programmers.  Visit http://diveintopython.org/ for the
  latest version.

However, http://diveintopython.org/ currently reads:

  The requested resource / is no longer available on this server and there is no forwarding address. Please remove all references to this resource.

You mi

[ docutils-Bugs-2993756 ] PIL import error

SourceForge.net — 2012-05-03T09:51:47

Bugs item #2993756, was opened at 2010-04-28 11:44
Message generated for change (Settings changed) made by milde
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2993756&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Priority: 5
Private: No
Submitted By: Jared ()
Assigned to: Nobody/Anonymous (nobody)
Summary: PIL import error

Initial Comment:
Docutils uses "import Image" to use the Python Imaging Library, which conflicts with django's "from PIL import Image" (essentially the module is imported twice and chokes. See this post http://jaredforsyth.com/blog/2010/apr/28/accessinit-hash-collision-3-both-1-and-1/ for more info).

I've attached a patch which fixes this problem.

----------------------------------------------------------------------

Date: 2012-05-03 02:51

Message:
The momentom seem

release 0.9

engelbert gruber — 2012-05-02T19:37:49

Release 0.9 (2012-05-02)

bigger changes are

General:
- reStructuredText "code" role and directive with syntax highlighting
by Pygments.
  "code" option of the "include" directive.
- Fix [ 3402314 ] allow non-ASCII whitespace, punctuation characters
and "international" quotes around inline markup.
- Fix handling of missing stylesheets.


setup.py
- Fix [ 2971827 ] and [ 3442827 ] extras/roman.py moved to
docutils/utils/roman.py


docutils/utils.py -> docutils/utils/__init__.py
- docutils.utils is now a package (providing a place for sub-modules)


docutils/writers/html4css1/__init__.py
- change default for math-output setting to MathJax


docutils/writers/latex2e/__init__.py
- Support the abbreviation and acronym standard roles.
- Record only files required to generate the LaTeX source as dependencies.
- Use \setcounter{secnumdepth}{0} instead of *-versions when
suppressing LaTeX section numbering.

please report any problems

all the best
  engelbert

[ docutils-Bugs-3519169 ] rst2pdf crashes inspanFixDim()

SourceForge.net — 2012-05-02T08:33:51

Bugs item #3519169, was opened at 2012-04-18 08:26
Message generated for change (Comment added) made by grubert
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3519169&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: James Hunt (jamesodhunt)
Assigned to: Nobody/Anonymous (nobody)
Summary: rst2pdf crashes in spanFixDim()

Initial Comment:
I have a large rst document [1] which passes through 'rst2html --strict' correctly but which fails with rst2pdf:

rst2pdf -o /tmp/upstart_cookbook.pdf /tmp/upstart_cookbook.rst
Traceback (most recent call last):
  File "/usr/bin/rst2pdf", line 9, in <module>
    load_entry_point('rst2pdf==0.16', 'console_scripts', 'rst2pdf')()
  File "/usr/lib/pymodules/python2.7/rst2pdf/createpdf.py", line 1456, in main
    co