docutils-users — General discussions, questions, help requests.

Re: [Docutils-users] Define Latex packages in reST file

[engelbert g. <eng...@gm...>]

hmm maybe latex_preamble or stylesheet

On 1 September 2015 at 09:43, Masood Azizi <ma...@gt...> wrote:
> Hello,
>
> We used Docutils to produce reST document, and then make a TeX file via
> rst2latex.
>
> In the rst file, we have added a lot of LaTeX code like:
>
> .. raw:: latex
>
>     ~\\
>     \rule{\textwidth}{1pt}
>     ~\\
>
> But I do not know where to add packages like \usepackage{tabulary}.
>
> If I add it in the rst file like I've shown above, even in the very
> beginning, this \usepackage line is automatically added after
> \begin{document} in the tex output file. This obviously generates an error.
>
> Any idea where can I add \usepackage commands in reST?
>
> Thanks
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Docutils-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/docutils-users
>
> Please use "Reply All" to reply to the list.
>

[Docutils-users] abuse of quote environment by LaTeX writers

[Alan G I. <ala...@gm...>]

I just ran into this bug again:
http://sourceforge.net/p/docutils/bugs/209/

Why it matters:
I have a presentation where I need to separately style quotes
and literal blocks.

Again I appeal that a decision be reached about how
to this long-standing bug will be fixed.

Alan Isaac

[Docutils-users] Define Latex packages in reST file

[Masood A. <ma...@gt...>]

Hello,

We used |Docutils| to produce reST document, and then make a TeX file
via |rst2latex|.

In the |rst| file, we have added a lot of LaTeX code like:

|.. raw:: latex ~\\ \rule{\textwidth}{1pt} ~\\ |

But I do not know where to add packages like |\usepackage{tabulary}|.

If I add it in the |rst| file like I've shown above, even in the very
beginning, this |\usepackage| line is automatically added
after |\begin{document}| in the tex output file. This obviously
generates an error.

Any idea where can I add |\usepackage| commands in reST?

Thanks

Re: [Docutils-users] install error - xhtml11 does not exist

[Lewis <lew...@op...>]

Guenter Milde <milde <at> users.sf.net> writes:

> 
> On 2015-08-31, engelbert gruber wrote:
> > a new snapshot is up


Hi,

New snapshot installs correctly.

Thanks
Lewis

Re: [Docutils-users] install error - xhtml11 does not exist

[Guenter M. <mi...@us...>]

On 2015-08-31, engelbert gruber wrote:
> a new snapshot is up

Thank you.

> and the link to sourceforge code snapshot is clickable
> (although this conains also sandbox, prest and web)

Maybe we can point potential users to
http://sourceforge.net/p/docutils/code/HEAD/tree/trunk/docutils/
where clicking on the [Download Snapshot] button will (hopefully) be limited
to the trunk without sandbox, prest, and web.
(the generated download is 
http://sourceforge.net/code-snapshots/svn/d/do/docutils/code/docutils-code-7914-trunk.zip
)

Günter

Re: [Docutils-users] install error - xhtml11 does not exist

[engelbert g. <eng...@gm...>]

a new snapshot is up
and the link to sourceforge code snapshot is clickable
(although this conains also sandbox, prest and web)



On 31 August 2015 at 15:23, Lewis <lew...@op...> wrote:
> Guenter Milde <milde <at> users.sf.net> writes:
>
>>
>> On 2015-08-30, Lewis wrote:
>> > Hi,
>> > I just downloaded and tried to install the latest package date
> (30/8/15)
>> > but I get this install error:
>> ...
>> > error: package directory 'docutils\writers\xhtml11' does not exist
>>
>> Does it work now?
>>
>> Thanks for reporting,
>>
>> Günter
>>
>> ----------------------------------------------------------------------
> --------
>> _______________________________________________
>> Docutils-users mailing list
>> Docutils-users <at> lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/docutils-users
>>
>> Please use "Reply All" to reply to the list.
>>
>
> Guenter,
>
> I tried the snapshot again but it appears to be the same file as before.
> Let me know if it's updated.
>
> Thanks
> Lewis
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Docutils-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/docutils-users
>
> Please use "Reply All" to reply to the list.

Re: [Docutils-users] install error - xhtml11 does not exist

[Lewis <lew...@op...>]

Guenter Milde <milde <at> users.sf.net> writes:

> 
> On 2015-08-30, Lewis wrote:
> > Hi,
> > I just downloaded and tried to install the latest package date 
(30/8/15) 
> > but I get this install error:
> ...
> > error: package directory 'docutils\writers\xhtml11' does not exist
> 
> Does it work now?
> 
> Thanks for reporting,
> 
> Günter
> 
> ----------------------------------------------------------------------
--------
> _______________________________________________
> Docutils-users mailing list
> Docutils-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/docutils-users
> 
> Please use "Reply All" to reply to the list.
> 

Guenter,

I tried the snapshot again but it appears to be the same file as before.
Let me know if it's updated.

Thanks
Lewis

Re: [Docutils-users] install error - xhtml11 does not exist

[Guenter M. <mi...@us...>]

On 2015-08-30, Lewis wrote:
> Hi,
> I just downloaded and tried to install the latest package date (30/8/15) 
> but I get this install error:
...
> error: package directory 'docutils\writers\xhtml11' does not exist

Does it work now?

Thanks for reporting,

Günter

[Docutils-users] install error - xhtml11 does not exist

[Lewis <lew...@op...>]

Hi,
I just downloaded and tried to install the latest package date (30/8/15) 
but I get this install error:

N:\downloads\docutils>c:\Python34\python setup.py install
running install
running build
running build_py
creating build
creating build\lib
creating build\lib\docutils
copying docutils\core.py -> build\lib\docutils
copying docutils\examples.py -> build\lib\docutils
copying docutils\frontend.py -> build\lib\docutils
copying docutils\io.py -> build\lib\docutils
copying docutils\nodes.py -> build\lib\docutils
copying docutils\statemachine.py -> build\lib\docutils
copying docutils\_compat.py -> build\lib\docutils
copying docutils\__init__.py -> build\lib\docutils
creating build\lib\docutils\languages
copying docutils\languages\af.py -> build\lib\docutils\languages
copying docutils\languages\ca.py -> build\lib\docutils\languages
copying docutils\languages\cs.py -> build\lib\docutils\languages
copying docutils\languages\da.py -> build\lib\docutils\languages
copying docutils\languages\de.py -> build\lib\docutils\languages
copying docutils\languages\en.py -> build\lib\docutils\languages
copying docutils\languages\eo.py -> build\lib\docutils\languages
copying docutils\languages\es.py -> build\lib\docutils\languages
copying docutils\languages\fi.py -> build\lib\docutils\languages
copying docutils\languages\fr.py -> build\lib\docutils\languages
copying docutils\languages\gl.py -> build\lib\docutils\languages
copying docutils\languages\he.py -> build\lib\docutils\languages
copying docutils\languages\it.py -> build\lib\docutils\languages
copying docutils\languages\ja.py -> build\lib\docutils\languages
copying docutils\languages\lt.py -> build\lib\docutils\languages
copying docutils\languages\nl.py -> build\lib\docutils\languages
copying docutils\languages\pl.py -> build\lib\docutils\languages
copying docutils\languages\pt_br.py -> build\lib\docutils\languages
copying docutils\languages\ru.py -> build\lib\docutils\languages
copying docutils\languages\sk.py -> build\lib\docutils\languages
copying docutils\languages\sv.py -> build\lib\docutils\languages
copying docutils\languages\zh_cn.py -> build\lib\docutils\languages
copying docutils\languages\zh_tw.py -> build\lib\docutils\languages
copying docutils\languages\__init__.py -> build\lib\docutils\languages
creating build\lib\docutils\parsers
copying docutils\parsers\null.py -> build\lib\docutils\parsers
copying docutils\parsers\__init__.py -> build\lib\docutils\parsers
creating build\lib\docutils\parsers\rst
copying docutils\parsers\rst\roles.py -> build\lib\docutils\parsers\rst
copying docutils\parsers\rst\states.py -> build\lib\docutils\parsers\rst
copying docutils\parsers\rst\tableparser.py -> 
build\lib\docutils\parsers\rst
copying docutils\parsers\rst\__init__.py -> 
build\lib\docutils\parsers\rst
creating build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\admonitions.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\body.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\html.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\images.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\misc.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\parts.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\references.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\tables.py -> 
build\lib\docutils\parsers\rst\directives
copying docutils\parsers\rst\directives\__init__.py -> 
build\lib\docutils\parsers\rst\directives
creating build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\af.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\ca.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\cs.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\da.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\de.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\en.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\eo.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\es.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\fi.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\fr.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\gl.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\he.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\it.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\ja.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\lt.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\nl.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\pl.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\pt_br.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\ru.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\sk.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\sv.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\zh_cn.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\zh_tw.py -> 
build\lib\docutils\parsers\rst\languages
copying docutils\parsers\rst\languages\__init__.py -> 
build\lib\docutils\parsers\rst\languages
creating build\lib\docutils\readers
copying docutils\readers\doctree.py -> build\lib\docutils\readers
copying docutils\readers\pep.py -> build\lib\docutils\readers
copying docutils\readers\standalone.py -> build\lib\docutils\readers
copying docutils\readers\__init__.py -> build\lib\docutils\readers
creating build\lib\docutils\transforms
copying docutils\transforms\components.py -> 
build\lib\docutils\transforms
copying docutils\transforms\frontmatter.py -> 
build\lib\docutils\transforms
copying docutils\transforms\misc.py -> build\lib\docutils\transforms
copying docutils\transforms\parts.py -> build\lib\docutils\transforms
copying docutils\transforms\peps.py -> build\lib\docutils\transforms
copying docutils\transforms\references.py -> 
build\lib\docutils\transforms
copying docutils\transforms\universal.py -> 
build\lib\docutils\transforms
copying docutils\transforms\writer_aux.py -> 
build\lib\docutils\transforms
copying docutils\transforms\__init__.py -> build\lib\docutils\transforms
creating build\lib\docutils\utils
copying docutils\utils\code_analyzer.py -> build\lib\docutils\utils
copying docutils\utils\error_reporting.py -> build\lib\docutils\utils
copying docutils\utils\punctuation_chars.py -> build\lib\docutils\utils
copying docutils\utils\roman.py -> build\lib\docutils\utils
copying docutils\utils\smartquotes.py -> build\lib\docutils\utils
copying docutils\utils\urischemes.py -> build\lib\docutils\utils
copying docutils\utils\__init__.py -> build\lib\docutils\utils
creating build\lib\docutils\utils\math
copying docutils\utils\math\latex2mathml.py -> 
build\lib\docutils\utils\math
copying docutils\utils\math\math2html.py -> 
build\lib\docutils\utils\math
copying docutils\utils\math\tex2mathml_extern.py -> 
build\lib\docutils\utils\math
copying docutils\utils\math\tex2unichar.py -> 
build\lib\docutils\utils\math
copying docutils\utils\math\unichar2tex.py -> 
build\lib\docutils\utils\math
copying docutils\utils\math\__init__.py -> build\lib\docutils\utils\math
creating build\lib\docutils\writers
copying docutils\writers\docutils_xml.py -> build\lib\docutils\writers
copying docutils\writers\manpage.py -> build\lib\docutils\writers
copying docutils\writers\null.py -> build\lib\docutils\writers
copying docutils\writers\pseudoxml.py -> build\lib\docutils\writers
copying docutils\writers\__init__.py -> build\lib\docutils\writers
creating build\lib\docutils\writers\html4css1
copying docutils\writers\html4css1\__init__.py -> 
build\lib\docutils\writers\html4css1
creating build\lib\docutils\writers\html_plain
copying docutils\writers\html_plain\__init__.py -> 
build\lib\docutils\writers\html_plain
error: package directory 'docutils\writers\xhtml11' does not exist

Regards
Lewis

Re: [Docutils-users] space in front of footnotes?

[Guenter M. <mi...@us...>]

On 2015-08-18, Gour wrote:
> Guenter Milde <mi...@us...> writes:

>> Use the `Config File Syntax`__ in the config file?

> Ahh, thank you. I did mis it. :-(

>>   [html4css1 writer]
>>   footnote-references: superscript

BTW, it is also possible to use the "=" like ::

  [writers]
  footnote-references=superscript

However, quoting the value leads to errors.

>> and using the html4css writer (rst2html.py), it works here.

> Here I get superscript in the running text, but the footnote reference
> is still in brackets, iow.

> [1]	this text belongs to the footnote..

> Is it normal?

It is the "state of the art". Currently, only the reference is set as
superscript.


OTOH, leading style guides say that the label should match in footnote
reference and footnote itself:

  example [1] text
  
  ----  
  [1] example note

or
  example² text
  
  ----
  ² example note
  
For superscript labels, there is also the recommendation to set the label in
normal size and position before the footnote:

  example³ text
  
  ----
  3 example note
  

I would like to implement this in the new "html_plain" writer.

Question for the developers: should this be "hard-coded" or as a class value
for styling with CSS?

hard-coded:  put [ and ] into the text

   +1 safe, works also without CSS

CSS-rules: use ``:before:`` and ``:after:`` pseudo-classes for [ and ]

   +1 customizable (can be changed by local style-sheet)
   
The implementation via CSS rules would also allow to open up the set of
allowed values (currently "brackets" or "superscript"): any value could be
used (and added as class argument to the label), for "brackets" and
"superscript" we would provide default rules in the "required" style-sheet
``minimal.css``.

Günter

Re: [Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

On 2015-08-18, 11:21 GMT, Guenter Milde wrote:
> With ::
>
>   [html4css1 writer]
>   footnote-references: superscript
>
> and using the html4css writer (rst2html.py), it works here.

>From the same config documentation:

    "name=value" is also accepted. 

What’s the problem with the standard win.ini convention?  
I thought that ConfigParser.ConfigParser should work with it 
quite well?

Best,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
A GOOD name is rather to be chosen than great riches.
   -- Proverbs 22:1

Re: [Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

On 2015-08-18, 11:14 GMT, Gour wrote:
> Matěj Cepl <mc...@ce...> writes:
>
>> It works perfectly well for HTML and LaTeX, but I think I would 
>> prefer ODT not to have space in front of the footnote label.
>
> What did you do for HTML, iow. how to use it?

Put the source somewhere on the net. This::

    rst2html --footnote-reference=superscript \
        how_church_does_not_die_EN.rst >how_church_does_not_die_EN.html

works for me just fine. (source file on 
https://gitlab.com/mcepl/madr/blob/master/jak_cirkev_neumira_EN.rst)

Best,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
A day without sunshine is like night.

Re: [Docutils-users] space in front of footnotes?

[Gour <go...@at...>]

Guenter Milde <mi...@us...> writes:

> Use the `Config File Syntax`__ in the config file?

Ahh, thank you. I did mis it. :-(

>   [html4css1 writer]
>   footnote-references: superscript
>
> and using the html4css writer (rst2html.py), it works here.

Here I get superscript in the running text, but the footnote reference
is still in brackets, iow.

[1]	this text belongs to the footnote..

Is it normal?

> It may require one additional confirmation step (telling Gmane that
> posting is OK).

Most of the lists I follow is via Gmane, but, somehow, I haven’t receive
its authorization message for this list.

> I don't recall the actual procedure but I use my news-reader via Gmane
> for reading and posting both docutils-user and docutils-devel.

OK. Thank you for confirmation, although for now I have to post
directly. :-(


Sincerely,
Gour

-- 
While contemplating the objects of the senses, a person 
develops attachment for them, and from such attachment lust 
develops, and from lust anger arises.

Re: [Docutils-users] space in front of footnotes?

[Guenter M. <mi...@us...>]

Dear Matěj,

On 2015-08-17, Matěj Cepl wrote:

> I cannot find on 
> http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#footnotes 
> concise explanation about the relationship between whitespace 
> and footnotes.

The problem with whitespace regards not the footnote itself, but what
Docutils names `footnote references`_.

I added cross-links for these related entries. However, even the footnote
references section does not explain the whitespace issue - for this you
need to know that footnote references are an instance of "inline markup"
and hence adhere to the "inline markup recognition rules".

I agree that a concise explanation whold help and addet it. The crosslinked
version with a paragraph about whitespace before footnote references is now
in the repository (as restructuredtext.txt).



I would be glad, if a Docutils developer with the required expertise could
update the documentation pages (outdated also regarding the new HTML writer
(now "html-plain"/"rst2html5.py")).

Günter


.. _footnote references:
  http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#footnote-references

Re: [Docutils-users] space in front of footnotes?

[Guenter M. <mi...@us...>]

On 2015-08-18, Gour wrote:
> Guenter Milde <mi...@us...> writes:

>> However, you are free to set your own defaults in a system-wide or user-
>> config file.
>> http://docutils.sourceforge.net/docs/user/config.html#configuration-files

> Using:

> [restructuredtext parser]
> trim_footnote_reference_space=yes

> in ~/.docutils this works, but I’ve tried with this one:

> [html4css1 writer]
> footnote_references="superscript"

> and it does not work. Any hint?

Use the `Config File Syntax`__ in the config file?

__ http://docutils.sourceforge.net/docs/user/config.html#configuration-file-syntax


With ::

  [html4css1 writer]
  footnote-references: superscript

and using the html4css writer (rst2html.py), it works here.

With ::

  [writers]
  footnote-references: superscript

it works also for rst2html5.py.


> p.s. Even after subscribing to the mailing list, posting via Gmane does
> not work. Any idea?

It may require one additional confirmation step (telling Gmane that
posting is OK). I don't recall the actual procedure but I use my
news-reader via Gmane for reading and posting both docutils-user and
docutils-devel.

Günter

Re: [Docutils-users] space in front of footnotes?

[Gour <go...@at...>]

Matěj Cepl <mc...@ce...> writes:

> It works perfectly well for HTML and LaTeX, but I think I would 
> prefer ODT not to have space in front of the footnote label.

What did you do for HTML, iow. how to use it?

I get:

gour@atmarama ~/p/n/n/posts> rst2html --traceback how-what-to-preach.rst 
Traceback (most recent call last):
  File "/usr/bin/rst2html", line 23, in <module>
    publish_cmdline(writer_name='html', description=description)
  File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 352, in publish_cmdline
    config_section=config_section, enable_exit_status=enable_exit_status)
  File "/usr/lib/python2.7/dist-packages/docutils/core.py", line 219, in publish
    output = self.writer.write(self.document, self.destination)
  File "/usr/lib/python2.7/dist-packages/docutils/writers/__init__.py", line 80, in write
    self.translate()
  File "/usr/lib/python2.7/dist-packages/docutils/writers/html4css1/__init__.py", line 176, in translate
    self.document.walkabout(visitor)
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 174, in walkabout
    if child.walkabout(visitor):
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 174, in walkabout
    if child.walkabout(visitor):
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 174, in walkabout
    if child.walkabout(visitor):
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 166, in walkabout
    visitor.dispatch_visit(self)
  File "/usr/lib/python2.7/dist-packages/docutils/nodes.py", line 1882, in dispatch_visit
    return method(node)
  File "/usr/lib/python2.7/dist-packages/docutils/writers/html4css1/__init__.py", line 992, in visit_footnote_reference
    assert format == 'superscript'
AssertionError

> Didn’t you miss to reply to some confirmation email?

Nope, no Gmane auth message received…


Sincerely,
Gour

-- 
The spirit soul bewildered by the influence of false ego thinks 
himself the doer of activities that are in actuality carried out 
by the three modes of material nature.

Re: [Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

On 2015-08-18, 10:24 GMT, Gour wrote:
>> However, you are free to set your own defaults in a system-wide or user-
>> config file.
>> http://docutils.sourceforge.net/docs/user/config.html#configuration-files
>
> [restructuredtext parser]
> trim_footnote_reference_space=yes
>
> in ~/.docutils this works, but I’ve tried with this one:
>
> [html4css1 writer]
> footnote_references="superscript"

It works perfectly well for HTML and LaTeX, but I think I would 
prefer ODT not to have space in front of the footnote label.

> p.s. Even after subscribing to the mailing list, posting via 
> Gmane does not work. Any idea?

Didn’t you miss to reply to some confirmation email?

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
The world is coming to an end!  Repent and return those library
books!

Re: [Docutils-users] space in front of footnotes?

[Gour <go...@at...>]

Guenter Milde <mi...@us...> writes:

> However, you are free to set your own defaults in a system-wide or user-
> config file.
> http://docutils.sourceforge.net/docs/user/config.html#configuration-files

Using:

[restructuredtext parser]
trim_footnote_reference_space=yes

in ~/.docutils this works, but I’ve tried with this one:

[html4css1 writer]
footnote_references="superscript"

and it does not work. Any hint?

> Also, there is the possibilty to escape the required whitespace like 
> this.\ [#]_

Thank you. Another very helpful info.

Sincerely,
Gour

p.s. Even after subscribing to the mailing list, posting via Gmane does
not work. Any idea?

-- 
But for one who takes pleasure in the self, whose human life 
is one of self-realization, and who is satisfied in the self only, 
fully satiated — for him there is no duty.

Re: [Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

On 2015-08-18, 07:49 GMT, Guenter Milde wrote:
> Also, with "bracket footnotes" [1] instead of superscript 
> ones² you may want to keep the space.
>
> Footnote references are by default "bracket" in HTML and 
> "superscript" in LaTeX.

I had an epiphany right now (again) … docutils maintainers are 
a way more smart than I am! 

Thanks,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
Experience is what you get when you don't get what you want.
   -- Dan Stanford

Re: [Docutils-users] space in front of footnotes?

[Guenter M. <mi...@us...>]

On 2015-08-17, Matěj Cepl wrote:
> On 2015-08-17, 22:06 GMT, Matěj Cepl wrote:
>> How can I get the footnote without the space in front of it?

> Oh, I got it. I have to add to docutils configuration:

>     [restructuredtext parser]
>     trim_footnote_reference_space=yes

> Why in the world is this not a default?

Probabely because it was introduced later and backwards compatibility was a
priority.

Also, with "bracket footnotes" [1] instead of superscript ones² you may
want to keep the space.

Footnote references are by default "bracket" in HTML and "superscript" in
LaTeX.
http://docutils.sourceforge.net/docs/user/config.html#footnote-references
http://docutils.sourceforge.net/docs/user/config.html#footnote-references-latex2e-writer

However, you are free to set your own defaults in a system-wide or user-
config file.
http://docutils.sourceforge.net/docs/user/config.html#configuration-files

Also, there is the possibilty to escape the required whitespace like 
this.\ [#]_

Günter


[1] this looks like a citation in a scientific article

² this looks like a footnote in a scientific article

Re: [Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

On 2015-08-17, 22:06 GMT, Matěj Cepl wrote:
> How can I get the footnote without the space in front of it?

Oh, I got it. I have to add to docutils configuration:

    [restructuredtext parser]
    trim_footnote_reference_space=yes

Why in the world is this not a default?

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
understand, v.:
    To reach a point, in your investigation of some subject, at
    which you cease to examine what is really present, and
    operate on the basis of your own internal model instead.

[Docutils-users] space in front of footnotes?

[Matěj C. <mc...@ce...>]

Hi, I cannot find on 
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#footnotes 
concise explanation about the relationship between whitespace 
and footnotes. Consider this paragraph (obviously all examples 
are not indendent in the original):

    There was a feeling of vanity and that lead me to the 
    theological mediation about the dying church.[#]_

However, I don’t want to have a space between the period 
character and the footnote label. When I write the rST source 
like this, rst2html (both 0.11 and 0.12 version) doesn’t 
recognize the footnote label as such, so I get in literally the 
footnote label:

    <p>There was a feeling of vanity and that lead me to the 
    theological mediation about the dying church.[#]_</p>

When I change the source to

    There was a feeling of vanity and that lead me to the 
    theological mediation about the dying church. [#]_

I get the footnote but with the space in front of it:

    <p>There was a feeling of vanity and that lead me to the 
    theological mediation about the dying church. <a 
    class="footnote-reference" href="#id8" id="id2">[1]</a></p>

How can I get the footnote without the space in front of it?

Thanks for any reply,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mc...@ce...
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
Faithful love is what people look for in a person; ...
   -- Proverbs 19:22 (NJB)

Re: [Docutils-users] A typo in "Docutils Front-End Tools" page

[Guenter M. <mi...@us...>]

On 2015-08-13, Apua wrote:
> Hi,

> I found a typo "hmtl" in page `Docutils Front-End Tools
><http://docutils.sourceforge.net/docs/user/tools.html#id29>`_.

Thanks for reporting.

The typo is fixed in the course of a complete rewrite of the documentation.
The new version is available as rST source in the repository and will
hopefully soon be also visible in the public HTML pages.

Thanks,

Günter

Re: [Docutils-users] Class Directive

[Guenter M. <mi...@us...>]

On 2015-08-14, Paul VonZimmerman wrote:

> [-- Type: text/plain, Encoding:  --]

> Hi everyone, having a lot of trouble figuring out how to define what
> content get's a particular class.

>  .. class:: drop-down

>     This is a header
>     ++++++++++++++++

>     I'm a bit of content

>     An H2
>     =====


Here, this example aborts with an 

 /tmp/class-arg.rst:4: (SEVERE/4) Unexpected section title.

error. This is in accordance with the documentation: section titles cannot
be nested in any directive. OTOH, the class directive 

  sets the "classes" attribute value on its content or on the first
  immediately following [4] non-comment element

  -- http://docutils.sourceforge.net/docs/ref/rst/directives.html#class

i.e. with the form::

  Leading text

  .. class:: drop-down
  
  This is a header
  ++++++++++++++++
  
  I'm a bit of content
  
  An H2
  =====

  Text in section 1.1 is a part of section 1.

the "drop-down" class argument is applied to section 1 "This is a header".

The document tree looks like 

  <document source="/tmp/class-arg.rst">
      <paragraph>
          Leading text
      <section classes="drop-down" ids="this-is-a-header" names="this\ is\ a\ header">
          <title>
              This is a header
          <paragraph>
              I’m a bit of content
          <section ids="an-h2" names="an\ h2">
              <title>
                  An H2
              <paragraph>
                  Text in section 1.1 is a part of section 1.

(output of rst2pseudoxml.py)



> So, what I want to do is make the H2 element not have the class "drop-down"
> applied to it. I've tried different indentations, etc. The only thing that
> seems to work is placing H1 before the h2, this seems to be the only thing
> that ends the class. Any help would be appreciated! Thank you!

There are some limitatins of the simple text input format rST:

You cannot give a class to the "title" element, only to the "section" element.

In Docutils, sections are nested. You cannot end a subsection and continue
the parent section. 

Depending on what you want to achieve, you may choose between several
workarounds:

* same level headings::

    .. class:: drop-down
    
    This is a header
    ++++++++++++++++
    
    I'm a bit of content
    
    next section of same level
    ++++++++++++++++++++++++++
    
* "overwrite" with more specific class arg::

  .. class:: drop-down
  
  This is a header
  ++++++++++++++++
  
  I'm a bit of content
  
  .. class:: not-drop-down
  
  An H2
  =====

* custom role for class with very limited scope
  http://docutils.sourceforge.net/docs/ref/rst/directives.html#custom-interpreted-text-roles
  ::

  .. role:: drop-down
  
  :drop-down:`This is a header`
  +++++++++++++++++++++++++++++
  
  I'm a bit of content
  
  An H2
  =====



* live with it and write more specific CSS rules.


If you explain what you want to achieve, we may find a way...

Günter

Re: [Docutils-users] LaTeX writer crash

[Mikołaj M. <mi...@wp...>]

Thank you very much Guenter :)
Both for fix and debugging of my document.

With kind regards,

Mikolaj