Menu
▾
▴
docutils-users — General discussions, questions, help requests.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(15) |
Oct
(21) |
Nov
(18) |
Dec
(59) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(43) |
Feb
(35) |
Mar
(78) |
Apr
(65) |
May
(163) |
Jun
(169) |
Jul
(137) |
Aug
(77) |
Sep
(47) |
Oct
(27) |
Nov
(43) |
Dec
(68) |
| 2004 |
Jan
(61) |
Feb
(39) |
Mar
(11) |
Apr
(42) |
May
(86) |
Jun
(82) |
Jul
(24) |
Aug
(26) |
Sep
(37) |
Oct
(62) |
Nov
(131) |
Dec
(43) |
| 2005 |
Jan
(31) |
Feb
(56) |
Mar
(65) |
Apr
(165) |
May
(106) |
Jun
(97) |
Jul
(65) |
Aug
(150) |
Sep
(78) |
Oct
(115) |
Nov
(41) |
Dec
(26) |
| 2006 |
Jan
(50) |
Feb
(39) |
Mar
(56) |
Apr
(67) |
May
(89) |
Jun
(68) |
Jul
(116) |
Aug
(65) |
Sep
(58) |
Oct
(103) |
Nov
(28) |
Dec
(52) |
| 2007 |
Jan
(92) |
Feb
(60) |
Mar
(124) |
Apr
(96) |
May
(69) |
Jun
(79) |
Jul
(25) |
Aug
(22) |
Sep
(7) |
Oct
(17) |
Nov
(27) |
Dec
(32) |
| 2008 |
Jan
(57) |
Feb
(87) |
Mar
(51) |
Apr
(43) |
May
(56) |
Jun
(62) |
Jul
(25) |
Aug
(82) |
Sep
(58) |
Oct
(42) |
Nov
(38) |
Dec
(86) |
| 2009 |
Jan
(50) |
Feb
(33) |
Mar
(84) |
Apr
(90) |
May
(109) |
Jun
(37) |
Jul
(22) |
Aug
(51) |
Sep
(93) |
Oct
(86) |
Nov
(31) |
Dec
(62) |
| 2010 |
Jan
(33) |
Feb
(57) |
Mar
(62) |
Apr
(43) |
May
(30) |
Jun
(49) |
Jul
(20) |
Aug
(40) |
Sep
(152) |
Oct
(38) |
Nov
(15) |
Dec
(32) |
| 2011 |
Jan
(29) |
Feb
(25) |
Mar
(65) |
Apr
(45) |
May
(27) |
Jun
(11) |
Jul
(14) |
Aug
(8) |
Sep
(13) |
Oct
(117) |
Nov
(60) |
Dec
(19) |
| 2012 |
Jan
(23) |
Feb
(32) |
Mar
(24) |
Apr
(41) |
May
(56) |
Jun
(24) |
Jul
(15) |
Aug
(11) |
Sep
(26) |
Oct
(21) |
Nov
(12) |
Dec
(31) |
| 2013 |
Jan
(32) |
Feb
(24) |
Mar
(39) |
Apr
(44) |
May
(44) |
Jun
(8) |
Jul
(9) |
Aug
(12) |
Sep
(34) |
Oct
(19) |
Nov
(5) |
Dec
(9) |
| 2014 |
Jan
(22) |
Feb
(12) |
Mar
(7) |
Apr
(2) |
May
(13) |
Jun
(17) |
Jul
(8) |
Aug
(10) |
Sep
(7) |
Oct
(4) |
Nov
|
Dec
(39) |
| 2015 |
Jan
(13) |
Feb
(12) |
Mar
(12) |
Apr
(40) |
May
(5) |
Jun
(22) |
Jul
(3) |
Aug
(42) |
Sep
(5) |
Oct
(10) |
Nov
|
Dec
(10) |
| 2016 |
Jan
(9) |
Feb
(43) |
Mar
(5) |
Apr
(14) |
May
(17) |
Jun
(5) |
Jul
(5) |
Aug
(22) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
(18) |
| 2017 |
Jan
(28) |
Feb
(29) |
Mar
(9) |
Apr
(23) |
May
(48) |
Jun
(5) |
Jul
(32) |
Aug
(9) |
Sep
(13) |
Oct
(13) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
(6) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
(17) |
Jul
(12) |
Aug
(15) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
(5) |
May
(10) |
Jun
(6) |
Jul
(6) |
Aug
|
Sep
(11) |
Oct
(18) |
Nov
(10) |
Dec
(7) |
| 2020 |
Jan
(3) |
Feb
(14) |
Mar
(2) |
Apr
(1) |
May
(5) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(14) |
| 2021 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
(8) |
May
(23) |
Jun
(7) |
Jul
(10) |
Aug
(1) |
Sep
|
Oct
(7) |
Nov
(10) |
Dec
(2) |
| 2022 |
Jan
|
Feb
(21) |
Mar
|
Apr
(3) |
May
(7) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(18) |
Feb
|
Mar
(1) |
Apr
|
May
(9) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(2) |
| 2025 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(6) |
Jul
(22) |
Aug
(5) |
Sep
(9) |
Oct
(24) |
Nov
|
Dec
|
|
From: Roger G. <rga...@ga...> - 2019-07-21 17:16:09
|
On 21 July 2019 10:39:58 BST, engelbert gruber <eng...@gm...> wrote: >Note > Docutils 0.15.x is compatible with Python versions 2.6, 2.7 and 3.3 to >3.5 Is there a problem with 3.6, 3.7 and 3.8 betas? Or is this an oversight in the announcement text -- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
From: engelbert g. <eng...@gm...> - 2019-07-21 09:40:18
|
Note
Docutils 0.15.x is compatible with Python versions 2.6, 2.7 and 3.3 to
3.5
* reStructuredText:
- Allow embedded colons in field list field names (before, tokens like
``:this:example:`` were considered ordinary text).
- Fixed a bug with the "trim" options of the "unicode" directive.
* languages: Added Korean (ko) mappings and latin.
* Several fixes to keep mor information on source in parsed elements,
isolate documents roles from other documents parsed, smartquotes,
table gets width and latex table multicolumn cells, ...
all the best
engelbert
|
|
From: Guenter M. <mi...@us...> - 2019-06-12 07:58:36
|
Dear Kent, On 2019-05-22, Kent Borg wrote: > Hello, > I am looking at using reStructuredText in the following custom way: > - Write documents using conventional rst for static data, > - And define my own custom directives and roles for dynamic data, > - Programmatically process my hybrid static/dynamic documents, > substituting/expanding my custom directives into static data, > - Likely write my own "writer"--or two or three--for custom output > formats, though that will come later. > I don't see a lot of documentation on this kind of work. Looking about I > made it as far as core.publish_programmatically() and that looks > promising, plus the documentation there says that if I think I want to > use this code I should ask on the list first. > So, two questions: > 1) And I crazy? Ambitious. Docutils is designed with this use-case in mind, so it is not too hard to achieve. However, there is no user manual for this task, so you will need to read and understand the source code. > 2) How should I go about this? I suggest starting with a custom `front end tool`__ that imports and enhances the parser prior to the call to publish_cmdline(). __ http://docutils.sourceforge.net/docs/api/cmdline-tool.html An example for this approach is http://docutils.sourceforge.net/sandbox/jensj/latex_math/tools/rst2latexmath.py from the times Docutils did not have native math support. * Get a general understanding of rST and Docutils. * Look for examples in the sandbox or other extensions__. __ http://docutils.sourceforge.net/docs/user/links.html#extensions * Look for examples for directives and roles in docutils/parsers/rst/ * Eventually study examples for "transforms" (working on the generated document tree Python object) in docutils/transforms Start with a simple example and come back to the list if there are specific questions. Good luck, Günter |
|
From: Alan I. <ala...@gm...> - 2019-06-11 19:22:28
|
Apologies, I shd have updated before reporting. It's fixed in latest Subversion (8256). (Unfortunately I did not check the revision I was updating from so I cannot report that.) Alan On 6/11/2019 3:44 AM, Guenter Milde via Docutils-users wrote: > On 2019-06-10, Alan Isaac wrote: >> If I understand the documentation, the following should work:: > >> .. csv-table:: Test >> :width: 50% > >> test01 >> test02 > >> The html5 write produces no content for this. >> If I remove the `width` specification, the output is as expected. > > I cannot reproduce. Here, with > `rst2html5 --link-stylesheet example.txt` I get the expected: > > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> > <head> > <meta charset="utf-8"/> > <meta name="generator" content="Docutils 0.15b.dev: http://docutils.sourceforge.net/" /> > <title>widetable.rst</title> > <link rel="stylesheet" href="<path-to>/docutils/writers/html5_polyglot/minimal.css" type="text/css" /> > <link rel="stylesheet" href="<path-to>/docutils/writers/html5_polyglot/plain.css" type="text/css" /> > </head> > <body> > <div class="document"> > > > <table style="width: 50%"> > <caption>Test</caption> > <colgroup> > <col style="width: 100%" /> > </colgroup> > <tbody> > <tr><td><p>test01</p></td> > </tr> > <tr><td><p>test02</p></td> > </tr> > </tbody> > </table> > </div> > </body> > </html> > > > Günter > > > > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. > |
|
From: Guenter M. <mi...@us...> - 2019-06-11 07:45:07
|
On 2019-06-10, Alan Isaac wrote: > If I understand the documentation, the following should work:: > .. csv-table:: Test > :width: 50% > test01 > test02 > The html5 write produces no content for this. > If I remove the `width` specification, the output is as expected. I cannot reproduce. Here, with `rst2html5 --link-stylesheet example.txt` I get the expected: <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta charset="utf-8"/> <meta name="generator" content="Docutils 0.15b.dev: http://docutils.sourceforge.net/" /> <title>widetable.rst</title> <link rel="stylesheet" href="<path-to>/docutils/writers/html5_polyglot/minimal.css" type="text/css" /> <link rel="stylesheet" href="<path-to>/docutils/writers/html5_polyglot/plain.css" type="text/css" /> </head> <body> <div class="document"> <table style="width: 50%"> <caption>Test</caption> <colgroup> <col style="width: 100%" /> </colgroup> <tbody> <tr><td><p>test01</p></td> </tr> <tr><td><p>test02</p></td> </tr> </tbody> </table> </div> </body> </html> Günter |
|
From: David G. <go...@py...> - 2019-06-10 18:18:04
|
Transitions are structural elements, along with sections & sidebars. Containers are body elements, which cannot contain structural elements. See docs/ref/docutils.dtd for complete technical details. You could simulate a transition with an empty paragraph (escaped space: "\ "). Compared to Docutils, HTML has a much more permissive, anything-goes, way-too-loose document model. David Goodger <https://david.goodger.org> On Mon, 10 Jun 2019 at 12:26, Alan Isaac <ala...@gm...> wrote: > > I want to indicate a thematic transition inside a containter. > > It seems that transitions (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#transitions) > are not allowed inside containers. Why is that? (E.g., an HR element can certainly go inside a DIV element > in an HTML document.) > > Thank you, > Alan Isaac > > > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. |
|
From: Alan I. <ala...@gm...> - 2019-06-10 18:10:26
|
If I understand the documentation, the following should work::
.. csv-table:: Test
:width: 50%
test01
test02
The html5 write produces no content for this.
If I remove the `width` specification, the output is as expected.
Alan Isaac
|
|
From: Alan I. <ala...@gm...> - 2019-06-10 17:26:05
|
I want to indicate a thematic transition inside a containter. It seems that transitions (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#transitions) are not allowed inside containers. Why is that? (E.g., an HR element can certainly go inside a DIV element in an HTML document.) Thank you, Alan Isaac |
|
From: Kent B. <ken...@bo...> - 2019-05-22 19:30:24
|
Hello, I am looking at using reStructuredText in the following custom way: - Write documents using conventional rst for static data, - And define my own custom directives and roles for dynamic data, - Programmatically process my hybrid static/dynamic documents, substituting/expanding my custom directives into static data, - Likely write my own "writer"--or two or three--for custom output formats, though that will come later. I don't see a lot of documentation on this kind of work. Looking about I made it as far as core.publish_programmatically() and that looks promising, plus the documentation there says that if I think I want to use this code I should ask on the list first. So, two questions: 1) And I crazy? 2) How should I go about this? Thanks, -kb |
|
From: Alan I. <ala...@gm...> - 2019-05-20 12:55:31
|
Thinking this through a bit more, I realize I have a more fundamental design question. As I struggle with the `table` directive, it seems that it behaves quite a bit differently than I would like, and that would I would find more useful would be something like the following: a table directive that is basically a container with a class, except that it accepts a title as an argument. With this perspective, I would then like to be able to add arbitrary content in the container. One type of content would be a normal reST table. Another type of content would be a `note` directive. Etc. This gets closer to the idea that a "table" environment is just a (usually numbered) environment that contains content that should be kept together (e.g., tabular content, source notes, other notes, etc). This notion of a table environment would be close to the LaTeX approach. Additionally, from this perpsective, the `csv-table` directive has conflated two things: the desire for a "table environment", and the desire to input tabular data in a certain format. Cheers, Alan |
|
From: Alan I. <ala...@gm...> - 2019-05-17 16:00:08
|
On 5/17/2019 10:49 AM, David Goodger wrote: > .. [1] But **not** a table legend; that still makes no sense to me. I was certainly not suggesting such a terminology. My point is rather that what reST refers to as a figure "legend" is in fact a rather multi-use container. In fact, I do not think I have ever used it to hold a legend; instead, I use it to hold figure notes. I would hazard that my usage is the most common, since legend information is very often part of the figure (in one way or another). Example attached (from Jones 2015). That said, tables often contain meaningful markers or colors, whose meaning needs to be explicated in the notes. (E.g., markers of statistical significance levels.) This is quite similar to a figure legend. Alan |
|
From: David G. <go...@py...> - 2019-05-17 14:50:32
|
My distinction between titles and captions comes straight from `The
Chicago Manual of Style`: tables have titles above, figures have
captions below. The HTML <caption> tag seems to be the result of
conflation, shown in the first link you provided:
The HTML Table Caption element (<caption>) specifies the caption
(or title) of a table
For table notes, I suggest simply adding them into the table itself.
This can be done now.
It's *possible* that Docutils could accommodate "table notes" [1]_,
but it would require specification (e.g. are they repeated when a
table is broken across pages, like a header? are they always at the
bottom of tables, even very long ones? etc.) and, of course,
implementation. I personally remain unconvinced.
.. [1] But **not** a table legend; that still makes no sense to me.
David Goodger
<https://david.goodger.org>
On Fri, 17 May 2019 at 08:38, Alan Isaac <ala...@gm...> wrote:
>
> I will try to keep it in mind when talking about reST,
> but I find your distinction between titles and captions to be
> unfamiliar. E.g., the following usage is more familiar to me:
> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/caption
> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/figcaption
>
> However, in this query my interest is (as in the Subject) how
> to handle table notes. My observation is that just as figures
> allow figure notes (as part of the "legend" content), a table could
> similarly allow table notes. These are a *very* often needed feature
> -- so much so, that tables without notes are often unacceptable.
> I've attached an "in the wild" example. My query is whether
> docutils could consider accommodating such optional content
> for tables, paralleling the feature in figures.
>
> Cheers, Alan
>
>
> On 5/16/2019 10:09 PM, David Goodger wrote:
> > The table directive as implemented doesn't allow for a legend, just a
> > title. I can't think of why a table would need a legend, and I've
> > never seen one in the wild.
> >
> > Note: figures have captions (below), tables have titles (above).
> > They're not the same thing, and shouldn't be conflated.
> >
> > David Goodger
> > <https://david.goodger.org>
> >
> > On Thu, 16 May 2019 at 16:59, Alan Isaac <ala...@gm...> wrote:
> >>
> >> I'm looking at the documentation at
> >> http://docutils.sourceforge.net/docs/ref/rst/directives.html#table
> >> On my reading, it does not allow for the equivalent of the "legend"
> >> content in a figure. What am I overlooking?
> >>
> >> Thanks, Alan Isaac
> >>
> >>
> >> On 5/16/2019 4:37 PM, David Goodger wrote:
> >>> That's what the "table" directive is for:
> >>> http://docutils.sourceforge.net/docs/ref/rst/directives.html#table
> >>>
> >>> David Goodger
> >>> <https://david.goodger.org>
> >>>
> >>> On Thu, 16 May 2019 at 15:03, Alan Isaac <ala...@gm...> wrote:
> >>>>
> >>>> In published work, tables and figures often require
> >>>> explanatory notes.
> >>>>
> >>>> In rst there appears to be an odd difference in structure between
> >>>> tables and figures. A figure is understood to have three possible
> >>>> types of content, and image, a caption, and what is called a "legend"
> >>>> (which can hold explanatory notes).
> >>>>
> >>>> A table does not do this, but it could.
> >>>> Might this be considered as a possible enhancement?
> >>>>
> >>>> Thanks, Alan Isaac
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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 mailing list
> >> Doc...@li...
> >> https://lists.sourceforge.net/lists/listinfo/docutils-users
> >>
> >> Please use "Reply All" to reply to the list.
>
|
|
From: Alan I. <ala...@gm...> - 2019-05-17 13:38:34
|
I will try to keep it in mind when talking about reST, but I find your distinction between titles and captions to be unfamiliar. E.g., the following usage is more familiar to me: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/caption https://developer.mozilla.org/en-US/docs/Web/HTML/Element/figcaption However, in this query my interest is (as in the Subject) how to handle table notes. My observation is that just as figures allow figure notes (as part of the "legend" content), a table could similarly allow table notes. These are a *very* often needed feature -- so much so, that tables without notes are often unacceptable. I've attached an "in the wild" example. My query is whether docutils could consider accommodating such optional content for tables, paralleling the feature in figures. Cheers, Alan On 5/16/2019 10:09 PM, David Goodger wrote: > The table directive as implemented doesn't allow for a legend, just a > title. I can't think of why a table would need a legend, and I've > never seen one in the wild. > > Note: figures have captions (below), tables have titles (above). > They're not the same thing, and shouldn't be conflated. > > David Goodger > <https://david.goodger.org> > > On Thu, 16 May 2019 at 16:59, Alan Isaac <ala...@gm...> wrote: >> >> I'm looking at the documentation at >> http://docutils.sourceforge.net/docs/ref/rst/directives.html#table >> On my reading, it does not allow for the equivalent of the "legend" >> content in a figure. What am I overlooking? >> >> Thanks, Alan Isaac >> >> >> On 5/16/2019 4:37 PM, David Goodger wrote: >>> That's what the "table" directive is for: >>> http://docutils.sourceforge.net/docs/ref/rst/directives.html#table >>> >>> David Goodger >>> <https://david.goodger.org> >>> >>> On Thu, 16 May 2019 at 15:03, Alan Isaac <ala...@gm...> wrote: >>>> >>>> In published work, tables and figures often require >>>> explanatory notes. >>>> >>>> In rst there appears to be an odd difference in structure between >>>> tables and figures. A figure is understood to have three possible >>>> types of content, and image, a caption, and what is called a "legend" >>>> (which can hold explanatory notes). >>>> >>>> A table does not do this, but it could. >>>> Might this be considered as a possible enhancement? >>>> >>>> Thanks, Alan Isaac >>>> >>>> >>>> _______________________________________________ >>>> 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 mailing list >> Doc...@li... >> https://lists.sourceforge.net/lists/listinfo/docutils-users >> >> Please use "Reply All" to reply to the list. |
|
From: David G. <go...@py...> - 2019-05-17 02:10:39
|
The table directive as implemented doesn't allow for a legend, just a title. I can't think of why a table would need a legend, and I've never seen one in the wild. Note: figures have captions (below), tables have titles (above). They're not the same thing, and shouldn't be conflated. David Goodger <https://david.goodger.org> On Thu, 16 May 2019 at 16:59, Alan Isaac <ala...@gm...> wrote: > > I'm looking at the documentation at > http://docutils.sourceforge.net/docs/ref/rst/directives.html#table > On my reading, it does not allow for the equivalent of the "legend" > content in a figure. What am I overlooking? > > Thanks, Alan Isaac > > > On 5/16/2019 4:37 PM, David Goodger wrote: > > That's what the "table" directive is for: > > http://docutils.sourceforge.net/docs/ref/rst/directives.html#table > > > > David Goodger > > <https://david.goodger.org> > > > > On Thu, 16 May 2019 at 15:03, Alan Isaac <ala...@gm...> wrote: > >> > >> In published work, tables and figures often require > >> explanatory notes. > >> > >> In rst there appears to be an odd difference in structure between > >> tables and figures. A figure is understood to have three possible > >> types of content, and image, a caption, and what is called a "legend" > >> (which can hold explanatory notes). > >> > >> A table does not do this, but it could. > >> Might this be considered as a possible enhancement? > >> > >> Thanks, Alan Isaac > >> > >> > >> _______________________________________________ > >> 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 mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. |
|
From: Alan I. <ala...@gm...> - 2019-05-16 21:59:25
|
I'm looking at the documentation at http://docutils.sourceforge.net/docs/ref/rst/directives.html#table On my reading, it does not allow for the equivalent of the "legend" content in a figure. What am I overlooking? Thanks, Alan Isaac On 5/16/2019 4:37 PM, David Goodger wrote: > That's what the "table" directive is for: > http://docutils.sourceforge.net/docs/ref/rst/directives.html#table > > David Goodger > <https://david.goodger.org> > > On Thu, 16 May 2019 at 15:03, Alan Isaac <ala...@gm...> wrote: >> >> In published work, tables and figures often require >> explanatory notes. >> >> In rst there appears to be an odd difference in structure between >> tables and figures. A figure is understood to have three possible >> types of content, and image, a caption, and what is called a "legend" >> (which can hold explanatory notes). >> >> A table does not do this, but it could. >> Might this be considered as a possible enhancement? >> >> Thanks, Alan Isaac >> >> >> _______________________________________________ >> Docutils-users mailing list >> Doc...@li... >> https://lists.sourceforge.net/lists/listinfo/docutils-users >> >> Please use "Reply All" to reply to the list. |
|
From: Alan G. I. <ai...@am...> - 2019-05-16 21:04:09
|
I am wondering why "admonition" is prepended to the title for the class attribute, given that "admonition" is one of the classes. If this is to accommodate another write, shouldn't that be handled by a multiple-class to single identifier convention? Also, has the current convention always applied? It took me by surprise, possibly due to forgetfulness. Thanks, Alan Isaac |
|
From: David G. <go...@py...> - 2019-05-16 20:38:18
|
That's what the "table" directive is for: http://docutils.sourceforge.net/docs/ref/rst/directives.html#table David Goodger <https://david.goodger.org> On Thu, 16 May 2019 at 15:03, Alan Isaac <ala...@gm...> wrote: > > In published work, tables and figures often require > explanatory notes. > > In rst there appears to be an odd difference in structure between > tables and figures. A figure is understood to have three possible > types of content, and image, a caption, and what is called a "legend" > (which can hold explanatory notes). > > A table does not do this, but it could. > Might this be considered as a possible enhancement? > > Thanks, Alan Isaac > > > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. |
|
From: Alan I. <ala...@gm...> - 2019-05-16 20:03:51
|
In published work, tables and figures often require explanatory notes. In rst there appears to be an odd difference in structure between tables and figures. A figure is understood to have three possible types of content, and image, a caption, and what is called a "legend" (which can hold explanatory notes). A table does not do this, but it could. Might this be considered as a possible enhancement? Thanks, Alan Isaac |
|
From: POIRET <gil...@bz...> - 2019-04-24 14:37:33
|
Hello,
I'm still trying to produce automatically odt documents from
rst file. I have currently two problems, when using docutils0.14 /
rst2odt tool.
With large table and images, those objects exceed table
boundaries, and so the produced document can't be used as is.
I'm
sharing below my wonderings/changes to fix that. Any comment are
welcome.
Regards,
--
Gilles Poiret
TABLE:
analysis:
in the visit_table function, the lines "style:width" are commented.
workaround Uncomment them solve my issue, even if using the
self.get_page_width() to compute the value should be better..I guess you
have chosen to comment them. Could you explain why please?
drawback : the small tables become bigger, but at least the document is
consistent.
IMAGE:
analysis & workaround : nothing seems planed to
avoid this behavior. I added the following in the
get_image_scaled_width_height function. Not perfect, especially if the
image is not put at the beginning of a line, but it's better than the
current situation, at least for me.
-- at the beginning of the
function
line_width = self.get_page_width() # GP - the call of
this code can be removed below, in the "if width_unit == '%' test"
--
at the end of the function
width *= scale
height *=
scale
if width > line_width: # GP - resize the image to
fit the page size if bigger
ratio_vs_pagesize = line_width /
width
width = line_width
height *=
ratio_vs_pagesize
width = '%.2fcm' % width
height =
'%.2fcm' % height
return width, height
Environment : Debian 10
"testing" / package python3-docutils 0.14+dfsg-4
|
|
From: Guenter M. <mi...@us...> - 2019-04-07 20:06:37
|
On 2019-04-07, D. Hugh Redelmeier wrote: >| From: D. Hugh Redelmeier <hu...@mi...> >| On Fedora 29, the dnf(1) has a formatting ugliness: ... > But wait! I do see problems with the input to nroff. > It is generated by sphinx. My impression is that sphinx is also a > part of the docutils project. Not exactly. Sphinx uses Docutils as a library for the conversion but adds an additional layer. So, the error may be in Sphinx, in the Docutils manpage writer, or in the input for Spinx or the Docutils manpage writer (should be a file with reStructured text like "dnf.rst" or "dnf.txt". There are some restrictions on the allowed input, especially for option lists. See http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#option-lists Günter |
|
From: D. H. R. <hu...@mi...> - 2019-04-07 19:31:19
|
| From: D. Hugh Redelmeier <hu...@mi...> | On Fedora 29, the dnf(1) has a formatting ugliness: In private email, it was pointed out that this ugliness probably didn't come from rst2man or sphinx. I'm trying to track down just where it comes from. I found out that the plumbing of the man command has gotten a lot more complicated than when I last paid attention (1980s?). In this case, a preformatted man page, generated by sphinx, is distributed by Fedora. When the man command is issued, apparently a pipeline is created. something does gunzip | /usr/bin/preconv -e UTF-8 | /usr/bin/tbl | /usr/bin/nroff -mandoc -Tutf8 | /usr/bin/less # as if -r At the moment, it looks as if nroff is the culprit. nroff performs nicely if it is invoked with -rLL=86n and badly with -rLL=85n The -r flag sets the "number register". According to groff_man(7), LL is line length. "n" is a scaling factor so that these numbers are in ens, the width of the character n. But wait! I do see problems with the input to nroff. It is generated by sphinx. My impression is that sphinx is also a part of the docutils project. I generated this with gunzip -c /usr/share/man/man8/dnf.8.gz | preconv -e UTF-8 | tbl Here is a section of interest: 203 .TP 204 .B \fB\-d <debug level>, \-\-debuglevel=<debug level>\fP 205 Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use \fB\-v\fP instead. 206 .TP 207 .B \fB\-\-debugsolver\fP 208 Dump data aiding in dependency solver debugging into \fB\&./debugdata\fP\&. 209 .UNINDENT 210 .sp 211 \fB\-\-disableexcludes=[all|main|<repoid>], \-\-disableexcludepkgs=[all|main|<repoid>]\fP 212 .INDENT 0.0 213 .INDENT 3.5 214 Disable the configuration file excludes. Takes one of the following three options: 215 .INDENT 0.0 216 .IP \(bu 2 217 \fBall\fP, disables all configuration file excludes 218 .IP \(bu 2 219 \fBmain\fP, disables excludes defined in the \fB[main]\fP section 220 .IP \(bu 2 221 \fBrepoid\fP, disables excludes defined for the given repository 222 .UNINDENT 223 .UNINDENT 224 .UNINDENT 225 .INDENT 0.0 226 .TP 227 .B \fB\-\-disable, \-\-set\-disabled\fP Lines 203-205 show what a normal option description turns into. Ditto 206-208. Notice that no explicit indentation is specified. man(7) descibes .TP as starting a paragraph with a hanging tag. The tag is given on the next line. (Note that the tag is emboldened twice-over (.B and \fB). This seems like an inconsequential bug.) Things go weird at line 209, for the --debugexcludes option. For one thing, .TP isn't used. For another, there seems to be a lot of explicit indenting going on. The indenting is wrong. It does not match that of other options. But even with these fixed (by manual editing of the generated nroff file), my original problem is not solved. The tag is still split in a bad place. Some explicit indentation is probably needed since the paragraph contains nested paragraphs (the bullet points). I don't know what the correct indentation is. |
|
From: D. H. R. <hu...@mi...> - 2019-04-06 19:23:41
|
Oops: this might be a problem with Sphinx, not rst2doc. I've not figured out the plumbing. | From: D. Hugh Redelmeier <hu...@mi...> | | On Fedora 29, the dnf(1) has a formatting ugliness: | | --disableexcludes=[all|main|<repoid>], --disableexcludep‐ | kgs=[all|main|<repoid>] | Disable the configuration file excludes. Takes one of the following | three options: | | (I hope your MUA doesn't muck that up.) | | The .rst is: | | ``--disableexcludes=[all|main|<repoid>], --disableexcludepkgs=[all|main|<repoid>]`` | | Disable the configuration file excludes. Takes one of the following three options: | | | Clearly, to a human, rst2man should break this differently: | | --disableexcludes=[all|main|<repoid>], | --disableexcludepkgs=[all|main|<repoid>] | Disable the configuration file excludes. Takes one of the following three options: | | Why? | | - placing a break in a keyword instead of at a space is wrong | | - placing a break in a keyword instead of at a word boundary is wrong | | - breaking a keyword at a random spot is wrong (although finding | syllable boundaries in made-up words is difficult) | | - turning the single space into 15 spaces is just putting salt on the wound | | Is this a bug in rst2man or a bug in the dnf.rst file? | | <https://github.com/rpm-software-management/dnf/blob/master/doc/command_ref.rst> |
|
From: D. H. R. <hu...@mi...> - 2019-04-06 17:23:30
|
On Fedora 29, the dnf(1) has a formatting ugliness:
--disableexcludes=[all|main|<repoid>], --disableexcludep‐
kgs=[all|main|<repoid>]
Disable the configuration file excludes. Takes one of the following
three options:
(I hope your MUA doesn't muck that up.)
The .rst is:
``--disableexcludes=[all|main|<repoid>], --disableexcludepkgs=[all|main|<repoid>]``
Disable the configuration file excludes. Takes one of the following three options:
Clearly, to a human, rst2man should break this differently:
--disableexcludes=[all|main|<repoid>],
--disableexcludepkgs=[all|main|<repoid>]
Disable the configuration file excludes. Takes one of the following three options:
Why?
- placing a break in a keyword instead of at a space is wrong
- placing a break in a keyword instead of at a word boundary is wrong
- breaking a keyword at a random spot is wrong (although finding
syllable boundaries in made-up words is difficult)
- turning the single space into 15 spaces is just putting salt on the wound
Is this a bug in rst2man or a bug in the dnf.rst file?
<https://github.com/rpm-software-management/dnf/blob/master/doc/command_ref.rst> |
|
From: Matěj C. <mc...@ce...> - 2019-03-03 18:00:22
|
On 2018-08-28, 08:08 GMT, R. Diez via Docutils-users wrote: > The one thing that bothers me most often with Microsoft Word > or LibreOffice Writer is that paragraphs or tables are not > kept together when generating a PDF or printing. LibreOffice Table/Insert table ... and in the dialog check "Don't split table over page breaks" (that's back-translation from Czech menus). Of course, I prefer reStructuredText myself, but it is not excuse for not knowing your tools. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mc...@ce... GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 See, when the GOVERNMENT spends money, it creates jobs; whereas when the money is left in the hands of TAXPAYERS, God only knows what they do with it. Bake it into pies, probably. Anything to avoid creating jobs. -- Dave Barry |
|
From: Guenter M. <mi...@us...> - 2019-03-02 12:15:16
|
Dear Tony, could you re-send as simple text message (no HTML), please? I am following the group via the GMANE news interface and all I see is: On 2019-03-02, Tony Craig wrote: > [-- Type: text/plain, Encoding: --] > [-- Skipped Type: text/html --] > [-- Type: text/plain, Encoding: 7bit --] > [-- Type: text/plain, Encoding: 7bit --] Thanks, Günter |
86 messages has been excluded from this view by a project administrator.
