Opened 19 years ago
Last modified 9 years ago
#1796 new enhancement
Stylesheet for Docutils output
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | rendering | Version: | 0.8.4 |
Severity: | minor | Keywords: | docutils restructuredtext css |
Cc: | Thijs Triemstra | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Some output elements (e.g. line blocks or admonitions) of reStructuredText look really crappy without a stylesheet.
May I suggest you store tools/stylesheets/default.css from the Docutils tarball at /trac_common/css/docutils.css and add @import url(/trac_common/css/docutils.css) in front of the other import statements?
The Docutils stylesheet shouldn't interfere with any elements outside the Docutils-generated HTML code.
Attachments (1)
Change History (21)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I can answer this question myself now:
The file templates/site_css.cs has to bee modified, as it has been described here:
comment:3 by , 19 years ago
Priority: | normal → low |
---|---|
Resolution: | worksforme |
Severity: | normal → minor |
Status: | closed → reopened |
It would still be nice if we fixed this in Trac.
comment:4 by , 18 years ago
Keywords: | docutils restructuredtext added |
---|---|
Milestone: | → 2.0 |
comment:6 by , 14 years ago
Milestone: | triaging → 0.13 |
---|---|
Owner: | changed from | to
Status: | reopened → new |
Need something better anyway for the API documentation (#8695).
comment:7 by , 14 years ago
Cc: | added |
---|
comment:8 by , 14 years ago
Type: | defect → enhancement |
---|
Not sure if it's a defect when something "looks crappy".
by , 14 years ago
Attachment: | html4css1.css added |
---|
File taken from docutils-0.7/docutils/writers/html4css1/html4css1.css
comment:9 by , 14 years ago
When you run rst2html.py test.rst test.html
it includes the attached css inline, which is published in the public domain.
comment:10 by , 14 years ago
Priority: | low → normal |
---|
follow-up: 13 comment:11 by , 14 years ago
Thanks for reviving the topic! We already have this version http://svn.edgewall.org/repos/edgewall/tools/doc/style/edgewall.css to integrate in Trac. It's 3 years older, but I think it was already customized a bit to better fit with the Trac style.
comment:13 by , 14 years ago
Replying to cboos:
Thanks for reviving the topic! We already have this version http://svn.edgewall.org/repos/edgewall/tools/doc/style/edgewall.css to integrate in Trac. It's 3 years older, but I think it was already customized a bit to better fit with the Trac style.
So what do you suggest happens next?
comment:14 by , 14 years ago
Cc: | added; removed |
---|
comment:15 by , 14 years ago
As I'm working on the ApiDoc, I gradually override the Sphinx's "sphinxdoc.css" style by adding rules in source:trunk/doc/utils/tracsphinx.css. It should be possible to collect all the resulting rules, remove the "sphinx*" specific ones to keep only the ones relevant for docutils, and consolidate them (i.e. remove rules from basic.css or sphinxdoc.css which are overridden later, be careful not to readd rules already there like ol.loweralpha
). At that point, we'll have tracdocutils.css.
comment:17 by , 12 years ago
Component: | general → rendering |
---|---|
Keywords: | css added |
Moving enhancements to dev.
comment:18 by , 12 years ago
Milestone: | next-stable-1.0.x → next-dev-1.1.x |
---|
I assume you meant to set the milestone.
comment:19 by , 10 years ago
Milestone: | next-dev-1.1.x → next-major-releases |
---|
Retargetting tickets to narrow focus for milestone:1.2. Please move the ticket back to milestone:next-dev-1.1.x if you intend to resolve it by milestone:1.2.
comment:20 by , 9 years ago
Owner: | removed |
---|
where exactly do you have to put this
to make /trac_common/css/docutils.css work?