## docutils-users — General discussions, questions, help requests.

You can subscribe to this list here.

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 Jan Feb Mar Apr May Jun Jul Aug (3) Sep (15) Oct (21) Nov (18) Dec (59) Jan (43) Feb (35) Mar (78) Apr (65) May (163) Jun (169) Jul (137) Aug (77) Sep (47) Oct (27) Nov (43) Dec (68) Jan (61) Feb (39) Mar (11) Apr (42) May (86) Jun (82) Jul (24) Aug (26) Sep (37) Oct (62) Nov (131) Dec (43) Jan (31) Feb (56) Mar (65) Apr (165) May (106) Jun (97) Jul (65) Aug (150) Sep (78) Oct (115) Nov (41) Dec (26) Jan (50) Feb (39) Mar (56) Apr (67) May (89) Jun (68) Jul (116) Aug (65) Sep (58) Oct (103) Nov (28) Dec (52) Jan (92) Feb (60) Mar (124) Apr (96) May (69) Jun (79) Jul (25) Aug (22) Sep (7) Oct (17) Nov (27) Dec (32) Jan (57) Feb (87) Mar (51) Apr (43) May (56) Jun (62) Jul (25) Aug (82) Sep (58) Oct (42) Nov (38) Dec (86) Jan (50) Feb (33) Mar (84) Apr (90) May (109) Jun (37) Jul (22) Aug (51) Sep (93) Oct (86) Nov (31) Dec (62) Jan (33) Feb (57) Mar (62) Apr (43) May (30) Jun (49) Jul (20) Aug (40) Sep (152) Oct (38) Nov (15) Dec (32) Jan (29) Feb (25) Mar (65) Apr (45) May (27) Jun (11) Jul (14) Aug (8) Sep (13) Oct (117) Nov (60) Dec (19) Jan (23) Feb (32) Mar (24) Apr (41) May (56) Jun (24) Jul (15) Aug (11) Sep (26) Oct (21) Nov (12) Dec (31) Jan (32) Feb (24) Mar (39) Apr (44) May (44) Jun (8) Jul (9) Aug (12) Sep (34) Oct (19) Nov (5) Dec (9) Jan (22) Feb (12) Mar (7) Apr (2) May (13) Jun (17) Jul (8) Aug (10) Sep (7) Oct (4) Nov Dec (39) Jan (13) Feb (12) Mar (12) Apr (40) May (5) Jun (22) Jul (3) Aug (42) Sep (5) Oct (10) Nov Dec (10) Jan (9) Feb (43) Mar (5) Apr (14) May (17) Jun (5) Jul (5) Aug (22) Sep (5) Oct Nov (4) Dec (18) Jan (28) Feb (29) Mar (9) Apr (23) May (48) Jun (5) Jul (32) Aug (9) Sep (13) Oct (13) Nov (6) Dec (4) Jan (6) Feb (2) Mar Apr May Jun Jul Aug Sep Oct Nov Dec
S M T W T F S
1

2
(2)
3
(2)
4
(1)
5

6
(2)
7
(2)
8

9
(1)
10
(2)
11

12

13

14

15

16

17

18
(2)
19

20

21

22

23

24

25
(5)
26
(8)
27
(5)
28
(3)
29
(2)
30
(4)

Showing results of 41

