gmane.text.docutils.devel

[ docutils-Bugs-2350865 ] Empty block commentscause wrong syntax coloring in Emacs

SourceForge.net — 2008-11-26T13:34:56

Bugs item #2350865, was opened at 2008-11-26 14:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2350865&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: Jérôme M. Berger (voiz) Assigned to: Nobody/Anonymous (nobody) Summary: Empty block comments cause wrong syntax coloring in Emacs Initial Comment: The following example will be colored entirely as if it were a block comment, including the normal text line at the end: ====================8<-------------------- .. First comment paragraph .. .. Second comment paragraph Normal text -------------------->8==================== This is with the ``rst.el`` from version 0.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2350865&group_id=38414 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Docutils-develop mailing list Docutils-develop< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list.

Python 3.0 porting

Georg Brandl — 2008-11-25T20:34:32

Hi, in order to get more people porting and testing things on Python 3000, I want to start by getting Sphinx running on it. That requires having Docutils. I'd like to port the Docutils to Python 3000. Assuming you all are OK with that, how should we organize that? Since the Docutils have quite strict compatibility requirements, it is very probably not sensible to use the "on codebase from which the 3000 version is converted by 2to3" strategy. Therefore, I propose the Python model: a separate branch in the repository into which new changes in the trunk are merged with the svnmerge tool. If that's fine, should the branch be in /branches/, or in /trunk/sandbox/? cheers, Georg ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

website updates: SF shell is back

David Goodger — 2008-11-25T20:06:39

It looks like SourceForge has re-enabled their shell service, details below. Should we use it, or stick to the local-build plan for website updates?

Acronym for Docutils?

Guenter Milde — 2008-11-11T08:12:05

Is there an abbreviation for Docutils (like DU, say)? (I am looking for a prefix for docutils specific LaTeX commands.) Günter ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Docutils-develop mailing list Docutils-develop< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list.

{ODF} Missing features in odtwriter

Stefan Merten — 2008-11-10T10:25:50

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list! < at >DaveK: I sent you this before more as a reminder for myself. But since we wanted to move the discussion to the list I'll put it here. May be there is an idea from someone here. The following features I consider missing / need improvement in odtwriter. * Mapping definition lists to ODF I looked also for something like definition lists in ODF but there seems to be no such beast indeed. At the moment the definition is done using `blockindent`. May be we could improve if we create a special style instead of `blockindent`. So users can redirect it to something which suits them better. * ``.. sectnum::`` / automatic numbering must be suppressed Numbering is better left to OOo. May be with a command line option controlling the exact behavior. * ``.. contents::`` must be suppressed or handled properly One option would be to recognize the directive and create the respective ODF field. But I don't know the details of how to do this right. May be should also come with a command line option controlling the exact behavior. * ``.. target-notes::`` "core dumps" A ``.. target-notes::`` directives stops the whole program with an error. Did no investigation so far. (I didn't try this for some time now - may be it's gone.) Grüße Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 iQCVAwUBSRgMLgnTZgC3zSk5AQJJLQP/RLu4yecIAjJXhOxUfiPYJ1CKMJhlZahX 1taXkltWOBvKNEo2OUbdOQ4BVeNwpaF4PW2m+OcwH76DxTw19EL//bYAZM37Ol+n znL6XYGhJw4SS9/SmXZn38Jw+RR+lCnl8mYvVDRuHZiKZCaElxzaBUpoUkXInWmC UjCOWZNh45E= =k+77 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

LaTeX writer patch: inline

Guenter Milde — 2008-11-04T11:16:36

