Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

## docutils-develop — For developer discussions of the implementation.

You can subscribe to this list here.

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 Jan Feb Mar Apr (5) May (27) Jun (22) Jul (72) Aug (82) Sep (86) Oct (138) Nov (100) Dec (62) Jan (122) Feb (147) Mar (92) Apr (82) May (101) Jun (153) Jul (37) Aug (34) Sep (46) Oct (46) Nov (6) Dec (38) Jan (64) Feb (81) Mar (36) Apr (194) May (329) Jun (272) Jul (68) Aug (74) Sep (150) Oct (57) Nov (62) Dec (63) Jan (78) Feb (30) Mar (137) Apr (78) May (54) Jun (122) Jul (72) Aug (110) Sep (80) Oct (75) Nov (125) Dec (79) Jan (100) Feb (15) Mar (41) Apr (67) May (30) Jun (11) Jul (14) Aug (22) Sep (20) Oct (14) Nov (11) Dec (15) Jan (17) Feb (16) Mar (35) Apr (21) May (33) Jun (50) Jul (12) Aug (7) Sep (2) Oct (6) Nov (5) Dec (2) Jan (14) Feb (20) Mar (35) Apr (9) May (57) Jun (21) Jul (42) Aug (4) Sep (13) Oct (76) Nov (40) Dec (55) Jan (26) Feb (15) Mar (3) Apr (67) May (32) Jun (39) Jul (59) Aug (31) Sep (59) Oct (64) Nov (21) Dec (10) Jan (21) Feb (3) Mar (116) Apr (33) May (6) Jun (28) Jul (21) Aug (23) Sep (146) Oct (70) Nov (31) Dec (57) Jan (33) Feb (22) Mar (11) Apr (21) May (51) Jun (47) Jul (35) Aug (26) Sep (25) Oct (34) Nov (61) Dec (51) Jan (75) Feb (31) Mar (26) Apr (16) May (24) Jun (24) Jul (31) Aug (46) Sep (36) Oct (28) Nov (37) Dec (21) Jan (16) Feb (56) Mar (31) Apr (44) May (45) Jun (29) Jul (38) Aug (18) Sep (12) Oct (16) Nov (21) Dec (11) Jan (13) Feb (14) Mar (28) Apr (7) May (72) Jun (33) Jul (21) Aug Sep Oct Nov Dec
S M T W T F S

1
(1)
2

3
(1)
4
(5)
5
(4)
6
(3)
7
(7)
8

9

10
(1)
11
(2)
12

13
(1)
14

15
(1)
16
(1)
17
(1)
18
(1)
19

20

21

22

23
(1)
24
(2)
25

26
(1)
27
(4)
28
(1)
29
(4)
30
(5)

Showing results of 47

