<?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 about="http://blog.gmane.org/gmane.text.docutils.user">
    <title>gmane.text.docutils.user</title>
    <link>http://blog.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/4744"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4743"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4742"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4741"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4740"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4739"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4738"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4737"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4736"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4735"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4734"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4733"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4732"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4731"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4730"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4729"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4728"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4727"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4726"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4725"/>
      </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/4744">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4744</link>
    <description>
No math, perhaps some citations (but numerical xrefs to a numbered bibliography 
will probably suffice), certainly some diagrams and figures, and certainly 
internal xrefs.  Think of a general-purpose technical book for software 
developers where source code is not a big component.


Around 300 pages, not including front matter or index.


Not well, but long ago I used it a lot for academic papers and a dissertation. 
I'm familiar with the basics, including bibtex, and I expect to be able to learn 
more as I need to.

Scott




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Scott Meyers</dc:creator>
    <dc:date>2008-12-03T23:11:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4743">
    <title>Re: Idea: Connecting paragraphs in reStructuredText</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4743</link>
    <description>David Goodger &lt;goodger&lt; at &gt;python.org&gt; schrieb:



OK


I will do this whith the planned change to stylesheet loading.


Done (might need improvement, though).

This results in the patches below.

Günter

Index: utils.py
===================================================================
--- utils.py(Revision 5735)
+++ utils.py(Arbeitskopie)
&lt; at &gt;&lt; at &gt; -436,6 +436,10 &lt; at &gt;&lt; at &gt;
 def get_stylesheet_reference(settings, relative_to=None):
     """
     Retrieve a stylesheet reference from the settings object.
+    
+    Depracated. Use get_stylesheet_reference_list() instead to
+    enable specification of multiple stylesheets as comma separated
+    list.
     """
     if settings.stylesheet_path:
         assert not settings.stylesheet, \
&lt; at &gt;&lt; at &gt; -446,6 +450,20 &lt; at &gt;&lt; at &gt;
     else:
         return settings.stylesheet
 
+def get_stylesheet_reference_list(settings, relative_to=None):
+    """
+    Retrieve list of stylesheet references from the settings object.
+    """
+    if settings.stylesheet_path:
+        assert not settings.stylesheet, \
+               'stylesheet and stylesheet_path are mutually exclusive.'
+        if relative_to == None:
+            relative_to = settings._destination
+        return [relative_path(relative_to, sheet)
+                for sheet in settings.stylesheet_path.split(",")]
+    else:
+        return settings.stylesheet.split(",")
+
 def get_trim_footnote_ref_space(settings):
     """
     Return whether or not to trim footnote space.

Dir: /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/html4css1/

Index: __init__.py
===================================================================
--- __init__.py(Revision 5735)
+++ __init__.py(Arbeitskopie)
&lt; at &gt;&lt; at &gt; -53,25 +53,26 &lt; at &gt;&lt; at &gt;
           % default_template_path,
           ['--template'],
           {'default': default_template_path, 'metavar': '&lt;file&gt;'}),
-        ('Specify a stylesheet URL, used verbatim.  Overrides '
-          '--stylesheet-path.',
+        ('Specify comma separated list of stylesheet URLs, used verbatim. '
+          ' Overrides existing configuration and --stylesheet-path.',
           ['--stylesheet'],
           {'metavar': '&lt;URL&gt;', 'overrides': 'stylesheet_path'}),
-         ('Specify a stylesheet file, relative to the current working '
-          'directory.  The path is adjusted relative to the output HTML '
-          'file.  Overrides --stylesheet.  Default: "%s"'
-          % default_stylesheet_path,
+         ('Specify  comma separated list of stylesheet file paths, '
+          'relative to the current working directory. '
+          ' The path is adjusted relative to the output HTML file. '
+          ' Overrides existing configuration and --stylesheet. '
+          ' Default: "%s"' % default_stylesheet_path,
           ['--stylesheet-path'],
           {'metavar': '&lt;file&gt;', 'overrides': 'stylesheet',
            'default': default_stylesheet_path}),
-         ('Embed the stylesheet in the output HTML file.  The stylesheet '
-          'file must be accessible during processing (--stylesheet-path is '
+         ('Embed the stylesheet(s) in the output HTML file.  The stylesheet '
+          'files must be accessible during processing (--stylesheet-path is '
           'recommended).  This is the default.',
           ['--embed-stylesheet'],
           {'default': 1, 'action': 'store_true',
            'validator': frontend.validate_boolean}),
-         ('Link to the stylesheet in the output HTML file.  Default: '
-          'embed the stylesheet, do not link to it.',
+         ('Link to the stylesheet(s) in the output HTML file. '
+          ' Default: embed stylesheets.',
           ['--link-stylesheet'],
           {'dest': 'embed_stylesheet', 'action': 'store_false'}),
          ('Specify the initial header level.  Default is 1 for "&lt;h1&gt;".  '
&lt; at &gt;&lt; at &gt; -254,18 +255,20 &lt; at &gt;&lt; at &gt;
                                  self.head_prefix_template % (lcode, lcode)])
         self.html_prolog.append(self.doctype)
         self.head = self.meta[:]
-        stylesheet = utils.get_stylesheet_reference(settings)
-        self.stylesheet = []
-        if stylesheet:
-            if settings.embed_stylesheet:
-                stylesheet = utils.get_stylesheet_reference(
-                    settings, os.path.join(os.getcwd(), 'dummy'))
+        
+        if settings.embed_stylesheet:
+            stylelib = os.path.join(os.getcwd(), 'dummy')
+            sheets = utils.get_stylesheet_reference_list(settings, stylelib)
+            self.stylesheet = []
+            for stylesheet in sheets:
                 settings.record_dependencies.add(stylesheet)
-                stylesheet_text = open(stylesheet).read()
-                self.stylesheet = [self.embedded_stylesheet % stylesheet_text]
-            else:
-                self.stylesheet = [self.stylesheet_link
-                                   % self.encode(stylesheet)]
+                self.stylesheet.append(self.embedded_stylesheet 
+                                       % open(stylesheet).read())
+        else:
+            sheets = utils.get_stylesheet_reference_list(settings)
+            self.stylesheet = [self.stylesheet_link % self.encode(stylesheet)
+                               for stylesheet in sheets]
+            
         self.body_prefix = ['&lt;/head&gt;\n&lt;body&gt;\n']
         # document title, subtitle display
         self.body_pre_docinfo = []


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T17:00:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4742">
    <title>Re: Adding a class to hrefs (reST --&gt; HTMLconversion)</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4742</link>
    <description>
Couldn't you apply the class to the paragraph and the css rule to links 
in the paragraph? (Although that breaks down if you have a paragraph 
with several links and want to special case one.)

.. class:: special_case

`And here`_ is a special case.
 
Michael Foord


</description>
    <dc:creator>Michael Foord</dc:creator>
    <dc:date>2008-12-03T15:43:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4741">
    <title>Re: Adding a class to hrefs (reST --&gt; HTMLconversion)</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4741</link>
    <description>
No, that's not currently possible. The best you can do is to put a
class on the containing paragraph, using the "class" directive.

To make it possible, we'd either have to a) extend the hyperlink
target syntax to allow for a class option, or b) add a "target"
directive which would be more powerful. (a) is not worth the effort or
added complexity. (b) is feasible.

</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2008-12-03T15:34:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4740">
    <title>Adding a class to hrefs (reST --&gt; HTML conversion)</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4740</link>
    <description>Hi All,

I'm new to Restructured Text so please forgive me if the answer to
this is obvious:

Let's take the following HTML fragment and convert to reST.

&lt;p&gt;&lt;a href="http://webserver/link/1"&gt;Here&lt;/a&gt; is a link&lt;/p&gt;
&lt;p&gt;&lt;a href="http://webserver/link/2"
class="special_css_case_for_this"&gt;And here&lt;/a&gt; is a special case&lt;/p&gt;

reST:

`Here`_ is a link

`And here`_ is a special case


.. _Here: http://webserver/link/1
.. _And here: http://webserver/link/2

How can I include the class in the href for link/2? Is it possible?

Many thanks in advance for any tips.

SM

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Simon Mullis</dc:creator>
    <dc:date>2008-12-03T15:27:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4739">
    <title>Re: Idea: Connecting paragraphs in reStructuredText</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4739</link>
    <description>
That's debatable. Not so hard to spot if a list is returned instead of
a string; it would break instantly. But
utils.get_stylesheet_reference_list() is a fine name and a better
solution.

The real issue is that changing the behavior of an existing API
function may break 3rd-party code. Better safe than sorry.


Please fix that separately.


Perhaps not, but the existing similar cases *do* append subsequent
arguments. Better to make it explicit.

</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2008-12-03T15:21:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4738">
    <title>Re: Idea: Connecting paragraphs in reStructuredText</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4738</link>
    <description>David Goodger &lt;goodger&lt; at &gt;python.org&gt; schrieb:



Because "docutils.utils.get_stylesheet_references" could very easily
be confused with "docutils.utils.get_stylesheet_reference" producing
hard to spot bugs.




Of course not. 
An estimation is grepping in the Docutils SVN working copy:

 grep -nH -r --include='*.py' get_stylesheet_references docutils-svn

However, I know the behaviour of utils.get_stylesheet_reference before
and after the change: 

* if there is no comma in the stylesheet argument, nothing is changed.
* if there is a comma in the stylesheet argument and
  settings.stylesheet_path == TRUE, the path expansion is done for every
  part of the comma separated list and it is joined again.
  
For the latex writer, this results in fixing a non-reported bug.

But if you prefer, I can define and use
utils.get_stylesheet_reference_list().







This is not new at all::

 rst2html --link-stylesheet --stylesheet=foo --stylesheet=bar example.txt

produces

 &lt;link rel="stylesheet" href="bar" type="text/css" /&gt;




Fine.

Günter



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T15:09:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4737">
    <title>Re: rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4737</link>
    <description>David Goodger &lt;goodger&lt; at &gt;python.org&gt; schrieb:


troff comes to my mind. There is a man-page writer in the sandbox that might
be of interest:

http://docutils.sourceforge.net/sandbox/manpage-writer/

Günter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T14:51:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4736">
    <title>Re: Idea: Connecting paragraphs in reStructuredText</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4736</link>
    <description>
I still call YAGNI. It's feature bloat, not needed, and difficult to
implement correctly.

I'm not saying don't implement it, just warning you that you're asking
for trouble.


No, it would be simpler. It doesn't risk breaking any code. Do you
know every existing use of docutils.utils.get_stylesheet_reference?


It keeps the processing of option syntax in one place, docutils.frontend.


OK, please document that behavior.


No. List comprehensions were added to Python 2.0.

</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2008-12-03T14:38:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4735">
    <title>Re: rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4735</link>
    <description>
Is there a Braille formatting back-end available? Something that takes
a properly-formatted input file (text or tagged) that is NOT
paginated, and does the line wrapping, pagination, etc.? Because there
are no facilities in Docutils for doing pagination &amp; line wrapping
etc. Those tasks are left to the back-end formatter -- the browser for
HTML, TeX for LaTeX.

I recommend that you do not try to do low-level formatting (pagination
etc.), if there is anything out there that already does the job.
Instead, target an existing back-end formatter and create a Docutils
Writer that outputs a compatible format.

</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2008-12-03T14:24:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4734">
    <title>Re: Idea: Connecting paragraphs in reStructuredText</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4734</link>
    <description>David Goodger &lt;goodger&lt; at &gt;python.org&gt; schrieb:


While, You AGNI, I will need it. 

Finding out that ``html4css1.css`` stands for 
``/home/milde/Code/Python/docutils-svn/docutils/docutils/writers/html4css1/html4css1.css``
is a task I would prefer the computer to do for me.
(And I am going to need this, e.g., for the html4strict writer.)

(For you, it might be easier to change the defaults to meet your needs,
the average user does not have this possibility.)




Because this would be more complicated than returning
``",".join(sheets)`` and using ``stylesheets.split(",")`` in the 
writer.


What would we gain from this?

Is this the way to get 
  [foo, bar] 
from
  --opt=foo --opt=bar
? Then we will not need it, as a subsequent arg should replace the
first one.




The patch for get_stylesheet_reference uses a list comprehension:

+        sheets = [relative_path(relative_to, sheet)
+                  for sheet in settings.stylesheet_path.split(",")]

which is certainly not compatible with python 2.2. Should I use a "for"
loop instead?

Günter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T11:05:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4733">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4733</link>
    <description>Roberto Alsina &lt;ralsina&lt; at &gt;netmanagers.com.ar&gt; schrieb:


No. In reST source, centering is an "attribute" of an object (paragraph,
image, table, ...) as it is in a LaTeX source::

 \centering this is a centered line in LaTeX
 

there is no such thing as a class attribute in LaTeX. This is why
Docutils' latex writer will need to convert the class attribute to a
corresponding LaTeX construct (or ignore it).





Or, more general 
http://docutils.sourceforge.net/docs/user/links.html#export

Günter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T10:41:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4732">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4732</link>
    <description>David Goodger &lt;goodger&lt; at &gt;python.org&gt; schrieb:

In Docutils, a class is a "layout hint" that can be used or ignored by
the "writer", i.e. the component generating output in a specific
output format (HTML, LaTeX, troff, PDF, OO).


The important part is that a class can be ignored in HTML/CSS: if there
is no special definition for this class in the CSS stylesheet, the
element is laid out ignoring this class argument.
Therefore, the HTML writer can simply pass through all class arguments
and let the CSS stylesheet "decide" what to do with it.

In LaTeX, semantic markup is done via macros (i.e. LaTeX commands) that
require a definition: if there is no definition in the LaTeX style file,
the document using this macro will fail to compile. This is why the LaTeX
writer has to "decide" which class arguments it uses and which it
ignores.

The problem is that while you can easily add layout options to HTML via 
class arguments in the rst source and a special style-sheet, 
LaTeX/PDF layout extensions usually require a change in the LaTeX writer
(i.e. the Python program part generating the LaTeX source). 


The latex2e writer in SVN trunk can now work around this restriction and
generates code that can be styled via *optional* macro definitions in
some cases.

However, this is not generally possible with LaTeX and is currently only
implemented for custom roles.
http://docutils.sourceforge.net/docs/ref/rst/roles.html


There is one exception, the (currently undocumented) 

.. class:: borderless

/* used to remove borders from tables and images */

is supported in the default stylesheet and by the latex writer.

I can imagine a "colums" class argument for tables that is translated to
the corresponding argument to the LaTeX table environment.


Günter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T10:34:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4731">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4731</link>
    <description>Scott Meyers &lt;smeyers&lt; at &gt;aristeia.com&gt; schrieb:


Short answer: you don't. 
You can style the presentation in HTML with a CSS stylesheet, though.


I do not know of any such summary.

...

How about Math, Citations, Graphics, internal references?

What is the size of the project?

How good do you know LaTeX?

Günter



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T10:09:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4730">
    <title>Re: rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4730</link>
    <description>Leo &lt;fhaxbox66&lt; at &gt;googlemail.com&gt; schrieb:

...


expanded automatic enumeration and section numbering etc. have IMO a
wider use.

So I would encourage a plain-text writer (and maybe a braille writer
built on this for the braille-specific extensions).

Günter


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
Docutils-users mailing list
Docutils-users&lt; at &gt;lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
</description>
    <dc:creator>Guenter Milde</dc:creator>
    <dc:date>2008-12-03T08:35:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4729">
    <title>rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4729</link>
    <description>I am interested in preparing text files for embossing on paper rather than
preparing text for refreshable Braille displays the latter being procured by
API's such as at-spi (Gnome), Java Access Bridge or MSAA (Windows).

The main task of a braille writer would be to generate a plain text file
that is neatly formatted. OK, you could generate this from HTML. But this is
probably even more difficult and error-prone. - The text files sent to the
Braille printer need to be fully formatted with spaces at the beginning of
indented lines, page numbers, headers and footers, footnotes, hyphenation
and all those language-specific details such as contractions, different char
sets etc. So we would not gain much with an HTML version.  Conversely, I
could imagine that some rst extensions introduced by rst2pdf would be useful
for Braille as well.

Any thoughts on this?


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Leo</dc:creator>
    <dc:date>2008-12-02T23:07:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4728">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4728</link>
    <description>
Right. reST generates LaTeX and sets a class attribute in your cell, then 
LaTeX needs to know how to display it centered as you want.

OTOH you are not limited to LaTeX, you can generate PDF at least by three 
other paths:

1) Generate HTML and pass it via PISA
2) Generate ODF and go through OpenOffice
3) Use rst2pdf (the reportlab one, not the LaTeX one ;-)

On each of these, there may or may not be a way to do what you want.
Since I wrote most of rst2pdf I can tell you it probably can't do it, but it 
can be made to do it without much trouble if there is a request.



http://rst2pdf.googlecode.com

Best regards,

</description>
    <dc:creator>Roberto Alsina</dc:creator>
    <dc:date>2008-12-02T21:07:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4727">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4727</link>
    <description>

Good question.  For me, I know them when I see them. :-)  Others can  
give you more definitive answers.

Directives are lines in the source (reST) file that describe how the  
upcoming paragraph is to be processed.  Directives can have  
attributes.  Roles are kind of like inline directives.  Classes are  
attributes put on document nodes which can be used to guide  
formatting, but not the formatting itself.  I think it's a lot like  
HTML classes which don't do anything themselves but can be used to  
identify parts of the document which are semantically similar.


ReST doesn't really care about formatting.  There is a "title" class  
and if the desired output is HTML, CSS can be used to make text in the  
title class centered.  But that's a different stage of the pipeline.


It depends on the final product.  Again, there's a difference between  
expression and formatting.  If you want the table in an HTML document  
and want to have all cells centered, you can do this:

.. list-table::
    :class: specialTable

    * - Criterion
      - Shared File System
      - Selective Broadcasting
      - Simple Database
      - Database with Views
      - Canonical Representation
    * - Writing New Tools
      - Good
      - Fair
      - Poor
      - Poor
      - Fair .. etc.

The generated HTML will look kind of like:

&lt;table class="specialTable"&gt;
   &lt;colgroup&gt;
     &lt;col width="16%" span="1" /&gt; ...
   &lt;/colgroup&gt;
   &lt;tr&gt;&lt;th&gt;Criterion&lt;/th&gt;...&lt;/tr&gt;
   &lt;tr&gt;&lt;td&gt;Writing New Tools&lt;/td&gt;...&lt;/tr&gt;
   ...
&lt;/table&gt;

Then make sure the stylesheet you include or embed in the HTML  
processing has in it:

table.specialTable td { text-align:center; }

But if you only want specific rows, columns, or cells to have a class,  
that's not possible in reST + rst2html.  You can't get the class any  
tighter than the table itself.  But the HTML generated by rst2html is  
valid XHTML so you can process that with XSLT.  I do this sometimes  
when rst2html isn't enough.  Say you wanted the first column of this  
table centered and not the rest.  Then you could hit the generated  
html file with an XSLT template like

&lt;xsl:template match="table[&lt; at &gt;class='specialTable']/colgroup/col[1]"&gt;
   &lt;xsl:copy-of select="."/&gt;
   &lt;xsl:attribute name="align"&gt;center&lt;/xsl:attribute&gt;
&lt;/xsl:template&gt;

Then the first &lt;col&gt; element should have an align="center" attribute  
stuck on it.  Or you could use this template to instead add an HTML  
class attribute, then CSS to designate how that should be formatted.   
This kind of workflow should work for any final document format that's  
essentially an XML application, such as HTML or WML or S5...

But the story completely changes when you move to PDF processing via  
LaTeX.  I kind of hoped that the latex writer would have a mechanism  
for formatting kind of like a CSS stylesheet.  This is very much part  
of the LaTeX philosophy--use macros for semantic markup and customize  
formatting at the level of the macro definition. Günter and others are  
working on a more flexible writer, but right now this capability  
doesn't exist.

--Matthew Leingang

--
Matthew Leingang
Clinical Associate Professor of Mathematics
leingang&lt; at &gt;cims.nyu.edu





-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Matthew Leingang</dc:creator>
    <dc:date>2008-12-02T20:18:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4726">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4726</link>
    <description>David Goodger wrote: 

Okay, maybe there's a disconnect here.  HTML is not an important output format for me, PDF is.  So presumably I have to find a way to get reST to tell whatever generates the PDF -- LaTeX? -- to do its centering thing in the places where I want things centered.  reST itself has no concept of centering.  Is that correct? 


I've seen these documents.  The problem is that they are not terribly meaningful  to me at this point.  Consider this definition of "class": 


To make sense of this, I need to know what a directive, an attribute, an attribute value, and an element are.  The definition of a directive isn't too difficult to understand, but the notions of attribute, attribute value, and element are rather vague. 

It seems that docutils assumes that there is some processor that translates reST source, including display information in the form of classes (and maybe attributes and elements) embedded in the reST, into some viewable output, e.g., HTML or PDF (via LaTeX?).  Presumably what I need is an overview of how the reST-to-XYZ translator passes display information to XYZ.  For HTML, it sounds like the mechanism is CSS classes.  It also sounds like there is already a reST-to-LaTeX translator, and I'd need to understand how that translator communicates display information to LaTeX.  Is that correct?  If so, can you tell me where I'd find a description of how this is done? 

Am I correct in assuming that there is no direct reST-to-PDF translator?  If there is, where can I find out about it? 

Thanks, 

Scott 



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Scott Meyers</dc:creator>
    <dc:date>2008-12-02T20:15:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4725">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4725</link>
    <description>
In HTML terms, &lt;p class="whatever"&gt; triggers the "whatever" class of
the stylesheet you use. There is a LaTeX equivalent being worked on
(maybe complete?), and I don't know how it works (I don't do LaTeX).

The syntax and purpose of directives are described here:
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#directives

The "class" directive is described here:
http://docutils.sourceforge.net/docs/ref/rst/directives.html#class

"Writing HTML (CSS) Stylesheets for Docutils":
http://docutils.sourceforge.net/docs/howto/html-stylesheets.html


In general, there are no pre-defined classes. You have to make them
(e.g. put ".. class:: center" before something), and trigger off those
classes in the stylesheet.


If all your tables are formatted that way, all you have to do is
update your stylesheet appropriately. You don't even have to mess with
setting classes in the doc. If only some tables are formatted that
way, do this:

"""
.. class:: centered-cells

=====  =====  =====
A      Table  ...
=====  =====  =====
"""

... *and* update your stylesheet accordingly.

</description>
    <dc:creator>David Goodger</dc:creator>
    <dc:date>2008-12-02T19:15:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4724">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4724</link>
    <description>David Goodger wrote: 

Can you elaborate a bit on what a class is?  The reST docs I've been consulting all seem to assume the reader already knows what things like classes, directives, attributes, and roles are, but I haven't found a document that explains these things for newbies like me. 

Is there a class for centering things?  I have not been able to find mention of one. 

I've attached a table I took from one of my documents generated from LaTeX. Here, everything is centered both vertically and horizontally.  Can this be expressed in reST?  If so, can you sketch how? 

Thanks, 

Scott 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/</description>
    <dc:creator>Scott Meyers</dc:creator>
    <dc:date>2008-12-02T18:54:27</dc:date>
  </item>
  <textinput 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>
