headers
John Plumridge | 4 Jan 2011 17:23
Picon

Re: html writer link-stylesheet can't be set in docutils.conf

Lea Wiemann <lewiemann <at> gmail.com> writes:

> 
> Berthold Höllmann wrote:
> 
> >   [html4css1 writer]
> > 
> >   link_stylesheet: yes
> >   stylesheet: http://www-intern.germanlloyd.de/pool/ho/software/style.css
> > 
> > in my docutils.conf lead to an error when calling rst2html.py::
> 
> The correct setting is "embed_stylesheet: no"; see

I find I cannot get a stylesheet link to generate 
using the ~/.docutils.conf, wher4eas I can on the 
command line. Am I doing domething wrong? 
E.g., in my docutils.conf:

[html4css1 writer]

embed_stylesheet: no
 link_stylesheet: yes
 stylesheet: ./style.css

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
(Continue reading)

Permalink | Reply | 1 comment |
headers
Guenter Milde | 6 Jan 2011 14:22
Picon

Re: html writer link-stylesheet can't be set in docutils.conf

On 2011-01-04, John Plumridge wrote:

> I find I cannot get a stylesheet link to generate 
> using the ~/.docutils.conf, wher4eas I can on the 
> command line. Am I doing domething wrong? 
> E.g., in my docutils.conf:

> [html4css1 writer]

> embed_stylesheet: no
>  link_stylesheet: yes
>  stylesheet: ./style.css

There are continuation lines in your example.
Try with

embed_stylesheet: no
stylesheet: ./style.css

Günter

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Docutils-users mailing list
Docutils-users <at> lists.sourceforge.net
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alan G Isaac | 8 Jan 2011 21:09
Picon

rst2beamer bug: handling System Messages

I was missing one of my references.
rst2beamer put the system message in only part of a frame (no end of frame).
See below.

Probably rst2beamer should use a frame *rather than* a section.

Alan Isaac

\begin{frame}

%___________________________________________________________________________

\section*{\color{red}Docutils System Messages}

\DUadmonition[system-message]{
\DUtitle[system-message]{system-message}
\raisebox{1em}{\hypertarget{id10}{}}

{\color{red}ERROR/3} in \texttt{models.rst}, line~924

\hyperlink{id11}{
Unknown target name: ``epstein-2006-gensocsci''.
}}

\end{document}

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dave Walker | 9 Jan 2011 18:19
Gravatar

Re: error in the documentation of the container directive in rst2odt

Amit Ramon <amit.ramon <at> gmail.com> writes:

> 
> Hello list,
> 
> The official documentation for rst2odt says that the directive should be 
> used as follows:
> 
> .. container:: rststyle-heading2
> 
> However, in practice the rst2odt prefixes the name of the style in the 
generated
> odt file with "rststyle-", as I can see in the content.xml part of the odt 
file,
> so the actual style name becomes, in the above example, "rststyle-rststyle-
heading2".
> There is no mentioning of this in the documentation, so either the 
documentation
> is incorrect or it is a bug in the tool.
> 
> I believe that the documentation is wrong, so the directive should be used as 
follows:
> 
> .. container:: <style>
> 
> with the understanding that the corresponding style in the odt file should be
> rststyle-<style>.
> 
> What do you think?
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Tremblay | 9 Jan 2011 18:26
Picon

configuration file for PDF

Hi group,

Is there any interest in developing a uniform set of criteria for PDF 
output?

I am working on a series of series of XSLFO stylesheets to convert RST 
to XSLFO, which then can be converted to PDF. When I am finished, a user 
can generate PDF this way:

rst2xml.py my_file | docutils2fo.py | fop -fo - -pdf out.pdf

As always, users will want to customize some of the formatting of the 
PDF file. Such a customization could occur in the .docutils.conf file, 
which might look like this;

# EXAMPLE of hypothetical docutils.conf file
[PDF]
#
default-paragraph.text-align = right
default-paragraph.font-family = Times
default-paragraph.font-size = 12pt
default-paragraph.space-before = 12pt
default-paragraph.space-after = 12pt

# for block quote
block-quote.start-indent = 6pt
block-quote.end-indent = 6pt

# general
suppress-first-page-header = True
(Continue reading)

Permalink | Reply | 8 comments |
headers
Roberto Alsina | 9 Jan 2011 18:33
Picon
Gravatar

Re: configuration file for PDF

On 1/9/2011 2:26 PM, Paul Tremblay wrote:
> By using such a file, a user does not have to know anything about XSLFO
> in order to achieve a great deal of customization. The customization
> file could also serve as the way to control output of not just of the
> XSL, but of LaTex as well. Hence, users would not have to know the code
> of LaTex or XSLFO in order to control a great many of the aspects of the
> PDF document. Last, a uniform set of criteria helps developers write the
> most useful goals to meet users needs, rather than having to guess at
> how to achieve output.
>
> I would like to hear what users think of this plan. If it seems a useful
> idea, I would like to develop it with other input and make it a standard.
But HTML already has a mechanism for this, LaTeX already has a mechanism 
for this, and rst2pdf has a mechanism for this, etc. So this would be 
just specific to your PDF generator, therefore why would it need to be 
part of docutils?

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl
Permalink | Reply | 7 comments |
headers
Paul Tremblay | 9 Jan 2011 20:11
Picon

Re: configuration file for PDF