The current implementation of custom roles in the latex2e writer produces LaTeX code that fails to compile if no special stylesheet is provided. IMO, this is a bug. E.g. the LaTeX file produced by the functional test for latex2e fails to compile! The patch below introduces a "dispatcher makro" ``\inlinenode`` that calls class-name specific LaTeX macros, but **only if they exist**. I.e.:: .. role:: custom3 :class: special custom3 exceptional Special :custom3:`interpreted text`. becomes:: Special \inlinenode{special,custom,exceptional}{interpreted text}. wich expands to the equivalent of:: Special {\docutilsrolespecial \docutilsrolecustom \docutilsroleexceptional interpreted text}. with the special feature that unknown ``docutilsrole*`` commands are silently ignored. Discussion ========== Backwards compatibility ----------------------- * Is this feature used at all (under LaTeX)? * Do we need to care for backwards compatibility? How far (weighting improved interface against full compatibility)? Naming ------ * Is there an abbreviation for Docutils (like DU, say)? * Should the dispatcher command be called \inlinenode, \DUinlinenode or \DUspan? * Could we shorten \docutilsrole* to e.g. \DUrole* or use the more generic name \DUclass*? Preamble "noise" ---------------- The patch introduces the concept of "fallback" definitions, that can be overwritten by defining in the style sheet with ``\newcommand`` (as opposed to ``\renewcommand``). This allows to make the insertion of the fallback definition optional without errors if the stylesheet has a custom version (in a future step). Multiple classes ---------------- The current implementation translates the above example to Special \docutilsrolespecial{\docutilsrolecustom{% \docutilsroleexceptional{interpreted text}}}. It cannot be reproduced with reasonable effort. * is this nesting compatible with the "order does not matter" concept for classes in CSS? * LaTeX styling uses different commands for macros with or without arguments, e.g. {\boldface foo} <--> \textbf{foo} would it be better to put the node content in an extra pair of braces to be backwards compatible in case of just one class argument? ({\boldface foo} and {\boldface {foo}} result in the same PDF output.) Günter Exec: svn 'diff' '__init__.py' 2>&1 Dir: /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/latex2e/ Index: __init__.py =================================================================== --- __init__.py(Revision 5680) +++ __init__.py(Arbeitskopie) < at >< at > -366,6 +366,22 < at >< at > ] } +latex_fallbacks = {} +latex_fallbacks['inlinenode'] = r""" +\makeatletter +\providecommand{\inlinenode}[2]{% + {% group ("span") to limit the scope of styling commands + \< at >for\node< at >class< at >name:=#1\do{% + \ifcsname docutilsrole\node< at >class< at >name\endcsname% + \csname docutilsrole\node< at >class< at >name\endcsname% + \fi% + }% + #2% node content + }% close "span" +} +\makeatother""" + + class DocumentClass: """Details of a LaTeX document class.""" < at >< at > -761,6 +777,12 < at >< at > self.head_prefix.append(open(stylesheet).read()) else: self.head_prefix.append(self.stylesheet % (stylesheet)) + + # Fallback|default definitions for docutils-specific latex objects + # (Ignored if there is a definition in the stylesheet) + # TODO insert only required commands and environments + self.head_prefix.append(latex_fallbacks['inlinenode']) + # hyperref after stylesheet self.head_prefix.append( self.linking % ( self.colorlinks, self.hyperlink_color, self.hyperlink_color)) < at >< at > -2207,14 +2229,12 < at >< at > self.body.append('\n') def visit_inline(self, node): # titlereference - classes = node.get('classes', ['Unknown', ]) - for cls in classes: - self.body.append( '\\docutilsrole%s{' % cls) - self.context.append('}'*len(classes)) - + classes = node.get('classes', []) + self.body.append(r'\inlinenode{%s}{' %','.join(classes)) + def depart_inline(self, node): - self.body.append(self.context.pop()) - + self.body.append('}') + def visit_rubric(self, node): self.body.append('\\rubric{') self.context.append('}\n') ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Docutils-develop mailing list Docutils-develop< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list.

autoindex on sourceforge

engelbert gruber — 2008-11-02T11:40:43

hello sourceforge seams to have disabled autoindexing therefore one gets a 403 for "http://docutils.sourceforge.net/sandbox/". does anyone know how to enable it, or do i have to generate index.html files. cheers ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

