Linux.com

Feature

Desktop publishing with Writer and Scribus

By Dmitri Popov on February 27, 2006 (8:00:00 AM)

Share    Print    Comments   

Although OpenOffice.org Writer offers many tools that allow you to create sophisticated layouts, you might want to use a dedicated desktop publishing application to lay out a brochure or a book. The latest version of the open source DTP application Scribus, 1.3.2, can import Writer's .odt documents, which makes Writer and Scribus a perfect combo for DTP work. Here's a brief overview of Scribus' essential tools and features from Writer users' point of view.

Although Scribus usually does a good job of importing Writer files, you should keep in mind that Scribus does not import embedded images, and it's not very good at importing tables and footnotes. This means that you must prepare your Writer document before you import them.

  • Make sure you have all the images used in Writer as separate graphics files in a format supported by Scribus, such as EPS, TIFF, JPEG, and PNG. If you don't have the images, you can extract them from the document using a simple trick. Make a copy of your Writer file, change its extension to .zip, and unzip the resulting archive. The unzipped folder contains the Pictures folder with all the pictures from the document in PNG format.
  • To prevent Scribus from messing up the tables during the import, you might want to convert them to text. To do this, select the table and use the Table -> Convert -> Table to Text command to convert the selection into text.
  • If the Writer document contains footnotes, you can use a workaround to preserve them during the import. In Writer, save the document as HTML and then import it into Scribus. The imported text will probably need manual tweaking, though.
  • Scribus doesn't support character styles, which you should also take into account when importing Writer documents. Since all the character-based formatting will be lost during the import, you might want to go through your document in Writer and replace character styles with manual formatting.
  • Scribus replaces spaces in the styles' names with _20_, so you might want to edit the styles' names before import to avoid confusion.
Once you've prepared your Writer file, you can import it into a Scribus document. In Scribus, insert a new text frame (Insert -> Text Frame) and choose File -> Import -> Get Text. Select the Writer file you want to import and press OK. In the OpenDocument Importer Options windows, you can specify how Scribus manages styles during the import:
  • Update Paragraph Styles -- This option changes the formatting of any created styles in your Scribus document to follow those in the Writer document.
  • Merge Paragraph Styles -- This option looks at the actual attributes (such as fonts and size) of the Writer document and merges styles that have common attributes. This can help to eliminate differently named but similar styles.
  • Use Document Name as a prefix for paragraph styles -- This option can be useful for sorting styles when importing from several documents.

Scribus doesn't reflow the inserted text automatically. This means that if you have imported a multi-page document into a one-page frame, you must first insert additional pages, then add frames to each page, and finally link the frames together. To insert a new page, choose Page -> Insert, select at End from the drop-down list, and press OK. Insert a text frame into the new page using the Insert -> Text Frame command. To link two frames together, select the frame containing text, press the Link Text Frames, and click on the new empty frame. If the frames are successfully linked, you will see a connection arrow between them, and the text will automatically spill over into the new frame. Repeat this procedure until the entire text is displayed properly.

Editing text

Although Scribus is not on a par with Writer when it comes to editing text, it does offer some powerful editing tools. Like Writer, Scribus supports paragraph styles. If you are familiar with the styles feature in Writer, you won't have any troubles with paragraph styles in Scribus. To add a new style in Scribus, choose Edit -> Paragraph Styles and press the New button. The Edit Style dialogue window provides access to all style settings, but there are fewer options compared to Writer. For example, you can't link styles, you can't apply borders, and you can't specify language. Scribus allows you to edit text directly in the text frame, but it also includes a so-called Story Editor, which is sort of a bare-bones word processor. It is, indeed, bare-bones: there is no WYSIWYG text editing, no spell checker, no other tools that Writer users take for granted. This leads to an obvious conclusion -- do all the heavyweight editing in Writer before you import the document into Scribus. Still, using Story Editor shouldn't cause any problems, even for users not familiar with Scribus. To invoke Story Editor, click in the text you want to edit and press Ctrl-Y.

Note: Scribus doesn't support bold and italics, meaning you can't just select some word and press the Bold or Italics button. You can cheat the application to work around this limitation, but a better approach could be to apply bold and italics in the Writer document prior to import.

Working with images

