Category:FAQ

Other languages: Polski (pl) Portuguese (pt_BR)

Work in progress
a.l.e: i'm trying to reformat this FAQ as a list of question *and* answers which -- i hope so -- will be easier to search through. if i don't succeed, please revert to the last version before the 13 december 2008.

How to fill a FAQ entry: you're welcome to add your entries to the FAQ. If possible, try to keep the FAQ entries as short as possible (and add links to one or more other wiki entries if necessary) and write about one topic at a time.

When to add a FAQ section?: the goal is to make simple to find a FAQ entry. So there should not be too many titles but the sections should not get too long or general either...


 * I don't think we need to replicate information that's easily available via www.docs.scribus.net and/or the Help Browser. Moreover, an FAQ is not a manual. --C schaefer 01:52, 26 September 2010 (UTC)

Installing and running Scribus
Which Scribus should I install on my computer?

How do I get Scribus for Linux?

 * If you don't need anything fancy, use your packet manager to install Scribus (synaptics, yum, apt-get, ...). This is the preferred way to install Scribus.
 * If you want to be more up to date than your distribution is, you can add Scribus's own repositories. They are available for Debian, Ubuntu, Fedora, CentOS, Red Hat, OpenSuse, SUSE Linux Enterprise, and Mandriva. This is the preferred way to install Scribus.
 * If you want to test the newest feature (or if there are no binaries for your platform) you can compile the source code you get from sourceforge or from the subversion server (svn://scribus.info/Scribus/)

How do I get Scribus for OS X?

 * The stable version is only available through Fink or Darwinports
 * Snapshots of the development version are availabe on Sourceforge.
 * At the moment, there is no (easy) way to compile yourself Scribus for OS X
 * You can get a Ghostscript .dmg from here
 * Images (.dmg) for more recent development versions won't work on OS X 10.4. If you want to install Scribus 1.3.8 or later you will have to install it through Fink:
 * Install Fink.
 * Then install finkcommander.
 * Activate the unstable packages (fink commander > preferences > fink, Use unstable packages").
 * Install scribus-135+ from sources or binaries (if you also install qt4 from sources, it will take a long time, but it will work).

How do I get Scribus for Windows?

 * Binaries are available on Sourceforge
 * stable (1.3.3.14)
 * development (1.3.5+)
 * svn snapshots
 * It's not easy to compile. The BUILDING_win32.txt explains how to do it.

Which version should I use?
New users doing productive work should stick with the stable version (1.3.3.14). However, if you don't care about some minor incoveniences, you may want to use 1.3.8+ for new projects, since it has many more features than 1.3.3.14 and will become the stable 1.4 version soon.

As a rule of thumb: all versions that have an odd number as a second (minor) version number (1.1, 1.3, 1.5, 1.7) are unstable/development versions, all version with an even minor number are stable versions (1.0, 1.2, 1.4, 1.6, ...)

1.3.3.x is an exception and has been declared stable because 1.2 was too old and 1.4 was too far away.

Stable version
1.3.3.14 is the stable version – use it for your normal work.

Development version
1.3.8+ is the development version. You can use it if you want to use features which are not in the stable version. It has now become quite usable, but keep in mind that if you save work with it, you will not be able to then load it into 1.3.3.14, since the file format has changed. You can load a file created with 1.3.3.14 or an earlier version into later versions. If you are using Mac OS X 10.5+, 1.3.8 is recommended since it avoids some Qt3-related problems, and also because a universal binary is available.

(todo: link to a page which describes how to protect yourself when you're using the development version)

1.3.4 is an old unstable Qt3-based version which unfortunately was latched onto by some distros. It had a number of bugs, most of which were never fixed. It quickly led to the 1.3.5 version which was based on Qt4, and has since advanced to 1.3.8 mentioned above.

Experimental branch
1.5 is the current experimental branch: Only for people wanting to experiment with the latest Scribus features should use it. Remember that if you use this latest version, its file format will not allow its files to be loaded on any older versions.

Compatibility
Since its beginnings, Scribus has always maintained backward compatibility, so that every later version will be able to load a file from an earlier version. Because new features are added, the reverse is not true. For example, you can't load a 1.3.6 file into 1.3.3.14, but you can load 1.3.3.x files into 1.3.6+ and 1.5.

So which one should I use?
If you are still wondering, please use the stable 1.3.3.14 – it will be hard to go wrong with this one (exception: Mac OS X as noted above). If you have purchased or plan to purchase Scribus: The Official Manual, the book was based on the 1.3.3.x series, but it can be used with later versions, too.

How do I compile Scribus?
There may be a few reasons for you to compile Scribus yourself:
 * There is no current Scribus for your platform (like Linux PPC or Mac OS X 10.4).
 * You need a fix that has been applied after the latest binary snapshot has been released.
 * You want to follow Scribus development to stay up to date and to test.

In the first case you should download a snapshot source package from Sourceforge. In all the other cases you're better off if you get the source code via subversion.

Further reading:
 * Building_SVN_versions_with_CMake
 * Scribus 1.3.5svn (Ubuntu; in French)

Dependencies
See http://docs.scribus.net/index.php?lang=en&page=install2

Where is my Ghostscript?
You have successfully installed Scribus and now you see a warning that Ghostscript is missing.

One approach is to simply ignore the warning, as you only need it for EPS import and the Print Preview. Or you can install it later.

Linux
It's highly unlikely you would ever get this alert under Linux, unless you have installed Ghostscript in some quite nonstandard location. If it happens anyway, just use your package manager to install Ghostscript.

Mac OS X

 * You can get a Ghostscript .dmg from here (it may not be the latest version, but will probably be sufficient).
 * You can install Ghostscript via Fink or MacPorts.

Once Ghostscript has been installed, go to Scribus > Preferences > External Tools, and browse (Change...) for the gs executable (the path will be something like "/usr/local/bin/gs").

Microsoft Windows

 * First of all, you need to download the Ghostscript installer.
 * Once installed, Scribus needs to find it, which may or may not work automatically on Windows. If Scribus doesn't detect the Ghostscript executable after the installation, go to File > Preferences > External Tools, and browse ("Change...") for the gs executable. For 32-bit, its gswin32c.exe, the important thing being that "c", since there is another executable without a "c" in the file name.

Configuration

 * Where are the preferences located?
 * On Linux:
 * On Mac OS X:
 * On OS/2 and eComStation:
 * On Windows 2000, XP and 2003:
 * On Windows Vista and 7:

Errors

 * On Windows, you may not be able to see the page or the buttons. Please make sure:
 * that you're not using third party Windows themes. Lots of those themes are broken and show similar behavior with other applications. You have to disable those themes in Control Panel > Display Properties > Themes and/or Appeareance.
 * that your display is set to use 32 bit depth: Control Panel > Display Properties > Settings – set display bit depth to 32 bit

Images
When you put an image in an image frame, Scribus will load that file into RAM (chip memory). Thus, if you have many large images in your document, loading may take very long and consume lots of memory, which can slow down your system. A possible solution to the loading issue is to reduce the image preview resolution for your document: Go to File > Document Setup > Tools, and click on the image frame icon (second from top). In the "Images" dialog, set "On Screen Preview" to "Low Resolution Preview", and click "OK". Note that you can also change the resolution for individual image frames from their context menu. In the context menu you can even switch off the preview of the image.

A large document with many high-resolution images may exhaust your RAM. Once you completely fill that up, along with any swap space, Scribus may freeze or crash. Here are some pointers:


 * Use an image editor to crop images to the section that you actually want to use in the image frame, then use that smaller file.
 * Decrease the resolution/size of the image file itself. For most printing targets 300 dpi is a good idea, whereas higher resolutions rarely make sense.
 * If you create a PDF for the web, much lower resolutions are recommended, e.g, 72-90 dpi, since monitors don't have a higher resolution and the files will be significantly smaller.
 * Use a computer with enough memory for your work. As a rule of thumb, there's only one thing better than a lot of RAM: even more RAM.
 * If you are making a large document with a large number of high-res images, you can manage by breaking up your work into 20-30 page sections, making PDFs of the sections, then joining them together with a program such as pdftk.

Text

 * You can import Openoffice.org .odt files. Scribus will recognize most text formatting options and style sheets, and you can decide how Scribus will handle style sheet during import.
 * You can directly import Microsoft Word (.doc) documents, but you will lose all formatting. You better use Openoffice.org and save the document in the .odt format.
 * Microsoft RTF documents can't be read from Scribus: you should use Openoffice.org to convert them to .odt or save them in the .doc format from Microsoft Word.
 * For the use of customtext filters see: Using the Text Filter.

OpenOffice.org
You can import the content of .odt files into text frames. Text formatting and style sheet will be kept, but not tables, footnotes or images.

Microsoft Word
You can import text from .doc files into text frames, but you will lose all formatting and style sheet. If you want to keep them, you should convert your files to the OpenDocument file format (*odt).

Adobe InDesign
An import filter for InDesign IDML files has been added to the experimental 1.5svn version, but it can't be backported to 1.3.8+.

Quark Xpress
An import filter for XPress Tag files (*.xtg) has been added to the experimental 1.5svn version, but it can't be backported to 1.3.8+.

Microsoft Publisher

 * Import Publisher to Scribus
 * Free online file conversion

Books
You can manage the following issues: But not these:
 * Currently, Scribus isn't very good at handling documents that are longer than 30 pages. You should split your work into several Scribus documents, export each of them to PDF and then join them into a single PDF file, for example, with pdftk.
 * You can set the value for the first page number or change the page numbering scheme in a document (see: Pagination).
 * You can create text frames that are automatically linked/chained when you create a new document.
 * You can't create a multi-level table of contents (TOC).
 * You can't automatically create a table of contents over several files.
 * You shouldn't make long chains of text frames, as this will slow down Scribus significantly.
 * Index and footnotes aren't available, yet.

Flyers
Create a file of the size of the whole flyer and use guides to separate the different "columns". (more...)

Typical errors

 * If you're using Windows and have a custom theme installed, you won't get any new page displayed when creating a new document: use the default Win theme or "Classic", and everything will work fine

How can I do Pagination?
There is no single "pagination" concept in DTP. Yet, the word is used often and can have several meanings:
 * If you want to add page numbering, see the page number howto.
 * If you want to impose the pages you have created with Scribus, please have a look at the howtos about imposition.
 * If you want to layout several pages on one Scribus page, please think again. There are some exceptions to this rule, like creating a threefold brochure.
 * If you want to create some pages and let text flow from page to page, you can learn more about this issue by reading the Scribus tutorial.

Writing Text

 * Why can I type some glyphs / letters in the Story Editor but they don't show up on the Canvas nor in the PDF generated by Scribus?

The story editor is still able to show more glyphs than scribus can handle. The fact is, that the story editor does not enforce the typographic quality of the glyphs and just delegates to Qt their visualization.

so, the fact that the story editor can show some characters, does not mean anything about scribus being able to display the glyphs themselves.

Language

 * The hyphenation language can be choosen in the "Hyphenation" section of the menu File > Preferences.
 * The language for the spell checker (if available in your Scribus version) can be selected in a character style.

Loading fonts

 * For a list of good font resources see Where can I get good fonts?.
 * Scribus will automatically discard fonts that may cause problems in offset printing.

Embedding and vectorizing fonts
see the section on PDF output.

PDF

 * The PDFs generated by Scribus are of very high quality and should never be a problem when delivered to a print shop.
 * Bugs related to the PDF generation are treated with very high priority by the Scribus team.

PDF/X

 * Supported versions: PDF/X-3 (1.3.3.x and 1.3.8+), PDF/X-1a and PDF/X-4 (1.5svn only, no backport possible).
 * ICC profiles must be installed.
 * You have to enable color management.
 * You have to fill the "info string" in the "Pre-Press" tab of the PDF export dialog.

Forms
Basically, forms created by Scribus can be filled with Acrobat Reader and Okular.

Embedding and/or outlining fonts

 * Scribus will try to embed your fonts when exporting to PDF.
 * Fonts with more than 2048 glyphs will be automatically converted to outlines to reduce the size of the PDF. This font-specific setting can be changed in Preferences > Fonts by unchecking the "Subset" option for a font.

Scripting / Command line

 * You can write Python scripts which will run inside Scribus.
 * If you have questions about scripting you should post them to the mailing list or join the Scribus IRC channel.

Installation

 * Where can I get Scribus builds for Solaris?
 * Building Scribus on Windows

Usage

 * How can I make a document of 100+ pages? – Scribus is getting slower and slower
 * How can I make a booklet using Scribus? – perhaps the most FAQ
 * How can I launch Scribus in my language?
 * Where can I get a monitor profiler for Linux?
 * How can I execute scribus on a remote machine and display it on the local machine?
 * How do I do text flow between frames in Scribus?
 * How can I move a Scribus file to another computer along with its images?
 * How can I execute a Python script from within Scribus?
 * Can I use a commandline interface with Scribus?

PDF issues

 * For whom is PDF/X-3 really desired?
 * How can I preserve transparency while exporting to PDF?
 * How do I prevent fonts from looking ugly in the exported PDF ?

Fonts

 * What is the difference between good and bad fonts?
 * Where can I get good fonts?
 * How can I see what fonts Scribus is loading

Other

 * How can I contribute to Scribus?
 * Is it necessary to ask or answer questions in English on the mailing list?
 * What are some good references to learn about layout and design?
 * Why Scribus doesn't support QuarkXpress and other major publishing applications