G. Milde | 2 Nov 10:24 2007
Picon

latex writer should include hyperref only at the end [ docutils-Bugs-1822272 ]

As there is IMO quite a lot to discuss here, I'd like to transfer this to
the devel list.

> Bugs item #1822272, was opened at 2007-10-29 18:36

> The problem is, hyperref is included before many extensions, among which the one that the user may specify
using the --stylesheet command-line option.
> This is highly likely to trigger incompatibilities.

> Comment By: Nicolas Girard (ngirard) Date: 2007-11-01 16:35

> > there are two problems ::
> > 1. the writer needs to read latex which might give new errors

> Well, which ones ? Given the question
> "Does the 'user stylesheet' s include hyperref",
> isn't the answer as straightforward as:

> 1. executing "kpathsea s" to locate the stylesheet file
> 2. opening the stylesheet file
> 3. looking for a line containing "\usepackage" or "\RequirePackage" and
> "hyperref", regardless of the comments

IMO, this is too complicated, I like the clear distinction of rst->tex
conversion (which works also without LaTeX installed) and tex->pdf
done independently (and maybe on a different computer).

> > A solution to this problem might be to have a default docutils latex
> > style file that can be *replaced* by user-specific one [...] See also
> > latex2e_external_stylesheet__ for a proposal of such a latex writer
(Continue reading)

G. Milde | 2 Nov 10:45 2007
Picon

Re: Handling the class directive in the LaTeX writer

On 31.10.07, Nicolas Girard wrote:
> Hi,
> for personal use in any case, and for anyone interested if any, I'd like to 
> change the way the LaTeX writer deals with:: 

>   .. class:: c1...ci...cn

> upon sections and paragraphs.

Actually, I'd like to see a generic solution as currently the handling of
classes is breaking `syntax highlight via pygments`__.

__ http://docutils.sourceforge.net/sandbox/code-block-directive/docs/syntax-highlight.html#writing

However, converting classes in the sense of CSS to something equivalent
in latex is a hard task.

* Class settings should be ignored by writers that do not implement them.

  Currently, you can style the html output with some class argument
  without affecting the PDF generation.

  With your proposal, such an rst-file would fail to convert to PDF if
  you do not have a stylesheet that defines all the \AtBegin* and \AtEnd*
  commands.

* The order of the class arguments is irrelevant:

  ``.. class:: c1 ci cn``   ==    ``.. class:: ci cn c1``

(Continue reading)

Facundo Batista | 7 Nov 18:05 2007
Picon

Re: Docutils, Python PEPs, and non-ASCII day names

2007/10/26, David Goodger <goodger <at> python.org>:

> The latest version should be fine, but needs to be tested well.  I
> don't have time to test.

If I say to the SVN in the pep branch to get docutils to the version
5461, the problem with Unicode is already fixed.

Everything runs smoothly with the newer version. The generated htmls
are a bit different, but as far I saw, with small changes that are for
better. For example...

    <div class="section">
    <h2><a class="toc-backref" href="#id33" id="numbers"
            name="numbers">Numbers</a></h2>

...changed for...

    <div class="section" id="numbers">
    <h2><a class="toc-backref" href="#id33">Numbers</a></h2>

. This and other change takes all the changes I saw reviewing several
files. The other one is that now we don't have 'class ="reference"',
but 'class ="reference internal"' or 'class ="reference external"'.

Visually, I didn't find any difference in all the files I checked.
Here I attach the diff for PEP 3000, as an example.

If you don't see any problem, I'll commit the change that makes this
branch to get the newer version of docutils.
(Continue reading)

SourceForge.net | 12 Nov 13:01 2007
Picon
Picon

[ docutils-Bugs-1830380 ] Replace with role :sup: does not work with language_code: fr

Bugs item #1830380, was opened at 2007-11-12 12:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=1830380&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: lpezard (lpezard)
Assigned to: Nobody/Anonymous (nobody)
Summary: Replace with role :sup: does not work with language_code: fr

Initial Comment:
Here is my original posting to docutils-user mailing list and David Goodger reply:

My posting:
-----------

I've tried the following replacements:

     .. |Na+| replace:: Na\ :sup:`+`

     Le |Na+| est l'ion sodium.

(Continue reading)

SourceForge.net | 12 Nov 14:50 2007
Picon
Picon

[ docutils-Bugs-1830442 ] Replace with role :sup: does not work with language_code: fr

Bugs item #1830442, was opened at 2007-11-12 13:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=422030&aid=1830442&group_id=38414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: lpezard (lpezard)
Assigned to: Nobody/Anonymous (nobody)
Summary: Replace with role :sup: does not work with language_code: fr

Initial Comment:
Here is my original posting to docutils-user mailing list and David Goodger reply:

My posting:
-----------

I've tried the following replacements:

     .. |Na+| replace:: Na\ :sup:`+`

     Le |Na+| est l'ion sodium.

(Continue reading)


Gmane