<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.text.docutils.user">
    <title>gmane.text.docutils.user</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6714"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6713"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6712"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6711"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6710"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6709"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6708"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6707"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6706"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6705"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6704"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6703"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6702"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6701"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6700"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6699"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6698"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6697"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6696"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/6695"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6714">
    <title>Re: Extra directories for python 3</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6714</link>
    <description>&lt;pre&gt;
They should not be in the site-packages directory.


Indeed, that is a bug.

The contents of the tools subdirectory (at least the rst2*.py files)
should be installed in the appropriate bin/ directory.

The test directory should not be installed at all IMO. It isn't
installed under Python 2.x. While it may need to be converted with
2to3.py for Python 3.x, I think that should be a separate step from
package installation.

Please file a bug report for this so it isn't lost in email.

I'm not familiar enough with Python 3 migration to take this on in the
near future. An idea for whoever implements a fix: perhaps we could
include a Makefile with a "make tests" clause for this (as well as
"make install" and anything else that makes sense).

&lt;/pre&gt;</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2012-05-15T14:06:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6713">
    <title>Re: Extra directories for python 3</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6713</link>
    <description>&lt;pre&gt;

Docutils is a pure Python package, so I suppose with "compiling" you refer
to installing?




The test and tools directories are required, as also the tests and tools
require the conversion with the 2to3 script.


The test and tools directories are for "internal use" and, like in a Python
2.x installation better moved to the docutils/ directory.

A patch for the setup skript (docutils/setup.py) is very welcome.

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-users mailing list
Docutils-users&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" t&lt;/pre&gt;</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2012-05-15T06:48:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6712">
    <title>Re: Warning info of compiling svn rst.el and twofiles for rst-mode</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6712</link>
    <description>&lt;pre&gt;Hi Wei-Wei!

Last month (40 days ago) Wei-Wei Guo wrote:

rst.el is now updated in the Emacs main development tree and Emacs
developers even did some patches for this (breaking loading of rst.el
;-)-: ). In other words: I'm caring about this topic right now.


Thanks for this. I guess you sent me an earlier version on Mon, 13 Dec
2010 09:05:36 +0800. I will consider it at some point. I guess this is
an update compared to what you sent me on so I'll archive the older
mail.


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/&lt;/pre&gt;</description>
    <dc:creator>Stefan Merten</dc:creator>
    <dc:date>2012-05-14T08:39:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6711">
    <title>Extra directories for python 3</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6711</link>
    <description>&lt;pre&gt;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/

Are these directories supposed to be here?  If so, can they be safely removed or
moved into the {root}/{prefix}/{site-packages}/docutils/ directory?  These are
fairly generic and uninformative names and I fear they may conflict with other
python packages.


------------------------------------------------------------------------------
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/
&lt;/pre&gt;</description>
    <dc:creator>Todd</dc:creator>
    <dc:date>2012-05-14T12:58:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6710">
    <title>Style guide for documentation</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6710</link>
    <description>&lt;pre&gt;Hi,

I am posting this message on docutils-users, sphinx-dev and doc-sig
mailing lists:

* &amp;lt; at &amp;gt;docutils-users, it's a proposal about some "restrictive"
  reStructuredText subset;
* &amp;lt; at &amp;gt;sphinx-dev, it's about Sphinx usage, i.e. best practices;
* &amp;lt; at &amp;gt;doc-sig, I wonder if it could be a PEP for documentation of Python
  packages.


I started to write down conventions for Sphinx-based documentations at
https://github.com/benoitbryon/documentation-style-guide-sphinx

I'd like to share this work, and I also need feedback.
I guess it could be compared to PEP-8, as a "style guide", but applied
to Sphinx-based documentations.
Python code can be valid even if it doesn't follow PEP-8; but Python
code should follow PEP-8 because it's the convention (and de facto 
best
practice).

More explanations below.


Story
=====

As a developer, I started using Sphinx five years ago. I contributed 
to
documentation of public or private projects using Sphinx. I also 
worked
in several teams with different background:

