You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(15) |
Oct
(21) |
Nov
(18) |
Dec
(59) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(43) |
Feb
(35) |
Mar
(78) |
Apr
(65) |
May
(163) |
Jun
(169) |
Jul
(137) |
Aug
(77) |
Sep
(47) |
Oct
(27) |
Nov
(43) |
Dec
(68) |
2004 |
Jan
(61) |
Feb
(39) |
Mar
(11) |
Apr
(42) |
May
(86) |
Jun
(82) |
Jul
(24) |
Aug
(26) |
Sep
(37) |
Oct
(62) |
Nov
(131) |
Dec
(43) |
2005 |
Jan
(31) |
Feb
(56) |
Mar
(65) |
Apr
(165) |
May
(106) |
Jun
(97) |
Jul
(65) |
Aug
(150) |
Sep
(78) |
Oct
(115) |
Nov
(41) |
Dec
(26) |
2006 |
Jan
(50) |
Feb
(39) |
Mar
(56) |
Apr
(67) |
May
(89) |
Jun
(68) |
Jul
(116) |
Aug
(65) |
Sep
(58) |
Oct
(103) |
Nov
(28) |
Dec
(52) |
2007 |
Jan
(92) |
Feb
(60) |
Mar
(124) |
Apr
(96) |
May
(69) |
Jun
(79) |
Jul
(25) |
Aug
(22) |
Sep
(7) |
Oct
(17) |
Nov
(27) |
Dec
(32) |
2008 |
Jan
(57) |
Feb
(87) |
Mar
(51) |
Apr
(43) |
May
(56) |
Jun
(62) |
Jul
(25) |
Aug
(82) |
Sep
(58) |
Oct
(42) |
Nov
(38) |
Dec
(86) |
2009 |
Jan
(50) |
Feb
(33) |
Mar
(84) |
Apr
(90) |
May
(109) |
Jun
(37) |
Jul
(22) |
Aug
(51) |
Sep
(93) |
Oct
(86) |
Nov
(31) |
Dec
(62) |
2010 |
Jan
(33) |
Feb
(57) |
Mar
(62) |
Apr
(43) |
May
(30) |
Jun
(49) |
Jul
(20) |
Aug
(40) |
Sep
(152) |
Oct
(38) |
Nov
(15) |
Dec
(32) |
2011 |
Jan
(29) |
Feb
(25) |
Mar
(65) |
Apr
(45) |
May
(27) |
Jun
(11) |
Jul
(14) |
Aug
(8) |
Sep
(13) |
Oct
(117) |
Nov
(60) |
Dec
(19) |
2012 |
Jan
(23) |
Feb
(32) |
Mar
(24) |
Apr
(41) |
May
(56) |
Jun
(24) |
Jul
(15) |
Aug
(11) |
Sep
(26) |
Oct
(21) |
Nov
(12) |
Dec
(31) |
2013 |
Jan
(32) |
Feb
(24) |
Mar
(39) |
Apr
(44) |
May
(44) |
Jun
(8) |
Jul
(9) |
Aug
(12) |
Sep
(34) |
Oct
(19) |
Nov
(5) |
Dec
(9) |
2014 |
Jan
(22) |
Feb
(12) |
Mar
(7) |
Apr
(2) |
May
(13) |
Jun
(17) |
Jul
(8) |
Aug
(10) |
Sep
(7) |
Oct
(4) |
Nov
|
Dec
(39) |
2015 |
Jan
(13) |
Feb
(12) |
Mar
(12) |
Apr
(40) |
May
(5) |
Jun
(22) |
Jul
(3) |
Aug
(42) |
Sep
(5) |
Oct
(10) |
Nov
|
Dec
(10) |
2016 |
Jan
(9) |
Feb
(43) |
Mar
(5) |
Apr
(14) |
May
(17) |
Jun
(5) |
Jul
(5) |
Aug
(22) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
(18) |
2017 |
Jan
(28) |
Feb
(29) |
Mar
(9) |
Apr
(23) |
May
(48) |
Jun
(5) |
Jul
(32) |
Aug
(9) |
Sep
(13) |
Oct
(13) |
Nov
(6) |
Dec
(4) |
2018 |
Jan
(6) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
(5) |
Jun
(17) |
Jul
(12) |
Aug
(15) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
(6) |
Mar
(3) |
Apr
(5) |
May
(10) |
Jun
(6) |
Jul
(6) |
Aug
|
Sep
(11) |
Oct
(18) |
Nov
(10) |
Dec
(7) |
2020 |
Jan
(3) |
Feb
(14) |
Mar
(2) |
Apr
(1) |
May
(5) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(14) |
2021 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
(8) |
May
(23) |
Jun
(7) |
Jul
(10) |
Aug
(1) |
Sep
|
Oct
(7) |
Nov
(10) |
Dec
(2) |
2022 |
Jan
|
Feb
(21) |
Mar
|
Apr
(3) |
May
(7) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2023 |
Jan
(18) |
Feb
|
Mar
(1) |
Apr
|
May
(9) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <in...@uk...> - 2002-10-01 10:16:23
|
<=1B$B;v6H<TL>=1B(B>=1B$B-k=1B(BExcis<=1B$BAw?.<TL>=1B(B>=1B$B-k=1B(BExci= s <=1B$BAw?.<T!&;v6H<T=1B(BURL>http://plaza15.mbn.or.jp/~1234/=1B$B!!"($3= $N=1B(B=D2=B0=D9=1B$B$O9-9p$G$9!#G[?.ITMW$NJ}$O=1B(B in...@uk... =1B$= BKx$4O"Mm2<$5$$!#G[?.$rDd;_CW$7$^$9=1B(B(=1B$BI,$:G[?.Dd;_$9$k%"%I%l%9$G$= 4JV?.2<$5$$!K=1B(B =1B$B?75,%*!<%W%s!*%A%g%C%H=1B(BH=1B$B$J=3DP2q$$%5%$%H$@$h!*=1B(B http://uki-2.net =1B$B:#$J$i%*!<%W%s5-G0$G$$$/$i=3Dq$-9~$s$G$bL5NA!*=1B(B http://uki-2.net =1B$B$3$N%A%c%s%9$K=3Dw$N;R$r=1B(BGET=1B$B$7$F$M!*=1B(B http://uki-2.net |
From: <dm...@v-...> - 2002-09-30 10:39:59
|
<=1B$B;v6H<TL>=1B(B>=1B$B-k%(%/%7%9=1B(B<=1B$BAw?.<T=1B(B>=1B$B-k%(%/%7%9= =1B(B<=1B$BAw?.<T!&;v6H<T=1B(BURL>=1B$B!!=1B(Bhttp://plaza15.mbn.or.jp/~1= 234/ =1B$B$3$N=1B(B=D2=B0=D9=1B$B$O9-9p$G$9!#G[?.ITMW$NJ}$O=1B(B mailstop= @melcon-c.com =1B$BKx$4O"Mm2<$5$$!#G[?.$rDd;_CW$7$^$9=1B(B(=1B$BI,$:G[?.= Dd;_$9$k%"%I%l%9$G$4JV?.2<$5$$!K=1B(B H=1B$B$J=3Dw$N;R5^A}Cf!*:#$,%A%c%s%9!*=1B(B http://www.melcon-c.com =1B$BB(%"%]B3=3DP!*=1B(B http://www.melcon-c.com =1B$B$^$:$OEPO?$7$F$M!*=1B(B http://www.melcon-c.com |
From: David G. <go...@us...> - 2002-09-18 01:36:14
|
[Dean] > a. reSTX implementation (and plans) in Zope and CMF. [David] > Richard Jones has implemented a "ReStructuredText "... Sorry, I meant to finish that. Should read: Richard Jones has implemented ZReST, a "ReStructuredText Document for Zope" application that is complete and ready to install. It's on Richard's Zope pages at: http://www.zope.org/Members/richard/ZReST/ The raw files are on the Docutils site at: http://docutils.sf.net/sandbox/richard/ZReST/ -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: David G. <go...@us...> - 2002-09-17 01:45:37
|
Dean Goodmanson wrote: > I'm looking for the proper place to find past discussions and > discuss the following (without annoying cross posting): Discussions take place on the Python Doc-SIG list and the Docutils-develop list. Doc-SIG archive: http://www.python.org/pipermail/doc-sig/ Docutils-develop archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8812 The Doc-SIG archive should be searchable at ActiveState or one of the other list mirrors. The SourceForge archive seems searchable too. > a. reSTX implementation (and plans) in Zope and CMF. Richard Jones has implemented a "ReStructuredText "... > b. StructuredText to reStructuredText conversion code, discussion, > etc. Not that I know of. > Similarly, HTML to reSTX as a potential migration tool: > STX->HTML->reSTX. Ditto. Contributions are welcome! > I'm looking to gather these resources and discussions > for supporting the implementation of reSTX in ZWiki ( > http://www.zwiki.org/ReStructuredText ) I looked at the page. Some corrections: Abbreviation : reSTX I've only seen this used in Zope-land, and I don't much like it. I prefer RST, but the most commonly used abbreviation is reST. Cons: Still requires double space "paragraph" seperation. I don't see how comparing equal counts a "con" against reStructuredText. :-) Add this to "Pros": Doesn't need blank lines between list items. Problems with STX Please use the permanent, up-to-date URL: http://docutils.sourceforge.net/spec/rst/problems.html Perhaps it's time for a Docutils FAQ. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Dean G. <goo...@ya...> - 2002-09-16 17:58:42
|
Greetings! I'm looking for the proper place to find past discussions and discuss the following (without annoying cross posting): a. reSTX implementation (and plans) in Zope and CMF. b. StructuredText to reStructuredText conversion code, discussion, etc. Similarly, HTML to reSTX as a potential migration tool: STX->HTML->reSTX. I'm looking to gather these resources and discussions for supporting the implementation of reSTX in ZWiki ( http://www.zwiki.org/ReStructuredText ) The motivation is similar to the "Problems with StructuredText" descriptions ( http://mail.python.org/pipermail/doc-sig/2000-November/001240.html ) , primarily indentation (#3) which is very cumbersome from a Browser Text Box interface and surprise formatting. Best Regards, Dean Goodmanson goo...@ya... http://www.pycs.net/sqr __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com |
From: Mark M. <mar...@mc...> - 2002-09-16 01:42:06
|
[David Goodger] > Is it really such a hardship? Is it not something you would do > anyhow, in a text file? Nope, it's not that much of a hardship. > I don't know of a better way. If there is one, I'm receptive. > Nothing I've seen so far comes close though. I never mastered the old StructuredText, but its approach, using merely indentation and whether text was a single line or more than one line (was that is?) to indicate H1 vs. H2 for instance seemed too fuzzy for my taste. So, in contrast, I like the precision of reStructuredText. Thanks for the warning about suppressing errors. Cheers, // mark - |
From: David G. <go...@us...> - 2002-09-16 00:57:27
|
Mark McEahern wrote: >> Because anything *less* than a full underline looks wrong. > > I agree, it does look unfinished. However, I keep thinking about all the > useless work involved in this scenario: > > 1. Type "The Political Landscape" > 2. Type "-----------------------" > 3. Change the title to "The Political Landscape of the US" > 4. Add underscores to the underline to match the new section title. > 5. Change the title to "Politics in the US" > 6. etc. > > Why should I have to keep adjusting the length of the line? Is it really such a hardship? Is it not something you would do anyhow, in a text file? The core of reStructuredText is merely a formalization of common long-standing conventions for plaintext documents. I didn't invent this particular convention, just chose and codified it (and wrote the code to parse it). The plaintext medium simply has limitations that we have to live with. I don't know of a better way. If there is one, I'm receptive. Nothing I've seen so far comes close though. Perhaps someday someone will write a reStructuredText mode for Emacs, which will automatically take care of such mundane issues. That would be great! Won't be me though; I can hack Emacs Lisp but not well enough to write a major mode. > I know you pointed out that I can just type 80 of the underline characters > (or 79 or whatever) and leave that alone--as long as it's longer than the > title. If it bugs you, this solution seems reasonable. > I'm reminded of Scott McConnell's comments on Commenting Efficiently in Code > Complete (pp 464-367): > > He writes of this: > > ########### > # globals # > ########### > > "Use styles that don't break down or discourage modification." Good advice. Whenever I've done something like that in a source file, I would write it like this:: ##################################################################### # Globals ##################################################################### Easy to edit. :-) > Perhaps I'm making mountains out of molehills, though? *I* think so, yes. ;-) >> In reStructuredText, section titles are underlined. Only full >> underlines get full marks. Are you seriously proposing some other >> behavior? If so, please be explicit. > > As it is, the current dev snapshot seems to intuit that I want an underline > in this case: > > The Political Landscape of the US > ---- The parser knows enough to assume you want an underline, but then it makes it very clear what the error is and where. I'd say that it's the assumption that's closer to being a "bug" than the error message. > The only thing I guess I'm asking is, "Can we at least make the error > suppressible?" And, it turns out, we can: -r3 does the trick just fine. -r3 does indeed suppress that error. Unfortunately, it also suppresses all other errors, and all warnings as well. Dangerous and not recommended. If you use -r3, you'll regret it in the long run. The error is meant as diagnostic feedback to the user, and isn't meant to be ignored. That's what the ERROR/3 level means: "a major issue that should be addressed. If ignored, the output will contain unpredictable errors." See http://www.python.org/peps/pep-0258.html#error-handling for details. I'm not inclined to remove the generated error. Asking if the error can be suppressed is approaching the issue from the wrong direction. If pressed, I'd rather remove the leniency: leave just the error and omit the section & title recognition. > I really like reStructuredText. Thank you for developing it! You're most welcome. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Mark M. <mar...@mc...> - 2002-09-15 22:33:23
|
[David Goodger] > You omitted this sentence: > > An underline/overline is a single repeated punctuation character > that begins in column 1 and forms a line extending at least as far > as the right edge of the title text. > > The "at least as far" is significant. My apologies. I missed that sentence. So the behavior is by design, I see. > Because anything *less* than a full underline looks wrong. I agree, it does look unfinished. However, I keep thinking about all the useless work involved in this scenario: 1. Type "The Political Landscape" 2. Type "-----------------------" 3. Change the title to "The Political Landscape of the US" 4. Add underscores to the underline to match the new section title. 5. Change the title to "Politics in the US" 6. etc. Why should I have to keep adjusting the length of the line? I know you pointed out that I can just type 80 of the underline characters (or 79 or whatever) and leave that alone--as long as it's longer than the title. I'm reminded of Scott McConnell's comments on Commenting Efficiently in Code Complete (pp 464-367): He writes of this: ########### # globals # ########### "Use styles that don't break down or discourage modification." Perhaps I'm making mountains out of molehills, though? > In reStructuredText, section titles are underlined. Only full > underlines get full marks. Are you seriously proposing some other > behavior? If so, please be explicit. As it is, the current dev snapshot seems to intuit that I want an underline in this case: The Political Landscape of the US ---- The only thing I guess I'm asking is, "Can we at least make the error suppressible?" And, it turns out, we can: -r3 does the trick just fine. I really like reStructuredText. Thank you for developing it! Cheers, // mark - |
From: David G. <go...@us...> - 2002-09-15 16:55:44
|
Gunnar Schwant has contributed DocFactory, a wxPython GUI application for Docutils. It is in the preliminary stages. For details, please see http://docutils.sf.net/sandbox/gschwant/docfactory/README.html I have begun a "To Do" list: http://docutils.sf.net/sandbox/gschwant/docfactory/NOTES.html The code is available via CVS or snapshot: http://docutils.sf.net/docutils-sandbox-snapshot.tgz Please try it out. Feedback is welcome: bug reports, patches, feature ideas, etc. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: David G. <go...@us...> - 2002-09-15 14:30:07
|
Mark McEahern wrote: > The documentation says: > > "An underline/overline must be at least 4 characters long (to avoid > mistaking ellipses ["..."] for overlines). When an overline is used, the > length and character used must match the underline." You omitted this sentence: An underline/overline is a single repeated punctuation character that begins in column 1 and forms a line extending at least as far as the right edge of the title text. The "at least as far" is significant. > http://docutils.sourceforge.net/spec/rst/reStructuredText.html#sections > > However, when I use this: > > My section is longer than the underline > ==== > > (left-aligned in actual source, indented for readability) > > I get this: > > System Message: WARNING/2 (user_task_matrix.rst, line 4) > > Title underline too short. > > Is that a bug? No, it's a diagnostic message, warning you that the markup is questionable. The parser assumes that a section title is intended, but the inserted warning is such an eyesore that you're sure to fix the underline. > Why make users type all those extra underline characters and > then have to keep adjusting them as the section title changes? Because anything *less* than a full underline looks wrong. There's no reason to limit your underlines to the exact length of the title though (thus "at least as far" above). You're welcome to use 80 column underlines for all titles, no matter how long. In reStructuredText, section titles are underlined. Only full underlines get full marks. Are you seriously proposing some other behavior? If so, please be explicit. Coincidentally, currently there is a proposal to remove the 4-character minimum on over- & underlines, for short titles. It and other proposed changes & additions to the markup are discussed on the Doc-SIG list: http://mail.python.org/mailman/listinfo/doc-sig Docutils implementation issues are discussed on the docutils-develop list: http://lists.sourceforge.net/lists/listinfo/docutils-develop Interested parties should subscribe to both since there is some overlap. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Mark M. <ma...@mc...> - 2002-09-13 20:49:57
|
The documentation says: "An underline/overline must be at least 4 characters long (to avoid mistaking ellipses ["..."] for overlines). When an overline is used, the length and character used must match the underline." http://docutils.sourceforge.net/spec/rst/reStructuredText.html#sections However, when I use this: My section is longer than the underline ==== (left-aligned in actual source, indented for readability) I get this: System Message: WARNING/2 (user_task_matrix.rst, line 4) Title underline too short. Is that a bug? Why make users type all those extra underline characters and then have to keep adjusting them as the section title changes? Cheers, // m - |
From:
<ta...@nz...> - 2002-09-10 06:28:44
|
<事業者>ジュエリーノン 2度と配信いたしませんので配信不要の方はこのままご返信くださいta...@la... <送信者>mcco taketu yosi拒否同上http://www6.plala.or.jp/taketu <内容>無料プレゼント ●リニューアルオープン記念につきシルバーリングまたは18金ピアスを500名様にプレゼントいたします。応募方法はこちらからどうぞ http://www6.plala.or.jp/taketu/rentpage1/ |
From: David G. <go...@us...> - 2002-09-10 02:06:01
|
The following message was sent to docutils-users. My Zope knowledge is zero. Can anybody here help Colin? Colin Leath wrote: > I'm attempting to make either (1) a new CMFDocument type or (2) a > script that can process the default CMFDocument to create a > collapsible/expandable (e.g. msword outline view) view of that > document. > > I would like the document to be able to be composed using STX or reST > (http://docutils.sourceforge.net/rst.html) ... The full message can be found here: http://sf.net/mailarchive/forum.php?thread_id=1045103&forum_id=11444 On a related note, I'd appreciate it if docutils-developers would subscribe to docutils-users to help answer the occasional question. Subscribe at: http://lists.sourceforge.net/mailman/listinfo/docutils-users -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Colin L. <cl...@po...> - 2002-09-07 19:43:54
|
I'm attempting to make either (1) a new CMFDocument type or (2) a script that can process the default CMFDocument to create a collapsible/expandable (e.g. msword outline view) view of that document. I would like the document to be able to be composed using STX or reST (http://docutils.sourceforge.net/rst.html) In the simplest implementation, the document/script would take the following (STX): o category 1 o 1.1 Some text here-- could be quite long. o 1.2 Some text here-- could be quite long. o 1.3 Some text here-- could be quite long. o 1.3.1 o 1.3.2 o 1.4 o category 2 and produce the following: + o category 1 o 1.1 Some text here-- could be quite long. o 1.2 Some text here-- could be quite long. + o 1.3 Some text here-- could be quite long. o 1.3.1 o 1.3.2 o 1.4 o category 2 Where each of the elements in the list that has sub-elements can be clicked to show or hide the contents below. The formatting of this tree would preferably be specified using ZPT [zope page templates], and would (someday) also allow for the use of javascript trees. What I've done so far: I've created a ParsedXML document: <?xml version="1.0" ?> <category title="body"> <category title="intro"> some long stx here... </category> <category title="categories"> <category title="most salient overall"> x. finish this project x. physical well-being x. relationships (?) </category> <category title="most important overall"> x. things to look forward to. <category title="subsubcat"> x. test 1 x. test 2 x. test 3 </category> </category> </category> </category> And following the example in zpt_example.zexp, created a tree document which behaves more or less as I'd like. The remaning problem is making the source document easy to create! (Currently I use VIM and its folding option. Just today I found: http://www.troubleshooters.com/projects/vimoutliner/) In getting more familiar with the StructuredText product, in particular, by following through thre readme, it appears that stx documents should be able to be manipulated like I was manipulating the parsed XML, e.g.: StructuredTextNode objects support the read-only subset of the Document Object Model (DOM) API. It should be possible to process 'StructuredTextNode' hierarchies using XML tools such as XSLT. If I follow option #2 above (a script to process CMF document), I expect I'd take the editable body from the CMFDocument, create a nodal object suitable for use with my tree page template. If not using reST, I might also add a script-created table of contents (reST has this feature). I'm trying not to spend my whole life attempting to code what I want. Has anyone else already done this? Do you have any pointers or suggestions on the easiest way to achieve this functionality? I would want to create something I could use on zettai.net/freezope.org (so I don't have to pay to run my own zope instance)--that is, it would have to either be a script I could add on my own, or written well enough that they'd add it as a product. Thanks for any suggestions! Would zope-dev be a better place to post this email? Colin |
From: David G. <go...@us...> - 2002-09-05 02:32:19
|
Arash Shahi wrote: > is it possible to create a dokumentation( HTML, XML, ... ) of a > python programm? I can't find any thing about it in the readme. Sorry, this hasn't been implemented yet. It is currently under development. There has been some work (see http://docutils.sf.net/sandbox/tibs/pysource/), but it's probably out of date. I'm looking at the pysource code as well as at HappyDoc (http://happydoc.sf.net/) for inspiration. It's the next major task on my list. If you'd like to help, you'd be very welcome! I will make a note in the README. > I don't want all of my surcecode including in the documentation, and > that's what happens when I create a html-file with buildhtml.py . The buildhtml.py front end is not intended for use with .py files, and it shouldn't read them. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: Arash S. <sh...@bi...> - 2002-09-04 11:53:20
|
Hello, is it possible to create a dokumentation( HTML, XML, ... ) of a python programm? I can't find any thing about it in the readme. I don't want all of my surcecode including in the documentation, and that's what happens when I create a html-file with buildhtml.py . Thank's, Arash. |
From: Richard J. <rj...@ek...> - 2002-08-12 23:30:52
|
On Tue, 13 Aug 2002 9:01 am, David Goodger wrote: > hem...@ph... wrote: > > I was wondering if a front-end exists to convert reStructuredText to > > slides using HTML and javascript, > > something similar to what 'pylize' does > > (http://www.chrisarndt.de/software/pylize/) > > Not exactly, no, although Richard Jones did begin to integrate > reStructuredText with PythonPoint (in the old project, pre-merge): > http://cvs.sf.net/cgi-bin/viewcvs.cgi/structuredtext/sandbox/richardj/ > > (Richard, have you done any more with PythonPoint? Any plans?) Sorry, haven't had a need to and I've got lots of other stuff to divert my attention ;) Richard |
From: David G. <go...@us...> - 2002-08-12 22:58:50
|
hem...@ph... wrote: > I was wondering if a front-end exists to convert reStructuredText to > slides using HTML and javascript, > something similar to what 'pylize' does > (http://www.chrisarndt.de/software/pylize/) Not exactly, no, although Richard Jones did begin to integrate reStructuredText with PythonPoint (in the old project, pre-merge): http://cvs.sf.net/cgi-bin/viewcvs.cgi/structuredtext/sandbox/richardj/ (Richard, have you done any more with PythonPoint? Any plans?) I am not familiar with pylize. I'd be happy to help if you'd like to try integrating it with Docutils. -- David Goodger <go...@us...> Open-source projects: - Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html) - The Go Tools Project: http://gotools.sourceforge.net/ |
From: <hem...@ph...> - 2002-08-12 08:47:41
|
I was wondering if a front-end exists to convert reStructuredText to slides using HTML and javascript, something similar to what 'pylize' does (http://www.chrisarndt.de/software/pylize/) -Hemanth hem...@ph... |