![[ICO]](/icons/blank.gif){kind=icon}
![[DIR]](/icons/back.gif){kind=icon}
![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/folder.gif){kind=icon}
| Name | Last modified | Size | Description |
|---|---|---|---|---|
| Parent Directory | - | ||
| REDME.txt | 05-Sep-2008 20:27 | 507 | |
| data/ | 18-Dec-2009 23:46 | - | |
| docs/ | 18-Dec-2009 23:46 | - | |
| latex2e_adaptive_preamble/ | 18-Dec-2009 23:46 | - | |
| latex2e_external_stylesheet/ | 18-Dec-2009 23:46 | - | |
| latex2e_listings/ | 18-Dec-2009 23:46 | - | |
| tests/ | 18-Dec-2009 23:46 | - | |
| tools/ | 18-Dec-2009 23:46 | - | |
| Author: | Günter Milde <milde@users.berlios.de> |
|---|---|
| Date: | 2009-10-15 |
This sandbox project is a place to try out and discuss latex2e writer extensions and alternative latex writers for special needs.
Contents
Which default font do you prefer for the output?
Did you have problems with Find or Export of words with non-ASCII chars (e.g. Umlauts) in the PDF reader (Acrobat, xpdf, ...)
Which font encoding do you prefer for the output?
Does the latex2e writer need a --stylesheet-path option?
Feature wishes or ideas of improvement for the latex2e writer.
Users of rst2latex2.py are encouraged to respond by mail to the docutils-users list.
See also the notes in http://docutils.sourceforge.net/docs/user/latex.html#problems and the TODO list in http://docutils.sourceforge.net/docs/dev/todo.html#latex-writer
Which default font do you prefer for the output?
Using different fonts (e.g. standard postscript fonts) can be achieved easily by selecting a font package with the --stylesheet command line option or in a custom style-sheet.
Font embedding must be configured in the LaTeX installation.
Use one of the Postscript default fonts supported by standard LaTeX (pages 10 and 11 of the PSNFSS documentation)
Implement as default stylesheet option, so it can be easily overridden.
My vote is for Palatino. --Matthew Leingang
There are 2 use cases:
Currently, 1) is done with --stylesheet and 2) with --stylesheet-path.
But:
complicated:
Explaining the two options and their interaction to the user is not straightforward.
This holds even more if you take into account the third related option, --embed-stylesheet.
| -1 | it is impossible to have some paths rewritten and some not, as in e.g. --stylesheet=mathpazo -stylesheet-path=mystyle.tex "mystyle.tex" would overwrite "mathpazo". |
Instead of two options, do "the right thing" based on simple rules, e.g:
Use the "package" vs. "custom style sheet" distinction:
Rewrite, if there is an filename extension and it is not .sty
--stylesheet='mathpazo,mystyle.tex'
will use 'mathpazo' verbatim and rewrite 'mystyle.tex'.
| -1 | will not work for latex packages in the pwd or outside the TEXINPUTS path. |
rewrite paths that have a directory part:
--stylesheet='mathpazo,./mystyle.sty'
will use 'mathpazo' verbatim and rewrite './mystyle.sty'.
| +1 | explicite and flexible |
| +1 | the common case (files in the TEXINPUTS path) is the most simple |
| -1 | need to document/learn special syntax |
rewrite path if this prevents errors:
| +1 | no need to explain any additional syntax |
| +1 | does "the right thing" in most usual cases |
| -1 | hidden automatism might lead to problems in corner cases |
| -1 | mechanism depends on the availability of files at the time of the run, which is harder to explain and less predictable than b) |
Provide fallback solutions for the use of "exotic" packages in case they do not exist on the target system.
Alan suggested a bibliography directive so that BibTex references are not automatically placed at the end (and bibtex for html via ... can be supported)
This would imply supression of the "Bibliography" or "References" header added by LaTeX which is possible with:
From: Martin Scharrer <martin@scharrer-online.de> Subject: Re: Literaturverzeichnis ?berschrift entfernen Date: Sun, 22 Mar 2009 06:30:33 -0700 (PDT)
On Mar 21, 11:10?pm, Elfish26111...@gmail.com wrote: > Hallo, > > ich benutze Bibtex und w?rde gerne die komplette ?berschrift, also > auch die daf?r reservierte Box entfernen. > Hat jemand eine Idee wie ich das machen kann? > > renewcommand{bibname}{} > > habe ich bereits versucht. Aber wie gesagt den reservierten Platz in > der Überschrift behält er immernoch.
Die Ueberschrift ist denk ich mal ein 'chapter*{bibname}' was du dann zu einem 'chapter*{}' machst. Die Loesung ist einfach das chapter macro umzudefinieren:
begingroup renewcommand{chapter}[2]{} % Literaturverzeichnis einbinden: ueber BibTeX oder manuell ... endgroup
Wobei der '*' hier einfach als ein zusaetzliches Argument genommen wird. Dann braucht bibname gar nicht mehr geaendert werden.
Gruesse, Martin
Changes to the latex2e writer in the SVN version since docutils version 0.5 are documented in the compatibility style sheet latex2e-compat.
Also see the Docutils Release Notes, the Docutils History.
Browse the SVN repository at berlios.de
The docs dir contains generic documentation and discussion.
Writer specific documentation is placed in the respective "literate" source.
Currently none.