Martin Blais | 1 Oct 21:35 2006
Picon

nabu blog related to python and docutils

Hello rst users,

I have setup an RSS feed with my presentation layer for my Nabu
datastore (for those not familiar with Nabu, it is a system I made to
automatically identify and extract information from text files using
rest and docutils).  For those interested, the following RSS URL will
track the Python and docutils entries from it:

http://furius.ca/blog/tag/Python/rss

(for the curious: one of the nabu extractors interprets the :Tags:
bibliographic field from the source documents.  Each tag gets a
corresponding index.  All I have to do to publish is... write a silly
little text file in reStructuredText format, and commit it to my
subversion server.  It then gets published automatically (there is a
svn hook that runs the new files through Nabu asynchyronously).  It
only looks like a blog because I support a date field and the indexes
sort by date... behind this public view lies much more content, I have
a variety of access levels, for friends, etc., the public view only
offers a small set of the documents, and not really enough to showcase
all the features of the presentation layer, but it's a start, see
http://furius.ca/nabu/ for more details, I will write a document about
Nabu's addition to reStructuredText to support detecting photos,
movies, books, contact info etc.)

cheers,

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
(Continue reading)

SourceForge.net | 7 Oct 01:59 2006
Picon
Picon

[ docutils-Bugs-1572466 ] Two failures in alltests.py

Bugs item #1572466, was opened at 2006-10-06 16:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=1572466&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
Submitted By: Chloe Lewis (hello_c)
Assigned to: Nobody/Anonymous (nobody)
Summary: Two failures in alltests.py

Initial Comment:
OS: Mac OS X 10.4.7 (still PPC)
Python 2.5 (r25:51918)
GCC 4.0.1

672 tests, 2 failures, FAIL output:

============================================
==========================
FAIL: test_parsers/test_rst/test_directives/test_contents.py: totest
['contents'][8]; test_parser (DocutilsTestSupport.ParserTestCase)
------------------------------------------------------------
----------
(Continue reading)

grubert | 8 Oct 11:49 2006
Picon
Picon

Re: [Docutils-users] latex writers

On Sat, 7 Oct 2006, Felix Wiemann wrote:

> Alan G Isaac wrote:
>
>> It would be helpful to have a
>> --suppress-image-extension
>> option in the LaTeX writers.
>
> I'm not sure if I wanna have such an option in the core.  It seems kinda
> kludgey.  Have to think about it though.

another possibility would be --image-extensions, taking a 
list of file extensions order by preferrence.

the use case

   A document with images, that should be converted to html and latex.
   the reST document has the images with path and extension for the html
   writer.

   When generating printable pdfs one might want to use high resolution
   images. Currently one has to use the ``.. raw:: latex`` and
   ``.. raw:: html``. This is not as bad as it seams as for larger
   documents ps/pdf image files might not be in the same directory as
   online png/jpg/gif files. But to make this easier for smaller projects
   one could

   a. suppress file extensions for image files in the latex writer
      and let latex find the files.
   b. change file extensions for image files in the latex writer, without
(Continue reading)

Felix Wiemann | 9 Oct 05:28 2006
Picon

Re: rst2newlatex generates \\* sequence in literal mode

Rick van Rein wrote:

> Note the \\* which is treated badly in LaTeX.  It is therefore better to
> generate \\{} instead of \\ alone.
>
> Simple replace
>
>                 text = text.replace('\n', '\mbox{}\\\\')
>
> with
>
>                 text = text.replace('\n', '\mbox{}\\\\{}')

Thank you!  And sorry for the delay.  I've checked in the change.

// Felix

--

-- 
Felix Wiemann -- http://www.ososo.de/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
SourceForge.net | 15 Oct 00:10 2006
Picon
Picon

[ docutils-Feature Requests-1577415 ] code-block directive

Feature Requests item #1577415, was opened at 2006-10-15 08:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422033&aid=1577415&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
Submitted By: Trent W. Buck (trentbuck)
Assigned to: Nobody/Anonymous (nobody)
Summary: code-block directive

Initial Comment:
Mailing lists show several variations of a code-block
directive that allowed for semantic markup to literal
code blocks.  One version appears to be in active use
within the Trac project's reST parser.

Why is the code-block directive still not present in
mainline docutils?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422033&aid=1577415&group_id=38414
(Continue reading)

Martin Blais | 15 Oct 09:10 2006
Picon

docinfo not recognized when there is a subtitle?

When there is a subtitle, the docinfo does not seem to be recognized.
Is this a bug?

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Alan G Isaac | 15 Oct 17:30 2006
Picon

Re: docinfo not recognized when there is a subtitle?

On Sun, 15 Oct 2006, Martin Blais apparently wrote: 
> When there is a subtitle, the docinfo does not seem to be 
> recognized. Is this a bug? 

I'm not seeing this problem.
(Using a recent snapshot.)

Cheers,
Alan Isaac

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
Martin Blais | 15 Oct 19:07 2006
Picon

Re: docinfo not recognized when there is a subtitle?

On 10/15/06, Alan G Isaac <aisaac <at> american.edu> wrote:
> On Sun, 15 Oct 2006, Martin Blais apparently wrote:
> > When there is a subtitle, the docinfo does not seem to be
> > recognized. Is this a bug?
>
> I'm not seeing this problem.
> (Using a recent snapshot.)

Oopsydo, my fault, here is what I was doing:

.. -*- coding: utf-8 -*-

=================================
   XXXXXXXXXXXXXXXXXXXXXXXXXX
=================================
XXXXXXXXXXXXXXXXXXXXXXXX
========================
:Id: XXXXXXXXXXXXXXXXXXXXXXXXX
:Tags: XXXX
:Disclosure: XXXXX
:Author: Martin Blais <blais <at> furius.ca>
:Date: 2006-07-11

XXXXXXXXXXX
===========

First section title happened to be at the same "level" as the subtitle.
This can be a bit fragile IMO.

-------------------------------------------------------------------------
(Continue reading)

Avishay Orpaz | 17 Oct 18:48 2006
Picon

Extracting sections of text

Hello everyone,
I'm interested in extracting section out of a document written in reStructuredText. I want to scan an existing document, find all level 1 sections and have each one edited separately, where each section is a reStructuredText by itself (copied from the source). I have already managed to scan the document and find the desired sections (using publish_doctee), but I can't figure out how to get the source of each section. Indeed the node class has a source member, but its value is always '<string>' and not the source itself.
 
Thnaks for your help,
Avishay

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
David Goodger | 17 Oct 19:27 2006

Re: Extracting sections of text

On 10/17/06, Avishay Orpaz <avishorp <at> yahoo.com> wrote:
> I'm interested in extracting section out of a document written in
> reStructuredText. I want to scan an existing document, find all level 1
> sections and have each one edited separately, where each section is a
> reStructuredText by itself (copied from the source). I have already managed
> to scan the document and find the desired sections (using publish_doctee),
> but I can't figure out how to get the source of each section. Indeed the
> node class has a source member, but its value is always '<string>' and not
> the source itself.

The "source" attribute of a node contains the *path* to the input (or
"source") text.  It does not provide the text itself. Since you're
providing the input text programmatically from a string, the
"<string>" value is correct.

The "rawsource" attribute of a node will often -- but not always --
contain the input text of the node. This attribute is for testing and
debugging purposes though, and there is no guarantee that it will
contain the data you're looking for. The "rawsource" attribute is
typically only populated for nodes directly containing text; it is not
populated for the "section" node and other containers.

You might be able to extract a section's source by noting the "line"
attributes from section nodes. Again, I can't guarantee that this will
work. The parser was not designed to do what you want it to do.

--

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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Gmane