From: Nicola L. <ni...@te...> - 2005-12-19 18:16:21
|
> By the way, the HTML writer is quite messy. Maybe we should refactor it > to generate a tree of XHTML elements and then dump that tree? That > would make a lot of things easier. Talking about the HTML writer, I just made a few mods to it. I am *not* proposing a patch to be applied to html4css1.py , I'll only use it as basis for discussion. @@ -721,7 +721,7 @@ def visit_field_list(self, node): self.body.append(self.starttag(node, 'table', frame='void', - rules='none', + rules='rows', CLASS='docutils field-list')) self.body.append('<col class="field-name" />\n' '<col class="field-body" />\n' I wanted thin lines between fields in a field list. It looks like adding the "frame='void'" and "rules='none'" to the table tag prevents any border styling by the CSS. Is there any way to get no borders via the CSS, so to avoid adding such attributes? The same thing is done in the visit methods for "citation", "docinfo", "footnote", and "option_list". @@ -764,8 +764,7 @@ def depart_footer(self, node): start = self.context.pop() - footer = [self.starttag(node, 'div', CLASS='footer'), - '<hr class="footer" />\n'] + footer = [self.starttag(node, 'div', CLASS='footer')] footer.extend(self.body[start:]) footer.append('\n</div>\n') self.footer.extend(footer) @@ -842,7 +841,7 @@ start = self.context.pop() header = [self.starttag(node, 'div', CLASS='header')] header.extend(self.body[start:]) - header.append('\n<hr class="header"/>\n</div>\n') + header.append('\n</div>\n') self.body_prefix.extend(header) self.header.extend(header) del self.body[start:] I want no horizontal rules in the header nor in the footer. I tried setting "visibility: hidden" in the CSS and it worked, but the hr's were still taking up space. It would be nice to have a way to disable them. Lastly, I set the "datestamp" general option in docutils.conf to get the "Generated on..." message in the footer. At the same time, I put a copyright notice in there. The notice and the message go in two separate paragraph tag, while I'd like to have them on the same line. Is there a way to do that? -- Nicola Larosa - http://www.tekNico.net/ The poster sounds new to Twisted, which means that they have at least 2 years worth of regular asynchronous programming ahead of them before they can make effective and judicious use of shortcuts like deferredGenerator. -- "Glyph" Lefkowitz, October 2005 |
From: Mikolaj M. <mi...@wp...> - 2005-12-19 22:54:24
|
Nicola Larosa scripsit: > I wanted thin lines between fields in a field list. It looks like adding > the "frame='void'" and "rules='none'" to the table tag prevents any border > styling by the CSS. Is there any way to get no borders via the CSS, so to > avoid adding such attributes? border: 0; Note: in tables you have to zero both <table> and <td>. > I want no horizontal rules in the header nor in the footer. I tried setting > "visibility: hidden" in the CSS and it worked, but the hr's were still > taking up space. It would be nice to have a way to disable them. visibility: collapse; should do it m. -- LaTeX + Vim = http://vim-latex.sourceforge.net/ Vim Universal Templates: http://vim.sf.net/script.php?script_id=1078 vim.pl - http://skawina.eu.org/mikolaj CLEWN - http://clewn.sf.net |
From: Nicola L. <ni...@te...> - 2005-12-20 21:58:51
|
Mikolaj Machowski wrote: > Nicola Larosa scripsit: > >> I wanted thin lines between fields in a field list. It looks like adding >> the "frame='void'" and "rules='none'" to the table tag prevents any border >> styling by the CSS. Is there any way to get no borders via the CSS, so to >> avoid adding such attributes? > > border: 0; > > Note: in tables you have to zero both <table> and <td>. Yes, of course. :-) I did not express myself clearly, I really meant: "Is it possible to set no borders in the default.css docutils CSS, and to avoid adding such attributes?" >> I want no horizontal rules in the header nor in the footer. I tried setting >> "visibility: hidden" in the CSS and it worked, but the hr's were still >> taking up space. It would be nice to have a way to disable them. > > visibility: collapse; > > should do it Thanks, I'll try it. -- Nicola Larosa - http://www.tekNico.net/ Lao Tzu suggested a solution to life's clutter: "Just remain in the center, watching. And then forget that you are there." These days, with all the racket, that's a lot easier said than done. -- Joe Nickell, October 2005 |
From: Mikolaj M. <mi...@wp...> - 2005-12-21 11:22:30
|
Nicola Larosa scripsit: > Mikolaj Machowski wrote: >> Nicola Larosa scripsit: >>> I wanted thin lines between fields in a field list. It looks like adding >>> the "frame='void'" and "rules='none'" to the table tag prevents any border >>> styling by the CSS. Is there any way to get no borders via the CSS, so to >>> avoid adding such attributes? >> border: 0; >> Note: in tables you have to zero both <table> and <td>. > > Yes, of course. :-) I did not express myself clearly, I really meant: "Is > it possible to set no borders in the default.css docutils CSS, and to avoid > adding such attributes?" Add your own CSS file to override default settings. m. -- LaTeX + Vim = http://vim-latex.sourceforge.net/ Vim Universal Templates: http://vim.sf.net/script.php?script_id=1078 vim.pl - http://skawina.eu.org/mikolaj CLEWN - http://clewn.sf.net |
From: Nicola L. <ni...@te...> - 2005-12-21 11:57:40
|
> Nicola Larosa scripsit: >> Mikolaj Machowski wrote: >>> Nicola Larosa scripsit: >>>> I wanted thin lines between fields in a field list. It looks like adding >>>> the "frame='void'" and "rules='none'" to the table tag prevents any border >>>> styling by the CSS. Is there any way to get no borders via the CSS, so to >>>> avoid adding such attributes? >>> >>> border: 0; >>> Note: in tables you have to zero both <table> and <td>. >> >> Yes, of course. :-) I did not express myself clearly, I really meant: "Is >> it possible to set no borders in the default.css docutils CSS, and to avoid >> adding such attributes?" > > Add your own CSS file to override default settings. Yes, I tried to do that before bothering anyone else, but did not succeed. I'll have to try harder. Are you sure it is possible to override those explicit attributes in the CSS? -- Nicola Larosa - http://www.tekNico.net/ Lao Tzu suggested a solution to life's clutter: "Just remain in the center, watching. And then forget that you are there." These days, with all the racket, that's a lot easier said than done. -- Joe Nickell, October 2005 |
From: Mikolaj M. <mi...@wp...> - 2005-12-22 00:40:25
|
Nicola Larosa scripsit: >> Nicola Larosa scripsit: >>> Mikolaj Machowski wrote: >>>> Nicola Larosa scripsit: >>>>> I wanted thin lines between fields in a field list. It looks like adding >>>>> the "frame='void'" and "rules='none'" to the table tag prevents any border >>>>> styling by the CSS. Is there any way to get no borders via the CSS, so to >>>>> avoid adding such attributes? >>>> border: 0; >>>> Note: in tables you have to zero both <table> and <td>. >>> Yes, of course. :-) I did not express myself clearly, I really meant: "Is >>> it possible to set no borders in the default.css docutils CSS, and to avoid >>> adding such attributes?" >> Add your own CSS file to override default settings. > > Yes, I tried to do that before bothering anyone else, but did not succeed. > I'll have to try harder. Are you sure it is possible to override those > explicit attributes in the CSS? Find html-stylesheets.(html|txt) file in docs. If you declare:: table {border:0;} table {border:1 solid #f00;} The second will be taken into account. m. ps. I am in delicate position here: I don't use reST, only use documentation for VST: http://skawina.eu.org/mikolaj/vst.html -- LaTeX + Vim = http://vim-latex.sourceforge.net/ Vim Universal Templates: http://vim.sf.net/script.php?script_id=1078 vim.pl - http://skawina.eu.org/mikolaj CLEWN - http://clewn.sf.net |
From: David G. <go...@py...> - 2005-12-22 16:16:05
Attachments:
signature.asc
|
[Nicola Larosa] > Talking about the HTML writer, I just made a few mods to it. I am > *not* proposing a patch to be applied to html4css1.py Why not? (0.5 ;-) > @@ -721,7 +721,7 @@ > > def visit_field_list(self, node): > self.body.append(self.starttag(node, 'table', frame=3D'void', > - rules=3D'none', > + rules=3D'rows', > CLASS=3D'docutils field-list')) > self.body.append('<col class=3D"field-name" />\n' > '<col class=3D"field-body" />\n' Which version of Docutils are you using? That doesn't match the HEAD at all. > I wanted thin lines between fields in a field list. It looks like > adding the "frame=3D'void'" and "rules=3D'none'" to the table tag > prevents any border styling by the CSS. Is there any way to get no > borders via the CSS, so to avoid adding such attributes? I suspect this may have been for Netscape 4 compatibility. > I want no horizontal rules in the header nor in the footer. I tried > setting "visibility: hidden" in the CSS and it worked, but the hr's > were still taking up space. It would be nice to have a way to > disable them. Use "display: none" to completely get rid of something. > Lastly, I set the "datestamp" general option in docutils.conf to get > the "Generated on..." message in the footer. At the same time, I put > a copyright notice in there. The notice and the message go in two > separate paragraph tag, while I'd like to have them on the same > line. Is there a way to do that? No, sorry. One idea (in the to-do list) is to implement a "date" directive combined with "canned macros", a set of pre-defined substitutions that provide limited dynamic content. Then you could do this: .. include:: <macros> .. footer:: Copyright notice. Generated on |date|. --=20 David Goodger <http://python.net/~goodger> |
From: Nicola L. <ni...@te...> - 2005-12-22 18:04:49
|
>>@@ -721,7 +721,7 @@ >> >> def visit_field_list(self, node): >> self.body.append(self.starttag(node, 'table', frame='void', >>- rules='none', >>+ rules='rows', >> CLASS='docutils field-list')) >> self.body.append('<col class="field-name" />\n' >> '<col class="field-body" />\n' > Which version of Docutils are you using? That doesn't match the HEAD > at all. 0.3.9. I'll have a look at a recent snapshot. >> I wanted thin lines between fields in a field list. It looks like >> adding the "frame='void'" and "rules='none'" to the table tag >> prevents any border styling by the CSS. Is there any way to get no >> borders via the CSS, so to avoid adding such attributes? > I suspect this may have been for Netscape 4 compatibility. Then maybe the time has come to get rid of it. Would you like a patch? :-) >> I want no horizontal rules in the header nor in the footer. I tried >> setting "visibility: hidden" in the CSS and it worked, but the hr's >> were still taking up space. It would be nice to have a way to >> disable them. > Use "display: none" to completely get rid of something. Great, will do. >> Lastly, I set the "datestamp" general option in docutils.conf to get >> the "Generated on..." message in the footer. At the same time, I put >> a copyright notice in there. The notice and the message go in two >> separate paragraph tag, while I'd like to have them on the same >> line. Is there a way to do that? > No, sorry. One idea (in the to-do list) is to implement a "date" > directive combined with "canned macros", a set of pre-defined > substitutions that provide limited dynamic content. Then you could do > this: > > .. include:: <macros> > > .. footer:: Copyright notice. Generated on |date|. That would be great. :-) -- Nicola Larosa - http://www.tekNico.net/ Lao Tzu suggested a solution to life's clutter: "Just remain in the center, watching. And then forget that you are there." These days, with all the racket, that's a lot easier said than done. -- Joe Nickell, October 2005 |
From: David G. <go...@py...> - 2005-12-22 23:47:20
Attachments:
signature.asc
|
[David Goodger] > One idea (in the to-do list) is to implement a "date" > directive I implemented a "date" directive during the train ride home today: http://docutils.sf.net/docs/ref/rst/directives.html#date . There are no "canned macros" yet; there's only one example so far. Example: .. |date| date:: .. footer:: Copyright notice. Generated on |date|. --=20 David Goodger <http://python.net/~goodger> |
From: Alan G I. <ai...@am...> - 2005-12-23 14:20:42
|
On Thu, 22 Dec 2005, David Goodger apparently wrote: > http://docutils.sf.net/docs/ref/rst/directives.html#date . > There are no "canned macros" yet; there's only one example so far. > Example: > .. |date| date:: > .. footer:: Copyright notice. Generated on |date|. How about a Python evaluation directive instead, only accepting a string as a return value, again only for substitutions. E.g., :: .. |date| eval:: time.strftime("%c") :needs: time Cheers, Alan Isaac |
From: Aahz <aa...@py...> - 2005-12-23 15:05:01
|
On Fri, Dec 23, 2005, Alan G Isaac wrote: > > How about a Python evaluation directive instead, only accepting a > string as a return value, again only for substitutions. No. This has been hashed out over and over and over again: no Python allowed in documents for standard reST. (Obviously, people can write their own extensions to allow it, and I have.) This is way way too big a security hole. Just start with ``open('/etc/passwd', 'w')``. -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "Don't listen to schmucks on USENET when making legal decisions. Hire yourself a competent schmuck." --USENET schmuck (aka Robert Kern) |
From: Alan G I. <ai...@am...> - 2005-12-23 15:26:52
|
> On Fri, Dec 23, 2005, Alan G Isaac wrote: >> How about a Python evaluation directive instead, only >> accepting a string as a return value, again only for >> substitutions. On Fri, 23 Dec 2005, Aahz apparently wrote: > No. This has been hashed out over and over and over > again: no Python allowed in documents for standard reST. > (Obviously, people can write their own extensions to allow > it, and I have.) This is way way too big a security hole. > Just start with ``open('/etc/passwd', 'w')``. An 'eval' directive could be disabled by default but still exist for the convenience of users, who would have to enable it explicitly. Like write18 in TeX. Cheers, Alan Isaac |
From: Mark N. <mar...@au...> - 2005-12-23 22:14:36
|
Alan G Isaac wrote: >>On Fri, Dec 23, 2005, Alan G Isaac wrote: >> >>>How about a Python evaluation directive instead, only >>>accepting a string as a return value, again only for >>>substitutions. >> > > On Fri, 23 Dec 2005, Aahz apparently wrote: > >>No. This has been hashed out over and over and over >>again: no Python allowed in documents for standard reST. >>(Obviously, people can write their own extensions to allow >>it, and I have.) This is way way too big a security hole. >>Just start with ``open('/etc/passwd', 'w')``. > > > > An 'eval' directive could be disabled by default but still > exist for the convenience of users, who would have to enable > it explicitly. Like write18 in TeX. What I did with the Perl reSt tool was allowed a Perl directive that operates within a "use Safe" box so that it can't do anything that might be dangerous, but can still do any safe operations, like computations. I don't know if Python has an equivalent to "use Safe". These safety restrictions can be lifted only by specifying "-D trusted" on the command line, the typing of which means that the person running the tool assumes explicit responsibility for anything that may go wrong. --Mark |
From: Marcelo G H. <mar...@gm...> - 2005-12-23 23:00:01
|
El 23/12/2005 a las 12:04, Aahz <aa...@py...> dijo, en su mensaje "[Docutils-develop] Some mods to the HTML writer [was: Re: "compact" lists and multiple paragraphs]": > No. This has been hashed out over and over and over again: no Python > allowed in documents for standard reST. (Obviously, people can write > their own extensions to allow it, and I have.) Just for your private use, or you have an URL you could point us to? I'm interested in this functionality. -- o-=< Marcelo >=-o |
From: Aahz <aa...@py...> - 2005-12-24 01:46:08
|
On Fri, Dec 23, 2005, Marcelo G Huerta wrote: > El 23/12/2005 a las 12:04, Aahz <aa...@py...> dijo, en su > mensaje "[Docutils-develop] Some mods to the HTML writer [was: Re: > "compact" lists and multiple paragraphs]": > >> No. This has been hashed out over and over and over again: no Python >> allowed in documents for standard reST. (Obviously, people can write >> their own extensions to allow it, and I have.) > > Just for your private use, or you have an URL you could point us to? > I'm interested in this functionality. It's in my sandbox, the OO and MIF writers. I haven't even looked at the tree since the SVN conversion, so I can't give you an URL (which should also warn you about how out of date the code is). -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "Don't listen to schmucks on USENET when making legal decisions. Hire yourself a competent schmuck." --USENET schmuck (aka Robert Kern) |
From: Felix W. <Fel...@gm...> - 2006-01-21 15:56:59
|
Mark Nodine wrote: > What I did with the Perl reSt tool was allowed a Perl directive that > operates within a "use Safe" box so that it can't do anything that > might be dangerous, but can still do any safe operations, like > computations. I don't know if Python has an equivalent to "use Safe". No, it doesn't, unfortunately. There used to be modules for that in Py2.1 (rexec and bastion), but they were found to be vulnerable and unfixable. -- For private mail please ensure that the header contains 'Felix Wiemann'. "the number of contributors [...] is strongly and inversely correlated with the number of hoops each project makes a contributing user go through." -- ESR |