Tables of Contents, Indexes and Other Special Tables in Scribus
Creating special tables in Scribus is not a straightforward task. The controls are scattered, and few users are likely to decipher the necessary steps or their necessary order without help. However, each step in creating a table of contents (TOC), index, or frame is simple in itself, and, once one is added, you can edit the result exactly as you would the contents of any text frame.
Because a special table depends on the information in the rest of the document, you need to add it after you are finished the document. Otherwise, you will simply have to regenerate it more than once. Avoiding this extra work means either leaving space on a page for adding the special table, or adding pages at the start or end of the document. For an index, whose entries are often short but numerous, you may want to create a two or three column layout, with connected text frames on two or more pages.
In addition, for a TOC and many indexes -- especially in a technical document -- you consider using sub-headings, each in a separate text frame, formatted with a paragraph style named something like Heading1 or Sub-Head. If you do, then finding the text frames you want to add to the special table will be easier.
Just as importantly, you won't need to come up with a meaningful tag as you create the special table, which can be mentally challenging, especially if you are adding the table after long hours of writing and editing. You can simply copy the text of the sub-heading.
Before you begin to create the special table, you will also need at least one paragraph style for its contents. If you have several levels of sub-headings, and want them to be visible in the special table, then you should also create a paragraph style for each level, even though initially only one will be used in the special table. Should you want leader dots to connect a table entry and its page number, you can edit the paragraph styles for the table so that the tabs use a fill character -- although this is a sloppy layout habit that you should avoid if at all possible.
Creating a special table
Creating a special table takes four steps:
- Press the T key to add a text frame for the special table to the document. Then press F2 to give it an easily identifiable name in the Properties window, such as TOCFrame.
- Select File -> Document Setup -> Document Item Attributes -> Add. Give the attribute a name such as TOC or Index, and click the OK button. You have just created a tag that can be applied to objects in the rest of the document.
- Select File -> Document Setup -> Table of Contents and Indexes -> Add to set up the special table. In the version of Scribus I am using, this procedure always produces something whose title is Table of Contents followed by a number (for instance, Table of Contents 2), but, despite the title, the special table can be of any sort you choose. On the right side of the window, set:
- Item Attribute Name to the one you created in step 2 of this prodcedure.
- Destination Frame to the text frame you have prepared for the special table.
- Page Placement to End, Beginning or Not Shown.
- Paragraph Style to the top level paragraph style created for the special table, such as TOC1. You will only be able to add the other paragraph styles after the special table is created.
When you are finished, click the OK button to exit Document Setup.
Adding and laying out the special table
With these preparations, you are ready to build the special table. Go to each text frame that you want listed in the special table, selecting the frame, then choosing Item -> Attributes. In the name column, select the tag you created in Document Item Attributes (for instance TOC) to add the text frame to the special table.
You also need to provide some text to display in the special table under Value. If you are using sub-headings and creating a TOC, you can simply enter the text of the sub-heading. If you are building an index, you might want to create multiple entries for some text frames, or reworded versions of the tag, such as "adding a text frame" and "text frame, adding."
When you are finished tagging paragraphs, select Extras -> Generate Table of Contents. The result displays in the text frame you designated in Table of Contents and Indexes, regardless of whether it is currently selected or not.
Unless you have created a special table in Scribus before, the result may not be exactly what you want, especially since a single paragraph style is used for the entire special table. You may need to experiment with the special table's paragraph styles, adjusting them in Edit -> Styles.
If you want multiple levels of sub-headings to use different styles in the special table, you will need to select its text frame and click Edit Text to open the Story Editor and apply the appropriate styles. Note, however, that if you ever need to regenerate the special table, this extra formatting is over-ridden, so you may want to delay this final bit of formatting until everything else is to your satisfaction. You may also want to place the heading for the special table in a separate text frame, since it, too, disappears with each regeneration.
Creating a special table that looks the way you want it to is not nearly as hard as you might first expect. However, it does require an understanding of both paragraph styles and of attributes if you are to automate the process as much as possible, and can be time-consuming, particularly if you are not familiar with the process.
For this reason, I suggest creatng a document that has a table of contents, index, list of illustrations, or any other special table that you use regularly setup, and save it has a templates. Templates are often important ways to minimize duplication of work in Scribus, and, if you create all the special tables you need in one, you can sidestep much of the drudgery involved in their creation.
-- Bruce Byfield (nanday)
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide