## A little WINE with Scribus

### Overview

One of the facts of life in the desktop publishing world, is the occasional need for working in a cross platform environment. Fortunately, for Linux users in particular, the Wine Project and Codeweavers have made much progress in being able to successfully run many Windows applications on top of Linux.

My main interest and focus for these notes is being able to run the latest versions of Adobe Acrobat Reader and the full version of Acrobat, in order to test Scribus created PDF files, as well as occasionally running the odd Windows or DOS based utility.

Since migrating my own personal workstation to Linux as my default environment, I have dabbled with installing various Windows apps and kept a eye on this project for several reasons:

1. Until the recent enhancements to Gnucash, I needed a Windows accounting application to run the books for my own company.
2. Professionally, I have to test and build training materials for a number of Windows applications, thus I try to avoid have to reboot into Windows.
3. I have run VMware in the past and it is superb, but is too resource intensive at times.
4. Sadly, many kinds of multimedia on the net needs a Windows based media application.

### Hints and my experience

My experience is packaged versions of Wine rarely work well, with the exception of the Codeweavers wine preview releases. I always build from source. Typically the Wine project releases a snapshot tarball once a month. With Wine, there is a slightly different way of building Wine from the usual:

`./configure && make && make install`

It is not quite obvious, but there is a way to use the Wine installer scripts which make installing much less difficult. To build the tarball from the root directory where you have un-tarred the source tarball, simply run ./tools/wineinstall and follow the instructions. Compiling from source, takes quite a while, so the ideal time for this is when your workstation will be idle. The benefit is the wine install will be carefully tailored to your setup, both software and hardware. I find it runs more reliably this way.

If you really do not want to install from source, grab the latest Codeweavers rpm or deb. Their wine package also includes a nice graphical configuration tool for creating the wine.conf file, which is the the key to making Wine work well.

After installation, you need a wine.conf file. This is hidden in .wine in your home directory. Open in a text editor and study it carefully, the slight adjustments you make here can make a big difference in its performance and reliability. This is well commented and documented in the docs as well.

Sometimes, there are regressions: I will typically keep the previous snapshot source until I have found the newest one to work well as well as before. Once or twice in the past couple of years, I have reverted to a previous release because something was broken.

Minuses: Printing support is weak. You can generate PostScript for later conversion via Distiller or GSview. Wine will support CUPS if you have the correct libraries installed, but in general it is nowhere a finished part of the code.

The good stuff: The Wine snapshot releases in the past few months have run Adobe Acrobat 5: both the 5.1 reader and full 5.0.5 version very reliably. After installation, find the intertrust plug-in folder and delete it before launching Acrobat. This was a very buggy plug-in to enable on-line buying of PDFs. In corporate installs of Acrobat, I make sure this is never installed because it has caused so many problems. The distiller part of Acrobat from Versions 3 to 5 install and work flawlessly, as long as it can locate all your font paths correctly. I have distilled hi-res 35 MB "press-ready" composite CMYK PDFs with ease. I have also loaded the free PDFInspektor plug-in from Callas. I use this to test PDF/X-3 conformance of Scribus PDF/X-3 files (They passed the very first time ;))

Installing applications has become much more reliable in the last year. Where Wine sometimes has troubles is custom installs. Sometimes, you just have to click through the defaults to get an application to install properly.

## The Alternatives

### Crossover Office from Codeweavers

Versions 5.0+ run a number of applications quite well, including Photoshop 5,6,7, as well as in my tests, Illustrator 10 and Indesign 2.0.2. The last two can be taxing even on real Windows at times. I found the demo to have a very polished and easy to use installer, which makes configuration a snap. Codeweavers has contributed a great deal to the success of the Wine project thus far. You can also get Crossover Office with some versions of the Suse and Xandros distributions.

### Win4Lin from Netraverse

Disclaimer: Netraverse has provided the Scribus Team with in-kind sponsorship.

Win4Lin allows you to run Win 2000 or XP natively on Linux with a translation layer, providing near native speeds and capabilities with few limitations. Basically, you need a licensed version of Win 2000 or XP and run the installer. It looks and works well and most Win32 applications can run.

I would not discourage anyone from buying either. Both companies have been good citizens in the open source community.

### Success

Although Acrobat 5.0.5 is not officially supported by Codeweavers, it installs and runs very well. Until the day when Linux/Unix has the same parity in commercial application support, Wine is a good transition strategy. Hopefully, you will find these notes useful in supporting your use of Scribus.