From: Matt C. <mat...@gm...> - 2009-07-26 02:06:32
|
Hello, docutils developers. I'm working on a writer for Texinfo format files, which is in the very early stages, but is progressing well enough. I've been trying to figure out how to unit test my translator class, subclassed from NodeVisitor. I'm using the parse tree returned by the rst reader's parser.parse() function. The trouble is, parser.parse() seems to return a different tree than is generated by core.publish_*. If I print the tree I get from calling parser.parse() directly, I get this: <document source="rst_test_utils"> <section ids="title" names="title!"> <title> Title! </title> <section ids="subtitle" names="subtitle"> <title> Subtitle </title> </section> </section> </document> but the tree that gets given to my writer.translate() function is: <document ids="title" names="title!" source="samples/subtitles.rst" title="Title!"> <title> Title! </title> <subtitle ids="subtitle" names="subtitle"> Subtitle </subtitle> </document> I presume I've got some error with the way I'm setting up the parser. Can anyone let me know what I'm doing wrong? The code where I'm setting up the parser is here: http://tinyurl.com/kofgdd You can browse the rest of the code here (on the web, you don't need git): http://repo.or.cz/w/rst2info.git Please note: I'm not subscribed to this list, so I'd appreciate it if you could CC me on any responses. Thanks in advance, Matt |
From: <gr...@us...> - 2009-07-26 19:36:28
|
On Sun, 26 Jul 2009, Matt Curtis wrote: > Hello, docutils developers. > > I'm working on a writer for Texinfo format files, which is in the very > early stages, but is progressing well enough. > > I've been trying to figure out how to unit test my translator class, > subclassed from NodeVisitor. I'm using the parse tree returned by the > rst reader's parser.parse() function. > > The trouble is, parser.parse() seems to return a different tree than > is generated by core.publish_*. If I print the tree I get from calling > parser.parse() directly, I get this: > > <document source="rst_test_utils"> > <section ids="title" names="title!"> > <title> > Title! > </title> > <section ids="subtitle" names="subtitle"> > <title> > Subtitle > </title> > </section> > </section> > </document> > > but the tree that gets given to my writer.translate() function is: > > <document ids="title" names="title!" source="samples/subtitles.rst" > title="Title!"> > <title> > Title! > </title> > <subtitle ids="subtitle" names="subtitle"> > Subtitle > </subtitle> > </document> > > I presume I've got some error with the way I'm setting up the > parser. Can anyone let me know what I'm doing wrong? > > The code where I'm setting up the parser is here: > http://tinyurl.com/kofgdd > > You can browse the rest of the code here (on the web, you don't need > git): http://repo.or.cz/w/rst2info.git i assume the you have transforms in the processing chain Transforms related to the front matter of a document or a section (information found before the main text): - `DocTitle`: Used to transform a lone top level section's title to the document title, promote a remaining lone top-level section's title to the document subtitle, and determine the document's title metadata (document['title']) based on the document title and/or the "title" setting. - `SectionSubTitle`: Used to transform a lone subsection into a subtitle. - `DocInfo`: Used to transform a bibliographic field list into docinfo elements. http://docutils.sourceforge.net/docs/ref/transforms.html cheers -- |
From: Matt C. <mat...@gm...> - 2009-07-28 14:21:15
|
On Mon, Jul 27, 2009 at 5:36 AM, <gr...@us...> wrote: > i assume the you have transforms in the processing chain Ah - that was what I was looking for. Thanks a lot, my tests work great now. cheers, Matt |