FeaturesCurrently, the "Table of Contents" plugin just appends the table of contents to the selected text frame.The paragraphs with the styles "h1", "h2", and "h3" get collected and they are inserted with the styles "toc1", "toc2", and "toc3". Please read the rest of this README for understanding how it works and how it will evolve.Create the table of content by selecting the text frame where you want it to appear and run "Insert > Table of Contents".This plugin is heavily inspired by the scribus/tocgenerator.cpp created by Cezary and available in Scribus-ece. There are two different ways to insert this variable, the first one being the keyboard shortcut Ctrl+Alt+Shift+P.This plugin is still in its very early stages.
define each level of the TOC with a source and a target style. But here is the direction we want to take: Testers (as soone as we have binaries to be downloaded)Not all details on the way this plugins should work are already defined.
allow collecting entries from other files. (eventually also the chapter number, once and if it's automotatic) a character styles should be possible for each level and
in the document settings like in scribus-ece, it is not yet defined how the table of contents are defined: it could be possible to define the table of contents in the same way the page number is defined (internal special char that is rendered with its content) with the scribus-ece model (defining a target frame in the document settings) you have to know the name of the frame. with the current model you have to delete the curent table of contents and insert a new one.
We probably need one char style for each part of the toc line optionally a char style for each part on each level of the toc line. We can use the same mechanism for other things that the user is supposed to maually check before exporting to PDF (and the user could add his own personal entrie) add an item at the top of the preflight verifier with two choices: If the TOC is not automatically updated, we could add a new "checkable" item to the preflight verifier: Depending on how it's implemented, the table of contents should be updated by the "Document update" command (or it should be an option in the TOC configuration) The old property based table of contents should probably be removed.
As soon as we have real pdf links, optionally add a link (and define a ref: we will have to make sure that we don't delete manual refs) It should be easy to switch among the tocs and update all of them. Multiple indipendent tocs should be possible When creating a new level, it duplicates the values for the current one? A "plus" button allows to create new levels
Per level option to show or not the page number Tab, space or vspace between title and number. A settings button could open the "Document settings" window with the TOC tab active.
This can be solved by defining a fake level (with no page number). In a book where you have multiple writers you might want their names to appear in the TOC, below the ChapterName, but with no page number associated to it. The scripter API should be extend to create custom TOCs. Some TOC entries might be without page numbers. Or should the TOC configuration be done in the Styles manager?
It should be possible to move up and down the levels. There is no need to see/set the level's names (it's just a sequence). It would be nice to see all levels at once. per level option to remove soft returns in the title.Cezary already implemented a styles based table of contents: Allow to grap the titles by char styles instead of paragraph styles Option to ignore the local formatting (which ones?) in the titles
Scribus Page Number Full Title Is
(or just create a new text frame at the default size if not?) make sure that the "Insert > Table of contents" item is only available when a text frame is selected. make sure that the full title is read if there are local formatting or character styles. Add API methods for storing and retreiveing settings. check for adding buttons to the buttonbox.
enhance the dialog with all the whistles and bells. create a dialog with basic choices (styles?) keep italics, subscript and superscript in the title (and eventually other formatting)
0 kommentar(er)
