Edgewall Software
Modify

Opened 19 years ago

Last modified 10 years ago

#1796 new enhancement

Stylesheet for Docutils output

Reported by: Felix Wiemann <Felix.Wiemann@…> 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)

html4css1.css (5.8 KB ) - added by Thijs Triemstra <lists@…> 14 years ago.
File taken from docutils-0.7/docutils/writers/html4css1/html4css1.css

Download all attachments as: .zip

Change History (21)

comment:1 by anonymous, 19 years ago

where exactly do you have to put this

@import url(/trac_common/css/docutils.css)

to make /trac_common/css/docutils.css work?

comment:2 by anonymous, 19 years ago

Resolution: worksforme
Status: newclosed

I can answer this question myself now:

The file templates/site_css.cs has to bee modified, as it has been described here:

Gentoo HOWTO Trac

comment:3 by Christopher Lenz, 19 years ago

Priority: normallow
Resolution: worksforme
Severity: normalminor
Status: closedreopened

It would still be nice if we fixed this in Trac.

comment:4 by Christian Boos, 18 years ago

Keywords: docutils restructuredtext added
Milestone: 2.0

comment:5 by Christian Boos, 15 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:6 by Christian Boos, 15 years ago

Milestone: triaging0.13
Owner: changed from Jonas Borgström to Christian Boos
Status: reopenednew

Need something better anyway for the API documentation (#8695).

comment:7 by Thijs Triemstra <lists@…>, 14 years ago

Cc: lists@… added

comment:8 by Thijs Triemstra <lists@…>, 14 years ago

Type: defectenhancement

Not sure if it's a defect when something "looks crappy".

by Thijs Triemstra <lists@…>, 14 years ago

Attachment: html4css1.css added

File taken from docutils-0.7/docutils/writers/html4css1/html4css1.css

comment:9 by Thijs Triemstra <lists@…>, 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 Thijs Triemstra <lists@…>, 14 years ago

Priority: lownormal

comment:11 by Christian Boos, 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:12 by bradley.ayers@…, 14 years ago

I for one would really like to see this happen.

in reply to:  11 comment:13 by Thijs Triemstra, 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 Thijs Triemstra, 14 years ago

Cc: Thijs Triemstra added; lists@… removed

comment:15 by Christian Boos, 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:16 by Remy Blank, 13 years ago

Milestone: 1.01.0-triage

Preparing for 1.0.

comment:17 by Christian Boos, 12 years ago

Component: generalrendering
Keywords: css added

Moving enhancements to dev.

comment:18 by Remy Blank, 12 years ago

Milestone: next-stable-1.0.xnext-dev-1.1.x

I assume you meant to set the milestone.

comment:19 by Ryan J Ollos, 10 years ago

Milestone: next-dev-1.1.xnext-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 Ryan J Ollos, 10 years ago

Owner: Christian Boos removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.