Changes between Version 50 and Version 70 of Ticket #16256


Ignore:
Timestamp:
10/25/14 08:00:03 (6 years ago)
Author:
nthiery
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16256

    • Property Dependencies changed from #16058 to #16058, #17189
    • Property Branch changed from u/nthiery/reorganize_the_documentation_indexes_into_src_sage_combinat to u/nthiery/ticket/16256
    • Property Commit changed from 2252c4453b5788a3c44fe05100fc0a9f93ea6919 to cef0ee08f43e178766f6a737b2d4ea18ac8fd90c
    • Property Work issues changed from Fix sphinx issues. to

  • Ticket #16256 – Description

    v50 v70  
    7575== TODO ==
    7676
    77 - Confirm that this is the right approach
    78 
    7977- Proof reading
    8078
    … …  
    8482  choosing the right entry points for each module)
    8583
    86   Could be postponed to a later ticket, since those are further
    87   enhancements not directly related to this ticket. It's just that,
    88   while browsing through the indexes suggested them to me.
     84  Postponed to a later ticket, since those are further enhancements
     85  not directly related to this ticket. It's just that, while browsing
     86  through the indexes suggested them to me.
    8987
    9088- Finish automatizing the building of module_list.rst.
    9189
    92   Could be postponed to a later ticket.
    93 
    94 - Sphinx issue to be investigated: currently `make doc` fails upon the
    95   first attempt, complaining about a broken link for
    96   `sage.coding`. One need to rerun it, and then the link is
    97   failed. This is probably just a glitch in how warnings are reported
    98   during the first pass of the reference manual compilation, but needs
    99   to be fixed before this ticket goes in.
     90  Postponed to a later ticket.
    10091
    10192- Sphinx issue to be investigated: deciding on how to link to
    10293  classes/functions: in the index we would want to have the title of
    10394  the documentation of the class rather than the name of the class; or
    104   maybe both. It might be ok to stick to the class name for now until
    105   we find a good way to do this with Sphinx.
     95  maybe both.
     96
     97  For now, we stick to the class name for now until we find a good way
     98  to do this with Sphinx.
    10699
    107100- Sphinx issue to be investigated: how to crossrefs documents in the
    108   thematic tutorial. For now we use a workaround.
     101  thematic tutorial.
     102
     103  For now we use a workaround.