1 2 > >> (Page 1 of 2)
 Re: [Docutils-users] new release? From: Alan G Isaac - 2012-04-30 12:28:04 > On 4/27/2012 12:21 PM, Alan G Isaac wrote: >> Just to be clear, does anyone assert that it is*not* >> a bug to disallow separately styling the quote environment >> and the literal block environment in LaTeX? (It is of >> course easily achievable in HTML.) >> If it*is* a bug, why would it be inappropriate to achieve >> Guenter's desired indentation of literal blocks with a >> custom environment, which can just duplicate the quote environment? On 4/30/2012 2:24 AM, Guenter Milde wrote: > If you believe it to be a bug, please add an entry to the bug tracker. This > way this problem can be handled the same way as all the other open problems. > Constant nagging in the mail-list will not result in prior treatment. I'm not asking for "prior treatment". I'm asking for acknowledgement of the bug and discussion of the proposed solution. I'd like to open a ticket that includes a discussed solution. This is pretty normal on other lists I'm on. Is it an oddity here for some reason? Thanks, Alan 
 Re: [Docutils-users] [Docutils-develop] Version 1.2.1 of rst.el released From: Stefan Merten - 2012-04-30 11:46:20 Attachments: application/pgp-signature Hi Ben and all! Today Ben Finney wrote: > Where is the web site for the development of ‘rst.el’? I have some > requests to make, but don't want to clutter this forum unnecessarily. Well there are several places from which rst.el is available. I'm still maintaining http://www.merten-home.de/FreeSoftware/rst_el/ but the version there should not be different from the version in the docutils repository - and soon not different from the version in Emacs. Besides a couple of tests there is also a file IDEAS.rst (though this will probably not be in the main Emacs repository). Please contact me for all aspects of rst.el. I work on rst.el once in a while. Grüße Stefan 
 Re: [Docutils-users] new release? From: Guenter Milde - 2012-04-30 06:24:47 On 2012-04-28, Alan G Isaac wrote: > On 4/27/2012 12:21 PM, Alan G Isaac wrote: > Just to be clear, does anyone assert that it is *not* > a bug to disallow separately styling the quote environment > and the literal block environment in LaTeX? (It is of > course easily achievable in HTML.) > If it *is* a bug, why would it be inappropriate to achieve > Guenter's desired indentation of literal blocks with a > custom environment, which can just duplicate the quote environment? If you believe it to be a bug, please add an entry to the bug tracker. This way this problem can be handled the same way as all the other open problems. Constant nagging in the mail-list will not result in prior treatment. Günter 
 [Docutils-users] how to incorporate a new role into distutils From: Angel Yanguas-Gil - 2012-04-30 04:45:50 Hi, I have been playing with docutils and I have created a new role :chem:, to process subscripts and superscripts for chemical formula (i.e. :chem: or :ch:Al2O3 == Al2O3). It worked, and now I have it running in my local copy. However, I still have a couple of questions: 1) So far I have included it in my local copy of roles.py. Is there any other way of loading custom roles / add-ons to distutils that does not involve modifying roles.py? (like a local directory where custom roles could be added/imported into distutils?). 2) Is nodes.Text the standard way of returning a text node? 3) Can roles be made to work recursively? In other words, am I missing a simple way of calling a role within a role (i.e. so that I can expand Al2O3 into "Al :subs:2\ O:subs:3\ " and that magically everything is taken care of)?. 4) Is a role the best way of doing this? Should I be using a directive instead, or is it an overkill? Many thanks, ay 
 [Docutils-users] Version 1.2.1 of rst.el released From: Stefan Merten - 2012-04-29 15:15:28 Attachments: application/pgp-signature Hi! I just released version 1.2.1 of rst.el. AFAICS this also will end up in the upcoming release 0.9 of docutils. I'll soon integrate a version based on this release into Emacs main line. My goal is to have the same release in Emacs repository as in Docutils repository. User visible changes: * Symbols follow reStructuredText syntax more closely This implies that role and directive names with internal underscores, plus signs and colons are handled correctly. This is particularly important for Sphinx users where embedded colons are used frequently for this purpose. * rst-compile-toolsets is now customizable In addition the default value first looks for a rst2*.py and uses it if found or uses the rst2* command. Thanks to Emacs developers for this. * Use faces not variables for font-lock customization There are now customizable rst-* faces which are used. The old rst-*-face variables are still there but deprecated. Thanks to Emacs developers for this. * Font-locking revised again slightly Other changes: * Merge with the changes made in Emacs main line up to bazaar revision 106782 * Minor cleanup Grüße Stefan 
 [Docutils-users] Align attribute for list-table and csv-table From: Bernhard Grotz - 2012-04-29 01:33:53 Attachments: signature.asc Dear developers, wouldn't it be nice if the list-table and csv-table directives have had an ":align:" attribute (much as like as the figure directive)? http://docutils.sourceforge.net/docs/ref/rst/directives.html#figure Would it take (too) much effort to accomplish this? Greetings and thanks in advance, Bernhard 
 Re: [Docutils-users] new release? From: Alan G Isaac - 2012-04-28 19:42:40 On 4/27/2012 12:21 PM, Alan G Isaac wrote: > What is your view of the proposal to simply replace > the quote environment with a custom environment that > behaves like quote, so that at least quotes and > literal blocks can be separately styled? This would > fix an important bug and otherwise leave things as > they are. Just to be clear, does anyone assert that it is *not* a bug to disallow separately styling the quote environment and the literal block environment in LaTeX? (It is of course easily achievable in HTML.) If it *is* a bug, why would it be inappropriate to achieve Guenter's desired indentation of literal blocks with a custom environment, which can just duplicate the quote environment? Alan Isaac 
 Re: [Docutils-users] new release? From: Guenter Milde - 2012-04-28 19:14:05 On 2012-04-28, engelbert gruber wrote: > does this mean release now ? Yes, please. Günter 
 Re: [Docutils-users] new release? From: engelbert gruber - 2012-04-28 15:04:21 does this mean release now ? On Fri, Apr 27, 2012 at 5:48 PM, Guenter Milde wrote: > On 2012-04-27, Alan G Isaac wrote: >> What is the status of the needed fix for the LaTeX writer, >> which was abusing the quote environment to add indentation >> to literal blocks? > >> 1. This meant that quotes and literal text could not >> be separately styled -- certainly a bug. > >> 2. The indentation fails to rely on the setting of the >> requested environment (e.g., lstlistings).  I have >> argued vigorously that this is a bug, but Guenter >> worried about abandoning past formatting practice. > >> I suggested a simple fix: use a custom environment >> instead of the quote environment. Then the writer >> can set a default indentation that can easily be >> overridden in a style sheet. > > > There will be no fix soon (unless someone does a proper one). > > This should certainly not hinder a release to get out major improvements > since the last one. > > Günter > > Changes Since 0.8.1 > =================== > > * General: > >  - New reStructuredText "code" role and directive and "code" option >    of the "include" directive with syntax highlighting by Pygments_. >  - Fix parse_option_marker for option arguments containing =. > > .. _Pygments: http://pygments.org/ > > * setup.py > >  - Fix [ 2971827 ] and [ 3442827 ] >    extras/roman.py moved to docutils/utils/roman.py > > * docutils/frontend.py > >  - Fix [ 3481980 ] Use os.getcwdu() in make_paths_absolute(). > > * docutils/io.py > >  - Fix [ 3395948 ] (Work around encoding problems in Py3k). >  - mode argument for FileOutput avoids code replication in >    BinaryFileOutput. >  - New exceptions InputError and OutputError for IO errors in >    FileInput/FileOutput. > > * docutils/core.py: > >  - No "hard" system exit on file IO errors: catch and report them in >    Publisher.reportException instead. Allows handling by a calling >    application if the configuration setting traceback is True. > > * docutils/utils.py -> docutils/utils/__init__.py > >  - docutils.utils is now a package (providing a place for sub-modules) > >  .. note:: docutils/math, docutils/error_reporting.py, and >     docutils/urischemes.py will move to the utils package in the next >     release, too. See RELEASE-NOTES__ > >     __ RELEASE-NOTES.html > >  - DependencyList uses io.FileOutput and 'utf8' encoding to prevent >    errors recording non-ASCII filenames (fixes [ 3434355 ]). > >  - Fix relative_path() with source=None and unicode target. > > * docutils/parsers/rst/states.py > >  - Fix [ 3402314 ] allow non-ASCII whitespace, punctuation >    characters and "international" quotes around inline markup. >  - Use field_marker pattern to look for start of a >    directive option block (fixes [ 3484857 ]). > > * docutils/parsers/rst/tableparser.py > >  - Fix [ 2926161 ] for simple tables. >    (Combining chars in grid tables still contribute to cell width.) > > * docutils/writers/latex2e/__init__.py > >  - Support the abbreviation and acronym standard roles. >  - Record only files required to generate the LaTeX source as dependencies. >  - Fix handling of missing stylesheets. >  - Use \setcounter{secnumdepth}{0} instead of *-versions >    when suppressing LaTeX section numbering. >  - Use \DUtitle for unsupported section levels >  - Apply [ 3512791 ] do not compare string literals with "is" > > * docutils/writers/xetex/__init__.py > >  - Avoid code duplication with latex2e writer (solves [ 3512728 ]). > > * docutils/writers/html4css1/__init__.py > >  - Change default for math-output setting to MathJax. >  - Fix handling of missing stylesheets. > > * docutils/writers/docutils_xml.py > >  - Use the visitor pattern with default_visit()/default_depart() methods >    instead of minidom to facilitate special handling of selected nodes. >  - Support raw XML (inserted as-is inside a node). > > * docutils/writers/manpage.py > >  - Do not emit comment line with trailing blank. Problematic for VCS. > > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Docutils-users mailing list > Docutils-users@... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. -- http://darefoot.blogspot.com 
 Re: [Docutils-users] new release? From: Alan G Isaac - 2012-04-27 16:21:34 On 4/27/2012 11:48 AM, Guenter Milde wrote: > There will be no fix soon (unless someone does a proper one). What is your view of the proposal to simply replace the quote environment with a custom environment that behaves like quote, so that at least quotes and literal blocks can be separately styled? This would fix an important bug and otherwise leave things as they are. Alan 
 Re: [Docutils-users] new release? From: Guenter Milde - 2012-04-27 15:49:19 On 2012-04-27, Alan G Isaac wrote: > What is the status of the needed fix for the LaTeX writer, > which was abusing the quote environment to add indentation > to literal blocks? > 1. This meant that quotes and literal text could not > be separately styled -- certainly a bug. > 2. The indentation fails to rely on the setting of the > requested environment (e.g., lstlistings). I have > argued vigorously that this is a bug, but Guenter > worried about abandoning past formatting practice. > I suggested a simple fix: use a custom environment > instead of the quote environment. Then the writer > can set a default indentation that can easily be > overridden in a style sheet. There will be no fix soon (unless someone does a proper one). This should certainly not hinder a release to get out major improvements since the last one. Günter Changes Since 0.8.1 =================== * General: - New reStructuredText "code" role and directive and "code" option of the "include" directive with syntax highlighting by Pygments_. - Fix parse_option_marker for option arguments containing =. .. _Pygments: http://pygments.org/ * setup.py - Fix [ 2971827 ] and [ 3442827 ] extras/roman.py moved to docutils/utils/roman.py * docutils/frontend.py - Fix [ 3481980 ] Use os.getcwdu() in make_paths_absolute(). * docutils/io.py - Fix [ 3395948 ] (Work around encoding problems in Py3k). - mode argument for FileOutput avoids code replication in BinaryFileOutput. - New exceptions InputError and OutputError for IO errors in FileInput/FileOutput. * docutils/core.py: - No "hard" system exit on file IO errors: catch and report them in Publisher.reportException instead. Allows handling by a calling application if the configuration setting traceback is True. * docutils/utils.py -> docutils/utils/__init__.py - docutils.utils is now a package (providing a place for sub-modules) .. note:: docutils/math, docutils/error_reporting.py, and docutils/urischemes.py will move to the utils package in the next release, too. See RELEASE-NOTES__ __ RELEASE-NOTES.html - DependencyList uses io.FileOutput and 'utf8' encoding to prevent errors recording non-ASCII filenames (fixes [ 3434355 ]). - Fix relative_path() with source=None and unicode target. * docutils/parsers/rst/states.py - Fix [ 3402314 ] allow non-ASCII whitespace, punctuation characters and "international" quotes around inline markup. - Use field_marker pattern to look for start of a directive option block (fixes [ 3484857 ]). * docutils/parsers/rst/tableparser.py - Fix [ 2926161 ] for simple tables. (Combining chars in grid tables still contribute to cell width.) * docutils/writers/latex2e/__init__.py - Support the abbreviation and acronym standard roles. - Record only files required to generate the LaTeX source as dependencies. - Fix handling of missing stylesheets. - Use \setcounter{secnumdepth}{0} instead of *-versions when suppressing LaTeX section numbering. - Use \DUtitle for unsupported section levels - Apply [ 3512791 ] do not compare string literals with "is" * docutils/writers/xetex/__init__.py - Avoid code duplication with latex2e writer (solves [ 3512728 ]). * docutils/writers/html4css1/__init__.py - Change default for math-output setting to MathJax. - Fix handling of missing stylesheets. * docutils/writers/docutils_xml.py - Use the visitor pattern with default_visit()/default_depart() methods instead of minidom to facilitate special handling of selected nodes. - Support raw XML (inserted as-is inside a node). * docutils/writers/manpage.py - Do not emit comment line with trailing blank. Problematic for VCS. 
 Re: [Docutils-users] new release? From: Alan G Isaac - 2012-04-27 13:20:02 What is the status of the needed fix for the LaTeX writer, which was abusing the quote environment to add indentation to literal blocks? 1. This meant that quotes and literal text could not be separately styled -- certainly a bug. 2. The indentation fails to rely on the setting of the requested environment (e.g., lstlistings). I have argued vigorously that this is a bug, but Guenter worried about abandoning past formatting practice. I suggested a simple fix: use a custom environment instead of the quote environment. Then the writer can set a default indentation that can easily be overridden in a style sheet. Apologies if I overlooked a commit for this. Thanks, Alan Isaac 
 [Docutils-users] new release? From: Guenter Milde - 2012-04-27 12:50:33 On 2012-04-02, engelbert gruber wrote: > hei > 1. releases are not that big an issue, i have to find some hours for > running tests on at least most supported python versions and maybe > some platforms. In this case, it might be a good idea to put out the next release without waiting for all the dust to settle. Maybe besides our testing, we could ask at the Sphinx list for someone to test with Sphinx. > 2. the proposed change is not that aggresiv to the enduser, because > the programm will > exit with a different message, but will exit anyway. > as the message should be more helpful after the change, i do not > think this is really > breaking much. > or am i totally wrong You are right. However, nothing is lost if we do the "behaviour change" and cleanup in the next cycle. Günter 
 Re: [Docutils-users] composing abstract sections for tex From: Guenter Milde - 2012-04-27 12:33:36 On 2012-04-26, Ronny Pfannschmidt wrote: > On 04/26/2012 09:36 PM, David Goodger wrote: >> On Thu, Apr 26, 2012 at 09:49, Ronny Pfannschmidt >> wrote: >>> for my thesis i want to use/create more more than one abstract section, >>> currently i don't see a nice way to create/add abstract sections in a >>> natural way >>> the abstract docinfo fields doesnt really fit my needs With: --use-latex-abstract Use LaTeX abstract environment for the document's abstract. the abstract docinfo field is translated to an \abstract. >> Are you aware than an abstract may contain multiple paragraphs etc.? >> However, an abstract is supposed to be brief. > when i refer to abstracts i mainly mean abstract environments in tex > with different titles set How would you set titles inside an abstract in LaTeX? > for my thesis the abstract is supposed to be roughly one page >> I don't understand why you need more than one abstract. I've never >> seen a paper with more than one. It is quite common in Germany to require both, German and English abstracts for papers, reports or dissertations. >> In any case, a Docutils abstract is merely a specially-formatted >> topic. You can use the "topic" directive arbitrarily. (e.g. nest them i an "abstract" docinfo item). Günter 
 Re: [Docutils-users] composing abstract sections for tex From: Ronny Pfannschmidt - 2012-04-26 21:14:44 On 04/26/2012 09:36 PM, David Goodger wrote: > On Thu, Apr 26, 2012 at 09:49, Ronny Pfannschmidt > wrote: >> for my thesis i want to use/create more more than one abstract section, >> currently i don't see a nice way to create/add abstract sections in a >> natural way >> >> the abstract docinfo fields doesnt really fit my needs > > In what way? > > Are you aware than an abstract may contain multiple paragraphs etc.? > However, an abstract is supposed to be brief. when i refer to abstracts i mainly mean abstract environments in tex with different titles set for my thesis the abstract is supposed to be roughly one page > > I don't understand why you need more than one abstract. I've never > seen a paper with more than one. > so its not a semantic abstract in the same sense, just creating some parts > In any case, a Docutils abstract is merely a specially-formatted > topic. You can use the "topic" directive arbitrarily. > how hard would it be to rewire topics that way 
 Re: [Docutils-users] composing abstract sections for tex From: David Goodger - 2012-04-26 19:36:54 On Thu, Apr 26, 2012 at 09:49, Ronny Pfannschmidt wrote: > for my thesis i want to use/create more more than one abstract section, > currently i don't see a nice way to create/add abstract sections in a > natural way > > the abstract docinfo fields doesnt really fit my needs In what way? Are you aware than an abstract may contain multiple paragraphs etc.? However, an abstract is supposed to be brief. I don't understand why you need more than one abstract. I've never seen a paper with more than one. In any case, a Docutils abstract is merely a specially-formatted topic. You can use the "topic" directive arbitrarily. -- David Goodger ; 
 [Docutils-users] 0.9/syntax highlighting timeframe? From: Marc Abramowitz - 2012-04-26 16:29:27 Not a subscriber - please cc me Curious about when 0.9 with the new "code" block and pygments syntax highlighting might be officially released? Thought that after it's out, maybe GitHub might adopt it for their rst rendering. -Marc http://marc-abramowitz.com Sent from my iPhone 4 
 [Docutils-users] composing abstract sections for tex From: Ronny Pfannschmidt - 2012-04-26 13:49:37 Hi, for my thesis i want to use/create more more than one abstract section, currently i don't see a nice way to create/add abstract sections in a natural way the abstract docinfo fields doesnt really fit my needs 
 Re: [Docutils-users] generating text fragments for use with input/include in a larger latex document From: Alli Quaknaa - 2012-04-26 10:28:01 Hi, the document isn't very polished (in the sense of someone else looking at the source code) and the actual content (some claims I make) aren't true (as my opponent found out), but it's in Czech anyway so most of you won't understand (hopefully :D). I hope everything necessary is provided, if not, feel free to ask. http://koutecky.name/thesis The end result is http://koutecky.name/thesis/bc.pdf, you can see that the HTML output (using MathJax) also works [mostly; what doesn't work are the algorithm passages I wrote about previously] -- http://koutecky.name/thesis/bc.html. You can see I defined a few directives to match the AMS styles, but it wasn't entirely necessary and (at least for the purposes of LaTeX output) I could've easily done with user defined roles. But it gave me more freedom in case I actually needed some more advanced customization. For citations management I recommend KBibTeX. Good luck :) al-Quaknaa On Thu, Apr 26, 2012 at 11:50 AM, Ronny Pfannschmidt wrote: > Hi Alli, > > i would appreciate an example of a titlepage/toc setup. > > -- Ronny > > > > On 04/26/2012 09:54 AM, Alli Quaknaa wrote: >> >> On Wed, Apr 25, 2012 at 10:16 PM, David Goodger >>  wrote: >>> >>> On Wed, Apr 25, 2012 at 13:36, Ronny Pfannschmidt >>>  wrote: >>>> >>>> for my thesis, >>>> i would like to write most of the text with restructuredtext, >>>> >>>> however for the added quality, i'd like to do things like the titlepage >>>> and some basic style stuff and the document structure in normal latex, >>>> and just include the generated fragments. >>>> >>>> what would be the best/canonical way to do that? >>> >>> >>> I would do it the other way around: use the "raw" directive to insert >>> raw LaTeX where appropriate. >> >> >> I agree. I've done exactly this for my thesis last year and ReST is >> really well suited for that -- you can supply the LaTeX template, >> define styles at the beginning of the document and then write it >> practically all in ReST. The only place where I needed a longer LaTeX >> block was some algorithm block. Besides that I just used the math >> directive and everything worked. Including citations, BTW (BibTeX). >> >> If you have any questions I'm able to answer I'll help gladly. >> >> al-Quaknaa >>> >>> >>> -- >>> David Goodger; >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> Docutils-users mailing list >>> Docutils-users@... >>> https://lists.sourceforge.net/lists/listinfo/docutils-users >>> >>> Please use "Reply All" to reply to the list. >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Docutils-users mailing list >> Docutils-users@... >> https://lists.sourceforge.net/lists/listinfo/docutils-users >> >> Please use "Reply All" to reply to the list. > > 
 Re: [Docutils-users] generating text fragments for use with input/include in a larger latex document From: Ronny Pfannschmidt - 2012-04-26 09:50:27 Hi Alli, i would appreciate an example of a titlepage/toc setup. -- Ronny On 04/26/2012 09:54 AM, Alli Quaknaa wrote: > On Wed, Apr 25, 2012 at 10:16 PM, David Goodger wrote: >> On Wed, Apr 25, 2012 at 13:36, Ronny Pfannschmidt >> wrote: >>> for my thesis, >>> i would like to write most of the text with restructuredtext, >>> >>> however for the added quality, i'd like to do things like the titlepage >>> and some basic style stuff and the document structure in normal latex, >>> and just include the generated fragments. >>> >>> what would be the best/canonical way to do that? >> >> I would do it the other way around: use the "raw" directive to insert >> raw LaTeX where appropriate. > > I agree. I've done exactly this for my thesis last year and ReST is > really well suited for that -- you can supply the LaTeX template, > define styles at the beginning of the document and then write it > practically all in ReST. The only place where I needed a longer LaTeX > block was some algorithm block. Besides that I just used the math > directive and everything worked. Including citations, BTW (BibTeX). > > If you have any questions I'm able to answer I'll help gladly. > > al-Quaknaa >> >> -- >> David Goodger; >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Docutils-users mailing list >> Docutils-users@... >> https://lists.sourceforge.net/lists/listinfo/docutils-users >> >> Please use "Reply All" to reply to the list. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Docutils-users mailing list > Docutils-users@... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. 
 Re: [Docutils-users] generating text fragments for use with input/include in a larger latex document From: Tomi Pieviläinen - 2012-04-26 08:08:07 Attachments: signature.asc On Thu, Apr 26, 2012 at 09:54:50AM +0200, Alli Quaknaa wrote: > On Wed, Apr 25, 2012 at 10:16 PM, David Goodger wrote: > > On Wed, Apr 25, 2012 at 13:36, Ronny Pfannschmidt > > wrote: > >> for my thesis, > >> i would like to write most of the text with restructuredtext, > >> > >> however for the added quality, i'd like to do things like the titlepage > >> and some basic style stuff and the document structure in normal latex, > >> and just include the generated fragments. > >> > >> what would be the best/canonical way to do that? > > > > I would do it the other way around: use the "raw" directive to insert > > raw LaTeX where appropriate. > > I agree. I've done exactly this for my thesis last year and ReST is > really well suited for that -- you can supply the LaTeX template, > define styles at the beginning of the document and then write it > practically all in ReST. The only place where I needed a longer LaTeX > block was some algorithm block. Besides that I just used the math > directive and everything worked. Including citations, BTW (BibTeX). > > If you have any questions I'm able to answer I'll help gladly. Would your thesis, with the source, happen to be freely available as an example? -- Tomi Pieviläinen, +358 400 487 504 A: Because it disrupts the natural way of thinking. Q: Why is top posting frowned upon? 
 Re: [Docutils-users] generating text fragments for use with input/include in a larger latex document From: Alli Quaknaa - 2012-04-26 07:54:57 On Wed, Apr 25, 2012 at 10:16 PM, David Goodger wrote: > On Wed, Apr 25, 2012 at 13:36, Ronny Pfannschmidt > wrote: >> for my thesis, >> i would like to write most of the text with restructuredtext, >> >> however for the added quality, i'd like to do things like the titlepage >> and some basic style stuff and the document structure in normal latex, >> and just include the generated fragments. >> >> what would be the best/canonical way to do that? > > I would do it the other way around: use the "raw" directive to insert > raw LaTeX where appropriate. I agree. I've done exactly this for my thesis last year and ReST is really well suited for that -- you can supply the LaTeX template, define styles at the beginning of the document and then write it practically all in ReST. The only place where I needed a longer LaTeX block was some algorithm block. Besides that I just used the math directive and everything worked. Including citations, BTW (BibTeX). If you have any questions I'm able to answer I'll help gladly. al-Quaknaa > > -- > David Goodger ; > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Docutils-users mailing list > Docutils-users@... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. 
 Re: [Docutils-users] Small text on s5? From: Paolo Cavallini - 2012-04-25 20:54:25 Il 25/04/2012 22:15, David Goodger ha scritto: > On Wed, Apr 25, 2012 at 11:16, Paolo Cavallini wrote: >> Hi all. >> I have found only one way of having smaller text on a slide, i.e. the >> :tiny:text directive, but this is ugly if I want all or most of the text on a >> slide smaller. In fact, lists and bullets are not well supported,and the >> directive must be repeated for each line. >> Is there a better way? > Yes. Use the "class" or "container" directives > (http://docutils.sourceforge.net/docs/ref/rst/directives.html). > > See http://docutils.sourceforge.net/docs/user/slide-shows.txt for examples. > oh, I see - thanks a lot! -- Paolo Cavallini See: http://www.faunalia.it/pc 
 Re: [Docutils-users] generating text fragments for use with input/include in a larger latex document From: David Goodger - 2012-04-25 20:17:26 On Wed, Apr 25, 2012 at 13:36, Ronny Pfannschmidt wrote: > for my thesis, > i would like to write most of the text with restructuredtext, > > however for the added quality, i'd like to do things like the titlepage > and some basic style stuff and the document structure in normal latex, > and just include the generated fragments. > > what would be the best/canonical way to do that? I would do it the other way around: use the "raw" directive to insert raw LaTeX where appropriate. -- David Goodger ; 
 Re: [Docutils-users] Small text on s5? From: David Goodger - 2012-04-25 20:15:50 On Wed, Apr 25, 2012 at 11:16, Paolo Cavallini wrote: > Hi all. > I have found only one way of having smaller text on a slide, i.e. the > :tiny:text directive, but this is ugly if I want all or most of the text on a > slide smaller. In fact, lists and bullets are not well supported,and the > directive must be repeated for each line. > Is there a better way? Yes. Use the "class" or "container" directives (http://docutils.sourceforge.net/docs/ref/rst/directives.html). See http://docutils.sourceforge.net/docs/user/slide-shows.txt for examples. -- David Goodger ; 

Showing results of 41

1 2 > >> (Page 1 of 2)