Code

Opened 5 years ago

Closed 5 years ago

#10707 closed (wontfix)

Sphinx & LaTeX: too many nesting section levels for LaTeX

Reported by: kgrandis Owned by: nobody
Component: Documentation Version: 1.0
Severity: Keywords: sphinx docs
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Using Sphinx v0.6.1,

make latex

results in the following error:

...
Markup is unsupported in LaTeX:
ref/contrib/admin/actions:: too many nesting section levels for LaTeX, at heading: Writing action functions
make: *** [latex] Error 1

affected file: docs/ref/contrib/admin/actions.txt : "Writing action functions"

Sphinx issue: http://bitbucket.org/birkenfeld/sphinx/issue/125/latex-cannot-cope-with-3-nested-section
this was flagged as wontfix since it is due to LaTeX only allowing up to \subsubsection

Attachments (1)

10707-latex-doc-depth-level-workaround.diff (625 bytes) - added by ramiro 5 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 5 years ago by kgrandis

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Summary changed from Sphinix & LaTeX: too many nesting section levels for LaTeX to Sphinx & LaTeX: too many nesting section levels for LaTeX

Changed 5 years ago by ramiro

comment:2 Changed 5 years ago by ramiro

  • Has patch set

comment:3 follow-up: Changed 5 years ago by ramiro

Seems like this change in Sphinx would also solve this by automatically converting the levels with a depth over the LaTeX limitation to the "subparagraph" style instead of raising an exception. It will be included in Sphinx >= 0.6.2

comment:4 in reply to: ↑ 3 Changed 5 years ago by ramiro

Replying to ramiro:

Seems like this change in Sphinx would also solve this by automatically converting the levels with a depth over the LaTeX limitation to the "subparagraph" style instead of raising an exception. It will be included in Sphinx >= 0.6.2

A follow-up: After r11162 (and r11165 for 1.0.x) this problem can be worked around by using Sphinx 0.6.2 (current stable release) without having to modify our docs at all. Just tested and verified this here.

A while back Jacob expressed on IRC he would be OK with making Sphinx 0.5 a requirement for building the Django docs. Perhaps we can raise that to 0.6.2 at some point?

comment:5 Changed 5 years ago by Alex

  • Resolution set to wontfix
  • Status changed from new to closed

Since ramiro has said it's fixed in Sphinx 0.6.2 closing as it's not our problem.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.