* private projects with&lt;/pre&gt;</description>
    <dc:creator>Benoît Bryon</dc:creator>
    <dc:date>2012-05-13T15:22:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6709">
    <title>s5: logo on slides</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6709</link>
    <description>&lt;pre&gt;Hi all.
Is there a template to produce slides with a small logo on top left?
We changed the CSS, but we found it difficult to produce a clean result.
In general, I think this is a very general requirement: perhaps better adding it as a
default in the standard template?
Thanks a lot.
&lt;/pre&gt;</description>
    <dc:creator>Paolo Cavallini</dc:creator>
    <dc:date>2012-05-12T05:16:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6708">
    <title>Re: rst2s5</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6708</link>
    <description>&lt;pre&gt;Il 09/05/2012 20:20, David Goodger ha scritto:


Great, thanks a lot.

&lt;/pre&gt;</description>
    <dc:creator>Paolo Cavallini</dc:creator>
    <dc:date>2012-05-09T18:18:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6707">
    <title>Re: rst2s5</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6707</link>
    <description>&lt;pre&gt;
Do you see the &amp;lt;dl&amp;gt;/&amp;lt;dt&amp;gt;/&amp;lt;dd&amp;gt; tags? It's because you're missing
vertical whitespace (blank lines). Your indentation may also be wrong
(start of sub-list must align with start of content above it). Rewrite
as follows:

"""
I comandi di GRASS
--------------------

- Centinaia di comandi

  - Ognuno con numerose opzioni  &amp;lt;&amp;lt;&amp;lt; NOTE: indentation == 2 spaces EXACTLY

- r.*= comandi per i raster
- v.*= comandi per i vettori
"""

From &amp;lt;http://docutils.sourceforge.net/docs/user/rst/quickref.html#bullet-lists&amp;gt;:
"Note that a blank line is required
before the first item and after the
last, but is optional between items."

This requirement also applies to sub-lists.

Because of the definition list, your outer bullet list is no longer
"simple". See:
http://docutils.sourceforge.net/FAQ.html#how-are-lists-formatted-in-html

Moral: be more liberal with vertical whitespace, and more exacting
with horizontal whitespace.

&lt;/pre&gt;</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2012-05-09T18:20:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6706">
    <title>rst2s5</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6706</link>
    <description>&lt;pre&gt;Hi all.
I'm just starting with rst and s5, so please forgive my ignorance.
Why this slide:

I comandi di GRASS
--------------------
- Centinaia di comandi
   - Ognuno con numerose opzioni
- r.*= comandi per i raster
- v.*= comandi per i vettori

Appears as:

&amp;lt;div class="slide" id="i-comandi-di-grass"&amp;gt;
&amp;lt;h1&amp;gt;I comandi di GRASS&amp;lt;/h1&amp;gt;
&amp;lt;ul&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;dl class="first docutils"&amp;gt;

&amp;lt;dt&amp;gt;Centinaia di comandi&amp;lt;/dt&amp;gt;
&amp;lt;dd&amp;gt;&amp;lt;ul class="first last simple"&amp;gt;
&amp;lt;li&amp;gt;Ognuno con numerose opzioni&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;
&amp;lt;/dd&amp;gt;
&amp;lt;/dl&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;p class="first"&amp;gt;r.*= comandi per i raster&amp;lt;/p&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;li&amp;gt;&amp;lt;p class="first"&amp;gt;v.*= comandi per i vettori&amp;lt;/p&amp;gt;
&amp;lt;/li&amp;gt;
&amp;lt;/ul&amp;gt;
&amp;lt;/div&amp;gt;

i.e., with unnecessary &amp;lt;/p&amp;gt; ?
Does this depend from the fact that there is a sublist?
Is it possible to avoid this unnecessary spacing (without editing the html, obviously)?
Thanks.
&lt;/pre&gt;</description>
    <dc:creator>Paolo Cavallini</dc:creator>
    <dc:date>2012-05-09T18:02:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6705">
    <title>Re: how to incorporate a new role into distutils</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6705</link>
    <description>&lt;pre&gt;Thanks for your input. Nesting the nodes in an inline node is a good
idea, so far I was returning them as a list, but an inline node is a
more elegant solution. I will definitely check out the sandbox for
front-end customization.