Inserting images into a Scribus document is easy: insert a new image frame (Insert -> Image Frame), right-click on the frame and choose Get Image, then select the image you want. (Keep in mind that, unlike Writer, Scribus doesn't insert images themselves but rather links to them.)

To resize an inserted image, right-click on the image frame, select Properties, click on the Shape tab, select the Scale to Frame Size option, and tick the Proportional check box. Right-click on the image frame and select Adjust Frame to Image. Now you can resize the image by dragging one of the frame's corner handles.

The next step is to make the surrounding text flow around the image. To do this, right-click on the image frame, select Properties, and click on the Shape tab. Tick the Text Flows Around Frame and Use Contour Line check boxes. Press the Edit Shape button, tick the Edit Contour Line check box. Now, use the blue round handles to adjust the contour line as you see fit.

You can also add captions to the images using the legende.py script. Select the image you want, choose Scripts -> Execute Script, and select the legende.py script (on Linux, the path to it may be usr/share/scribus/samples/legende.py). The script inserts a new text frame containing the name of the image.

Working with master pages

As any DTP application worth its salt, Scribus uses Master pages, which are roughly similar to page styles in Writer. Master pages can be immediately useful for a number of things -- for example, for adding automatic page numbering and running footers. To add page numbers to your Scribus document, choose Edit -> Master Pages. In the master page insert a text frame where you want to display the page numbers, then click in the frame and press Shift-Ctrl-Alt-P to insert the # symbol, which signifies the page numbers. If the Shift-Ctrl-Alt-P shortcut doesn't do the trick, go to Edit -> Preferences -> Keyboard Shortcuts and check the Page Number shortcut. Now, close the Edit Master pages window, and you should see the page numbers. If you don't, make sure that the master page is applied to the current pages: Choose Page -> Apply Master Page, then select and apply the appropriate master page.

By default, Scribus uses Arabic numbers, but you can quickly switch to Roman numbers, if necessary. To do this, choose File -> Document Setup -> Sections and select the numbering style you want from the Style drop-down list. Keep in mind that in order to display multiple-digit page numbers, you have to insert the corresponding number of the # signs. For example, for numbers equal or bigger than III, you must add three # signs, so the code looks like this: Page ###.

Naturally, Scribus supports multiple paginations and different numbering styles. Let's say you want to create two separate paginations: one with the Roman numbering style for use with the book's preface, and another with Arabic numbering for use with the rest of the book. Choose File -> Document Setup -> Sections and define two sections with the Roman and the Arabic numbering styles. Use the From and To fields to specify the paginations' ranges and the Start field to specify the page offset. If you hover the mouse over a field, you can read a more detailed description of each field in a tool tip.

In a similar way, you can add running headers and footers. However, unlike Writer, Scribus doesn't allow you to add dynamic fields with chapter names. This means that you have to create a separate master page for each chapter and hard-code chapter names in the master page.

Conclusion

Scribus may feel like uncharted territory for many Writer users, but it's pretty easy to come to grips with, and many Writer skills can be translated to Scribus. Of course, both applications have their strengths and weak spots, but combined they provide a powerful end-to-end publishing solution.

Dmitri Popov is a freelance writer whose articles have appeared in Russian, British, and Danish computer magazines.

Dmitri Popov is a freelance writer whose articles have appeared in Russian, British, US, German, and Danish computer magazines.

Share    Print    Comments   

Comments

on Desktop publishing with Writer and Scribus

Note: Comments are owned by the poster. We are not responsible for their content.

Scribus doesn't do....

Posted by: Anonymous Coward on February 28, 2006 01:49 AM
Let me check this....

(quoted directly)
* - Scribus does not import embedded images, and it's not very good at importing tables and footnotes

* - To prevent Scribus from messing up the tables during the import, you might want to convert them to text

* - If the Writer document contains footnotes, you can use a workaround to preserve them during the import.

* - Scribus doesn't support character styles

* - Scribus replaces spaces in the styles' names with _20_

* - Scribus doesn't reflow the inserted text automatically

* - you can't link styles, you can't apply borders, and you can't specify language

* - Scribus doesn't support bold and italics (WTF?! )

* - Scribus doesn't allow you to add dynamic fields with chapter names

Okay, so why is Scribus even considered to be a worthwhile DTP program -- because it supports frames and Master Pages? If I recall, Publisher 97 had more features and power, which is pretty sad.

#

Re:Scribus doesn't do....

Posted by: Anonymous Coward on February 28, 2006 03:21 AM
Scribus does not import embedded images, and it's not very good at importing tables and footnotes

Ever tried Quark? If you have just a little experience in DTP, you know that images are always stored separately.

To prevent Scribus from messing up the tables during the import, you might want to convert them to text

Yes, and you can use even better ways. This is page layout app, not an office suite!

If the Writer document contains footnotes, you can use a workaround to preserve them during the import.

See above: QuarkXPress?

Scribus doesn't support character styles

Not yet, but soon they will be there.

Scribus replaces spaces in the styles' names with _20_

That's not nice, but doesn't do any damage.

Scribus doesn't reflow the inserted text automatically

Not true.

you can't link styles, you can't apply borders, and you can't specify language

As part of paragraph styles, not yet. But of course you can apply language settings to text.

Scribus doesn't support bold and italics (WTF?! )

As a real DTP app, Scribus doesn't support fake italics and bolds. You need bolds and italics installed. That's a professional feature, not a shortcoming!

Scribus doesn't allow you to add dynamic fields with chapter names

Again, this a feature most commonly used in word processors or apps like FrameMaker. However, all of this will be implemented before the next stable version (1.4) is released. It seems you have never worked with QXP or PageMaker.

#

Re:Scribus doesn't do....

Posted by: Anonymous Coward on February 28, 2006 03:51 AM
Even though he hasn't worked with DTP software, it would perhaps be better to explain why DTP software does so little of what a word processor does. What is the rationale today of working in this many steps?

#

Re:Scribus doesn't do....

Posted by: Anonymous Coward on February 28, 2006 05:10 PM
DTP softare are used for specific things which need complicated layouts, eg newspapers, books with many images, etc. For simple books, it's better to use word processor.

But try to make "The New York Times" with OOWriter, you will never be able to... That's the use of DTP softwares...

#

Re:Scribus doesn't do....

Posted by: Administrator on March 01, 2006 12:48 AM
No, the parent poster is correct. If a layout app can't import paragraph, table, and font styles correctly, then the layout app can't be taken seriously.

Frankly, I'd be a lot happier if something like Lyx supported ODT as an import format. Far, far better tool for creating large documents.

#

Re:Scribus doesn't do....

Posted by: Anonymous Coward on February 28, 2006 03:23 AM
"Okay, so why is Scribus even considered to be a worthwhile DTP program -- because it supports frames and Master Pages? If I recall, Publisher 97 had more features and power, which is pretty sad."

Maybe you should first figure out why anybody bothers to write free software at all - then you may also understand why Scribus is developed. Until then - or if you are not interested reasons for free software - keep using Publisher 97 or whatever you like.

#

Re:Scribus doesn't do....

Posted by: Administrator on March 01, 2006 01:13 AM
I haven't used Scribus but based on this article I'm not going to.<nobr> <wbr></nobr>;>

Writer has a huge number of features, and I didn't really see what Scribus adds. Some OOo features are a bit painful to implement but you can do a lot.
Jean Weber has a site about how to bend Writer to your will for techwriting.
<a href="http://www.taming-openoffice-org.com/" title="taming-ope...ce-org.com">http://www.taming-openoffice-org.com/</a taming-ope...ce-org.com>

I've outlined some of the issues with Writer for books.
<a href="http://openoffice.blogs.com/openoffice/2005/10/is_openofficeor.html" title="blogs.com">http://openoffice.blogs.com/openoffice/2005/10/is<nobr>_<wbr></nobr> openofficeor.html</a blogs.com>

That said, OpenOffice.org Writer will do most of what you need.

-Frames that can skip from one page to another. Start typing on page 12 and the text pops out in the connected frame on page 12.
-Sections and frames can both have multi-column layouts, shading, borders, etc.
-Nice built-in writing tools and word art tools (FontWork).
-Very powerful styles. Huge. Including page styles which you can use like master pages.
-Master files, cross-referencing within and between documents in master files
-Lots of page setup stuff like backgrounds, borders, any page size you want

You might want to just consider using Draw as a brochure layout tool. The text boxes are pretty limited but if it's a mostly graphical brochure rather than based on text flow, the grid and other aspects of Draw might be better for some brochures, postcards, etc.

#

OK for a brochure, but a book???

Posted by: Anonymous Coward on February 28, 2006 01:42 PM
I could see using writer+scribus to lay out something akin to a brochure, but why on earth would you use it for a book when Lyx/LaTex will do 90%+ of this stuff (numbering, headers, etc) automatically? And make it look good?

#

Re:OK for a brochure, but a book???

Posted by: Anonymous Coward on March 01, 2006 12:36 PM

I use Lyx regularly and like it (check out my <a href="http://therandymon.com/content/view/16/79/" title="therandymon.com">Woodnotes Guide to
Emacs for Writers</a therandymon.com>, written entirely in LaTeX, but both LaTeX and Lyx
are tools written for another task.


Desktop publishing is different and requires different tools. I happen
to use Adobe CS (formerly Pagemaker) because it's feature complete and
because Scribus is still weak in some ways that are important to me,
plus it doesn't run well on my old PIII 550Mhz Linux box, while Adobe
runs well on my shiny new powerbook.


But I still give Scribus a lot of kudos and look forward to when it can
handle more complex tasks. For one, it creates better PDF than any
other document producer I know of, including Writer. It allows you to
downsample images on the fly and has the right idea about text
formatting mechanisms. Don't get me wrong, I dig LaTeX but I use it for
what it was intended for, like my woodnotes guide. Publications that
are graphics intensive don't work well in LaTeX, which, for graphics,
offers fewer features.


As always, the rule is, use the right tool for the job. For some jobs,
Scribus is just the right tool.

#

Re:Scribus doesn't do....

Posted by: Anonymous Coward on March 01, 2006 02:11 AM
Scribus *can* import paragraph styles. It doesn't import tables, and it doesn't import character styles yet.

In a page layout app, you work in different way than in a typesetting program. Page layout software is used for things like newspapers, magazines, books with lots of illustrations in colour, flyers etc.

This means you want control over each letter and it's nothing you would use LyX or LaTeX for.

#

Not a word processing package

Posted by: Anonymous Coward on March 01, 2006 07:29 AM
Reading these comments makes me wonder if anyone actually knows what a professional layout program does. Comparing Scribus to OOWriter is like Postgres to OOBase. They just aren't the same apps, sure, they share some concepts, but they do different things.

Anyone who imports formatted text is a fool. Period. Full stop. Carriage return. Think orphans, widows, earlugs and linked text boxes for the reasons why. Then after that, think _design_.

Anyone who doesn't understand why graphics are a separate entity from the document hasn't worked with an 40 MB Tiff on a single page in a 40 pg magazine in 8 page forms.

Nor do they comprehend running to single page seps for form layout, film or plate seps via an OPI process instead of "print to file".

Anyone who doesn't understand the difference between an oblique font and "italics" doesn't understand the profession. (See above about real fonts.)

Remember . . . process to press, not print to printer. That means that a doc might go through four or more different machines for processing. OPI, seperation, PDF, Film, plate, press. If anyone of those doesn't support font styles you end up w/ courier. That's why real fonts (PS, TTF) include a normal, bold, and oblique font in all variations.

It isn't uncommon for a 40 page document to be broken up into 5 files each with non-sequential pagination. (Depending on press and bindery; work and turn, work and tumble, straight-through)

Scribus isn't your friendly neighbourhood Office Suite and shouldn't be used as such.

If you want to do layout that's useable in PDF form by almost any commercial printer then it's the tool to use. If you want to write a letter, it isn't, stick to OO.

Comparing AutoCad and GIMP (Hey! they both do lines then must be comparable!), comparing AccPac and GnuCash, they both tally numbers! Foolish article.

#

Well said!

Posted by: Anonymous Coward on March 01, 2006 08:27 AM
Thank you!

#

Re:Not a word processing package

Posted by: Anonymous Coward on March 01, 2006 06:20 PM
The author wasn't comparing both packages. He was stating that it might be a good idea to use both in the workflow. OOo to prepare texts and spell check them. Scribus to do the prepress thing.

Jo

#

Re:Not a word processing package

Posted by: Anonymous Coward on March 03, 2006 09:57 AM
Thats the insight I was trying to understand. Please provide me links for further understanding the differences between Word-Processing and Publishing (Professional Layout).

Could you also planning tips, if I have to publish my content which I am writing in a word processor! Smooth transition Guide from OOo to Scribus for publishing as a HOWTO is a suggestion for lay users like me.

-a

#

Re:Not a word processing package

Posted by: Anonymous Coward on May 05, 2007 04:43 AM
I found this a very helpful article, it explained clearly for a complete amateur some points I did not know. I guess a lot of people are not really looking for a professional publishing program, I have a laser printer and all I need is a nice layout for the occasional flyer etc. Maybe it is true that I don't use much of the power in Scribus but if I can do what I need I am happy.

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya