<?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://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/4749"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4748"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4747"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4746"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.text.docutils.user/4745"/>
        <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: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/4749">
    <title>Re: rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4749</link>
    <description>
I don't know about Braille embossing, but for general use pagination can
be achieved using the UNIX utilities like

    pr - convert text files for printing
    nl - number lines of files
    fmt - simple optimal text formatter


-------------------------------------------------------------------------
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>Trent W. Buck</dc:creator>
    <dc:date>2008-12-04T05:08:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4748">
    <title>Re: rst2braille - HTML- or native writer?</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4748</link>
    <description>

So essentially what you're talking about is a "plain text" writer
(rst2txt) that produces better results than using rst2html and a
tty browser (e.g. lynx or w3m -dump).

I'm interested in this: I've noticed issues in the past like *emphasis*
being lost or :foo: definition lists looking stupid (because TH gets
centered).

I also believe that Festival (a text-to-speech engine) can handle a
special XML input format as well as plain text files, and that allows
you to do things like encoding *emphasis* as a change in pitch.  I don't
know how much speech metadata can be inferred from the semantic layout,
but a writer for that might be interesting.


Are you talking about new, embosser/braille-specific foo:`bar`
attributes, or to use existing markup -- for example, maybe something
interesting could be done with the ..image:: declaration and bump
mapping.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build th</description>
    <dc:creator>Trent W. Buck</dc:creator>
    <dc:date>2008-12-04T05:05:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4747">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4747</link>
    <description>
What is PISA?  Is it related to Prince XML?
(http://en.wikipedia.org/wiki/Prince_XML)

Currently I use html2ps (and ps2pdf) to generate PDFs of arbitrary
webpages, such as Wikipedia and HTML generated from Docbook (where the
original Docbook sources aren't published).


-------------------------------------------------------------------------
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>Trent W. Buck</dc:creator>
    <dc:date>2008-12-04T04:52:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4746">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4746</link>
    <description>
As it happens, I generally create my own camera-ready copy, so things like that 
are important to me.  Details of presentation are not terribly important to most 
book authors, however, for the reason you mentioned.

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-04T04:48:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.text.docutils.user/4745">
    <title>Re: Newbie Questions: reST vs LaTeX</title>
    <link>http://permalink.gmane.org/gmane.text.docutils.user/4745</link>
    <description>
I imagine that as Scott is writing a book, an editor is responsible for
formatting.  That being the case, issues like not having an analogue for
\appendix in reST wouldn't be a big issue, because they'd be fixed after
Scott hands over the manuscript.


-------------------------------------------------------------------------
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>Trent W. Buck</dc:creator>
    <dc:date>2008-12-04T04:44:09</dc:date>
  </item>
  <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.stylesh</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" </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 us</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/d</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 ch</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
Buil</description>
    <dc:creator>Leo</dc:creator>
    <dc:date>2008-12-02T23:07:44</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>