change of development status on sourceforge

engelbert gruber — 2008-11-02T11:10:04

Hello i removed the status: planning and alpha and changed to stable hope this is ok for everybody. all the best ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

rst2odt questions

m h — 2008-10-24T04:52:06

dkuhlman/smerten- Since you both appear to be hacking on the .odt backend, could you explain the logic for styles? What styles do you put in styles.xml and what you you generate locally in content.xml? Isn't there a combinatoric explosion with say a big, right aligned bold monospaced, etc font? How do you handle that? Also what are you using to test? I'm doing manual inspection on small docs right now, but I think I want to throw in into a regression suite. I'm leaning towards doing it all in unittest, but would be curious to have input from you. There appear to be some differences between odt and odp, lists being one example that sticks out. cheers, -matt ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

preparing the latex2e writer for the code-blockdirective

Guenter Milde — 2008-10-21T16:02:27

The following patch is (IMO) necessary to make latex2e fit for the upcoming code-block directive. latex2e writer patch ******************** Currently, an inline node with a class unknown to the latex writer like:: def is converted to a function:: \docutilsroleNone{def} which is not defined in the preamble and hence leads to an error if the documents is translated to PDF without a special stylesheet. The missing feature is a "failsave" handling of class information: In HTML, the semantic syntax markup can be simply stored in a class argument to a element. It can be used by the CSS stylesheet for syntax highlight and is simply ignored if no CSS rule for the given class exists. LaTeX does not have a "class" attribute, so an emulation of this concept is needed. Proposal ======== The attached patch provides a "stylable" command with the fallback definition:: \newcommand{\inlinenode}[2]{#2} which typesets the content without any styling. Example ------- .. role:: bold-italic The custom role ``.. role:: bold-italic`` is used like :bold-italic:`bold italic inline-text` in a normal paragraph. It translates to ``\inlinenode{bold-italic}{bold italic inline-text}`` which is typeset without any markup with the fallback definition. However, a style-sheet with the definition:: \renewcommand{\inlinenode}[2]{% \ifthenelse{\equal{#1}{bold-italic}}% {\textit{\textbf{#2}}}% {#2}% } will style the custom role as bold-italic. Test ~~~~ .. raw:: latex \renewcommand{\inlinenode}[2]{% \ifthenelse{\equal{#1}{bold-italic}}% {\textit{\textbf{#2}}}% {#2}% } The custom role ``.. role:: bold-italic`` is used like :bold-italic:`bold italic inline-text` in a normal paragraph. It is typeset in bold-italic now. Extensions ---------- If there are several distinct roles (or other occurences of "classified" inline nodes, the re-definition would be:: \renewcommand{\inlinenode}[2]{% \ifthenelse{\equal{#1}{bold-italic}}% {\textbf{\textit{#2}}}% {}% empty else clause \ifthenelse{\equal{#1}{bold-sans}}% {\textbf{\textsf{#2}}}% {}% % ... other tests \ifthenelse{\equal{#1}{small-caps}}% {\textsc{#2}}}% {#2}% fallback as else clause for last test } A test in a comma-separated list of class names is possible as well. Like in the CSS case, the order of the class arguments does not matter:: \renewcommand{\inlinenode}[2]{% \makeatletter \< at >for\class< at >name:=#1\do{% \ifthenelse{\equal{\class< at >name}{bold-italic}}% {\textbf{\textit{#2}}}% {}% empty else clause } Role extensions =============== .. role:: ibold (emphasis) The custom role ``.. role:: ibold (italic)`` (based on the emphasis rule) is used like :ibold:`bold emphatic inline-text` in a normal paragraph. It translates to ``\emph{bold emphatic inline-text}`` (i.e. ignoring the class argument) and cannot be styled. Fixing this would require patching all standard inline roles to wrap the content in \inlinenode commands. Is it OK to apply this patch? Günter Dir: /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/latex2e/ Index: __init__.py =================================================================== --- __init__.py(Revision 5680) +++ __init__.py(Arbeitskopie) < at >< at > -362,6 +362,7 < at >< at > '\\newcommand{\\rubric}[1]' '{\\subsection*{~\\hfill {\\it #1} \\hfill ~}}\n' '\\newcommand{\\titlereference}[1]{\\textsl{#1}}\n' + '\\newcommand{\\inlinenode}[2]{#2}\n' '% end of "some commands"\n', ] } < at >< at > -2207,14 +2208,12 < at >< at > self.body.append('\n') def visit_inline(self, node): # titlereference - classes = node.get('classes', ['Unknown', ]) - for cls in classes: - self.body.append( '\\docutilsrole%s{' % cls) - self.context.append('}'*len(classes)) - + classes = node.get('classes', []) + self.body.append(r'\inlinenode{%s}{' %','.join(classes)) + def depart_inline(self, node): - self.body.append(self.context.pop()) - + self.body.append('}') + def visit_rubric(self, node): self.body.append('\\rubric{') self.context.append('}\n') ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Docutils-develop mailing list Docutils-develop< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list.

LaTeX writer patch: inline

Guenter Milde — 2008-10-13T11:54:10

The latex2e writer currently translates nodes with a class argument (e.g. produced by a custom role or the upcoming syntax-highlighting souce-code directive) to specific LaTeX macros, e.g.:: \docutilsrolevery{\docutilsrolespecial{interpreted text}} which allows a style sheet to define this macro but leaves the document uncompilable without a special style sheet. OTOH, the doctree guide says: The classes attribute's contents should be ignorable. Writers that are not familiar with the variant expressed should be able to ignore the attribute. -- /docutils/docs/ref/doctree.html#classes The patch below lets the latex2ewriter produce code that 1. compiles without error ignoring the unknown classes 2. allows styling of the marked-up code in a custom stylesheet (using \renewcommand and \ifthen{#1} ... branches). It would require an adaption of docutils/test/functional/expected/standalone_rst_latex.tex (which currently fails to compile with latex). Günter Dir: /home/milde/Code/Python/docutils-svn/docutils/docutils/writers/latex2e/ Index: __init__.py =================================================================== --- __init__.py(Revision 5671) +++ __init__.py(Arbeitskopie) < at >< at > -355,6 +355,7 < at >< at > '\\newcommand{\\rubric}[1]' '{\\subsection*{~\\hfill {\\it #1} \\hfill ~}}\n' '\\newcommand{\\titlereference}[1]{\\textsl{#1}}\n' + '\\newcommand{\\docutilsinline}[2][]{#2}\n' '% end of "some commands"\n', ] } < at >< at > -2196,13 +2197,11 < at >< at > def visit_inline(self, node): # titlereference classes = node.get('classes', ['Unknown', ]) - for cls in classes: - self.body.append( '\\docutilsrole%s{' % cls) - self.context.append('}'*len(classes)) - + self.body.append(r'\docutilsinline[%s]{' %','.join(classes)) + def depart_inline(self, node): - self.body.append(self.context.pop()) - + self.body.append('}') + def visit_rubric(self, node): self.body.append('\\rubric{') self.context.append('}\n') ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Docutils-develop mailing list Docutils-develop< at >lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/docutils-develop Please use "Reply All" to reply to the list.

rst2odp

m h — 2008-10-08T17:57:41

Hey Folks- I've been wanting rst2odp for a long time. I like the s5 and bruce frontends (and have used both for presenting), but am beginning to think that impress (and open standards) are the way to go. Anyway enough chit chat. I had an itch and am now scratching. Thanks to the work by rst2odt, which inspired me, now I have the start of something. The following somewhat works: * titles * basic text * lists * images I'd like to get this into the sandbox and continue dev there, with others who are interested in this. I'm interested in taking this to the point where it can render my talk from pycon [0] (I used s5 at the conference. For the handout/slides I used latex backend. Note that the latex backend doesn't/didn't at that time support code/pygments). If it get's to that point I'll be happy. Also I've some questions about testing, but those can wait for another time... cheers, -matt 0 - http://panela.blog-city.com/pycon_2008_managing_complexity_slides.htm ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

[ docutils-Bugs-2152541 ] double-quotes insidecode block get translated by htmlwriter

SourceForge.net — 2008-10-08T03:20:22

Bugs item #2152541, was opened at 2008-10-07 22:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2152541&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: Jeet Sukumaran (jeetsukumaran) Assigned to: Nobody/Anonymous (nobody) Summary: double-quotes inside code block get translated by htmlwriter Initial Comment: The following rst source: This is a sample of Python code:: print "Hello, world" Results in the following HTML: u'

This is a sample of Python code:

\nprint "Hello, world"\n

\n' Using 'core.publish_parts(s, writer_name="html")["fragment"]'. Because the code is in a "

" block, then the '"' does not get rendered into quote characters by browsers, resulting in very messed up quote. Basically, quotes and other special characters should not get translated into their HTML counterparts if the text is in a code block.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2152541&group_id=38414

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

Fw: Creating a file-like object.

Sebastian Noack — 2008-10-06T14:14:54

------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Creating a file-like object.

Sebastian Noack — 2008-09-29T16:13:07

Adding rst2odt/odtwriter to the queue for thenext release

Dave Kuhlman — 2008-09-29T17:52:00

I'd like rst2odt/odtwriter to be considered for the the next release of Docutils. Currently, when I run rst2odt.py on demo.txt, it successfully runs; it produces an output file that looks good to me; and it shows me that rst2odt does not support citations and sidebars. Are these required for inclusion? I suppose that I am asking how we decide whether to include it. I suspect that there needs to be some demand for it and that it needs to pass certain tests. I believe that David (G.) said that the ability to process demo.txt without failing was a requirement, so it has passed that test. So, is there anything I can do to move this forward or at least have it considered? And, by the way, we will have the same questions with rst2pdf, which I'm also hoping will be included in the Docutils distribution, soon. - Dave ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

I was thinking that reST would be just the thingfor thisapplication...

Martin Maney — 2008-09-22T15:09:42

How to describe it? I need a not too user-unfriendly format for entering items that are mostly a scrap of descriptive text and a hypertext link. The tricky bit is that this is part of a system that has a catalog of URLs, and I want to allow items to refere to cataloged links by name - so that when a URL changes, there's one place to fix it, or to redirect to a "sorry, this resource is no longer available" (and, in my dreams, maybe suggest alternatives... but that's only a dream for now). I've been trying to avoid reinventing this wheel, but the first few things I looked at didn't do well on the user ratings. reST's hyperlink syntax has always seemed kind of funky to me, but my users seem to like it. The problem then would be that this seems to call for a transform, and it's probably quite simple... except that the documentation of that area is so incomplete as to be useless. I've groveled the code enough to decide that if I have to go that route it truly will be simpler to reinvent the wheel once again (this so is a Pythonic trope, isn't it?). I'd lose the other things that reST provides, but frankly they're not of great importance for items, at least we currently envision using them. So sorry, but code is really crappy documentation, even when the trees aren't lost in an ocean of do-nothing classes (was this designed by someone with extensive Jave experience, perhaps?). From what I've been able to make out, dimly, I believe I need to 1) get the item parsed into nodes - that turns out to be easier than the __doc__ suggested, just publish_doctree(item_string) (okay, with stderr redirected if my extended syntax isn't quite legal reST form). 2) I think I can see how to walk the tree - this might actually be easiest if I do use an invalid syntax, since then I can ignore everything but problematic nodes, and I then get the source text from their single Text child. Here I encounter a problem - how the heck do I construct a proper reference node to replace the problematical? After tracing all the twisted class inheritance, all I see in the constructor is the raw source, a text item, and the who knows what they should/can hold *children and **attributes. ...or is that not a reasonable way to get there? I did think at first that it might be handled during parsing, but that part of the process seemed even less well-lit. Okay, that's enough questions for now - I'm already basing most of this on guesswork in lieu of documentation. All suggestions, pointers to more obscure docs, examples of similar work appreciated. And contrary to my usual preferences, please do CC me on replies as I'm not hooked up to the list. Thanks!

Include roman.py as a submodule?

Georg Brandl — 2008-09-12T17:20:54

Just a suggestion for the next release: why not include roman.py as a submodule of docutils? There are lots of problems people have with the status quo, where roman is distributed and installed as a separate toplevel module... Georg

[ docutils-Support Requests-2100641 ] not oninternap mirror (San Jose)

SourceForge.net — 2008-09-08T17:23:38

Support Requests item #2100641, was opened at 2008-09-08 10:23 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422031&aid=2100641&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: Install Problem (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nathan Youngman (nyoungman) Assigned to: Nobody/Anonymous (nobody) Summary: not on internap mirror (San Jose) Initial Comment: The default mirror SF picks for me is internap in San Jose. Seems the 0.5.0 download isn't there, and gives an error. I originally got this error while trying to easy_install Sphinx. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422031&aid=2100641&group_id=38414 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Patch [ 1878977 ] make_id(): deaccent characters

engelbert gruber — 2008-09-01T14:26:21

hello, any objections to apply this patch --- docutils/nodes.py (revision 5503) +++ docutils/nodes.py (working copy) < at >< at > -1766,13 +1766,183 < at >< at > .. _HTML 4.01 spec: http://www.w3.org/TR/html401 .. _CSS1 spec: http://www.w3.org/TR/REC-CSS1 """ - id = _non_id_chars.sub('-', ' '.join(string.lower().split())) + if isinstance(string, unicode): + id = string.lower().translate(_non_id_translate) + else: + try: + id = string.decode().lower().translate(_non_id_translate) + except UnicodeDecodeError: + id = string.lower() + id = _non_id_chars.sub('-', ' '.join(id.split())) id = _non_id_at_ends.sub('', id) return str(id) _non_id_chars = re.compile('[^a-z0-9]+') _non_id_at_ends = re.compile('^[-0-9]+|-+$') +_non_id_translate = { + # From Latin-1 Supplement + 0x00df: u'ss', # sharp s + 0x00e0: ord('a'), # a with grave and 180 other mappings is the test ``isinstance(string, unicode)`` required ? tests pass and i would extend test_nodes.test_make_id a little cheers ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

[ docutils-Bugs-2080572 ] RFE: document links

SourceForge.net — 2008-08-28T13:51:48

Bugs item #2080572, was opened at 2008-08-28 09:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2080572&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: Matthew Leingang (leingang) Assigned to: Nobody/Anonymous (nobody) Summary: RFE: document links Initial Comment: Metadata is good. Much in the same way that ReST authors can specify metadata that gets converted to HTML meta elements by rst2html, they should be able to use document links as specified in http://www.w3.org/TR/html4/struct/links.html#edef-LINK One way to implement this would be a copy of the meta directive, with an interface something like .. link:: :next type=text/html: chapter3.html :next type=text/plain: chapter3.txt :previous type=text/html: chapter1.html :previous type=text/html dir=rev: chapter :index type=text/html: index.html producing in the HTML document Types could be inferred from the URI by the writer, possibly. Another possible interface could a new directive for each of the linktypes described in http://www.w3.org/TR/html4/types.html#type-links such as: .. link-next:: chapter3.html :type: text/html .. link-next:: chapter3.txt :type: text/plain .. link-previous:: chapter1.html .. link-previous:: chapter3.html :direction: rev .. link-alternate:: chapter2.pdf :type: application/pdf :media: print This has the advantage of looking more like some of the other ReST metadata directives and less like a duplication of HTML. In this case, there should be a mechanism for defining custom linktypes, too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=422030&aid=2080572&group_id=38414 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/