<< < 1 2 (Page 2 of 2)
 [Docutils-develop] Is stdlib inclusion still aspired? From: Guenter Milde - 2011-06-10 15:25:12 Dear Docutils devels, dear David, is it still the aim of Docutils to be included into the Python stdlib? How are the chances of this happen, in which time frame? Or, should/could we drop this aim from both, documentation and planning? I am asking, because the answer will influence the selection of a "recommended license" for people with reservations about (or legal problems with) giving up copyright and, more specific, an appropriate license for my contributions. Günter 
 [Docutils-develop] [ docutils-Patches-2903929 ] patch to make figure and table captions hyperlink targets From: SourceForge.net - 2011-06-07 15:18:35 Patches item #2903929, was opened at 2009-11-25 18:10 Message generated for change (Comment added) made by milde You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=2903929&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Terry Brown (terry_n_brown) Assigned to: Nobody/Anonymous (nobody) Summary: patch to make figure and table captions hyperlink targets Initial Comment: This patch makes figure and table captions hyperlink targets. It was difficult to set the \label{} inserted into the latex longtable in the required place (after the \caption, but not at the end where it added trailing garbage) so the patch assumes the id in get_caption(). Only HTML and (old)latex supported. ---------------------------------------------------------------------- >Comment By: Gnter Milde (milde) Date: 2011-06-07 15:18 Message: Thanks for the patch. However, I'd prefer manual labeling over the auto-labels for all figures and tables. Also, +++ docutils/docutils/writers/latex2e/__init__.py 2009-11-25 12:05:28.000000000 -0600 @@ -743,8 +743,9 @@ if not self.caption: return '' caption = ''.join(self.caption) + label = "\\label{%s}" % '-'.join(caption.lower().split()) will fail if the caption contains any special ("forbidden") characters like _^\$~ {[]} ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=2903929&group_id=38414 
 [Docutils-develop] [ docutils-Patches-2993967 ] Rendering DOM for tuple attributes From: SourceForge.net - 2011-06-07 15:07:32 Patches item #2993967, was opened at 2010-04-29 04:09 Message generated for change (Comment added) made by milde You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=2993967&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Stargaming (stargaming) Assigned to: Nobody/Anonymous (nobody) Summary: Rendering DOM for tuple attributes Initial Comment: When there are any attributes which have tuple attribute values DOM rendering fails because string interpolation receives a wrong number of arguments. It needs to be safeguarded against this case by carefully packing the values into a tuple beforehand. I attached a possible fix but this problem might crop up in other places as well. ---------------------------------------------------------------------- >Comment By: Gnter Milde (milde) Date: 2011-06-07 15:07 Message: Applied in revision 7054. Thanks. ---------------------------------------------------------------------- Comment By: Gnter Milde (milde) Date: 2011-06-07 15:07 Message: Thank you for your contribution! It has been checked in to the Docutils repository. You can download the most current snapshot from: http://docutils.sourceforge.net/docutils-snapshot.tgz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=2993967&group_id=38414 
 [Docutils-develop] [ docutils-Patches-3000541 ] Small mistake in frontmatter xform From: SourceForge.net - 2011-06-07 14:59:34 Patches item #3000541, was opened at 2010-05-12 16:11 Message generated for change (Comment added) made by milde You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3000541&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Berend (codeofarms) Assigned to: Nobody/Anonymous (nobody) Summary: Small mistake in frontmatter xform Initial Comment: DocTitle does not apply when there is a decoration in the tree. The proper test is there, but there's a typo or an surpluss condititional i think.. DocTtitle's apply() bails out when candidate_index() is none. node.first_child_not_matching_class gives that index, which is none or an index within the bounds of the node. So the test len(node) > (index + 1) can go I'd think (see patch). And otherwise it should be len(node) <= (index + 1) ---------------------------------------------------------------------- >Comment By: Gnter Milde (milde) Date: 2011-06-07 14:59 Message: Unfortunately, the author of the relevant code is no loger active. Could you provide a test that fails wihtout but works with the patch (Patch to the Docutils test suite and/or example document)? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422032&aid=3000541&group_id=38414 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Guenter Milde - 2011-06-07 14:49:59 On 2011-06-07, Alan G Isaac wrote: > On 6/7/2011 2:39 AM, Guenter Milde wrote: >> There is no consensus on a solution. > I posted simple solutions. But we did not agree on your suggestions beeing solutions. > This needs a fix. > Please treat the problem seriously. Please open an issue at the Docutils tracker. > Imo, it is broken enough to be a blocker. I don't think this should block a new release considering the 15 other bug reports, 11 feature requests and 11 patch submissions still open on http://sourceforge.net/tracker/?group_id=38414 . Günter 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Alan G Isaac - 2011-06-07 13:24:47 On 6/7/2011 9:10 AM, Alan G Isaac wrote: > The problem just happens to be showing up in the slide writers. Just to clarify: the problem "shows up" in every LaTeX write, but it only becomes truly pressing in the slide writers. In every LaTeX writer, if I change the styling of quotes, it changes the styling of all verbatim environments. This is clearly broken. Alan 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Alan G Isaac - 2011-06-07 13:11:01 On 6/7/2011 2:39 AM, Guenter Milde wrote: > The slide writers are not in docutils core. The code that is breaking them is in the core, and it is broken code. It misuses the quote environment, where misuse has a specific meaning: the code display cannot be fixed without breaking quote displays. The problem just happens to be showing up in the slide writers. That the actual writers are not in the core is irrelevant. > There is no consensus on a solution. I posted simple solutions. Before version 1.0, such changes should be easy. After 1.0 rigid stability will be expected. This needs a fix. Please treat the problem seriously. Imo, it is broken enough to be a blocker. Again, the code makes it possible for a user to request a specific environment for verbatim. The problem is that they are not given that environment. Instead they are given that environment nested in a quote environment. Just give the user the environment they request, and all will be well. This is the simple and salient solution. Trust the user to know what s/he is asking for! Alan 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Guenter Milde - 2011-06-07 06:39:42 On 2011-06-06, Alan G Isaac wrote: > On 6/6/2011 7:37 AM, Guenter Milde wrote: >> So the open points are > Why is the broken code display in LaTeX slide > writers not a open issue? Was it fixed? The slide writers are not in docutils core. There is no consensus on a solution. Günter 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Alan G Isaac - 2011-06-06 11:48:31 On 6/6/2011 7:37 AM, Guenter Milde wrote: > So the open points are Why is the broken code display in LaTeX slide writers not a open issue? Was it fixed? Alan 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Guenter Milde - 2011-06-06 11:37:37 On 6.06.11, engelbert gruber wrote: > releases can be done anytime except someone has a showstopper. > wishes what should go into the release are no stoppers, because they > would be pushed > into, which is more on unstable side IMHO. > small fixes not big packages or wishes, please :-) OK. So the open points are * sort out math for HTML * sort out the licensing problems (Docutils license policy is outdated, see bug 3304675: http://sourceforge.net/tracker/?func=detail&atid=422030&aid=3304675&group_id=38414 and docs/dev/policies.txt Is the sentence One of the goals of the Docutils project, once complete, is to be incorporated into the Python standard library. still true? If yes, * will the PSF accept "public domain" code? * should we "keep in stock" a Contributor Agreement from all authors contributing to the core under a free license? What is/shall be the preferred license for authors prefering to keep copyright or unable to give it up due to local copyright legislation? Günter 
 Re: [Docutils-develop] any objections to release 0.7.1 From: engelbert gruber - 2011-06-06 06:27:55 8< --- BIG SNIP --- >8 -- cut from both sides > Also, I'd like to finish the "sourcecode" (or just "source") directive > with syntax highlight via pygments. But maybe another release can be > done relatively fast... releases can be done anytime except someone has a showstopper. wishes what should go into the release are no stoppers, because they would be pushed into, which is more on unstable side IMHO. small fixes not big packages or wishes, please :-) engelbert -- http://darefoot.blogspot.com 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Guenter Milde - 2011-06-05 20:57:34 On 2011-06-05, engelbert gruber wrote: > or should it be 0.8 With the math-addition, yes. However, there are still issues with math in HTML: * using MathML with the html4css1 writer (XHTML 1.0/traditional) does not produce validable documents (there is no dtd with this combination) The html4strict writer can output documents conforming to ''; but it is still in the sandbox. * using the Math to HTML conversion from eLyXer solves this problem and also works with legacy browsers without MathML support. However, it requires loading a stylesheet which currently implies rather unhandsome config values (or command line args) like:: [html4css1 writer] stylesheet-path: /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/html4css1/html4css1.css, /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/html4css1/math.css, embed-stylesheet: yes Solutions could be: a) inclusion of the math stylesheet in the default html4css1.css +1 simple -1 blows up the default style for only sometimes required feature -2 math.css is requires CSS2 constructs. b) a list of directories to search for stylesheets +1 scales (providing also for simple selection of syntax highlighting styles for source code (see below)) +1 a well know concept (although the usual name "...path" cannot be used due to the existing stylesheet-path option which does something completely different). Two expansion variants: i. like the binary PATH and the PythonPath: expand relative filenames until a match is found. ii. like the "include" directive: expand only if the path argument is enclosed in [ ]. * the "MathJax" output variant seems the most stable and best supported. -1 requires java script -1 requires an internet connection (or local http server and MathJax installation). Maybe this should become the default anyway. Also, I'd like to finish the "sourcecode" (or just "source") directive with syntax highlight via pygments. But maybe another release can be done relatively fast... Günter 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Alan G Isaac - 2011-06-05 18:37:29 As discussed in detail about a month ago (and as far as I know it was not fixed), the current handling of verbatim text (putting it in a quote environment) breaks LaTeX slide writers. I would hope for a fix to this before the next release. (I suggested some fixes.) Alan Isaac 
 Re: [Docutils-develop] any objections to release 0.7.1 From: Arfrever Frehtes Taifersar Arahesis - 2011-06-05 17:48:00 Attachments: Message as HTML 2011-06-05 19:03:49 engelbert gruber napisał(a): > or should it be 0.8 I think that 0.8 would be more appropriate due to addition of many new features. -- Arfrever Frehtes Taifersar Arahesis 
 [Docutils-develop] any objections to release 0.7.1 From: engelbert gruber - 2011-06-05 17:03:56 or should it be 0.8 cheers 
 Re: [Docutils-develop] Tee encoding From: Guenter Milde - 2011-06-04 21:59:50 On 2011-06-04, engelbert gruber wrote: > hei everyone, > while on bugfixtour in the manpage-writer alltests.py did report :: > ====================================================================== > ERROR: test_functional.py: functional/tests/standalone_rst_manpage.py > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/Users/engelbert/projects/docutils/trunk/docutils/test/test_functional.py", > line 197, in test > diff = diff.encode(sys.stderr.encoding or 'ascii', 'replace') > AttributeError: Tee instance has no attribute 'encoding' > running functional alone reports the errors in manpage-writer. > my quick fix was :: > class Tee: > """Write to a file and a stream (default: stdout) simultaneously.""" > def __init__(self, filename, stream=sys.__stdout__): > self.file = open(filename, 'w') > self.stream = stream > + self.encoding = stream.encoding > def write(self, string): > self.stream.write(string) > self.file.write(string) > is this acceptable, ... ? Is where is this "Tee" class defined (originally)? If it's from Docutils, passing the stream.encoding is "the right thing". If it is from stdlib, we should drop the assumption that stdout always has an 'encoding' attribute and program defensively:: diff = diff.encode(getattr(sys.stderr, 'encoding', 'ascii'), 'replace') The same holds for the Tee class:: > + self.encoding = getattr(stream, 'encoding', None) Günter 
 [Docutils-develop] Tee encoding From: engelbert gruber - 2011-06-04 14:40:14 hei everyone, while on bugfixtour in the manpage-writer alltests.py did report :: ====================================================================== ERROR: test_functional.py: functional/tests/standalone_rst_manpage.py ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/engelbert/projects/docutils/trunk/docutils/test/test_functional.py", line 197, in test diff = diff.encode(sys.stderr.encoding or 'ascii', 'replace') AttributeError: Tee instance has no attribute 'encoding' running functional alone reports the errors in manpage-writer. my quick fix was :: class Tee: """Write to a file and a stream (default: stdout) simultaneously.""" def __init__(self, filename, stream=sys.__stdout__): self.file = open(filename, 'w') self.stream = stream + self.encoding = stream.encoding def write(self, string): self.stream.write(string) self.file.write(string) is this acceptable, ... ? revert if not. all the best engelbert 
 [Docutils-develop] [ docutils-Bugs-3219183 ] rst2man: Extra vertical space in definition list definition From: SourceForge.net - 2011-06-04 12:44:24 Bugs item #3219183, was opened at 2011-03-17 09:54 Message generated for change (Settings changed) made by grubert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Petri Lehtinen (akheron) Assigned to: engelbert gruber (grubert) Summary: rst2man: Extra vertical space in definition list definition Initial Comment: If the definition list term consists only of plain text, there's no vertical space between the term and the definition. However, if I add an emphasis, for example, to the term, then there's a vertical gap added. Here's the reStructuredText source: ==== test ==== ---------------------- testing rst2man output ---------------------- :Manual section: 1 :Manual group: User Commands CHAPTER TITLE ============= plain text term definition paragraph 1 definition paragraph 2 term with *emphasis* in it definition paragraph 1 definition paragraph 2 I also attached a screenshot that shows the problem. The manpage writer has some hacky logic in astext() that removes ".sp" directives (vertical gap) from the output in certain situations. It seems that when the definition list term has no other markup inside, the code works correctly, otherwise not. I'm saying that the logic is "hacky" because, in my opinion, the

removal logic in the html writer is better, as it looks at the doctree structure rather than the flat textual output. ---------------------------------------------------------------------- Comment By: engelbert gruber (grubert) Date: 2011-06-04 14:43 Message: Fixed; thanks for the bug report. You can download a current snapshot from: http://docutils.sf.net/docutils-snapshot.tgz ---------------------------------------------------------------------- Comment By: engelbert gruber (grubert) Date: 2011-06-03 17:43 Message: revision 7043 unifies but now even more vertical space ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:59 Message: Ah, I added the rst source as another attachment. ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:57 Message: It seems that whitespace in my rst example was removed. The "definition paragraph X" lines should be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 

 [Docutils-develop] [ docutils-Bugs-3219183 ] rst2man: Extra vertical space in definition list definition From: SourceForge.net - 2011-06-04 12:43:32 Bugs item #3219183, was opened at 2011-03-17 09:54 Message generated for change (Comment added) made by grubert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Petri Lehtinen (akheron) Assigned to: engelbert gruber (grubert) Summary: rst2man: Extra vertical space in definition list definition Initial Comment: If the definition list term consists only of plain text, there's no vertical space between the term and the definition. However, if I add an emphasis, for example, to the term, then there's a vertical gap added. Here's the reStructuredText source: ==== test ==== ---------------------- testing rst2man output ---------------------- :Manual section: 1 :Manual group: User Commands CHAPTER TITLE ============= plain text term definition paragraph 1 definition paragraph 2 term with *emphasis* in it definition paragraph 1 definition paragraph 2 I also attached a screenshot that shows the problem. The manpage writer has some hacky logic in astext() that removes ".sp" directives (vertical gap) from the output in certain situations. It seems that when the definition list term has no other markup inside, the code works correctly, otherwise not. I'm saying that the logic is "hacky" because, in my opinion, the

removal logic in the html writer is better, as it looks at the doctree structure rather than the flat textual output. ---------------------------------------------------------------------- Comment By: engelbert gruber (grubert) Date: 2011-06-04 14:43 Message: Fixed; thanks for the bug report. You can download a current snapshot from: http://docutils.sf.net/docutils-snapshot.tgz ---------------------------------------------------------------------- Comment By: engelbert gruber (grubert) Date: 2011-06-03 17:43 Message: revision 7043 unifies but now even more vertical space ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:59 Message: Ah, I added the rst source as another attachment. ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:57 Message: It seems that whitespace in my rst example was removed. The "definition paragraph X" lines should be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 

 [Docutils-develop] [ docutils-Bugs-3219183 ] rst2man: Extra vertical space in definition list definition From: SourceForge.net - 2011-06-04 12:36:27 Bugs item #3219183, was opened at 2011-03-17 09:54 Message generated for change (Settings changed) made by grubert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Petri Lehtinen (akheron) Assigned to: engelbert gruber (grubert) Summary: rst2man: Extra vertical space in definition list definition Initial Comment: If the definition list term consists only of plain text, there's no vertical space between the term and the definition. However, if I add an emphasis, for example, to the term, then there's a vertical gap added. Here's the reStructuredText source: ==== test ==== ---------------------- testing rst2man output ---------------------- :Manual section: 1 :Manual group: User Commands CHAPTER TITLE ============= plain text term definition paragraph 1 definition paragraph 2 term with *emphasis* in it definition paragraph 1 definition paragraph 2 I also attached a screenshot that shows the problem. The manpage writer has some hacky logic in astext() that removes ".sp" directives (vertical gap) from the output in certain situations. It seems that when the definition list term has no other markup inside, the code works correctly, otherwise not. I'm saying that the logic is "hacky" because, in my opinion, the

removal logic in the html writer is better, as it looks at the doctree structure rather than the flat textual output. ---------------------------------------------------------------------- Comment By: engelbert gruber (grubert) Date: 2011-06-03 17:43 Message: revision 7043 unifies but now even more vertical space ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:59 Message: Ah, I added the rst source as another attachment. ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:57 Message: It seems that whitespace in my rst example was removed. The "definition paragraph X" lines should be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 

 [Docutils-develop] [ docutils-Bugs-3219183 ] rst2man: Extra vertical space in definition list definition From: SourceForge.net - 2011-06-03 15:43:43 Bugs item #3219183, was opened at 2011-03-17 09:54 Message generated for change (Comment added) made by grubert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Petri Lehtinen (akheron) Assigned to: engelbert gruber (grubert) Summary: rst2man: Extra vertical space in definition list definition Initial Comment: If the definition list term consists only of plain text, there's no vertical space between the term and the definition. However, if I add an emphasis, for example, to the term, then there's a vertical gap added. Here's the reStructuredText source: ==== test ==== ---------------------- testing rst2man output ---------------------- :Manual section: 1 :Manual group: User Commands CHAPTER TITLE ============= plain text term definition paragraph 1 definition paragraph 2 term with *emphasis* in it definition paragraph 1 definition paragraph 2 I also attached a screenshot that shows the problem. The manpage writer has some hacky logic in astext() that removes ".sp" directives (vertical gap) from the output in certain situations. It seems that when the definition list term has no other markup inside, the code works correctly, otherwise not. I'm saying that the logic is "hacky" because, in my opinion, the

removal logic in the html writer is better, as it looks at the doctree structure rather than the flat textual output. ---------------------------------------------------------------------- >Comment By: engelbert gruber (grubert) Date: 2011-06-03 17:43 Message: revision 7043 unifies but now even more vertical space ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:59 Message: Ah, I added the rst source as another attachment. ---------------------------------------------------------------------- Comment By: Petri Lehtinen (akheron) Date: 2011-03-17 09:57 Message: It seems that whitespace in my rst example was removed. The "definition paragraph X" lines should be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=3219183&group_id=38414 

 Re: [Docutils-develop] --debug crashes for non-ASCII input files From: Stefan Merten - 2011-06-01 17:52:48 Attachments: Message as HTML Hi Günter! 3 weeks (22 days) ago Guenter Milde wrote: > On 2011-04-25, Stefan Merten wrote: >> Last week (8 days ago) Guenter Milde wrote: >>>> 3 days ago Guenter Milde wrote: >>> I suppose the problem are "implicit" unicode -> str conversions that >>> use the "ASCII, strict" encoding. > >> I thought that, too. But some tests on the command line showed this is >> not the case. It's really the print which causes the problem. >> Probably it's there where there is the conversion to ASCII which >> fails. > > With the new ErrorOutput class, error reporting should be failsafe now in > both, Python2 and Python3. Could you test? Sorry for the delay and thanks for the work. My initial case now works with r7032 :-) . Grüße Stefan 

Showing results of 47

<< < 1 2 (Page 2 of 2)