On 1/9/11 12:33 PM, Roberto Alsina wrote:
> On 1/9/2011 2:26 PM, Paul Tremblay wrote:
>> By using such a file, a user does not have to know anything about XSLFO
>> in order to achieve a great deal of customization. The customization
>> file could also serve as the way to control output of not just of the
>> XSL, but of LaTex as well. Hence, users would not have to know the code
>> of LaTex or XSLFO in order to control a great many of the aspects of the
>> PDF document. Last, a uniform set of criteria helps developers write the
>> most useful goals to meet users needs, rather than having to guess at
>> how to achieve output.
>>
>> I would like to hear what users think of this plan. If it seems a useful
>> idea, I would like to develop it with other input and make it a standard.
> But HTML already has a mechanism for this, LaTeX already has a mechanism
> for this, and rst2pdf has a mechanism for this, etc. So this would be
> just specific to your PDF generator, therefore why would it need to be
> part of docutils?
>
>
>
Can you point me to the mechanism for HTML and LaTeX? I have looked 
already already, but perhaps not in the right spot.

To be clear, I don't want any new python code to be written. Instead, I 
want a standard for one section of the configuration file, if 
appropriate. Conversely, If it turns out that each generator should have 
its own section in the configuration file, then I could simply make my 
own section (or completely new file):

#FO section
(Continue reading)

Permalink | Reply | 6 comments |
headers
Roberto Alsina | 9 Jan 2011 20:25
Picon
Gravatar

Re: configuration file for PDF

On 1/9/2011 4:11 PM, Paul Tremblay wrote:
> On 1/9/11 12:33 PM, Roberto Alsina wrote:
>> On 1/9/2011 2:26 PM, Paul Tremblay wrote:
>>> By using such a file, a user does not have to know anything about XSLFO
>>> in order to achieve a great deal of customization. The customization
>>> file could also serve as the way to control output of not just of the
>>> XSL, but of LaTex as well. Hence, users would not have to know the code
>>> of LaTex or XSLFO in order to control a great many of the aspects of the
>>> PDF document. Last, a uniform set of criteria helps developers write the
>>> most useful goals to meet users needs, rather than having to guess at
>>> how to achieve output.
>>>
>>> I would like to hear what users think of this plan. If it seems a useful
>>> idea, I would like to develop it with other input and make it a standard.
>> But HTML already has a mechanism for this, LaTeX already has a mechanism
>> for this, and rst2pdf has a mechanism for this, etc. So this would be
>> just specific to your PDF generator, therefore why would it need to be
>> part of docutils?
>>
>>
>>
> Can you point me to the mechanism for HTML and LaTeX? I have looked
> already already, but perhaps not in the right spot.
Their stylesheets, of course. In particular, the default stylesheet for 
each writer.
As an example, here's rst2pdf's:

http://code.google.com/p/rst2pdf/source/browse/trunk/rst2pdf/styles/styles.style?r=2417

> To be clear, I don't want any new python code to be written. Instead, I
(Continue reading)

Permalink | Reply | 5 comments |
headers
Paul Tremblay | 10 Jan 2011 03:31
Picon

Re: configuration file for PDF

On 1/9/11 2:25 PM, Roberto Alsina wrote:
> On 1/9/2011 4:11 PM, Paul Tremblay wrote:
>> On 1/9/11 12:33 PM, Roberto Alsina wrote:
>>> On 1/9/2011 2:26 PM, Paul Tremblay wrote:
>>>> By using such a file, a user does not have to know anything about XSLFO
>>>> in order to achieve a great deal of customization. The customization
>>>> file could also serve as the way to control output of not just of the
>>>> XSL, but of LaTex as well. Hence, users would not have to know the code
>>>> of LaTex or XSLFO in order to control a great many of the aspects of the
>>>> PDF document. Last, a uniform set of criteria helps developers write the
>>>> most useful goals to meet users needs, rather than having to guess at
>>>> how to achieve output.
>>>>
>>>> I would like to hear what users think of this plan. If it seems a useful
>>>> idea, I would like to develop it with other input and make it a standard.
>>> But HTML already has a mechanism for this, LaTeX already has a mechanism
>>> for this, and rst2pdf has a mechanism for this, etc. So this would be
>>> just specific to your PDF generator, therefore why would it need to be
>>> part of docutils?
>>>
>>>
>>>
>> Can you point me to the mechanism for HTML and LaTeX? I have looked
>> already already, but perhaps not in the right spot.
> Their stylesheets, of course. In particular, the default stylesheet for
> each writer.
> As an example, here's rst2pdf's:
>
> http://code.google.com/p/rst2pdf/source/browse/trunk/rst2pdf/styles/styles.style?r=2417
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Roberto Alsina | 10 Jan 2011 03:42
Picon
Gravatar

Re: configuration file for PDF

On 1/9/2011 11:31 PM, Paul Tremblay wrote:
> No, you are not missing anything. I wasn't clear in my message. I 
> should have said that a developer would not have to add much more 
> code. For example, the rst2pdf indicates space before a block with:
>
> spaceBefore: 4
>
>
> FO uses
>
> space-before = 12pt
> Assume that the standard became
>
> SpaceBef = 12pt
>
>
> rst2pdf merely has to write enough code to recognize the change at the 
> very beginning, before any of the formatting takes place. I would have 
> to do the same. Making such a change might be as easy as having a 
> dictionary perform the work.

 From what kind of file does FO take that? A INI file? If yes, then if 
you are using the section for [PDF] or [FO] you probably don't have 
enough structure to describe the document style. For example, you 
probably want to set the space-before for block quotes different than 
for normal paragraphs.

If you do that by using a space-before and a blockquote-space-before 
then I expect an explicit stylesheet to be roughly 20 times longer than 
rst2pdf's, since on a PDF you don't have defaults as in HTML's CSS,
(Continue reading)

Permalink | Reply | 3 comments |

Gmane