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: Guenter M. <mi...@us...> - 2023-01-30 09:03:05
|
On 2023-01-19, Alan G. Isaac wrote: > On 1/18/2023 5:05 AM, Guenter Milde via Docutils-users wrote: >> Dear Alan, >> On 2023-01-14, Alan G. Isaac wrote: >>> In the latex writer, in >>> LaTeXTranslator.depart_document >>> might it be considered to move the docinfo section >>> to a separate method? This is now done at [r9324]. Please keep in mind: * The new functions are not part of the public API. Like all undocumented objects (i.e. elements without a docstring), they are only provisional, without the promise of backwards compatibility. * As a general rule, if subclassing a Translator class: Safe subclassing: when overriding methods, treat ``visit_*`` and ``depart_*`` methods as a unit to prevent breaks due to internal changes. Günter |
From: Alan G. I. <ala...@gm...> - 2023-01-19 13:56:53
|
On 1/18/2023 5:05 AM, Guenter Milde via Docutils-users wrote: > Dear Alan, > > On 2023-01-14, Alan G. Isaac wrote: >> In the latex writer, in >> LaTeXTranslator.depart_document >> might it be considered to move the docinfo section >> to a separate method? Say `depart_document_docinfo` >> or something like that? > >> Motivation: it is the only part of the method that >> rst2beamer changes, but there has been churn in >> the other parts of `depart_document`. (So there >> was really no need for the rst2beamer method to >> get out of sync as it has.) > > Something like the patch below? > > Günter > -- > > From: milde <mi...@us...> > Date: Wed, 18 Jan 2023 10:57:51 +0100 > Subject: [PATCH] LaTeX writer: outsourcing of some code from `depart_document()`. > > Move parts of the spaghetti code in `LaTeXTranslator.depart_document() > to new auxiliary methods `LaTeXTranslator.append_title()` and > `LaTeXTranslator.append_bibliography()`. > --- > docutils/docutils/writers/latex2e/__init__.py | 72 ++++++++++++++++++++++++++++++++++++++++++++---------------------------- > 1 file changed, 44 insertions(+), 28 deletions(-) > > diff --git a/docutils/docutils/writers/latex2e/__init__.py b/docutils/docutils/writers/latex2e/__init__.py > index d46272a..4386620 100644 > --- a/docutils/docutils/writers/latex2e/__init__.py > +++ b/docutils/docutils/writers/latex2e/__init__.py > @@ -1995,5 +1995,5 @@ class LaTeXTranslator(nodes.NodeVisitor): > > def depart_document(self, node): > - # Complete header with information gained from walkabout > + # Complete "parts" with information gained from walkabout > # * language setup > if (self.babel.otherlanguages > @@ -2011,30 +2011,49 @@ class LaTeXTranslator(nodes.NodeVisitor): > if self.pdfinfo: > self.pdfsetup += [r'\hypersetup{'] + self.pdfinfo + ['}'] > - # Complete body > - # * document title (with "use_latex_docinfo" also > - # 'author', 'organization', 'contact', 'address' and 'date') > - if self.title or ( > - self.use_latex_docinfo and (self.author_stack or self.date)): > - # \title (empty \title prevents error with \maketitle) > - title = [''.join(self.title)] > - if self.title: > - title += self.title_labels > - if self.subtitle: > - title += [r'\\', > + # * title (including author(s) and date if using "latex_docinfo") > + self.append_title() # see below > + # * bibliography > + self.append_bibliogaphy() # see below > + # * make sure to generate a toc file if needed for local contents: > + if 'minitoc' in self.requirements and not self.has_latex_toc: > + self.out.append('\n\\faketableofcontents % for local ToCs\n') > + > + def append_title(self): > + # Append ``\title``, ``\author``, and ``\date`` to "titledata" > + # and ``\maketitle`` to "body_pre_docinfo" parts. > + # > + # Auxiliary function called by `self.depart_document()`. > + if not (self.title > + or (self.use_latex_docinfo > + and (self.author_stack or self.date))): > + return # do nothing, there is no title data > + # We need all three of ``\title``, ``\author``, and ``\date`` > + # (even if empty) to prevent errors and/or automatic display > + # of the current date by \maketitle. > + # \title > + title_arg = [''.join(self.title)] # ensure len == 1 > + if self.title: > + title_arg += self.title_labels > + if self.subtitle: > + title_arg += [r'\\', > r'\DUdocumentsubtitle{%s}' % ''.join(self.subtitle), > ] + self.subtitle_labels > - self.titledata.append(r'\title{%s}' % '%\n '.join(title)) > - # \author (empty \author prevents warning with \maketitle) > - authors = ['\\\\\n'.join(author_entry) > - for author_entry in self.author_stack] > - self.titledata.append(r'\author{%s}' % > - ' \\and\n'.join(authors)) > - # \date (empty \date prevents defaulting to \today) > - self.titledata.append(r'\date{%s}' % ', '.join(self.date)) > - # \maketitle in the body formats title with LaTeX > - self.body_pre_docinfo.append('\\maketitle\n') > - > - # * bibliography > - # TODO insertion point of bibliography should be configurable. > + self.titledata.append(r'\title{%s}' % '%\n '.join(title_arg)) > + # \author > + author_arg = ['\\\\\n'.join(author_entry) > + for author_entry in self.author_stack] > + self.titledata.append(r'\author{%s}' % > + ' \\and\n'.join(author_arg)) > + # \date > + self.titledata.append(r'\date{%s}' % ', '.join(self.date)) > + # \maketitle > + # Must be in the document body. We add it to `body_pre_docinfo` > + # to allow templates to put `titledata` into the document preamble. > + self.body_pre_docinfo.append('\\maketitle\n') > + > + def append_bibliogaphy(self): > + # Add bibliography at end of document. > + # TODO insertion point should be configurable. > + # Auxiliary function called by `depart_document`. > if self.bibtex and self._bibitems: > self.out.append('\n\\bibliographystyle{%s}\n' % self.bibtex[0]) > @@ -2054,7 +2073,4 @@ class LaTeXTranslator(nodes.NodeVisitor): > (bibitem[0], cite_key, bibitem[1])) > self.out.append('\\end{thebibliography}\n') > - # * make sure to generate a toc file if needed for local contents: > - if 'minitoc' in self.requirements and not self.has_latex_toc: > - self.out.append('\n\\faketableofcontents % for local ToCs\n') > > def visit_emphasis(self, node): > -- > libgit2 1.1.0 > Yes, that seems much better to me. Please announce when/if you apply it. Thanks! Alan |
From: Guenter M. <mi...@us...> - 2023-01-18 10:06:15
|
Dear Alan, On 2023-01-14, Alan G. Isaac wrote: > In the latex writer, in > LaTeXTranslator.depart_document > might it be considered to move the docinfo section > to a separate method? Say `depart_document_docinfo` > or something like that? > Motivation: it is the only part of the method that > rst2beamer changes, but there has been churn in > the other parts of `depart_document`. (So there > was really no need for the rst2beamer method to > get out of sync as it has.) Something like the patch below? Günter -- From: milde <mi...@us...> Date: Wed, 18 Jan 2023 10:57:51 +0100 Subject: [PATCH] LaTeX writer: outsourcing of some code from `depart_document()`. Move parts of the spaghetti code in `LaTeXTranslator.depart_document() to new auxiliary methods `LaTeXTranslator.append_title()` and `LaTeXTranslator.append_bibliography()`. --- docutils/docutils/writers/latex2e/__init__.py | 72 ++++++++++++++++++++++++++++++++++++++++++++---------------------------- 1 file changed, 44 insertions(+), 28 deletions(-) diff --git a/docutils/docutils/writers/latex2e/__init__.py b/docutils/docutils/writers/latex2e/__init__.py index d46272a..4386620 100644 --- a/docutils/docutils/writers/latex2e/__init__.py +++ b/docutils/docutils/writers/latex2e/__init__.py @@ -1995,5 +1995,5 @@ class LaTeXTranslator(nodes.NodeVisitor): def depart_document(self, node): - # Complete header with information gained from walkabout + # Complete "parts" with information gained from walkabout # * language setup if (self.babel.otherlanguages @@ -2011,30 +2011,49 @@ class LaTeXTranslator(nodes.NodeVisitor): if self.pdfinfo: self.pdfsetup += [r'\hypersetup{'] + self.pdfinfo + ['}'] - # Complete body - # * document title (with "use_latex_docinfo" also - # 'author', 'organization', 'contact', 'address' and 'date') - if self.title or ( - self.use_latex_docinfo and (self.author_stack or self.date)): - # \title (empty \title prevents error with \maketitle) - title = [''.join(self.title)] - if self.title: - title += self.title_labels - if self.subtitle: - title += [r'\\', + # * title (including author(s) and date if using "latex_docinfo") + self.append_title() # see below + # * bibliography + self.append_bibliogaphy() # see below + # * make sure to generate a toc file if needed for local contents: + if 'minitoc' in self.requirements and not self.has_latex_toc: + self.out.append('\n\\faketableofcontents % for local ToCs\n') + + def append_title(self): + # Append ``\title``, ``\author``, and ``\date`` to "titledata" + # and ``\maketitle`` to "body_pre_docinfo" parts. + # + # Auxiliary function called by `self.depart_document()`. + if not (self.title + or (self.use_latex_docinfo + and (self.author_stack or self.date))): + return # do nothing, there is no title data + # We need all three of ``\title``, ``\author``, and ``\date`` + # (even if empty) to prevent errors and/or automatic display + # of the current date by \maketitle. + # \title + title_arg = [''.join(self.title)] # ensure len == 1 + if self.title: + title_arg += self.title_labels + if self.subtitle: + title_arg += [r'\\', r'\DUdocumentsubtitle{%s}' % ''.join(self.subtitle), ] + self.subtitle_labels - self.titledata.append(r'\title{%s}' % '%\n '.join(title)) - # \author (empty \author prevents warning with \maketitle) - authors = ['\\\\\n'.join(author_entry) - for author_entry in self.author_stack] - self.titledata.append(r'\author{%s}' % - ' \\and\n'.join(authors)) - # \date (empty \date prevents defaulting to \today) - self.titledata.append(r'\date{%s}' % ', '.join(self.date)) - # \maketitle in the body formats title with LaTeX - self.body_pre_docinfo.append('\\maketitle\n') - - # * bibliography - # TODO insertion point of bibliography should be configurable. + self.titledata.append(r'\title{%s}' % '%\n '.join(title_arg)) + # \author + author_arg = ['\\\\\n'.join(author_entry) + for author_entry in self.author_stack] + self.titledata.append(r'\author{%s}' % + ' \\and\n'.join(author_arg)) + # \date + self.titledata.append(r'\date{%s}' % ', '.join(self.date)) + # \maketitle + # Must be in the document body. We add it to `body_pre_docinfo` + # to allow templates to put `titledata` into the document preamble. + self.body_pre_docinfo.append('\\maketitle\n') + + def append_bibliogaphy(self): + # Add bibliography at end of document. + # TODO insertion point should be configurable. + # Auxiliary function called by `depart_document`. if self.bibtex and self._bibitems: self.out.append('\n\\bibliographystyle{%s}\n' % self.bibtex[0]) @@ -2054,7 +2073,4 @@ class LaTeXTranslator(nodes.NodeVisitor): (bibitem[0], cite_key, bibitem[1])) self.out.append('\\end{thebibliography}\n') - # * make sure to generate a toc file if needed for local contents: - if 'minitoc' in self.requirements and not self.has_latex_toc: - self.out.append('\n\\faketableofcontents % for local ToCs\n') def visit_emphasis(self, node): -- libgit2 1.1.0 |
From: Guenter M. <mi...@us...> - 2023-01-17 17:23:08
|
On 2023-01-16, Alan G. Isaac wrote: > One test failed in ``alltests.py``. If I understand correctly, the > result is correct, but the expected result needs fixing. Could you try again with [r9323]? Thanks, Günter Milde |
From: Alan G. I. <ala...@gm...> - 2023-01-16 23:00:34
|
On 1/16/2023 5:45 PM, Guenter Milde via Docutils-users wrote: > Could you try with --stylesheet-path and also try running the test suite > (docutils/tests/alltests.py), please? Done. I ran into only the following problem: One test failed in ``alltests.py``. If I understand correctly, the result is correct, but the expected result needs fixing. Alan ====================================================================== FAIL: test_find_file_in_dirs (test_utils.HelperFunctionTests.test_find_file_in_dirs) ---------------------------------------------------------------------- Traceback (most recent call last): File "D:\software\svn\docutils-code\docutils\test\test_utils.py", line 361, in test_find_file_in_dirs self.assertEqual(utils.find_file_in_dirs('alltests.py', dirs), AssertionError: 'D:/software/svn/docutils-code/docutils/test/alltests.py' != 'D:\\software\\svn\\docutils-code\\docutils\\test\\alltests.py' - D:/software/svn/docutils-code/docutils/test/alltests.py ? ^ ^ ^ ^ ^ ^ + D:\software\svn\docutils-code\docutils\test\alltests.py ? ^ ^ ^ ^ ^ ^ ---------------------------------------------------------------------- Ran 1751 tests in 4.267s FAILED (failures=1, skipped=2) |
From: Guenter M. <mi...@us...> - 2023-01-16 22:46:18
|
On 2023-01-16, Alan G. Isaac wrote: > On 1/16/2023 4:29 AM, Guenter Milde via Docutils-users wrote: >> Dear Alan Isaac, >> thank you for the bug report and fix proposal. >> The commit [r9316] implements a version that avoids fixes side-effects >> that broke the test suite with the original proposal and tries to clarify >> the documentation. >> Could you please test and tell if this is what you intended >> (I don't have Windows). > This works for me. > Note: I use --styleshseet, not --stylesheet-path > I did try out the latter just fyi, and it worked, > but I did not try out the relative-path expansion. Could you try with --stylesheet-path and also try running the test suite (docutils/tests/alltests.py), please? Günter |
From: Alan G. I. <ala...@gm...> - 2023-01-16 17:14:15
|
On 1/16/2023 4:29 AM, Guenter Milde via Docutils-users wrote: > Dear Alan Isaac, > > thank you for the bug report and fix proposal. > > > The commit [r9316] implements a version that avoids fixes side-effects > that broke the test suite with the original proposal and tries to clarify > the documentation. > > Could you please test and tell if this is what you intended > (I don't have Windows). > This works for me. Note: I use --styleshseet, not --stylesheet-path I did try out the latter just fyi, and it worked, but I did not try out the relative-path expansion. Thanks! Alan |
From: Guenter M. <mi...@us...> - 2023-01-16 09:29:47
|
Dear Alan Isaac, thank you for the bug report and fix proposal. On 2023-01-14, Alan G. Isaac wrote: > This is fixed by changing the return of LaTeXTranslator.stylesheet_call to > return cmd % path.as_posix() > (I.e., by converting the path to a posix representation.) This change would mean that with ``rst2latex --stylesheet=C:\tmp\test.sty`` we will get \usepackage{C:/tmp/test} i.e. a conversion of backwards to forward slashes instead of a "literal" use as announced for "--stylesheet" arguments with the HTML writers. However, I believe this would be "the right thing" as LaTeX struggles with the backwards slashes anyway. The commit [r9316] implements a version that avoids fixes side-effects that broke the test suite with the original proposal and tries to clarify the documentation. Could you please test and tell if this is what you intended (I don't have Windows). Thanks again, Günter Milde > On 1/14/2023 12:39 PM, Alan G. Isaac wrote: >> With current docutils on Windows: >> --stylesheet=C:/Users/aisaac/svn/aisaac/mydocs/372/372slides >> is producing >> %%% User specified packages and stylesheets >> \usepackage{C:\Users\aisaac\svn\aisaac\mydocs\372\372slides} >> The forward slashes need to be retained, of course. >> This might (?) be related to this in the history: >> docutils/utils/__init__.py >> find_file_in_dirs() now returns a POSIX path also on Windows; get_stylesheet_list() no longer converts "" to "/". >> If so, that is a breaking change. >> Alan Isaac > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > Please use "Reply All" to reply to the list. |
From: Guenter M. <mi...@us...> - 2023-01-15 20:40:18
|
On 2023-01-15, Alan G. Isaac wrote: > What is the current status of pygments support > for LaTeX writers? Syntax highlighting with Pygments is implemented in Docutils since version 0.9. Code is parsed by the Pygments syntax highlighter and tokens are stored in nested inline elements with class arguments according to their syntactic category. As inline elements are supported by all writers, no change is required on the writer side. The actual highlighting requires a style-sheet (e.g. one generated by Pygments, see the sandbox/stylesheets for examples). See https://docutils.sourceforge.io/docs/ref/rst/directives.html#code https://docutils.sourceforge.io/docs/user/config.html#syntax-highlight and just try it out. Günter Milde |
From: Alan G. I. <ala...@gm...> - 2023-01-15 17:15:33
|
What is the current status of pygments support for LaTeX writers? I couldn't find much in the history, and search made it seem that this https://docutils.sourceforge.io/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/rst2latex-pygments (in the sandbox) is the basic answer. Note that I am not advocating for or against support. I am just trying to understand whether it is dormant or not. Thanks! Alan |
From: Alan G. I. <ala...@gm...> - 2023-01-14 22:55:20
|
In the latex writer, in LaTeXTranslator.depart_document might it be considered to move the docinfo section to a separate method? Say `depart_document_docinfo` or something like that? Motivation: it is the only part of the method that rst2beamer changes, but there has been churn in the other parts of `depart_document`. (So there was really no need for the rst2beamer method to get out of sync as it has.) Thanks for considering, Alan Isaac |
From: Guenter M. <mi...@us...> - 2023-01-14 18:42:53
|
On 2023-01-14, Alan G. Isaac wrote: > I'm using current docutils. > rst2beamer uses the LaTeX writer. > Has a ``_use_latex_citations`` attribute > been removed from the docutils LaTeXTranslator? The name has been normalized with the other "use_latex_..." attributes in r8880 from 05.11.21 Günter |
From: Alan G. I. <ala...@gm...> - 2023-01-14 18:38:41
|
This is fixed by changing the return of LaTeXTranslator.stylesheet_call to return cmd % path.as_posix() (I.e., by converting the path to a posix representation.) Alan Isaac On 1/14/2023 12:39 PM, Alan G. Isaac wrote: > With current docutils on Windows: > --stylesheet=C:/Users/aisaac/svn/aisaac/mydocs/372/372slides > is producing > %%% User specified packages and stylesheets > \usepackage{C:\Users\aisaac\svn\aisaac\mydocs\372\372slides} > > The forward slashes need to be retained, of course. > > This might (?) be related to this in the history: > > docutils/utils/__init__.py > > find_file_in_dirs() now returns a POSIX path also on Windows; get_stylesheet_list() no longer converts "" to "/". > > If so, that is a breaking change. > > Alan Isaac |
From: Alan G. I. <ala...@gm...> - 2023-01-14 17:39:54
|
With current docutils on Windows: --stylesheet=C:/Users/aisaac/svn/aisaac/mydocs/372/372slides is producing %%% User specified packages and stylesheets \usepackage{C:\Users\aisaac\svn\aisaac\mydocs\372\372slides} The forward slashes need to be retained, of course. This might (?) be related to this in the history: docutils/utils/__init__.py find_file_in_dirs() now returns a POSIX path also on Windows; get_stylesheet_list() no longer converts "" to "/". If so, that is a breaking change. Alan Isaac |
From: Alan G. I. <ala...@gm...> - 2023-01-14 16:42:45
|
I'm using current docutils. rst2beamer uses the LaTeX writer. Has a ``_use_latex_citations`` attribute been removed from the docutils LaTeXTranslator? This missing attribute looks to be causing the problem. Thanks, Alan On 1/14/2023 3:42 AM, Guenter Milde via Docutils-users wrote: > On 2023-01-14, Alan G. Isaac wrote: >> I can no longer compile some documents with rst2beamer. >> (They compiled a year ago.) > > Which Docutils version are you using now, which a year ago? > Are you using the LaTeX or the XeTeX writer? > >> Did something change with --use-latex-citations? >> (I'm not setting it.) > > Not yet. (See RELEASE-NOTES) > > Suggested diagnosis: > > Look out for changes between the relevant versions in the RELEASE-NOTES and > the HISTORY (there were some default changes recently). > >> Suggested fix? > > Adapt rst2beamer.py to the new behaviour. > > As a stop gap measure: try the various "--legacy..." and "--use-latex..." > settings. > > > Günter > > > > _______________________________________________ > Docutils-users mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-users > > Please use "Reply All" to reply to the list. |
From: Guenter M. <mi...@us...> - 2023-01-14 08:43:05
|
On 2023-01-14, Alan G. Isaac wrote: > I can no longer compile some documents with rst2beamer. > (They compiled a year ago.) Which Docutils version are you using now, which a year ago? Are you using the LaTeX or the XeTeX writer? > Did something change with --use-latex-citations? > (I'm not setting it.) Not yet. (See RELEASE-NOTES) Suggested diagnosis: Look out for changes between the relevant versions in the RELEASE-NOTES and the HISTORY (there were some default changes recently). > Suggested fix? Adapt rst2beamer.py to the new behaviour. As a stop gap measure: try the various "--legacy..." and "--use-latex..." settings. Günter |
From: Alan G. I. <ala...@gm...> - 2023-01-14 00:45:44
|
I can no longer compile some documents with rst2beamer. (They compiled a year ago.) Did something change with --use-latex-citations? (I'm not setting it.) Suggested fix? Alan Isaac Traceback (most recent call last): File "C:\Program Files\Python38\Scripts\rst2beamer-script.py", line 11, in <module> load_entry_point('rst2beamer3k==0.9.1', 'console_scripts', 'rst2beamer')() File "C:\Program Files\Python38\lib\site-packages\rst2beamer.py", line 1304, in main publish_cmdline( File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\core.py", line 391, in publish_cmdline output = pub.publish( File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\core.py", line 227, in publish output = self.writer.write(self.document, self.destination) File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\writers\__init__.py", line 76, in write self.translate() File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\writers\latex2e\__init__.py", line 267, in translate self.document.walkabout(visitor) File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\nodes.py", line 199, in walkabout visitor.dispatch_departure(self) File "C:\Program Files\Python38\lib\site-packages\docutils-0.20b0.dev0-py3.8.egg\docutils\nodes.py", line 2019, in dispatch_departure return method(node) File "C:\Program Files\Python38\lib\site-packages\rst2beamer.py", line 930, in depart_document if self._use_latex_citations and len(self._bibitems) > 0: AttributeError: 'BeamerTranslator' object has no attribute '_use_latex_citations' |
From: Matthias G. <mat...@gm...> - 2023-01-07 11:20:26
|
Dear docutils maintainers. A few months ago, I've reported a problem with sphinxcontrib-bibtex (https://github.com/mcmtroffaes/sphinxcontrib-bibtex/issues/309), which turned out to actually be a problem with docutils. There is also a related Sphinx issue (https://github.com/sphinx-doc/sphinx/issues/10784) which shows that the problem can also appear without using sphinxcontrib-bibtex. The maintainer of sphinxcontrib-bibtex has kindly provided a patch (https://sourceforge.net/p/docutils/patches/195/), which has already been merged in the meantime. I don't know the release procedure nor the roadmap of docutils, but would it be possible to create a new docutils release that contains this fix (and maybe other improvements)? Thanks in advance! In case you are wondering how the problem looks in practice, here is an example: https://nbsphinx.readthedocs.io/en/0.8.11/a-normal-rst-file.html#citations cheers, Matthias |
From: Satish B.D. <bds...@gm...> - 2022-09-12 13:29:51
|
Thanks Günter, > I know of a "math extension" for sphinx that designs a special meaning > (start/stop mathematical mode) to $. There may be other extensions or > pre-/post-processing changing the outcome... Indeed it was a post-processing bug, where the dollar had to be escaped. Sorry for the noise. Regards, Satish |
From: Guenter M. <mi...@us...> - 2022-09-12 12:32:41
|
On 2022-09-09, Satish B.D. wrote: > Hi, > Does the dollar sign have any meaning inside double asterisks in rst? > I want the following in bold: > **US $25** > The HTML is rendered as: ><p><strong>US 5<p><strong> Here, converting your example line with both, `rst2html` as well as `rst2html5` results in:: <p><strong>US $25</strong></p> Docutils version 0.19.1dev > Where did the $2 disappear? Am I missing something? I can only guess: In standard rST, the character "$" has no special meaning. I know of a "math extension" for sphinx that designs a special meaning (start/stop mathematical mode) to $. There may be other extensions or pre-/post-processing changing the outcome... Günter |
From: Satish B.D. <bds...@gm...> - 2022-09-09 17:33:15
|
Hi, Does the dollar sign have any meaning inside double asterisks in rst? I want the following in bold: **US $25** The HTML is rendered as: <p><strong>US 5<p><strong> Where did the $2 disappear? Am I missing something? Thanks and regards, Satish |
From: engelbert g. <eng...@gm...> - 2022-07-05 20:24:08
|
Release 0.19 (2022-07-05) ========================= (Release 0.19b1 (2022-06-21)) * Drop support for Python 2.7, 3.5, and 3.6. * Output changes: HTML5: Wrap groups of footnotes in an ``<aside>`` for easier styling. The CSS rule ``.footnote-list { display: contents; }`` can be used to restore the behaviour of custom CSS styles. * After package installation, the CLI commands ``python -m docutils`` and ``docutils`` start the `generic command line front end tool`__. __ docs/user/tools.html#generic-command-line-front-end * Support parsing "Markdown" input with 3rd party parsers myst_, pycmark_, or recommonmark_. * The default values for the "pep-references", "rfc-base-url", and "python-home" `configuration settings`_ now use the "https:" scheme. The PEP-writer template's header is updated to fix links and resemble the header of official PEPs. * Various bugfixes and improvements (see HISTORY_). .. _myst: https://pypi.org/project/myst-docutils .. _pycmark: https://pypi.org/project/pycmark/ .. _recommonmark: https://pypi.org/project/recommonmark/ .. _configuration settings: docs/user/config.html |
From: engelbert g. <eng...@gm...> - 2022-06-21 22:25:20
|
Thanks to Günter and Adam several changes happened that made a release necessary RELEASE NOTES 0.19 * Drop support for Python 2.7, 3.5, and 3.6. * Output changes: HTML5: Wrap groups of footnotes in an ``<aside>`` for easier styling. The CSS rule ``.footnote-list { display: contents; }`` can be used to restore the behaviour of custom CSS styles. * After package installation, the CLI commands ``python -m docutils`` and ``docutils`` start the `generic command line front end tool`__. __ docs/user/tools.html#generic-command-line-front-end * Support parsing "Markdown" input with 3rd party parsers myst_, pycmark_, or recommonmark_. * The default values for the "pep-references", "rfc-base-url", and "python-home" `configuration settings`_ now use the "https:" scheme. The PEP-writer template's header is updated to fix links and resemble the header of official PEPs. * Various bugfixes and improvements (see HISTORY_). install with : pip install docutils --pre Release 0.19 is planned for july 5th cheers and all the best engelbert |
From: engelbert g. <eng...@gm...> - 2022-06-19 12:54:45
|
Hello due to the work of Günter and Adam a release is necessary current plan is 0.19.0b1 on tuesday june 21 0.19 on july 5 cheers and thanks for the work e |
From: Adam T. <aat...@ou...> - 2022-06-09 11:55:53
|
Using Python 3.10's ``-X warn_default_encoding`` argument to Python, we can see a large number of places where the default encoding is used. On posix systems this is now UTF-8 following PEP 538 [1], but on Windows a non-unicode codepage can be used. The attached patch fixes the majority of these instances. A [1]: https://peps.python.org/pep-0538/ |