Angel

On Fri, May 4, 2012 at 2:56 AM, Guenter Milde &amp;lt;milde&amp;lt; at &amp;gt;users.sf.net&amp;gt; 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/
&lt;/pre&gt;</description>
    <dc:creator>Angel Yanguas-Gil</dc:creator>
    <dc:date>2012-05-09T17:06:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6704">
    <title>Re: Unable to get syntax highlight with new codedirective in LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6704</link>
    <description>&lt;pre&gt;



Thanks for the report. This is fixed in the sandbox SVN now. I also put
example stylesheets in the styles repository ``sandbox/stylesheets/``.

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-users mailing list
Docutils-users&amp;lt; at &amp;gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
&lt;/pre&gt;</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2012-05-09T10:44:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6703">
    <title>Re: Unable to get syntax highlight with new codedirective in LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6703</link>
    <description>&lt;pre&gt;Thank you for your answer Günter (sorry for not answering myself, but it
seems I wasn't receiving emails from the list correctly). I tried the
script you uploaded to the sandbox, and it worked but it has a little bug:
it expects all the lines in the CSS stylesheet to have a comment:

    print "% " + l.split('*')[1]

but if it isn't the case, it just breaks. Apart from this detail I got a
nice coloured PDF. Thank you again!
------------------------------------------------------------------------------
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/&lt;/pre&gt;</description>
    <dc:creator>Juan Luis Cano Rodríguez</dc:creator>
    <dc:date>2012-05-08T19:08:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6702">
    <title>Re: Unable to get syntax highlight with new codedirective in LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6702</link>
    <description>&lt;pre&gt;



As with the HTML export, you need a stylesheet (but you may know this
already).

(Remember that for syntax highlight of a "code" role, you need to define
a custom text role based on "code". See the test input file
"standard.txt" for an example.)





Docutils does syntax highlight via text roles. This means that in all output
variants, styling is possible with rules similar to styling custom text roles.

For LaTeX, you have two options:

* Raphael 'kena' Poss contributed a CSS-&amp;gt;TeX converter pygments
  stylesheets. I jut put it on the sandbox, together with an example
  stylesheet:
  http://docutils.svn.sourceforge.net/viewvc/docutils/trunk/sandbox/code-block-directive/tools/

  Use with, e.g. ::
  
   pygmentize -S default -f html | python makesty.py &amp;gt;pygments-DUroles.sty
   
  A proper solution would be to provide a new output format for pygmentize,
  volunteers?  

* Alternatively, you can create a stylesheet "by hand". 

  For this, I recommend to use the option --syntax-highlight=long, which
  gener&lt;/pre&gt;</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2012-05-06T19:41:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6701">
    <title>Unable to get syntax highlight with new codedirective in LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6701</link>
    <description>&lt;pre&gt;Hello everyone, I just read the other day the release notes of the 0.9
version and decided to test the new code directive and role [1].

My problem is that, though I have Pygments installed and the code seems to
be well parsed, I can't get it colored when I export to LaTeX using
rst2latex.

If I export to HTML, I can then do

    pygmentize -f html -S trac &amp;gt; style.css

add the stylesheet to the generated .html file and there I have the colors.
On the other hand, I cannot figure out how to do this with LaTeX.

I stumbled upon an old document on the sandbox mentioning rst2html-pygments
and rst2latex-pygments [2], which seems to be exactly what I want, but
these scripts are not included in the main distribution.

Any help?

[1]: http://docutils.sourceforge.net/docs/ref/rst/directives.html#code
[2]:
http://docutils.sourceforge.net/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusi&lt;/pre&gt;</description>
    <dc:creator>Juan Luis Cano Rodríguez</dc:creator>
    <dc:date>2012-05-05T18:00:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6700">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6700</link>
    <description>&lt;pre&gt;wrt your directives,
i understand directives that affect the writer with inline data

i got trouble with understanding how to lay out things when the 
directive needs to output image files for later inclusion

On 05/05/2012 06:53 PM, Alli Quaknaa 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/
&lt;/pre&gt;</description>
    <dc:creator>Ronny Pfannschmidt</dc:creator>
    <dc:date>2012-05-05T17:08:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6699">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6699</link>
    <description>&lt;pre&gt;Hi,

On Sat, May 5, 2012 at 6:03 PM, Ronny Pfannschmidt
&amp;lt;Ronny.Pfannschmidt&amp;lt; at &amp;gt;gmx.de&amp;gt; wrote:
Yeah, that happened to me all the time. Stuck for too long a time
because of an oversight like that.

As I said earlier, for my purposes I defined some amsthm (mathematics
in latex) directives; see
http://koutecky.name/thesis/rst/math_latex.py &amp;amp;
http://koutecky.name/thesis/rst/rst2xetex-amsthm . It doesn't do much,
but could serve as a template for doing more complicated stuff.

al-Quaknaa





------------------------------------------------------------------------------
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/
&lt;/pre&gt;</description>
    <dc:creator>Alli Quaknaa</dc:creator>
    <dc:date>2012-05-05T16:53:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6698">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6698</link>
    <description>&lt;pre&gt;I just figured what went wrong in part,
a different file had inconsistent section underlines,
somehow it all came out the same


i still get the chapter* calls tho,

im currently calling::

  rst2latex main.rst out/main.tex \
    --template tex/template.tex \
    --documentclass book


btw, i had to remove the main title of the file,
since it got added as chapter* as well


i would like to get chapter/section numbers on the chapter/section 
titles (wich i currently dont)


On 05/05/2012 04:55 PM, Alli Quaknaa 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/
&lt;/pre&gt;</description>
    <dc:creator>Ronny Pfannschmidt</dc:creator>
    <dc:date>2012-05-05T15:04:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6697">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6697</link>
    <description>&lt;pre&gt;actually i get section numbers now, i just completely deleted my output 
directory,

i suppose i had some lingeringing .toc file around that didn't get updated


so now the basics work like i want,
only extra directives for the diagrams need to be created/added
(see the other topic i started)


thanks for the hints

On 05/05/2012 05:22 PM, Alli Quaknaa 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/
&lt;/pre&gt;</description>
    <dc:creator>Ronny Pfannschmidt</dc:creator>
    <dc:date>2012-05-05T16:03:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6696">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6696</link>
    <description>&lt;pre&gt;What arguments do you call rst2latex with? My default settings give me
chapter/section/subsection etc.

Can you try rst2html? It just ignores whatever custom TeX you have
there so that shouldn't be a problem.

al-Quaknaa

On Sat, May 5, 2012 at 4:26 PM, Ronny Pfannschmidt
&amp;lt;Ronny.Pfannschmidt&amp;lt; at &amp;gt;gmx.de&amp;gt; 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/
&lt;/pre&gt;</description>
    <dc:creator>Alli Quaknaa</dc:creator>
    <dc:date>2012-05-05T14:55:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6695">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6695</link>
    <description>&lt;pre&gt;We'd probably also need to see tex/title.tex, ./content/einleitung.rst
and ./content/grobkonzept.rst as there are really no sections in this
document.

I don't know how new sectnum is but it was definitely there last
summer when I was working on my thesis (and it works fine for me).

al-Quaknaa

------------------------------------------------------------------------------
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/
&lt;/pre&gt;</description>
    <dc:creator>Alli Quaknaa</dc:creator>
    <dc:date>2012-05-05T15:22:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/6694">
    <title>Re: how to use latex section levels</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/6694</link>
    <description>&lt;pre&gt;currently the content is


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

.. raw:: latex
   :file: tex/title.tex

.. sectnum::
   :depth: 3

.. contents::

.. include:: ./content/einleitung.rst
.. include:: ./content/grobkonzept.rst

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

originally it also had a title with = as underline
the sectnum directive is new, i found that a while after writing my mail

however section Numbers aren't added in the table of contents



On 05/05/2012 05:11 PM, Alli Quaknaa 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/
&lt;/pre&gt;</description>
    <dc:creator>Ronny Pfannschmidt</dc:creator>
    <dc:date>2012-05-05T15:17:03</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.docutils.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.docutils.user</link>
  </textinput>
</rdf:RDF>

