From: Dave K. <dku...@re...> - 2008-02-27 01:01:21
|
G. Milde <milde <at> users.berlios.de> writes: > > You might ask the helpfull odtwriter author D. Kuhlman to look into the > problem. > > I assume (but did not test) that adding `visit_raw` and `depart_raw` > methods that just pass to the odtwriter class might solve your problem > (but of course not provide raw access to odtwriter output which is a more > complicated task). > OK. I'll try. But, I'm not sure I'll know what to do. Would someone actually try to pass through the "raw" XML code to be inserted into a ODF .odt file? Here is an example of what that might look like:: .. raw:: odt <text:list text:style-name="rststyle-bulletlist"> <text:list-item> <text:p text:style-name="rststyle-bulletitem"> Python does what you want it to do <text:span text:style-name="rststyle-emphasis"> most </text:span> of the time so that you only have to add extra characters <text:span text:style-name="rststyle-emphasis"> some </text:span> of the time. </text:p> </text:list-item> o o o Gack! Of course, you would have to remove all (most? some?) of the indentation and whitespace. Would someone really want to do that? Or, should I just add the visit_raw and depart_raw methods, but ignore any content. Basically, this is what odtwriter does now. It is printing out that "missing" warning message and ignoring the raw directive. - Dave |