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
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
(2) |
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
(1) |
18
(1) |
19
|
20
|
21
(1) |
22
|
23
|
24
(3) |
25
(1) |
26
(5) |
27
(8) |
28
(3) |
|
|
|
|
|
From: Alan G I. <ai...@am...> - 2011-02-28 14:08:05
|
> On 2011-02-21, Alan G Isaac wrote: >> Why are literal blocks put in a quote environment? On 2/28/2011 5:05 AM, Guenter Milde wrote: > Because this shows up in the PDF similar to the way they are presented > in HTML (indented and with vertical separation). This seems to justify an unfortunate LaTeX display by referencing an unfortunate HTML display, which in turn is (I think?) just a reflection of unfortunate decisions early on in various browsers. (I don't think it reflects a W3C recommendation.) In any case, two comments on LaTeX output. 1. Can we agree this is undesirable in *slides* at least? Code I need to display gets cutoff *because of* this quote environment. 2. Given (1), then we should allow easy styling, and nesting in a quote environment does not (because it abuses the quote environment). So how about styling the verbatim environment in the preamble (using e.g. Victor's final solution here: http://stackoverflow.com/questions/2143687/latexs-verbatim-how-to-indent-every-instance) and leaving all other environments (e.g., lstlisting) alone, since they are already optimized for code display. This gets rid of the undesirable quote environment but keeps the indentation of the verbatim environment for those who want it, while allowing the latter to be easily restyled. Alan Isaac PS Possibly related to this ... could it be better to submit the reST style for distribution with LaTeX distros rather than repeating it in the header of every written LaTeX file? (Not sure how this would interact with writer options; maybe it's impossible?) |
From: Guenter M. <mi...@us...> - 2011-02-28 10:20:16
|
On 2011-02-26, Roger Frank wrote: > In the FAQ it states "Line blocks are designed for address blocks, > verse, and other cases where line breaks are significant and must be > preserved." The example shows poetry with indentation and the example > works because the indentation is monotonically increasing. If I try > that with something where indentation is significant, it doesn't > preserve the indent. Here is a poem from page [51] of > http://www.gutenberg.org/files/35364/35364-h/35364-h.htm for example: ... > The last line will be indented exactly as the second line, ignoring > that "Fun and frolic" starts with two leading spaces and "Chee, chee" > starts with ten, as the poem was originally published. Is there a way > not only respect the line break but the relative indentation shown in > this example? This construction shows up often in the books that we are > trying to produce based on RST. The example looks as requested in both HTML and PDF (via latex2e), if I replace the leading spaces with runs of no-break spaces (NBSP, "\u00A0"):: | Summer wanes, the children are grown; | Fun and frolic no more he knows; | Robert of Lincoln’s a humdrum crone; | Off he flies and we sing as he goes: | Bob-o’link, bob-o’-link, | Spink, spank, spink; | When you can pipe that merry old strain, | Robert of Lincoln, come back again. | Chee, chee, chee. The parser treats the no-break spaces a normal characters, all lines have the same (CSS) indentation but the leading NBSPs are preserved. The exact amount of the indentation depends on the font - in proportional fonts it is typically considerably smaller than in a fixed-width font, so either replacing one space with two NBSPs or using a monospace font might get the look of the input verses. Günter |
From: Guenter M. <mi...@us...> - 2011-02-28 10:05:27
|
On 2011-02-21, Alan G Isaac wrote: > Why are literal blocks put in a quote environment? Because this shows up in the PDF similar to the way they are presented in HTML (indented and with vertical separation). Unfortunately, configuring this via stylesheets is more difficult, because environments for verbatim input cannot be wrapped in a custom command, i.e. \newenvironment{DUlisting}% {\beginquote\ttfamily\raggedright\noindent}% {\endquote} would work with the standard (escaping LaTeX special chars by Docutils), but e.g. \newenvironment{DUlisting}% {\begin{lstlisting}% {\end{lstlisting} fails. Also, there is already code to omit the quote environment inside tables: if not self.active_table.is_open(): # no quote inside tables, to avoid vertical space between # table border and literal block. # BUG: fails if normal text preceeds the literal block. self.out.append('%\n\\begin{quote}') self.context.append('\n\\end{quote}\n') > Can it be removed from all LaTeX writers? Maybe as an option. Unfortunately, we already have too many options so that it should be well-considered how/whether to implement it. Günter |
From: Paul T. <pau...@gm...> - 2011-02-27 16:23:00
|
I was looking for parsed literal blocks last night in regards to this problem, and could not find it. I thought I had imagined that it existed. Nice to know it really does exist! On 2/27/11 11:19 AM, engelbert gruber wrote: > On Sun, Feb 27, 2011 at 5:15 PM, Paul Tremblay<pau...@gm...> wrote: >> You should be able to change the font in a literal block. I don't know >> how it is done in HTML. I know the stylesheets (converting to PDF) I am >> working on (and are nearly finished) make such a change easy. The >> problem with a literal block is that no other markup is possible. If a >> line of poetry has emphasis, this emphasis would be lost in a literal >> block. > http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-block > > ? |
From: engelbert g. <eng...@gm...> - 2011-02-27 16:19:07
|
On Sun, Feb 27, 2011 at 5:15 PM, Paul Tremblay <pau...@gm...> wrote: > You should be able to change the font in a literal block. I don't know > how it is done in HTML. I know the stylesheets (converting to PDF) I am > working on (and are nearly finished) make such a change easy. The > problem with a literal block is that no other markup is possible. If a > line of poetry has emphasis, this emphasis would be lost in a literal > block. http://docutils.sourceforge.net/docs/ref/rst/directives.html#parsed-literal-block ? |
From: Paul T. <pau...@gm...> - 2011-02-27 16:15:33
|
You should be able to change the font in a literal block. I don't know how it is done in HTML. I know the stylesheets (converting to PDF) I am working on (and are nearly finished) make such a change easy. The problem with a literal block is that no other markup is possible. If a line of poetry has emphasis, this emphasis would be lost in a literal block. As far as one line of poetry disqualifying the text from RST, it seems that should not be the case. One line of poetry will always be indented, and again, it seems a stylesheet should allow you to control the indentation. Paul On 2/27/11 10:19 AM, Roger Frank wrote: > On Feb 27, 2011, at 6:09 AM, engelbert gruber wrote: > >> how about using literal-block >> >> con: it uses typewriter font, might be changed in css >> pro: it uses typewriter font. if horizontal placement (indentation) is >> important, what else do you want to use. > Interesting suggestion. David's suggested workarounds work just fine > as far as I can tell. We'll have to train the post-processors to use > the "workaround" markup, but that's better than having to hand-edit > each text after it is generated or regenerated, if changes such as > from errata reports, are applied. > > Your suggestion, with "pre.literal-block { font-family:serif; }" in > the CSS, shows promise also. Thanks! > > > |
From: Roger F. <rf...@fa...> - 2011-02-27 15:19:47
|
On Feb 27, 2011, at 6:09 AM, engelbert gruber wrote: > how about using literal-block > > con: it uses typewriter font, might be changed in css > pro: it uses typewriter font. if horizontal placement (indentation) is > important, what else do you want to use. Interesting suggestion. David's suggested workarounds work just fine as far as I can tell. We'll have to train the post-processors to use the "workaround" markup, but that's better than having to hand-edit each text after it is generated or regenerated, if changes such as from errata reports, are applied. Your suggestion, with "pre.literal-block { font-family:serif; }" in the CSS, shows promise also. Thanks! |
From: engelbert g. <eng...@gm...> - 2011-02-27 13:10:03
|
how about using literal-block con: it uses typewriter font, might be changed in css pro: it uses typewriter font. if horizontal placement (indentation) is important, what else do you want to use. On Sun, Feb 27, 2011 at 1:02 PM, Roger Frank <rf...@fa...> wrote: > David's explained that "in the reST parser implementation, the > preservation of indentation is relative, not absolute" and that > this design decision is unlikely to change. We are trying to use > reST to produce etexts. From the start we knew that some books > would not be appropriate candidates for a one-source, many-output > model based on reST. It appears that any book with poetry that > uses absolute indentation is not a candidate for reST markup > without manual post-processing. It's not what I had hoped for, > since in many books that are otherwise excellent candidates for > reST, one line of poetry now can disqualify the whole book > from the automated process. We can deal with it, though. > > To be clear, the "we" in this case is DP Canada, which is not > to be confused with the work at Project Gutenberg, where their > implementation of RST has already been modified to preserve > absolute indentation. > > > > > > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. > |
From: Roger F. <rf...@fa...> - 2011-02-27 12:02:46
|
David's explained that "in the reST parser implementation, the preservation of indentation is relative, not absolute" and that this design decision is unlikely to change. We are trying to use reST to produce etexts. From the start we knew that some books would not be appropriate candidates for a one-source, many-output model based on reST. It appears that any book with poetry that uses absolute indentation is not a candidate for reST markup without manual post-processing. It's not what I had hoped for, since in many books that are otherwise excellent candidates for reST, one line of poetry now can disqualify the whole book from the automated process. We can deal with it, though. To be clear, the "we" in this case is DP Canada, which is not to be confused with the work at Project Gutenberg, where their implementation of RST has already been modified to preserve absolute indentation. |
From: engelbert g. <eng...@gm...> - 2011-02-27 10:56:43
|
hi maybe the verse-writer could be used. but AFAIR it produces latex cheers engelbert On Sun, Feb 27, 2011 at 6:12 AM, Paul Tremblay <pau...@gm...> wrote: > The file is not okay, according to what Roger wants. He wants the "Che che" > to line up with the Lincoln of the preceding line. Or, put another way, the > "Che che" to line up with the "Bob-o-link" of the 5th line. > > Paul > > On 2/26/11 3:57 PM, lu...@gm... wrote: > > El 26/02/11 13:40, Roger Frank escribió: > > On Feb 26, 2011, at 6:51 AM, lu...@gm... wrote: > > I try the code of the poem... and I run *rst2pdf* and *rst2html* and it > work fine. I think I don't know what you say when you say *it doesn't > preserve...* > > I should have been more clear. The final line should align somewhere > under the word "Lincoln" to match how the poem was written and > originally typeset. Indentation matters in a poem; it conveys > meaning that should not be lost. > > Checking the HTML generated with rst2html, I see the final line: > > <div class="line-block"> > <div class="line">Chee, chee, chee.</div> > </div> > > is the same construction as the second line: > > <div class="line-block"> > <div class="line">Fun and frolic no more he knows;</div> > </div> > > and they both will be indented the same amount (1.5em) which is > what I mean by "it doesn't preserve" the indentation. > > Thanks for taking the time to look at this, Rod. > > Roger, I send attach the .*rst and the .html* that my *rst2html* > generate. It's ok... I se it en *chrome* and look fine. See the code... > > Success > > Rod > > > > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT > data > generated by your applications, servers and devices whether physical, > virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. > > |
From: Paul T. <pau...@gm...> - 2011-02-27 05:12:11
|
The file is not okay, according to what Roger wants. He wants the "Che che" to line up with the Lincoln of the preceding line. Or, put another way, the "Che che" to line up with the "Bob-o-link" of the 5th line. Paul On 2/26/11 3:57 PM, lu...@gm... wrote: > El 26/02/11 13:40, Roger Frank escribió: >> On Feb 26, 2011, at 6:51 AM, lu...@gm... wrote: >> >>> I try the code of the poem... and I run *rst2pdf* and *rst2html* and it >>> work fine. I think I don't know what you say when you say *it doesn't >>> preserve...* >> I should have been more clear. The final line should align somewhere >> under the word "Lincoln" to match how the poem was written and >> originally typeset. Indentation matters in a poem; it conveys >> meaning that should not be lost. >> >> Checking the HTML generated with rst2html, I see the final line: >> >> <div class="line-block"> >> <div class="line">Chee, chee, chee.</div> >> </div> >> >> is the same construction as the second line: >> >> <div class="line-block"> >> <div class="line">Fun and frolic no more he knows;</div> >> </div> >> >> and they both will be indented the same amount (1.5em) which is >> what I mean by "it doesn't preserve" the indentation. >> >> Thanks for taking the time to look at this, Rod. >> > Roger, I send attach the .*rst and the .html* that my *rst2html* > generate. It's ok... I se it en *chrome* and look fine. See the code... > > Success > > Rod > > > > |
From: David G. <go...@py...> - 2011-02-26 23:06:35
|
On Sat, Feb 26, 2011 at 08:37, Roger Frank <rf...@fa...> wrote: > In the FAQ it states "Line blocks are designed for address blocks, verse, and other cases where line breaks are significant and must be preserved." The example shows poetry with indentation and the example works because the indentation is monotonically increasing. If I try that with something where indentation is significant, it doesn't preserve the > indent. Here is a poem from page [51] of http://www.gutenberg.org/files/35364/35364-h/35364-h.htm for example: > > | Summer wanes, the children are grown; > | Fun and frolic no more he knows; > | Robert of Lincoln’s a humdrum crone; > | Off he flies and we sing as he goes: > | Bob-o’link, bob-o’-link, > | Spink, spank, spink; > | When you can pipe that merry old strain, > | Robert of Lincoln, come back again. > | Chee, chee, chee. > > The last line will be indented exactly as the second line, ignoring that "Fun and frolic" starts with two leading spaces and "Chee, chee" starts with ten, as the poem was originally published. Is there a way not only respect the line break but the relative indentation shown in this example? This construction shows up often in the books that we are trying to produce based on RST. In the reST parser implementation, the preservation of indentation is relative, not absolute. The last line is only indented one level relative to its "parent", the line above. There's no concept of "indent X spaces", it's "indent X levels" -- and the last line has only one level of indent, relative to the second-last line. This is intentional, for two reasons: a simpler parser, and so that small differences in input indentation over a poem don't cause weird output indentation artifacts. There may be a way to work around this limitation (e.g. lines with intermediate indentation and backslash-escapes, see below), but there's currently no support for the indentation pattern desired. Supporting this pattern would require changes to the parser. I don't know if I'd be willing to make those changes though, because this level of precision would make other common cases behave strangely. Workarounds that make the extra indentation levels explicit: | Summer wanes, the children are grown; | Fun and frolic no more he knows; | Robert of Lincoln’s a humdrum crone; | Off he flies and we sing as he goes: | Bob-o’link, bob-o’-link, | Spink, spank, spink; | When you can pipe that merry old strain, | Robert of Lincoln, come back again. | \ | \ | \ | \ | Chee, chee, chee. | Summer wanes, the children are grown; | Fun and frolic no more he knows; | Robert of Lincoln’s a humdrum crone; | Off he flies and we sing as he goes: | Bob-o’link, bob-o’-link, | Spink, spank, spink; | When you can pipe that merry old strain, | Robert of Lincoln, come back again. | Chee, chee, chee. | \ | \ | \ | \ -- David Goodger <http://python.net/~goodger> |
From: <lu...@gm...> - 2011-02-26 20:58:06
|
El 26/02/11 13:40, Roger Frank escribió: > > On Feb 26, 2011, at 6:51 AM, lu...@gm... wrote: > >> I try the code of the poem... and I run *rst2pdf* and *rst2html* and it >> work fine. I think I don't know what you say when you say *it doesn't >> preserve...* > > I should have been more clear. The final line should align somewhere > under the word "Lincoln" to match how the poem was written and > originally typeset. Indentation matters in a poem; it conveys > meaning that should not be lost. > > Checking the HTML generated with rst2html, I see the final line: > > <div class="line-block"> > <div class="line">Chee, chee, chee.</div> > </div> > > is the same construction as the second line: > > <div class="line-block"> > <div class="line">Fun and frolic no more he knows;</div> > </div> > > and they both will be indented the same amount (1.5em) which is > what I mean by "it doesn't preserve" the indentation. > > Thanks for taking the time to look at this, Rod. > Roger, I send attach the .*rst and the .html* that my *rst2html* generate. It's ok... I se it en *chrome* and look fine. See the code... Success Rod -- *** Rodolfo H. González - Pigüé *** *** Usuario Full Software Libre *** ** Desarrollos de Software Libre ** ** Clave GPG en serv.: 4A63483C ** |
From: Roger F. <rf...@fa...> - 2011-02-26 17:06:58
|
On Feb 26, 2011, at 6:51 AM, lu...@gm... wrote: > I try the code of the poem... and I run *rst2pdf* and *rst2html* and it > work fine. I think I don't know what you say when you say *it doesn't > preserve...* I should have been more clear. The final line should align somewhere under the word "Lincoln" to match how the poem was written and originally typeset. Indentation matters in a poem; it conveys meaning that should not be lost. Checking the HTML generated with rst2html, I see the final line: <div class="line-block"> <div class="line">Chee, chee, chee.</div> </div> is the same construction as the second line: <div class="line-block"> <div class="line">Fun and frolic no more he knows;</div> </div> and they both will be indented the same amount (1.5em) which is what I mean by "it doesn't preserve" the indentation. Thanks for taking the time to look at this, Rod. |
From: <lu...@gm...> - 2011-02-26 13:53:32
|
El 26/02/11 10:37, Roger Frank escribió: > In the FAQ it states "Line blocks are designed for address blocks, verse, and other cases where line breaks are significant and must be preserved." The example shows poetry with indentation and the example works because the indentation is monotonically increasing. If I try that with something where indentation is significant, it doesn't preserve the > indent. Here is a poem from page [51] of http://www.gutenberg.org/files/35364/35364-h/35364-h.htm for example: > > | Summer wanes, the children are grown; > | Fun and frolic no more he knows; > | Robert of Lincoln’s a humdrum crone; > | Off he flies and we sing as he goes: > | Bob-o’link, bob-o’-link, > | Spink, spank, spink; > | When you can pipe that merry old strain, > | Robert of Lincoln, come back again. > | Chee, chee, chee. > > The last line will be indented exactly as the second line, ignoring that "Fun and frolic" starts with two leading spaces and "Chee, chee" starts with ten, as the poem was originally published. Is there a way not only respect the line break but the relative indentation shown in this example? This construction shows up often in the books that we are trying to produce based on RST. > ------------------------------------------------------------------------------ Hello Roger... I try the code of the poem... and I run *rst2pdf* and *rst2html* and it work fine. I think I don't know what you say when you say *it doesn't preserve...* Succsess Rod (ARG) -- *** Rodolfo H. González - Pigüé *** *** Usuario Full Software Libre *** ** Desarrollos de Software Libre ** ** Clave GPG en serv.: 4A63483C ** |
From: Roger F. <rf...@fa...> - 2011-02-26 13:37:23
|
In the FAQ it states "Line blocks are designed for address blocks, verse, and other cases where line breaks are significant and must be preserved." The example shows poetry with indentation and the example works because the indentation is monotonically increasing. If I try that with something where indentation is significant, it doesn't preserve the indent. Here is a poem from page [51] of http://www.gutenberg.org/files/35364/35364-h/35364-h.htm for example: | Summer wanes, the children are grown; | Fun and frolic no more he knows; | Robert of Lincoln’s a humdrum crone; | Off he flies and we sing as he goes: | Bob-o’link, bob-o’-link, | Spink, spank, spink; | When you can pipe that merry old strain, | Robert of Lincoln, come back again. | Chee, chee, chee. The last line will be indented exactly as the second line, ignoring that "Fun and frolic" starts with two leading spaces and "Chee, chee" starts with ten, as the poem was originally published. Is there a way not only respect the line break but the relative indentation shown in this example? This construction shows up often in the books that we are trying to produce based on RST. |
From: Uwe H. <uh...@gm...> - 2011-02-25 07:44:04
|
Hi Stefan, it not a problem of the rst-mode. This youtube video shows the way to create and modify tables. That's of course possible today. The problem is that the syntax of tables are different. http://www.youtube.com/watch?v=EQAd41VAXWo -uhe Am 24.02.2011 um 21:06 schrieb Stefan Merten: > Hi Uwe! > > Today Uwe Hentzschel wrote: >> are there a way to use the orgtbl-mode in docutils? > > I'm not familiar with orgtbl-mode but maintain rst.el. May be you can > tell us what you exactly mean by "using in docutils"? > > > Grüße > > Stefan |
From: Stefan M. <sm...@oe...> - 2011-02-24 20:06:47
|
Hi Uwe! Today Uwe Hentzschel wrote: > are there a way to use the orgtbl-mode in docutils? I'm not familiar with orgtbl-mode but maintain rst.el. May be you can tell us what you exactly mean by "using in docutils"? Grüße Stefan |
From: David G. <go...@py...> - 2011-02-24 14:20:08
|
On Thu, Feb 24, 2011 at 05:18, Uwe Hentzschel <uh...@gm...> wrote: > are there a way to use the orgtbl-mode in docutils? Nothing built-in that I know of. It looks like it's possible though (and contributions are welcome): http://www.gnu.org/software/emacs/manual/html_node/org/Tables-in-arbitrary-syntax.html -- David Goodger <http://python.net/~goodger> |
From: Uwe H. <uh...@gm...> - 2011-02-24 10:40:34
|
Hello list, are there a way to use the orgtbl-mode in docutils? -uhe -- Uwe Hentzschel uh...@gm... · PGP/GPG Key ID: 0xC1CDDDFC |
From: Alan G I. <ala...@gm...> - 2011-02-21 22:33:04
|
Why are literal blocks put in a quote environment? This is especially undesirable in slides. Can it be removed from all LaTeX writers? If not, can it be removed at least from rst2beamer? Thanks, Alan Isaac |
From: Timothy W. G. <tim...@si...> - 2011-02-18 23:09:58
|
Thanks Alan, I'll look into this. If anyone else has replied to my message on either of these lists, could you please resend? There has been a problem with my mail server in the last couple of days which may have caused your emails to be blocked. Thanks. Best regards, Tim Grove On 17/02/2011 1:30 PM, Alan G Isaac wrote: > On 2/17/2011 8:00 AM, Timothy W. Grove wrote: >> If this project is dead or even if it is still alive, how do I >> contribute code to the project? > I'm just a user, but I'll summarize what I've heard. > > Read http://docutils.sourceforge.net/docs/dev/repository.html > Get a Berlios account. > Then write to this list requesting commit privileges. > > I'd guess you'll want to fork the project if > no one knows how to contact Gunnar: just make > a sandbox/docfactory folder and work there, > unless someone posts a better suggestion. > > fwiw, > Alan Isaac > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. > |
From: Timothy W. G. <tim...@si...> - 2011-02-17 13:01:00
|
-------- Original Message -------- Subject: [Docutils-develop] DocFactory - still alive? Date: Wed, 16 Feb 2011 11:37:46 +0000 From: Timothy W. Grove <tim...@si...> To: doc...@li... Hello! I'm new to docutils and to this list, but have been programming with python and wxpython under Windows for the past few years. I was recently looking for a ReST editor and discovered the "DocFactory" snapshot listed on your website. Can anyone tell me if this project is still alive? I've tried contacting Gunnar Schwant at the email address attached to the project (g.s...@gm...) but the email was bounced back to me. If this project is dead or even if it is still alive, how do I contribute code to the project? I haven't added any new features (yet!), but I've downloaded the snapshot and have updated it to work with python 2.7, wxpython 2.9 and docutils 0.8 under Windows7. I've also tried it out with python 2.6, wxpython 2.9 and docutils 0.8 under Windows XP Pro. It may very well work under Linux, but I haven't had the chance to test that yet. How best can I share my work with the community? Best regards, Tim Grove ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Docutils-develop mailing list Doc...@li... https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list. |
From: Ben F. <ben...@be...> - 2011-02-01 09:22:41
|
Stefan Merten <sm...@oe...> writes: > I know rebinding keys has a high user impact. I hate it myself. But I > think there are enough reasons to do it and I do my best to make the > shift as smooth as possible. If someone comes up with a better > alternative which also complies with the Emacs conventions I'm happy > to implement this. Well, as the person doing the work you have more of a say in how it gets done than me. So, thank you for your effort and maintenance of the useful rst-mode :-) -- \ “Stop — Drive sideways.” —detour sign, Kyushu, Japan | `\ | _o__) | Ben Finney |
From: Stefan M. <sm...@oe...> - 2011-02-01 08:55:20
|
Hi Ben and all! Yesterday Ben Finney wrote: >> Key bindings changed >> ==================== >> >> According to Emacs standards the old key bindings left no room for new >> commands. I decided to rebind most keys to have two keys after the >> leading C-c so there is room for new commands. > > By my reading, that means most commands use three keys in total (leading > C-c plus two keys). Is that right? True. > If so, I don't see why that's been done. Isn't the point of a leading > C-c to make the key combinations not clash with Emacs built-ins? Surely > the C-c prefixed commands should be mostly two keys total, no? There is an Emacs internal standard that major modes should use only certain key bindings: * Sequences consisting of `C-c' followed by a control character or a digit are reserved for major modes. -- (elisp)Key Binding Conventions I'm trying to follow this convention. For major modes this means that there are only ~36 possible key bindings with a single key. Since for feature rich major modes like reST mode this is pretty few and leads to meaningless and thus hard to remember key combinations there needs to be another solution. Using two keys is the best I found so far. Also this is not unusual - see for instance the history of key bindings of MH-E. I know rebinding keys has a high user impact. I hate it myself. But I think there are enough reasons to do it and I do my best to make the shift as smooth as possible. If someone comes up with a better alternative which also complies with the Emacs conventions I'm happy to implement this. BTW: I'm also in the process of becoming a regular Emacs developer so I can maintain rst.el in the main Emacs development as well. But so far I tend to maintain the upstream version here since the feedback here is much better. Grüße Stefan |