Subversion Repositories Scribus

Compare Revisions

Ignore whitespace Rev 13526 → Rev 13527

/trunk/Scribus/doc/en/install1.html
0,0 → 1,56
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>How to obtain the Scribus source</title>
</head>
<body>
<h2>How to obtain the Scribus source</h2>
<p>You can get the most recent version of Scribus from:</p>
<ul class="simple">
<li>Main Scribus Website - <a href="http://www.scribus.net">http://www.scribus.net</a></li>
<li> <a href="http://sourceforge.net/project/showfiles.php?group_id=125235">Scribus Sourceforge Downloads</a></li>
 
 
</ul>
<p>There is also thanks to <a href="http://Anduin.net">Anduin.net</a>, anonymous CVS access is updated daily. Only recommended for those who want to stay on the bleeding edge. <strong>Scribus 1.2.x is now deprecated.</strong> Instructions for getting the latest source via svn: </p>
 
<p><strong>Scribus 1.3.3.x - Stable</strong></p>
<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
<pre>
svn co svn://scribus.info/Scribus/branches/Version133x
</pre>
or, for those with closed SVN ports on their firewalls:
<pre>
svn co http://scribus.info/svn/Scribus/branches/Version133x/
</pre>
</td></tr></table></blockquote>
 
<p>From here, continue with the <a href="install3.html">Compiling and Installing using autotools</a> instructions.</p>
 
<p><strong>Scribus 1.3.5 target branch</strong>. This branch is the code that will end up as 1.3.5, and eventually 1.4.0.</p>
<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
<pre>
svn co svn://scribus.info/Scribus/branches/Version135
</pre>
or, once again for those with closed SVN ports on their firewalls:
<pre>
svn co http://scribus.info/svn/Scribus/branches/Version135
</pre>
</td></tr></table></blockquote>
 
<p><strong>Scribus 1.5.0svn - Development</strong></p>
<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
<pre>
svn co svn://scribus.info/Scribus/trunk
</pre>
or, once again for those with closed SVN ports on their firewalls:
<pre>
svn co http://scribus.info/svn/Scribus/trunk
</pre>
</td></tr></table></blockquote>
 
<p>CMake is required for any version after 1.3.4, as autotools support has been removed.</p>
<p>From here, continue with the <a href="install4.html">Compiling and Installing using CMake</a> instructions.</p>
 
</body>
</html>
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/readme-macosx.html
===================================================================
--- Scribus/doc/en/readme-macosx.html (nonexistent)
+++ Scribus/doc/en/readme-macosx.html (revision 13527)
@@ -0,0 +1,53 @@
+<html><head>
+
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <title>Scribus on Mac OS X</title>
+</head><body>
+ <h2>Scribus on Mac OS X - Read Me</h2>
+ <h3>Hardware/Software Minimum Requirements:</h3>
+ <p>PowerPC or Intel-based Mac, although using the dual core Intel systems will give a much better experience.</p>
+ <p>512
+Mb in addition to system memory requirements – the more the better. 1-2
+Gb or more is strongly recommended for larger or more complex
+documents. </p>
+ <h3>Before Installing Scribus</h3>
+ <ul>
+ <li>Install Ghostscript for Mac OSX – <a href="http://idisk.mac.com/yhonda-Public/ghostscript.dmg">Ghostscript 8.60+</a> or newer is recommended. This is important for EPS, PS import and printing. You may also install this via <a href="http://www.macports.org/">MacPorts</a> or <a href="http://www.finkproject.org/">Fink</a>. The end result is the same.</li>
+ <li>This
+is beta software which is undergoing many code changes daily. While it
+is fairly stable and usable, caution is advised. It is not recommended
+yet for production use. </li>
+ </ul>
+ <h3>Installing</h3>
+ <ul>
+ <li>Simply <a href="http://sourceforge.net/project/showfiles.php?group_id=125235&amp;package_id=201484">download</a>
+the Mac OSX dmg format file from Sourceforge, open it and drag the
+Scribus icon to the location of your choice. The dmg Finder window
+offers the default system Application directory. From there you may
+click on the icon and run Scribus.</li>
+ <li>The first launch of
+Scribus or when a new user launches Scribus will be much longer than
+usual. This is because Scribus is creating a cache file of your fonts.
+Later re-starts will be much quicker.</li>
+ </ul>
+<h3>Additional Software</h3>
+<ul>
+<li>As of version 1.3.5, Scribus provides a new type of frame, called
+Render Frame. It allows the use of other programs to render their
+outpout in a Scribus document. To take full advantage of this feature,
+you need to install these programs. By default, Scribus is
+preconfigured to use <a href="http://www.tug.org/mactex/">LaTeX</a>, <a href="http://lilypond.org/web/install/">Lilypond</a>, <a href="http://www.povray.org/redirect/www.povray.org/ftp/pub/povray/Official/Macintosh/povpmac.sit">POV-Ray</a>, <a href="http://www.pixelglow.com/graphviz/">Graphviz</a>, and <a href="http://lee-phillips.org/info/Macintosh/gnuplot.html">Gnuplot</a>.
+</li>
+</ul>
+ <h3>Console Mode for Diagnostics</h3>
+ <p>There is a second way to launch Scribus: <strong>Console Mode</strong>.
+If you open Console.app from the Applications Utilities folder, you are
+able to see the output of Scribus on startup. This will give you
+information on the fonts discovered on startup, and list any issues
+found while starting.</p>
+ <p><a href="http://docs.scribus.net/">Scribus Documentation Site</a> (EN,FR,DE, PL) - http://docs.scribus.net</p>
+ <p><a href="http://www.scribus.net/">Scribus Home Page</a> - http://www.scribus.net</p>
+ <p><a href="http://bugs.scribus.net/">Scribus Bug Tracker</a> - http://bugs.scribus.net</p>
+ <p><a href="http://wiki.scribus.net/">Scribus Wiki</a> (users for users) - http://wiki.scribus.net</p>
+ <p><a href="http://lists.scribus.info/mailman/listinfo/scribus">Mailing list</a> (subscription, archives etc.) -http://lists.scribus.info/mailman/listinfo/scribus </p>
+</body></html>
Index: Scribus/doc/en/readme.html
===================================================================
--- Scribus/doc/en/readme.html (nonexistent)
+++ Scribus/doc/en/readme.html (revision 13527)
@@ -0,0 +1,60 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Version 1.3.5 Readme</title>
+</head>
+<body>
+<h2>Scribus Version 1.3.5 Readme</h2>
+<h4>What's New ?</h4>
+<p>The Scribus 1.3.5 is the fifth development release of the next generation for Scribus. This release is the first based on Qt4 and on first use some GUI elements have changed along with new features made possible with Qt. </p>
+<h4>The file format has changed and is NOT backwardly compatible. You have been warned. We have specifically disabled the ability to open 1.3.4+ files in the stable 1.3.3.x versions. Our plans for a new file format should be settled in the 1.3.6 -1.3.7 development period.</h4>
+<ol>
+<li>Windows users are <strong>strongly encouraged</strong> to install the latest <a href="http://ghostscript.com">Ghostscript</a> <strong>before</strong> installing Scribus. This greatly simplifies setting up EPS importing. Ghostscript is a mature PostScript interpreter and is essential for EPS import and print preview in Scribus.</li>
+<li>Because of the new enhanced menu/keyboard shortcuts code, 1.2.x keyboard short cuts are not migrated and will be recreated once on the first launch 1.3.x. There are vastly more keyboard shortcuts and they can be exported to use on other machines if customized.</li>
+<li>On initial launch, 1.3.5 will offer to inherit preferences from any existing prior version, but store them separately, so you can run 1.3.3.x in parallel with 1.3.5. </li>
+<li>You <strong>can</strong> install both versions in parallel and run them at the same time. The only caveat is to install them using different prefix/ directories e.g 1.3.3.x in /usr/local and 1.3.5 in /opt or $home/bin. You can use the <code>-DCMAKE_INSTALL_PREFIX:PATH=</code> argument to configure to set where Scribus should be installed.</li>
+<li>Many of the new or revised GUI functions have extensive tool tips. To enable tool tips, make sure <strong>Help &#062; Tooltips </strong>is checked. </li>
+</ol>
+<h4>New In Scribus 1.3.5</h4>
+<ul>
+<li>Porting to Qt4 should provide vastly better performance under OSX. Scribus 1.3.5 will run on OSX 10.3.9+ </li>
+<li>Much more extensive support for CMYK images, including clipping paths in TIFF and JPEG files, as well as extensive support for native Photoshop &#174; PSD files. 16 bit CMYK TIFF and PSD support will follow soon. Use of CMYK images is recommended with color management properly setup and active for best on screen appearance. CMYK-JPEG is also supported. </li>
+<<!--li>There is a new imposition tool which allows you to create booklets. This enables for example printing 2 pages of A5 on A4 paper.</li>-->
+<li>The other new major addtion is the new latex import capabilties. This is explained in detail in the online help.</li>
+
+
+</ul>
+<p>For detailed changes please see the ChangeLog and the Roadmap on <a href="http://wiki.scribus.net/">http://wiki.scribus.net/</a>.</p>
+<p>To use Scribus in your native language be sure that the environment variable LC_ALL, LC_MESSAGES, LANG, Qt locale, OR the command line option of -l/--lang &#060;lang&#062; is set correctly. This also can be changed in the preferences and takes effect immediately.</p>
+
+<p>The EPS/PS import features in 1.3.x uses advanced features of Ghostscript. We recommend ALL users update to the newest version of Ghostscript available for your distribution. There are detailed hints on docs.scribus.net for installing GS 8.x in parallel to the GS installed by your distribution.</p>
+
+<p>Activating Color Management <strong>requires</strong> installation of CMYK and RGB ICC profiles. Grey scale icc profiles in images are not supported in this release. Scribus comes with 2 icc profiles only to ensure color management works immediately. These profiles are not sufficient to provide correctly working color management. Please see the included help files and <a href="http://docs.scribus.net">http://docs.scribus.net</a> for details.</p>
+<!--<p>If you have a 64-bit version of Qt, sometimes ./configure will not detect the 64-bit version headers. Try : <pre>./configure --enable-libsuffix=64</pre> to test for 64-bit versions of libraries.</p>-->
+<h4>Other notes/known issues at the time of release:</h4>
+
+<p>There is a bug in font outline handling for some fonts in the freetype libraries. It's being worked on upstream. Don't file a bug report. Instead change the font used if you need the outlines. This is not a Scribus bug. Some testing has shown that this bug is not present in freetype 2.1.10+, but we counsel caution trying to upgrade freetype2. Upgrading freetype2 on some distributions can be quite difficult.</p>
+
+
+<h4>Font Issues</h4>
+<p>There are extensive notes and detailed on documentation on fonts and trouble shooting of font issues in the help documentation and online at http://docs.scribus.net. Please read these carefully before filing bugs.</p>
+<p>There are issues with the PostScript naming conventions with the Computer Modern Type 1 fonts, depending on distribution. In some cases, not all fonts from the same family are visible in Scribus. We are working on a more complete solution for the next release.
+</p>
+
+<h4>For Debian Users: </h4>
+<p>If Scribus does not start while complaining about the absence of PostScript fonts please install either xfonts-scalable or gsfonts-x11. They are in the "Recommends" and will be installed by all sensible apt front-ends.
+</p>
+<h4>For Suse 10.x/11.x Users:</h4>
+<ul>
+<li>There are both 32 and 64 bit packages in OpenSuse Build server. Within the same repo are several programs which are useful with Scribus including GSview and other graphics utilities.</li>
+<li>Should you compile your own from source, to enable direct CUPS support which we recommend, make sure both cups-devel and openssl-devel are installed. Suse enables ssl support in CUPS. See the BUILDING file.</li></ul>
+<p>There is a separate file, PACKAGING for detailed hints and notes on building packages for Scribus.</p>
+<p> More hints and other information are on the <a href="http://www.scribus.net">http://www.scribus.net</a> and <a href="http://docs.scribus.net">http://docs.scribus.net</a> sites. Full compile, install and FAQs are available there.</p>
+
+<p>There is a lively on-line community, both on IRC @ #scribus on irc.freenode.net and the mailing list. Mailing list info can be found at: http://lists.scribus.info/mailman/listinfo/scribus</p>
+<p>For the Scribus Team,</p>
+<p>Peter Linnell<br />
+in April 2009 <br />
+</p>
+</body>
+</html>
/Scribus/doc/en/readme.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/index.html
===================================================================
--- Scribus/doc/en/index.html (nonexistent)
+++ Scribus/doc/en/index.html (revision 13527)
@@ -0,0 +1,78 @@
+<qt>
+<title>Open Source Desktop Publishing for Linux, Mac OS&#174; X and Windows&#174;</title>
+<table border="0" cellspacing="0" cellpadding="0" width="100%" bgcolor="#2780b9" >
+ <tr>
+ <td align="left"><img src="images/docheader1.png" width="222" height="87"></td>
+ <td align="right"><img src="images/docheader2.png" width="318" height="87"></td>
+ </tr>
+</table>
+<h2>Scribus - Open Source Desktop Publishing</h2>
+
+<!--marker for image gallery-->
+
+<p>Scribus brings award-winning professional page layout to Linux/Unix, MacOSX, OS/2 and Windows desktops with a combination of &#034;press-ready&#034; output and new approaches to page layout.</p>
+
+<p>Since its humble beginning in the spring of 2001, Scribus has rapidly developed into one of the premier desktop applications for Linux. Called by Newsforge, <b>"..one of the killer applications for Linux"</b>, Scribus brings powerful and versatile tools for desktop publishing. New features like separation previews, cross-platform python scripting, advanced PDF 1.4 support are just some of the hundreds of improvements large and small in Scribus. Beginning with the 1.3.3.7 release, Scribus is now completely cross-platform and runs natively on Linux/Unix, MacOSX, OS/2 and Windows.</p>
+
+<p>Underneath the modern and user friendly interface, Scribus supports professional publishing features, such as CMYK color, separations, ICC color management and versatile PDF creation. <b>Scribus was the first DTP application on the planet to directly support PDF/X-3 output, a rigorous ISO standard.</b> Scribus did so by almost a year. Other features include PDF Import, EPS import/export, Unicode text including right to left scripts such as Arabic and Hebrew.</p>
+
+<p><b>Scribus also has unexpected touches such as: useful vector drawing tools, SVG import/export and support for OpenType Fonts.</b> The Scribus file format is XML based; open and completely documented. Unlike proprietary binary file formats, even damaged documents can be recovered with a simple text editor - sometimes a challenging problem with other page layout programs. There is an easy to use drag and drop scrapbook. Scribus has been translated into more than 25 languages and more are coming in the future. <b>The Scribus team prides itself on excellent end user support with a lively IRC channel and friendly mailing list.</b></p>
+
+
+<div class="news">
+<div class="item">
+<h3>Release History</h3>
+<ul>
+<li><b>15/04/2008</b> - Scribus 1.3.3.13 released </li>
+<li><b>12/06/2008</b> - Scribus 1.3.3.12 released </li>
+<li><b>12/01/2008</b> - Scribus 1.3.3.11 released </li>
+<li><b>08/01/2008</b> - Scribus 1.3.3.10 released </li>
+<li><b>28/05/2007</b> - Scribus 1.3.4 (devel) released </li>
+<li><b>05/05/2007</b> - Scribus 1.3.3.9 released </li>
+<li><b>23/02/2007</b> - Scribus 1.3.3.8 released </li>
+<li><b>09/01/2007</b> - Scribus 1.3.3.7 released (added OS/2 Port)</li>
+<li><b>04/12/2006</b> - Scribus 1.3.3.6 released</li>
+<li><b>09/11/2006</b> - Scribus 1.3.3.5 released</li>
+<li><b>03/10/2006</b> - Scribus 1.3.3.4 released</li>
+<li><b>07/08/2006</b> - Scribus 1.3.3.3 released</li>
+<li><b>14/07/2006</b> - Scribus 1.2.5 released</li>
+<li><b>29/05/2006</b> - Scribus 1.3.3.2 (devel) released</li>
+<li><b>10/04/2006</b> - Scribus 1.3.3.1 (devel) released</li>
+<li><b>27/01/2006</b> - Scribus 1.3.3 (devel) released</li>
+<li><b>22/01/2006</b> - Scribus 1.3.2 (devel) released (added Win32 port)</li>
+<li><b>05/01/2006</b> - Scribus 1.2.4.1 released</li>
+<li><b>03/10/2005</b> - Scribus 1.3.1 (devel) released</li>
+<li><b>12/09/2005</b> - Scribus 1.2.3 released</li>
+<li><b>14/07/2005</b> - Scribus 1.3.0 released (added Mac OSX port)</li>
+<li><b>05/07/2005</b> - Scribus 1.2.2.1 released</li>
+<li><b>8/01/2005</b> - Scribus 1.2.1 released</li>
+<li><b>28/08/2004</b> - Scribus 1.2 released</li>
+<li><b>06/06/2004</b> - Scribus 1.1.7 released</li>
+<li><b>28/03/2004</b> - Scribus 1.1.6 released</li>
+<li><b>14/02/2004</b> - Scribus 1.1.5 released</li>
+<li><b>18/12/2003</b> - Scribus 1.1.4 released</li>
+<li><b>28/11/2003</b> - Scribus 1.1.3 released</li>
+<li><b>28/10/2003</b> - Scribus 1.1.2 released</li>
+<li><b>03/10/2003</b> - Scribus 1.1.1 released</li>
+<li><b>06/09/2003</b> - Scribus 1.1.0 released</li>
+<li><b>07/08/2003</b> - Scribus 1.0.1 released</li>
+<li><b>21/06/2003</b> - Scribus 1.0 released</li>
+<!--
+<li><b>13/06/2003</b> - Scribus 0.9.11.1 released</li>
+<li><b>16/05/2003</b> - Scribus 0.9.10 released</li>
+<li><b>18/04/2003</b> - Scribus 0.9.9 released</li>
+<li><b>25/03/2003</b> - Scribus 0.9.8 released</li>
+<li><b>21/02/2003</b> - Scribus 0.9.7 released</li>
+<li><b>11/01/2003</b> - Scribus 0.9.6 released</li>
+<li><b>14/12/2002</b> - Scribus 0.9.4 released</li>
+<li><b>23/11/2002</b> - Scribus 0.9.3 released</li>
+<li><b>14/11/2002</b> - Scribus 0.9.2 released</li>
+<li><b>30/12/2002</b> - Scribus 0.9.1 released</li>
+<li><b>09/11/2002</b> - Scribus 0.9.0 released</li>
+<li><b>24/09/2002</b> - Scribus 0.8.0 released</li>
+<li><b>30/12/2002</b> - Scribus 0.7.8 released</li>-->
+</ul>
+</div>
+</div>
+</qt>
+
/Scribus/doc/en/index.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/keys.html
===================================================================
--- Scribus/doc/en/keys.html (nonexistent)
+++ Scribus/doc/en/keys.html (revision 13527)
@@ -0,0 +1,231 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Keyboard Shortcut Settings</title>
+</head>
+<body>
+<h2>Keyboard Shortcut Settings</h2>
+<p>In Scribus 1.3.x, the keyboard shortcuts are completely revised. There is still some ongoing work, so the most updated information is here: </p>
+<a href="http://wiki.scribus.net/index.php/Keyboard_Shortcuts_by_Key">http://wiki.scribus.net/index.php/Keyboard_Shortcuts_by_Key</a>
+<p>See also: <a href="mouse.html">Mouse Usage Hints</a><strong> Note:</strong> Keyboard Short Cuts are completely customizable and can be exported for use on other machines under the Keyboard Preferences.</p>
+
+<h3> Default Keyboard Shortcuts for Scribus 1.3.x </h3>
+
+<h3> Function Keys </h3>
+<table >
+<tr><td> <b>Function</b> </td><td> <b>Shortcut</b></td></tr>
+
+<tr><td> Show Help Manual </td><td> F1</td></tr>
+<tr><td> Show Properties Palette</td><td> F2</td></tr>
+
+<tr><td> Show Layers Palette </td><td> F6</td></tr>
+<tr><td> Toggle All Palettes </td><td> F10</td></tr>
+
+<tr><td> Toggle All Guides </td><td> F11</td></tr>
+<tr><td> Insert Unicode Character </td><td> F12 &#043; 4 digit hex value</td></tr>
+ </table>
+<h3> Control, Shift, Alt Keys </h3>
+
+<table >
+<tr><td> <b>Function</b> </td><td> <b>Shortcut</b></td></tr>
+<tr><td> Select All </td><td> Control-A</td></tr>
+<tr><td> Deselect All </td><td> Control-Shift-A</td></tr>
+<tr><td> Copy </td><td> Control-C</td></tr>
+<tr><td> Copy Contents (Images Only) </td><td>Control &#043;Shift&#043;C</td></tr>
+<tr><td> Paste Contents (Images Only) </td><td>Control &#043;Shift&#043;P</td></tr>
+<tr><td> Absolute Paste Contents (Images Only) </td><td>Control &#043;Alt&#043;Shift&#043;P</td></tr>
+<tr><td> Get Text or Image depending on selection </td><td> Control-D</td></tr>
+<tr><td> Item Duplicate </td><td> Control&#043;Alt&#043;Shift&#043;D</td></tr>
+<tr><td>Image Effects </td><td>Control-E</td></tr>
+<tr><td> Search and Replace </td><td> Control-F</td></tr>
+<tr><td> Lock Item </td><td> Control-L</td></tr>
+<tr><td> Lock Item Size </td><td> Control-Shift-L</td></tr>
+<tr><td> Group Items </td><td> Control-G</td></tr>
+<tr><td> Ungroup Item </td><td> Control&#043;Shift&#043;G</td></tr>
+<tr><td> Document Information </td><td> Control-I</td></tr>
+<tr><td> Delete Item </td><td> Control-K</td></tr>
+<tr><td> New File </td><td> Control-N</td></tr>
+<tr><td> Open File </td><td> Control-O</td></tr>
+<tr><td> Print </td><td> Control-P</td></tr>
+<tr><td> Quit </td><td> Control-Q</td></tr>
+<tr><td> Save </td><td> Control-S</td></tr>
+<tr><td> Save As </td><td> Control-Shift-S</td></tr>
+<tr><td> Paste </td><td> Control-V</td></tr>
+<tr><td> Close File </td><td> Control-W</td></tr>
+<tr><td> Cut </td><td> Control-X</td></tr>
+<tr>
+<td> Edit with Story Editor </td><td> Control-Y
+</td></tr>
+<tr>
+<td> Undo </td><td> Control-Z
+</td></tr>
+<tr>
+<td> Redo </td><td> Control-Shift-Z
+
+</td></tr>
+<tr>
+<td> Select All </td><td> Control-A
+</td></tr>
+<tr>
+<td> DeSelect All </td><td> Control-Shift-A
+</td></tr>
+<tr>
+<td> Zoom to fit </td><td> Control-0
+
+</td></tr>
+<tr>
+<td> Zoom to 100% </td><td> Control-1
+</td></tr>
+<tr>
+<td> Zoom In </td><td> Control-Plus
+</td></tr>
+<tr>
+<td> Zoom Out </td><td> Control-Minus
+
+</td></tr>
+<tr>
+<td> Smart Hyphen </td><td> Control-Shift-Minus
+</td></tr>
+<tr>
+<td> Non Breaking Space </td><td> Control-Space
+</td></tr>
+<tr>
+<td> Insert Page Number </td><td> Control-Alt-Shift-P
+
+</td></tr>
+<tr>
+<td> Raise </td><td> Control-Home
+</td></tr>
+<tr>
+<td> Lower </td><td> Control-End
+</td></tr>
+<tr>
+<td> Raise to top </td><td> Home
+
+</td></tr>
+<tr>
+<td> Lower to bottom </td><td> End
+</td></tr>
+<tr>
+<td> New Line </td><td> Shift-Return
+</td></tr>
+<tr><td> Frame Break </td><td> Control-Return</td></tr>
+<tr><td> Column Break </td><td> Control-Shift-Return</td></tr>
+<tr><td> Stacked Objects, next in Z-order </td><td> Control-Shift-LMouse</td></tr>
+<tr><td> Resizing object when other object on top </td><td> Control-drag</td></tr>
+<tr><td> Resize proportionally </td><td> Control-drag</td></tr>
+<tr><td> Move image in image frame without entering frame edit mode </td><td> Control-Alt-drag</td></tr>
+<tr>
+<td> Move frame/group with X/Y constrained </td><td> Control-drag
+</td></tr>
+<tr>
+<td> Rotate a line or when creating a line, constrain the angle of rotation </td><td> Control-drag and rotate
+</td></tr>
+<tr>
+<td> Rotate an existing item on the page other than a line and<br/>constrain the angle of rotation </td><td> Control-drag and rotate
+
+</td></tr>
+<tr>
+<td> Resize to a square </td><td> Shift-drag
+</td></tr>
+<tr>
+
+
+
+</table>
+
+<p>You can <em>constrain</em> objects when re-sizing them with Ctrl-drag. <em>Constraining</em> keeps the aspect ratio the same as the original shape.</p>
+
+<h3> Normal Keys </h3>
+<table >
+<tr>
+<td> <b>Function</b> </td><td> <b>Shortcut</b>
+</td></tr>
+<tr>
+
+<td> A </td><td> Insert Table Frame
+</td></tr>
+<tr>
+<td> B </td><td> Insert Bezier Curve
+</td></tr>
+<tr>
+<td> C </td><td> Select (Temporary until the rest are sorted out)
+</td></tr>
+
+<tr>
+<td> E </td><td> Edit Contents (text in a text frame, or image location in an image frame)
+</td></tr>
+<tr>
+<td> F </td><td> Insert Freehand Line
+</td></tr>
+<tr>
+<td> I </td><td> Insert Image Frame
+
+</td></tr>
+<tr>
+<td> N </td><td> Link Text Frame
+</td></tr>
+<tr>
+<td> L </td><td> Insert Line
+</td></tr>
+<tr>
+<td> P </td><td> Insert Polygon
+
+</td></tr>
+<tr>
+<td> R </td><td> Rotate
+</td></tr>
+<tr>
+<td> S </td><td> Insert Shape
+</td></tr>
+<tr>
+<td> T </td><td> Insert Text Frame
+
+</td></tr>
+<tr>
+<td> U </td><td> Unlink Text Frame
+</td></tr>
+<tr>
+<td> Z </td><td> Zoom
+</td></tr></table>
+<h3>Story Editor</h3>
+<table>
+<tbody>
+<tr> <td>Esc </td><td>Closes Story Editor</td></tr>
+<tr> <td>Ctrl &#043;W </td><td>Save Changes and Close Story Editor</td></tr>
+<tr><td>Ctrl &#043;S </td><td>Save File While Editing in Story Editor</td></tr>
+</tbody>
+</table>
+
+<h3>Moving and Re-sizing using Arrow Keys</h3>
+<p>Move item 1 unit (current: pt,mm,in,c,p,cm) Arrow key up/down/left/right</p>
+ <p>Move item 10 units (current: pt,mm,in,c,p,cm) Ctrl+Arrow keys</p>
+ <p>Move item 0.1 units (current: pt,mm,in,c,p,cm) Shift+Arrow keys</p>
+<p>Move item 0.01 units (current: pt,mm,in,c,p,cm) Control+Shift+Arrow keys</p>
+ <p>Resize item 1 unit outwards (current: pt,mm,in,c,p,cm) Alt+Arrow keys</p>
+ <p>Resize item 1 unit inwards(current: pt,mm,in,c,p,cm) Shift+Alt+Arrow keys</p>
+ <p>Resize item 10 units outwards (current: pt,mm,in,c,p,cm) Control+Alt+Arrow keys</p>
+ <p>Resize item 10 units inwards(current: pt,mm,in,c,p,cm) Control+Shift+Alt+Arrow keys</p>
+<h3>Resizing Images in Edit Mode</h3>
+<p>Alt right arrow, move right side outwards (expand)</p>
+<p>Alt left arrow, move left side outwards (expand)</p>
+<p>Alt Shift right arrow, move left side inwards (shrink)</p>
+<p>Alt Shift left arrow, move right side inwards (shrink)</p>
+
+<h3>Selection/Navigation Keys</h3>
+<p>Shift &#043; Left Click = Selecting more than one object.</p>
+<p>Shift&#043;Cursor Key selects Characters</p>
+<p>Ctrl&#043;Shift&#043;Cursor Key selects Words</p>
+<p>Ctrl&#043;Cursor Up/Down selects Lines</p>
+<p>Ctrl&#043;Home selects Text from the Start to the Cursor Position</p>
+<p>Ctrl&#043;End selects Text from the Cursor Position to the End</p>
+<p>Ctrl&#043;Cursor Key moves to the next Word</p>
+<p>Home moves to the beginning of the line</p>
+<p>End moves to the end of the line</p>
+<p>Ctrl&#043;Shift&#043;Click selects the Object beneath another</p>
+<p>Shift&#043;Click adds an Object to the Selection</p>
+<p>Ctrl&#043;Alt&#043;Click selects a single Object out of a Groups</p>
+<p>Overlapping objects - Control shift select any frame on any level on one layer to select it. Then to move or resize the frame you have selected, hold down control.</p>
+<p>You can <strong><em>constrain</em></strong> objects when re-sizing them with Ctrl&#043drag. <em>Constraining</em> keeps the aspect ratio the same as the original shape.</p>
+</body>
+</html>
/Scribus/doc/en/keys.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install4.html
===================================================================
--- Scribus/doc/en/install4.html (nonexistent)
+++ Scribus/doc/en/install4.html (revision 13527)
@@ -0,0 +1,161 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
+ <title>Compiling and Installing Using CMake and Scribus 1.3.3.6+ and 1.3.4+</title>
+</head>
+
+<body>
+ <h2>Compiling and Installing using CMake and Scribus 1.3.3.6 and 1.3.4 or higher</h2>
+
+ <p>After many years of using the autotools build system, the developers of Scribus have selected CMake as a replacement system. It provides a much more flexible setup with a lot less complexity. It also provides compatibility with build tools on Linux and variants of Unix, Windows and Mac OS X.</p>
+
+ <p>To build with the CMake build system you will of course need CMake itself. Most Linux and some Unix distributions provide it as a standard package. If not, please <a href="http://www.cmake.org">download it</a>, make sure you get a recent version, like 2.4.3 or higher. Mac OS X users can also find installers there, as well as, getting it from <a href="http://macports.org">macports.org</a>. Scribus does not yet use CMake for Windows, although this may be added in the future.</p>
+
+ <p>One of the advantages of CMake is that we can build "out of source". By creating a separate directory where the program is being being compiled, the temporary files and resulting application files are not stored in the same location as the Scribus source files. This helps keep directory structures clean and will also reduce the download time for updating your source tree a little. This is the preferred method and strongly recommended by our developers. CMake is also much simpler to maintain for developers and errors can be understood by mere mortals. <!--However, both methods are described below; the first is recommended.--></p>
+
+ <h3>Preparation</h3>
+
+ <p>Let's assume the following:</p>
+
+ <ul>
+ <li>Scribus source is in a directory like <code>/home/username/scribussource/</code> (where <em>username</em> is your username)</li>
+
+ <li>CMake is in <code>/usr/bin/</code></li>
+
+ <li>You want to install into <code>/home/username/scribusinstall/</code></li>
+ </ul>
+
+ <h3>Starting an Out-of-Source Build</h3>
+
+ <p>Change to the source directory:</p>
+ <pre>
+cd /home/username/scribussource/
+</pre>
+
+ <p>Make a directory to build Scribus in:</p>
+ <pre>
+mkdir builddir
+</pre>
+
+ <p>Change to the build directory:</p>
+ <pre>
+cd builddir
+</pre>
+
+ <p>Then run:</p>
+ <pre>
+/usr/bin/cmake ../Scribus -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall/
+</pre>
+
+ <p>If this is the build location you have chosen, please skip down to the <strong>Build Stage</strong> section</p><!--<h3>Starting an In-Source Build</h3>
+<p>Change to the source directory:</p>
+<pre>cd /home/username/scribussource/</pre>
+<p>Then run:</p>
+<pre>/usr/bin/cmake . -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall/</pre>-->
+
+ <h3>Continuing onto the Build Stage</h3>
+
+ <p>Once the CMake command you have chosen above has completed successfully (remember it needs to find the dependencies of Scribus and record their locations), then you need to run:</p>
+ <pre>
+make &amp;&amp; make install
+</pre>
+
+ <h2>Advanced Options</h2>
+
+ <h3>Build Options</h3>
+
+ <p>Some options that the <b>Scribus 1.3.3.x</b> CMake files know about:</p>
+
+ <ul>
+ <li><strong>WANT_VERSIONING=1</strong>: Sets the build to use the VERSION setting as a suffix for the install directories and the binary. Eg, the binary could be scribus-1.3.4cvs. This should mean that you can install multiple versions with the same prefix with no clashes.</li>
+
+ <li><strong>WANT_DEBUG=1</strong>: Sets the build to be a debug release and use -O0 -g3, instead of -O2 (This is the default for now, and cannot be turned off unless you edit the CMakeFiles.txt file).</li>
+
+ <li><strong>WANT_CAIRO=1</strong>: Makes CMake search for cairo and build with cairo instead of LibArt_LGPL.</li>
+
+ <li><strong>WANT_LIBART=1</strong> (default): Makes CMake search for and build with LibArt_LGPL instead of cairo.</li>
+
+ <li><strong>WANT_NOHEADERINSTALL=1</strong>: Do not install header files used for developers. Distributions should not use this if they split up Scribus into multiple packages.
+ </ul>
+
+ <p>Some options that the <b>Scribus 1.3.5+</b> CMake files know about (more to come!):</p>
+
+ <ul>
+ <li><strong>WANT_VERSIONING=1</strong>: Sets the build to use the VERSION setting as a suffix for the install directories and the binary. Eg, the binary could be scribus-1.3.4cvs. This should mean that you can install multiple versions with the same prefix with no clashes.</li>
+
+ <li><strong>WANT_DEBUG=1</strong>: Sets the build to be a debug release and use -O0 -g3, instead of -O2 (This is the default for now, and cannot be turned off unless you edit the CMakeFiles.txt file).</li>
+
+ <li><strong>WANT_CAIRO=1</strong> (default): Makes CMake search for cairo and build with cairo instead of Qt's Arthur.</li>
+
+ <li><strong>WANT_QTARTHUR=1</strong>: Makes CMake search for and build with Qt's Arthur instead of cairo.</li>
+
+ <li><strong>WANT_NOHEADERINSTALL=1</strong>: Do not install header files used for developers. Distributions should not use this if they split up Scribus into multiple packages.
+
+ <li><strong>WANT_NORPATH</strong>: Turn off setting a specific RPATH.</li>
+ <li><strong>WANT_DISTROBUILD</strong>: An option for OS distributors to use for their builds options.</li>
+ <li><strong>WANT_LIB64</strong>: Force 64 bit builds.</li>
+ <li><strong>WANT_RELEASEWITHDEBUG</strong>: Set Release style build flags, but also include debug information.</li>
+ <li><strong>WANT_UNIVERSAL_BUNDLE</strong>: Mac OS X only, enable building of a .app bundle.</li>
+ <li><strong>WANT_QT4MAC_COCOA</strong>: Mac OS X only, enable the Cocoa version Qt4.5+.</li>
+ <li><strong>WANT_QT3SUPPORT</strong>: Enable Qt3 support in case you have a custom plugin that you have not converted fully to Qt4. Not needed for base Scribus code.</li>
+ <li><strong>APPLICATION_DATA_DIR</strong>: Set the name of the preferences location for Scribus (instead of default of ~/.scribus on *nix and /Users/username/Library/Preferences/Scribus on Mac OS X.)</li>
+ </ul>
+ <p>For example: to make a cairo debug build, then something like this (all on one line):</p>
+ <pre>
+/usr/bin/cmake . -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall
+ -DWANT_CAIRO=1 -DWANT_DEBUG=1 -DWANT_VERSIONING=1
+</pre>
+
+ <h3>Specifying Library Locations</h3>
+
+ <p>Whenever your distribution releases their package for a library Scribus depends on, it may still not be the very latest stable or unstable version from the writers of the library. In some cases, the Scribus developers have had to rely on the very latest code to further some parts of Scribus. In this case it is necessary to build your own version of such a library.</p>
+
+ <p>On example of this is the cairo graphics library. Right now, 1.3.4+ has the capability to use the very very latest code from the just released cairo 1.4.10 or later and we recommend it for performance reasons as well.</p>
+
+ <p>To specify a new cairo install path, other than your system's default add this to the cmake command line: <code>-DPREFIX_CAIRO:PATH=/path/to/your/cairo/install</code></p>
+
+ <h3>When system has both Qt3 and Qt4 installed</h3>
+
+ <p>Systems with both Qt3 and Qt4 installed: You have <code>uic</code> and <code>moc</code> from Qt4 in the path and it may results to the compilation crash. This should NOT be the case with CMake 2.4.2 and higher, or when using current Scribus SVN. However, this might be a useful workaround:</p>
+
+ <p>Remove cached options from previous cmake configuration run from your build location: <code>rm CMakeCache.txt</code></p>
+
+ <p>Then change PATH variable (for Gentoo) e.g.:</p>
+ <pre>
+export PATH=/usr/qt/3/bin/:$PATH
+</pre>
+
+ <p>And run cmake config phase again:</p>
+ <pre>
+/usr/bin/cmake . -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall/
+</pre>
+
+ <h3>Making a tarball for distribution</h3>
+
+ <p>To make a tarball for distribution, the old way would be to <code>make dist</code>.</p>
+
+ <p>The new way is to run:</p>
+ <pre>
+make package_source
+</pre>
+
+ <p>or</p>
+ <pre>
+/usr/bin/cpack -G TBZ2 --config CPackSourceConfig.cmake
+</pre>
+
+ <p>to give you a bundle of the source.</p>
+
+ <p><strong>Important:</strong> If you need to re-run cpack remove the <code>_CPack_Packages/</code> before running this a second time.</p>
+
+ <p>You can also use svn export</p>
+ <pre>
+/path/to/scribus/svn
+</pre>in a temporary directory and then tar or zip the directory to create a tarball.
+
+ <h3>Troubleshooting and Success Stories</h3>
+
+ <p>If after reading these instructions through and you still have issues, please join us on <a href="irc.html">IRC</a> or post a mail to our <a href="resources.html">mailing list</a> with specifics of your problem. We also are interested in hearing from folks who have successfully compiled Scribus on non-Linux platforms too. We know it is very reliable on Mac OS X as well.</p>
+</body>
+</html>
/Scribus/doc/en/install4.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-textframes.html
===================================================================
--- Scribus/doc/en/scripterapi-textframes.html (nonexistent)
+++ Scribus/doc/en/scripterapi-textframes.html (revision 13527)
@@ -0,0 +1,163 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Handling Text Frames</title>
+</head>
+<body>
+<h2>Handling Text Frames</h2>
+
+<dl>
+
+<dt><a name="-dehyphenateText"><strong>dehyphenateText</strong></a>(...)</dt>
+<dd><code>dehyphenateText(["name"]) -&gt; bool</code>
+<p>Does dehyphenation on text frame "name". If "name" is not given the currently selected item is used.</p>
+<p>May raise WrongFrameTypeError if the target frame is not a text frame</p></dd>
+
+<dt><a name="-deleteText"><strong>deleteText</strong></a>(...)</dt>
+<dd><code>deleteText(["name"])</code>
+<p>Deletes any text in the text frame "name". If there is some text selected, only the selected text will be deleted. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getAllText"><strong>getAllText</strong></a>(...)</dt>
+<dd><code>getAllText(["name"]) -&gt; string</code>
+<p>Returns the text of the text frame "name" and of all text frames which are linked with this frame. If this textframe has some text selected, the selected text is returned. If "name" is not given the currently selected item is used.</p></dd></dt>
+
+<dt><a name="-getColumnGap"><strong>getColumnGap</strong></a>(...)</dt>
+<dd><code>getColumnGap(["name"]) -&gt; float</code>
+<p>Returns the column gap size of the text frame "name" expressed in points. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getColumns"><strong>getColumns</strong></a>(...)</dt>
+<dd><code>getColumns(["name"]) -&gt; integer</code>
+<p>Gets the number of columns of the text frame "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getFont"><strong>getFont</strong></a>(...)</dt>
+<dd><code>getFont(["name"]) -&gt; string</code>
+<p>Returns the font name for the text frame "name". If this text frame has some text selected the value assigned to the first character of the selection is returned. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getFontSize"><strong>getFontSize</strong></a>(...)</dt>
+<dd><code>getFontSize(["name"]) -&gt; float</code>
+<p>Returns the font size in points for the text frame "name". If this text frame has some text selected the value assigned to the first character of the selection is returned. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getLineSpacing"><strong>getLineSpacing</strong></a>(...)</dt>
+<dd><code>getLineSpacing(["name"]) -&gt; float</code>
+<p>Returns the line spacing ("leading") of the text frame "name" expressed in points. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getText"><strong>getText</strong></a>(...)</dt>
+<dd><code>getText(["name"]) -&gt; string</code>
+<p>Returns the text of the text frame "name". If this text frame has some text selected, the selected text is returned. All text in the frame, not just currently visible text, is returned. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getTextColor"><strong>getTextColor</strong></a>(...)</dt>
+<dd><code>getLineColor(["name"]) -&gt; string</code>
+<p>Returns the name of the line color of the object "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getTextDistances"><strong>getTextDistances</strong></a>(...)</dt>
+<dd><code>getTextDistances(["name"]) -&gt; tuple</code>
+<p>Returns the text distances of the text frame "name" expressed in points. The
+distances are returned as a tuple like (left, right, top, bottom). If "name"
+is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getTextLength"><strong>getTextLength</strong></a>(...)</dt>
+<dd><code>getTextLength(["name"]) -&gt; integer</code>
+<p>Returns the length of the text in the text frame "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getTextLines"><strong>getTextLines</strong>(...)</a></dt>
+<dd><code>getTextLines(["name"]) -&gt; integer</code>
+<p>Returns the number of lines of the text in the text frame "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getTextShade"><strong>getTextShade</strong></a>(...)</dt>
+<dd><code>getLineShade(["name"]) -&gt; integer</code>
+<p>Returns the shading value of the line color of the object "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-hyphenateText"><strong>hyphenateText</strong></a>(...)</dt>
+<dd><code>hyphenateText(["name"]) -&gt; bool</code>
+<p>Does hyphenation on text frame "name". If "name" is not given the currently selected item is used.</p>
+<p>May raise WrongFrameTypeError if the target frame is not a text frame</p></dd>
+
+<dt><a name="-insertText"><strong>insertText</strong></a>(...)</dt>
+<dd><code>insertText("text", pos, ["name"])</code>
+<p>Inserts the text "text" at the position "pos" into the text frame "name". Text must be UTF encoded (see <a href="#-setText">setText</a>() as reference) The first character has an index of 0. Inserting text at position -1 appends it to the frame. If "name" is not given the currently selected Item is used.</p>
+<p>May throw IndexError for an insertion out of bounds.</p></dd>
+
+<dt><a name="-isPDFBookmark"><strong>isPDFBookmark</strong>(...)</a></dt>
+<dd><code>isPDFBookmark(["name"]) -&gt; bool</code>
+<p>Returns true if the text frame "name" is a PDF bookmark. If "name" is not given the currently selected item is used.</p>
+<p>May raise WrongFrameTypeError if the target frame is not a text frame</p></dd>
+
+<dt><a name="-selectText"><strong>selectText</strong></a>(...)</dt>
+<dd><code>selectText(start, count, ["name"])</code>
+<p>Selects "count" characters of text in the text frame "name" starting from the character "start". Character counting starts at 0. If "count" is zero, any text selection will be cleared. If "name" is not given the currently selected item is used.</p>
+<p>May throw IndexError if the selection is outside the bounds of the text.</p></dd>
+
+<dt><a name="-setColumns"><strong>setColumns</strong></a>(...)</dt>
+<dd><code>setColumns(nr, ["name"])</code>
+<p>Sets the number of columns of the text frame "name" to the integer "nr". If "name" is not given the currently selected item is used.</p>
+<p>May throw ValueError if number of columns is not at least one.</p></dd>
+
+<dt><a name="-setColumnGap"><strong>setColumnGap</strong></a>(...)</dt>
+<dd><code>setColumnGap(size, ["name"])</code>
+<p>Sets the column gap of the text frame "name" to the value "size". If "name" is not given the currently selected item is used.</p>
+<p>May throw ValueError if the column gap is out of bounds (must be positive).</p></dd>
+
+<dt><a name="-setFont"><strong>setFont</strong></a>(...)</dt>
+<dd><code>setFont("font", ["name"])</code>
+<p>Sets the font of the text frame "name" to "font". If there is some text selected only the selected text is changed. If "name" is not given the currently selected item is used.</p>
+<p>May throw ValueError if the font cannot be found.</p></dd>
+
+<dt><a name="-setFontSize"><strong>setFontSize</strong></a>(...)</dt>
+<dd><code>setFontSize(size, ["name"])</code>
+<p>Sets the font size of the text frame "name" to "size". "size" is treated as a value in points. If there is some text selected only the selected text is changed. "size" must be in the range 1 to 512. If "name" is not given the currently selected item is used.</p>
+<p>May throw ValueError for a font size that's out of bounds.</p></dd>
+
+<dt><a name="-setLineSpacing"><strong>setLineSpacing</strong></a>(...)</dt>
+<dd><code>setLineSpacing(size, ["name"])</code>
+<p>Sets the line spacing ("leading") of the text frame "name" to "size". "size" is a value in points. If "name" is not given the currently selected item is used.</p>
+<p>May throw ValueError if the line spacing is out of bounds.</p></dd>
+
+<dt><a name="-setPDFBookmark"><strong>setPDFBookmark</strong>(...)</a></dt>
+<dd><code>setPDFBookmark("toggle", ["name"])</code>
+<p>Sets wether (toggle = 1) the text frame "name" is a bookmark nor not. If "name" is not given the currently selected item is used.</p>
+<p>May raise WrongFrameTypeError if the target frame is not a text frame</p></dd>
+
+<dt><a name="-setText"><strong>setText</strong></a>(...)</dt>
+<dd><code>setText("text", ["name"])</code>
+<p>Sets the text of the text frame "name" to the text of the string "text". Text must be UTF8 encoded - use e.g. unicode(text, 'iso-8859-2'). See the FAQ for more details. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setTextAlignment"><strong>setTextAlignment</strong></a>(...)</dt>
+<dd><code>setTextAlignment(align, ["name"])</code>
+<p>Sets the text alignment of the text frame "name" to the specified alignment. If "name" is not given the currently selected item is used. "align" should be one of the ALIGN_ constants defined in this module - see dir(scribus).</p>
+<p>May throw ValueError for an invalid alignment constant.</p></dd>
+
+<dt><a name="-setTextDistances"><strong>setTextDistances</strong></a>(...)</dt>
+<dd><code>setTextDistances(left, right, top, bottom, ["name"])</code>
+<p>Sets the text distances of the text frame "name" to the values "left"
+"right", "top" and "bottom". If "name" is not given the currently
+selected item is used.</p>
+<p>May throw ValueError if any of the distances are out of bounds (must be positive).</p></dd>
+
+<dt><a name="-setTextScalingH"><strong>setTextScalingH</strong></a>(...)</dt>
+<dd><code>setTextScalingH(scale, ["name"]))</code>
+<p>Sets the horizontal character scaling of the object "name" to "scale" in percent. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setTextScalingV"><strong>setTextScalingV</strong></a>(...)</dt>
+<dd><code>setTextScalingV(scale, ["name"]))</code>
+<p>Sets the vertical character scaling of the object "name" to "scale" in percent. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setTextColor"><strong>setTextColor</strong></a>(...)</dt>
+<dd><code>setTextColor("color", ["name"])</code>
+<p>Sets the text color of the text frame "name" to the color "color". If there is some text selected only the selected text is changed. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setTextShade"><strong>setTextShade</strong></a>(...)</dt>
+<dd><code>setTextShade(shade, ["name"])</code>
+<p>Sets the shading of the text color of the object "name" to "shade". If there is some text selected only the selected text is changed. "shade" must be an integer value in the range from 0 (lightest) to 100 (full color intensity). If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setTextStroke"><strong>setTextStroke</strong></a>(...)</dt>
+<dd><code>setTextStroke("color", ["name"])</code>
+<p>Set "color" of the text stroke. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-textOverflows"><strong>textOverflows</strong></a>(...)</dt>
+<dd><code>textOverflows(["name", nolinks]) -&gt; integer</code>
+<p>Returns the actual number of overflowing characters in text frame "name". If is nolinks set to non zero value it takes only one frame - it doesn't use text frame linking. Without this parameter it search all linking chain.</p>
+<p>May raise WrongFrameTypeError if the target frame is not an text frame</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-textframes.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-setobjprop.html
===================================================================
--- Scribus/doc/en/scripterapi-setobjprop.html (nonexistent)
+++ Scribus/doc/en/scripterapi-setobjprop.html (revision 13527)
@@ -0,0 +1,111 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Setting Object Properties</title>
+</head>
+<body>
+<h2>Setting Object Properties</h2>
+
+<dl>
+
+<dt><a name="-linkTextFrames"><strong>linkTextFrames</strong></a>(...)</dt>
+<dd><code>linkTextFrames("fromname", "toname")</code>
+<p>Link two text frames. The frame named "fromname" is linked to the frame named "toname". The target frame must be an empty text frame and must not link to or be linked from any other frames already.</p>
+<p>May throw <a href="#ScribusException">ScribusException</a> if linking rules are violated.</p></dd>
+
+<dt><a name="-loadImage"><strong>loadImage</strong></a>(...)</dt>
+<dd><code>loadImage("filename" [, "name"])</code>
+<p>Loads the picture "picture" into the image frame "name". If "name" is not given the currently selected item is used.</p>
+<p>May raise <a href="scripterapi.html#WrongFrameTypeError">WrongFrameTypeError</a> if the target frame is not an image frame</p></dd></dt>
+
+<dt><a name="-setFillBlendmode"><strong>setFillBlendmode</strong>(...)</a></dt>
+<dd><code>setFillBlendmode(blendmode, ["name"])</code>
+<p>Sets the fill blendmode of the object "name" to blendmode is the name of one of the defined colors. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setCornerRadius"><strong>setCornerRadius</strong></a>(...)</dt>
+<dd><code>setCornerRadius(radius, ["name"])</code>
+<p>Sets the corner radius of the object "name". The radius is expressed in points. If "name" is not given the currently selected item is used.</p>
+<p>May raise ValueError if the corner radius is negative.</p></dd>
+
+<dt><a name="-setFillColor"><strong>setFillColor</strong></a>(...)</dt>
+<dd><code>setFillColor("color", ["name"])</code>
+<p>Sets the fill color of the object "name" to the color "color". "color" is the name of one of the defined colors. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setFillShade"><strong>setFillShade</strong></a>(...)</dt>
+<dd><code>setFillShade(shade, ["name"])</code>
+<p>Sets the shading of the fill color of the object "name" to "shade". "shade" must be an integer value in the range from 0 (lightest) to 100 (full Color intensity). If "name" is not given the currently selected Item is used.<p>
+<p>May raise ValueError if the fill shade is out of bounds.</p></dd>
+
+<dt><a name="-setFillTransparency"><strong>setFillTransparency</strong>(...)</a></dt>
+<dd><code>setFillTransparency(transparency, ["name"])</code>
+<p>Sets the fill transparency of the object "name" to transparency is the name of one of the defined colors. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setLineBlendmode"><strong>setLineBlendmode</strong>(...)</a></dt>
+<dd><code>setLineBlendmode(blendmode, ["name"])</code>
+<p>Sets the line blendmode of the object "name" to blendmode is the name of one of the defined colors. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setLineTransparency"><strong>setLineTransparency</strong>(...)</a></dt>
+<dd><code>setLineTransparency(transparency, ["name"])</code>
+<p>Sets the line transparency of the object "name" to transparency is the name of one of the defined colors. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setGradientFill"><strong>setGradientFill</strong></a>(...)</dt>
+<dd><code>setGradientFill(type, "color1", shade1, "color2", shade2, ["name"])</code>
+<p>Sets the gradient fill of the object "name" to type. Color descriptions are the same as for <a href="#-setFillColor">setFillColor</a>() and <a href="#-setFillShade">setFillShade</a>(). See the constants for available types (FILL_&lt;type&gt;).</p></dd>
+
+<dt><a name="-setGradientStop"><strong>setGradientStop</strong></a>(...)</dt>
+<dd><code>setGradientStop("color", shade, opacity, ramppoint, ["name"])</code>
+<p>Set or add a gradient stop to the gradient fill of the object \"name\" at position ramppoint. Color descriptions are the same as for <a href="#-setFillColor">setFillColor</a>() and <a href="#-setFillShade">setFillShade</a>(). setGradientFill() must have been called previously for the gradient fill to be visible.</p></dd>
+
+<dt><a name="-setLineCap"><strong>setLineCap</strong></a>(...)</dt>
+<dd><code>setLineEnd(endtype, ["name"])</code>
+<p>Sets the line cap style of the object "name" to the style "cap". If "name" is not given the currently selected item is used. There are predefined constants for "cap" - CAP_&lt;type&gt;.</p></dd>
+
+<dt><a name="-setLineColor"><strong>setLineColor</strong></a>(...)</dt>
+<dd><code>setLineColor("color", ["name"])</code>
+<p>Sets the line color of the object "name" to the color "color". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-setMultiLine"><strong>setMultiLine</strong></a>(...)</dt>
+<dd><code>setMultiLine("namedStyle", ["name"])</code>
+<p>Sets the line style of the object "name" to the named style "namedStyle". If "name" is not given the currently selected item is used.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the line style doesn't exist.</p></dd>
+
+<dt><a name="-setLineJoin"><strong>setLineJoin</strong></a>(...)</dt>
+<dd><code>setLineJoin(join, ["name"])</code>
+<p>Sets the line join style of the object "name" to the style "join". If "name" is not given the currently selected item is used. There are predefined constants for join - JOIN_&lt;type&gt;.</p></dd>
+
+<dt><a name="-setLineShade"><strong>setLineShade</strong></a>(...)</dt>
+<dd><code>setLineShade(shade, ["name"])</code>
+<p>Sets the shading of the line color of the object "name" to "shade". "shade" must be an integer value in the range from 0 (lightest) to 100 (full color intensity). If "name" is not given the currently selected item is used.</p>
+<p>May raise ValueError if the line shade is out of bounds.</p></dd>
+
+<dt><a name="-setLineStyle"><strong>setLineStyle</strong></a>(...)</dt>
+<dd><code>setLineStyle(style, ["name"])</code>
+<p>Sets the line style of the object "name" to the style "style". If "name" is not given the currently selected item is used. There are predefined constants for "style" - LINE_&lt;style&gt;.</p></dd>
+
+<dt><a name="-setLineWidth"><strong>setLineWidth</strong></a>(...)</dt>
+<dd><code>setLineWidth(width, ["name"])</code>
+<p>Sets line width of the object "name" to "width". "width" must be in the range from 0.0 to 12.0 inclusive, and is measured in points. If "name" is not given the currently selected item is used.</p>
+<p>May raise ValueError if the line width is out of bounds.</p></dd>
+
+<dt><a name="-scaleImage"><strong>scaleImage</strong></a>(...)</dt>
+<dd><code>scaleImage(x, y [, "name"])</code>
+<p>Sets the internal scaling factors of the picture in the image frame "name". If "name" is not given the currently selected item is used. A number of 1 means 100 %. Internal scaling factors are different from the values shown on properties palette. Note : deprecated, use setImageScale() instead.</p>
+<p>May raise <a href="scripterapi.html#WrongFrameTypeError">WrongFrameTypeError</a> if the target frame is not an image frame</p></dd>
+
+<dt><a name="-setImageScale"><strong>setImageScale</strong></a>(...)</dt>
+<dd><code>setImageScale(x, y [, "name"])</code>
+<p>Sets the scaling factors of the picture in the image frame "name". If "name" is not given the currently selected item is used. A number of 1 means 100 %. Scaling factors are equal to the values shown on properties palette.</p>
+<p>May raise <a href="scripterapi.html#WrongFrameTypeError">WrongFrameTypeError</a> if the target frame is not an image frame</p></dd>
+
+<dt><a name="-traceText"><strong>traceText</strong></a>(...)</dt>
+<dd><code>traceText(["name"])</code>
+<p>Convert the text frame "name" to outlines. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-unlinkTextFrames"><strong>unlinkTextFrames</strong></a>(...)</dt>
+<dd><code>unlinkTextFrames("name")</code>
+<p>Remove the specified (named) object from the text frame flow/linkage. If the frame was in the middle of a chain, the previous and next frames will be connected, eg 'a-&gt;b-&gt;c' becomes 'a-&gt;c' when you <a href="#-unlinkTextFrames">unlinkTextFrames</a>(b)'</p>
+<p>May throw <a href="#ScribusException">ScribusException</a> if linking rules are violated.</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-setobjprop.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/mouse.html
===================================================================
--- Scribus/doc/en/mouse.html (nonexistent)
+++ Scribus/doc/en/mouse.html (revision 13527)
@@ -0,0 +1,42 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Mouse Usage Hints </title>
+</head>
+<body>
+<h2>Mouse Usage Hints</h2>
+
+<p>Mouse usage in Scribus has some subtle, but once learned, very useful shortcuts with the mouse.</p>
+<ul>
+<li>Space Bar + Left Click - toggles panning mode for the mouse</li>
+<li>Click third button, or on two button mice ("chord" them by click left and right together), refreshes the view</li>
+<li>Ctrl - select an object beneath the currently selected one</li>
+<li>Shift - dont clear the selection but add to it</li>
+<li>Alt - allow selection of objects within groups</li>
+<li>Hence, Ctrl-Shift-Click is extends the selection with the item below the currently selected one beneath the cursor</li>
+<li>Ctrl-Click cycles through all objects at the position from top to bottom, finally deselecting all and then starting with the top again</li>
+<li>Ctrl-Alt-Click will include group members in the cycle</li>
+<li>Control left click resize/move for lower objects. Release + drag resizes. Hold down Control+Drag moves.</li>
+<li>Left Click &#062;Drag Resizes Frames</li>
+<li>Right Click &#062;Drag Copies or Moves Frames- a context menu will pop up asking your choice</li>
+<li>Ctrl &#062;Wheel - Zooms the view in and out.</li>
+<li>Ctrl &#062;Right Button Drag - Allows you to pan the document up or down and/or left to right depending on the zoom factor.</li>
+</ul>
+
+<h4>Working with the Color Eye Dropper</h4>
+<ul><li>Fill color with click</li>
+<li>Text color with Control click</li>
+<li>Line color with Alt click.</li></ul>
+<h4>In the Properties Palette</h4>
+<ul>
+<li>Ctrl &#043;Wheel - Increases/Decreases units 10 at a time.</li>
+<li>Shift &#043;Wheel - Increases/Decreases units 1/10 at a time.</li>
+<li>Ctrl &#043;Shift &#043;Wheel - Increases/Decreases units 1/100 at a time.</li>
+</ul>
+<p>Alternatively:</p>
+<ul>
+<li>Shift &#043; Arrow Key Increases/Decreases units 10 at a time.</li>
+<li>Crtl &#043; Arrow Key Increases/Decreases units 1/10 at a time.</li>
+</ul>
+</body>
+</html>
/Scribus/doc/en/mouse.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-color.html
===================================================================
--- Scribus/doc/en/scripterapi-color.html (nonexistent)
+++ Scribus/doc/en/scripterapi-color.html (revision 13527)
@@ -0,0 +1,63 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Color related Commands</title>
+</head>
+<body>
+<h2>Color related Commands</h2>
+
+<dl>
+
+<dt><a name="-changeColor"><strong>changeColor</strong></a>(...)</dt>
+<dd><code>changeColor("name", c, m, y, k)</code>
+<p>Changes the color "name" to the specified CMYK value. The color value is defined via four components c = Cyan, m = Magenta, y = Yellow and k = Black. Color components should be in the range from 0 to 255.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the named color wasn't found. May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-defineColor"><strong>defineColor</strong></a>(...)</dt>
+<dd><code>defineColor("name", c, m, y, k)</code>
+<p>Defines a new color "name". The color Value is defined via four components: c = Cyan, m = Magenta, y = Yellow and k = Black. Color components should be in the range from 0 to 255.</p>
+<p>May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-deleteColor"><strong>deleteColor</strong></a>(...)</dt>
+<dd><code>deleteColor("name", "replace")</code>
+<p>Deletes the color "name". Every occurence of that color is replaced by the color "replace". If not specified, "replace" defaults to the color "None" - transparent.</p>
+<p>deleteColor works on the default document colors if there is no document open. In that case, "replace", if specified, has no effect.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if a named color wasn't found. May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-getColor"><strong>getColor</strong></a>(...)</dt>
+<dd><code>getColor("name") -&gt; tuple</code>
+<p>Returns a tuple (C, M, Y, K) containing the four color components of the color "name" from the current document. If no document is open, returns the value of the named color from the default document colors.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the named color wasn't found. May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-getColorAsRGB"><strong>getColorAsRGB</strong>(...)</a></dt>
+<dd><code>getColorAsRGB("name") -&gt; tuple</code>
+<p>Returns a tuple (R,G,B) containing the three color components of the color "name" from the current document, converted to the RGB color space. If no document is open, returns the value of the named color from the default document colors.</p>
+<p>May raise NotFoundError if the named color wasn't found. May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-getColorNames"><strong>getColorNames</strong></a>(...)</dt>
+<dd><code>getColorNames() -&gt; list</code>
+<p>Returns a list containing the names of all defined colors in the document. If no document is open, returns a list of the default document colors.</p></dd>
+
+<dt><a name="-isSpotColor"><strong>isSpotColor</strong></a>(...)</dt>
+<dd><code>isSpotColor("name") -&gt; bool</code>
+<p>Returns True if the color "name" is a spot color.</p>
+<p>See also setSpotColor()</p>
+<p>May raise NotFoundError if a named color wasn't found.</p>
+<p>May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-replaceColor"><strong>replaceColor</strong></a>(...)</dt>
+<dd><code>replaceColor("name", "replace")</code>
+<p>Every occurence of the color "name" is replaced by the color "replace".</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if a named color wasn't found. May raise ValueError if an invalid color name is specified.</p></dd>
+
+<dt><a name="-setSpotColor"><strong>setSpotColor</strong></a>(...)</dt>
+<dd><code>setSpotColor("name", spot)</code>
+<p>Set the color "name" as a spot color if spot parameter is True.</p>
+<p>See also isSpotColor().</p>
+<p>May raise NotFoundError if a named color wasn't found.</p>
+<p>May raise ValueError if an invalid color name is specified.</p></dd>
+
+</dl>
+
+</body>
+</html>
/Scribus/doc/en/scripterapi-color.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/menu.xml
===================================================================
--- Scribus/doc/en/menu.xml (nonexistent)
+++ Scribus/doc/en/menu.xml (revision 13527)
@@ -0,0 +1,142 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<menu>
+ <area text="Welcome" file="index.html">
+ <submenuitem text="Readme First" file="readme.html"/>
+ </area>
+ <area text="Documentation" file="documentation.html">
+ <submenuitem text="Introduction" file="intro.html">
+ <submenuitem text="About the team" file="about1.html"/>
+ <submenuitem text="Specifications" file="specs.html"/>
+ </submenuitem>
+ <submenuitem text="Installation" file="install.html">
+ <submenuitem text="Scribus Source &amp; SVN" file="install1.html"/>
+ <submenuitem text="Requirements" file="install2.html"/>
+ <submenuitem text="Compiling &amp; Installing" file="install3.html"/>
+ <submenuitem text="Compiling using CMake" file="install4.html"/>
+ <submenuitem text="Compiling using CMake on OS X" file="install5.html"/>
+ <submenuitem text="Parallel Install" file="parallel-install.html"/>
+ <submenuitem text="Debian dpkg Information" file="install-dpkg.html"/>
+ </submenuitem>
+ <submenuitem text="Cross Platform" file="cross-platform.html">
+ <submenuitem text="Mac OSX Readme" file="readme-macosx.html"/>
+ <submenuitem text="Mac OSX/Fink" file="machints1.html"/>
+ <submenuitem text="Mac OSX/Fink &amp; SVN" file="machints2.html"/>
+ <submenuitem text="OS/2 Readme" file="readme-os2.html"/>
+ <submenuitem text="Windows Readme" file="readme-win32.html"/>
+ </submenuitem>
+ <submenuitem text="Setup" file="settings1.html">
+ <submenuitem text="Keyboard Shortcuts" file="keys.html"/>
+ <submenuitem text="Mouse Shortcuts" file="mouse.html"/>
+ <submenuitem text="Hyphenation" file="hyphenator.html"/>
+ <submenuitem text="Font Setup" file="fonts1.html"/>
+ <submenuitem text="Fonts in Depth" file="fonts2.html"/>
+ <submenuitem text="GS Fonts" file="gsfont.html"/>
+ <submenuitem text="Non-Latin Fonts" file="fonts3.html"/>
+ <submenuitem text="Basic Font Tests" file="fonts4.html"/>
+ <submenuitem text="Basic Font Tests 2" file="fonts5.html"/>
+ <submenuitem text="Fonts Setup Win32" file="fonts-win32.html"/>
+ </submenuitem>
+ <submenuitem text="Scribus Basics" file="about2.html" >
+ <submenuitem file="docinfo.html" text="Document Information" />
+ <submenuitem text="Master Pages" file="pagetemplate1.html" />
+ <submenuitem text="Page Numbering" file="pagenumber.html" />
+ <submenuitem text="Short Words Plug-in" file="short-words.html" />
+ <submenuitem text="Editing Colors" file="color1.html" />
+ <submenuitem text="Layers" file="layers.html" />
+ </submenuitem>
+ <submenuitem text="Importing" file="importhints.html">
+ <submenuitem text="Importing EPS" file="importhints1.html"/>
+ <submenuitem text="Importing (Advanced)" file="importhints2.html"/>
+ <submenuitem file="importhints3.html" text="OpenOffice.org Docs" />
+ <submenuitem file="importhints4.html" text="HTML Importing" />
+ <submenuitem file="scribus-svg.html" text="Importing SVGs" />
+ <submenuitem file="psd.html" text="Importing PSD" />
+ </submenuitem>
+ <submenuitem text="Exporting to PDF" file="pdfexport1.html">
+ <submenuitem text="Export Workflow" file="pdfexport2.html"/>
+ <submenuitem text="PDF Flavors" file="pdflavor.html"/>
+ <submenuitem text="PDF/X-3" file="pdfx3.html"/>
+ <submenuitem text="PDF Forms" file="pdfexport3.html"/>
+ <submenuitem text="PDF and JavaScript" file="javascriptpdf.html"/>
+ <submenuitem text="PDF Forms and PHP" file="pdf_form.html"/>
+ <submenuitem text="PDF Presentations" file="pdfexport4.html"/>
+ </submenuitem>
+ <submenuitem text="Printing" file="print1.html">
+ <submenuitem text="Print Preview" file="print2.html"/>
+ <submenuitem text="CUPS" file="cups.html"/>
+ <submenuitem text="Preparing for Press" file="print3.html"/>
+ <submenuitem text="Pre-Press" file="prepress.html"/>
+ </submenuitem>
+ <submenuitem text="Color Management" file="cms.html">
+ <submenuitem text="Part 2 " file="cms2.html"/>
+ <submenuitem text="Part 3 " file="cms3.html"/>
+ <submenuitem text="Part 4 " file="cms4.html"/>
+ <submenuitem text="Monitor Profiling" file="moncal.html"/>
+ </submenuitem>
+ <submenuitem text="DTP ToolBox" file="toolbox.html">
+ <submenuitem text="Adobe Reader" file="toolbox1.html"/>
+ <submenuitem text="Other PDF Viewers" file="toolbox2.html"/>
+ <submenuitem text="Batik" file="toolbox3.html"/>
+ <submenuitem text="Gimp" file="toolbox4.html"/>
+ <submenuitem text="Ghostscript" file="toolbox5.html"/>
+ <submenuitem text="GSview" file="toolbox6.html"/>
+ <submenuitem text="Advanced Ghostscript &amp; GSView" file="toolbox7.html"/>
+ <submenuitem text="Imagemagick" file="toolbox8.html"/>
+ <submenuitem text="Inkscape" file="toolbox9.html"/>
+ <submenuitem text="KSnapshot" file="toolbox10.html"/>
+ <submenuitem text="Tracing Tools" file="toolbox11.html"/>
+ <submenuitem text="WINE" file="toolbox12.html"/>
+ <submenuitem text="Xnview" file="toolbox13.html"/>
+ <submenuitem text="Lprof" file="toolbox14.html"/>
+ <submenuitem text="Krita" file="toolbox15.html"/>
+ <submenuitem text="Fontmatrix" file="toolbox16.html"/>
+ </submenuitem>
+ <submenuitem text="Hints &amp; FAQs" file="topten.html">
+ <submenuitem text="Help" file="faq1.html"/>
+ <submenuitem text="Miscellaneous" file="faq2.html"/>
+ <submenuitem text="Development" file="faq3.html"/>
+ </submenuitem>
+ </area>
+ <area text="Tutorials" file="tutorials.html" section="tutorials">
+ </area>
+ <area text="For Developers" file="developers.html">
+ <submenuitem text="Scribus Document Format" file="scribusfileformat.html"/>
+ <submenuitem text="Scripter" file="scripter1.html"/>
+ <submenuitem text="Scripter FAQ" file="scripter-faq.html"/>
+ <submenuitem text="Scripter API" file="scripterapi.html">
+ <submenuitem text="Document Commands" file="scripterapi-doc.html"/>
+ <submenuitem text="Page Commands" file="scripterapi-page.html"/>
+ <submenuitem text="Creating &amp; Destroying Objects" file="scripterapi-object.html"/>
+ <submenuitem text="Selecting Objects" file="scripterapi-select.html"/>
+ <submenuitem text="Setting Object Properties" file="scripterapi-setobjprop.html"/>
+ <submenuitem text="Getting Object Properties" file="scripterapi-getobjprop.html"/>
+ <submenuitem text="Manipulating Objects" file="scripterapi-manobj.html"/>
+ <submenuitem text="Handling Text Frames" file="scripterapi-textframes.html"/>
+ <submenuitem text="Color Commands" file="scripterapi-color.html"/>
+ <submenuitem text="Font Commands" file="scripterapi-font.html"/>
+ <submenuitem text="Layer Commands" file="scripterapi-layer.html"/>
+ <submenuitem text="Using Dialogs" file="scripterapi-dialogs.html"/>
+ <submenuitem text="PDF Export" file="scripterapi-PDFfile.html"/>
+ <submenuitem text="Printing" file="scripterapi-Printer.html"/>
+ <submenuitem text="Image Export" file="scripterapi-ImageExport.html"/>
+ <submenuitem text="Predefined Constants" file="scripterapi-constants.html"/>
+ <submenuitem text="Scripter Extensions" file="scripter-extensions.html"/>
+ <submenuitem text="Scripter Extensions API" file="scripterapi-extensions.html"/>
+ </submenuitem>
+ <submenuitem text="Plugin Howto" file="plugin_howto.html"/>
+ <submenuitem text="GetText Howto" file="gettexthowto.html"/>
+ <submenuitem text="Coding Standards" file="codingstandards.html"/>
+ <submenuitem text="Translation Howto" file="translation_howto.html"/>
+ <submenuitem text="Lipsum Howto" file="lipsum.html"/>
+ </area>
+ <area text="Other Information" file="otherinfo.html">
+ <submenuitem text="Community" file="resources.html"/>
+ <submenuitem text="Mailing Lists" file="mailing_lists.html"/>
+ <submenuitem file="irc.html" text="IRC"/>
+ <submenuitem text="Printers" file="scprinters.html"/>
+ <submenuitem text="Download" file="download.html"/>
+ <submenuitem text="Contributions" file="contributions.html"/>
+ <submenuitem text="Scribus Copyright" file="scribuscopyright.html"/>
+ <submenuitem text="Documentation Copyright" file="doccopyright.html"/>
+ </area>
+</menu>
/Scribus/doc/en/menu.xml
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/about1.html
===================================================================
--- Scribus/doc/en/about1.html (nonexistent)
+++ Scribus/doc/en/about1.html (revision 13527)
@@ -0,0 +1,68 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>About the Scribus Team</title>
+</head>
+<body>
+<h2>About the Scribus Team (in order of joining)</h2>
+
+<p>Franz Schmid - "Our Linus..." original author, main coder, software developer for a publishing company</p>
+
+<p>Peter Linnell - aka mrdocs - started with testing the 0.3.6 version, took over the documentation writing for 0.5.0; tester, rpm builder, original web master for <a href="http://www.scribus.net/">www.scribus.net,</a> Pre-Press/IT consultant for publishing and e-commerce companies.</p>
+
+<p>Craig Bradney - aka MrB - started with 1.1.1, testing, setup of docs.scribus.net and bugs.scribus.net, manages the IRC channel #scribus on freenode.net; IT Manager for global e-commerce company.
+
+<p>Petr Van&#283;k - started with 1.1.4, plug-in specialist, has written several Scribus plug-ins and the how-to for Scribus plug-in writing; software engineer.</p>
+
+<p>Riku Leino - aka Tsoots - started with 1.1.5, wrote the Document Template plug-in and the OO/HTML importers for 1.2.2; IT Manager for large non-profit in Finland.</p>
+
+<p>Craig Ringer - Worked on the scripter, build system and tested Windows and Mac OSX port beginnings. Contributed fixes for Python and other enhancements; IT/DTP administrator for daily newspaper. </p>
+
+<p>Andreas Vox - pronounced [fox] -- started with 1.3.0. Developed original Mac OS X native port, font API specialist, hates C++, likes good layout and has a stupid comment for anything: software developer.</p>
+
+<p>Jean Ghali - handles the Windows native port and much of the color management coding. Pre-press and software engineer for printing company.</p>
+
+<p>Oleksandr Moskalenko, Phd.- aka malex - maintainer of Scribus Debian packages, helps with internationalization, translation, and user support in #scribus on IRC, tool scripts and the new Drupal-based www.scribus.net site, GSoC representative; molecular biologist.</p>
+
+<p>Pierre Marchand - fonts, canvas, text layout and shaping. Developer of FontMatrix, has own IT company. </p>
+
+<p>Christoph Schäfer - Leading bug reporter and tester for bleeding edge Scribus. Wiki editor and doc translator/proofreader. </p>
+
+<p>Hermann Kraus - Wrote the Render frame system and GraphicsMagick and UniConvertor integration.</p>
+
+<h2>The Supporting Cast and Former Developers</h2>
+<h4>Active users/contributors who have added to the Scribus community (in no particular order):</h4>
+
+<p>Paul F. Johnson - aka Nodoid - started with sending patches for 0.8, did code review and code optimizing. </p>
+
+<p>Steve Callcott - aka sjc - wrote the Python plugin font sampler, which showed the real power of the Python Scripter in Scribus; works on systems control and consumer electronics, custom software and support.</p>
+
+<p>Alessandro Rimoldi - added fixes for localization and code clean-ups.</p>
+
+<p>J.J. Sarton - added some key patches for improving image handling and other improvements. Added the GIMP support to Scribus.</p>
+
+<p>Alistair Robinson - added some important fixes for font handling in early Scribus versions. Also wrote the clever hack for GIMP to create CMYK TIFFs.</p>
+
+<p>Maciej Hanski - Polish translator and writer of the PDF Forms how-to. One of the primary contributors to the scribus wiki.</p>
+
+<p>Yves Ceccone - Original French translator, wrote many of the Python scripts included with Scribus, maintained a large number of Docs for Scribus in French.</p>
+
+<p>Martin Costabel - maintains the Scribus port and support libraries for Fink, allowing Scribus to run under X11 on MacOSX.</p>
+
+<p>Niyam Bhushan - contributed a terrific tutorial on Scribus.</p>
+
+<p>Marti Maria - for answering tons of our questions on color managemetn and providing littlecms.</p>
+
+<p>Johannes R&#252;schel - Excellent bug finder, German translator; German Civil Service</p>
+
+<p>Alexandre Prokoudine - Russian Translator, has helped a bunch with internationalization issues, as well as designing UI improvements; professional technical writer.</p>
+
+<p>"Lukasz [DeeJay1] Jernas" - PLD Linux package maintainer and user support in #scribus </p>
+
+<p>Howard White - Retired Pre-Press Engineer - Testing and testing and more testing. Always daring to test bleeding edge code. </p>
+
+<p>Cedric Gemy - Graphics Professor and author - UI testing and feedback, GSoC mentor.</p>
+
+<p>Dr. Greg Pittman - One of the primary contributors to the scribus wiki and future documentation.</p>
+</body>
+</html>
/Scribus/doc/en/about1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/docinfo.html
===================================================================
--- Scribus/doc/en/docinfo.html (nonexistent)
+++ Scribus/doc/en/docinfo.html (revision 13527)
@@ -0,0 +1,64 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Document Information</title>
+</head>
+<body>
+<h2>Scribus Document Information</h2>
+<h3>Overview</h3>
+<p align="justify">There are a couple of important points to consider in the doc info fields: 1) Scribus supports an initiative called the <a href="http://dublincore.org/">Dublin Core Initiative</a>. Dublin Core, for short, is a set of specification on document meta-data. 2) The other feature is the fields on the first tab are used in PDF export, as well as also being part of Dublin Core meta-data. This data can be used by special indexing servers which can index PDF files, as well as Acrobat Reader. The second tab contains meta-data in Dublin Core form which can also be used for using a database to track Scribus files.</p>
+<table width="100%"><tr><td align="center"><img src="images/docinfo.png" alt="PDF Doc Info" title="PDF Doc Info" /></td></tr></table>
+<p>The second tab is document info which is strictly Dublin Core, thus defined by the specifications:</p>
+
+<table width="100%"><tr><td align="center"><img src="images/docinfo2.png" alt="Dublin Core Properties" border="0" title="Dublin Core Properties in Document" /></td></tr></table>
+
+<table width="550" border="0" align="center">
+ <tbody>
+ <tr>
+ <td align="left" >Publisher</td>
+ <td align="justify" > The person or organization responsible for making the document available or for putting into print.</td>
+ </tr>
+ <tr>
+ <td align="left">Contributors</td>
+ <td align="justify"> A person or organization responsible for making contributions to the content of the document.</td>
+ </tr>
+ <tr>
+ <td align="left">Date</td>
+ <td align="justify"> A date associated with an event in the life cycle of the document, in YYYY-MM-DD format, as per ISO 8601.</td>
+ </tr>
+ <tr>
+ <td align="left">Type</td>
+ <td align="justify"> The nature or genre of the content of the document, eg. categories, functions, etc.</td>
+ </tr>
+ <tr>
+ <td align="left">Format</td>
+ <td align="justify"> The physical or digital manifestation of the document. Media type and dimensions would be worth noting. RFC2045,RFC2046 for MIME types are also useful here.</td>
+ </tr>
+ <tr>
+ <td align="left">Identifier</td>
+ <td align="justify"> An unambiguous reference to the document within a given context such as ISBN or URI.</td>
+ </tr>
+ <tr>
+ <td align="left">Source</td>
+ <td align="justify"> A reference to a document from which the present document is derived, eg. ISDN or URI.</td>
+ </tr>
+ <tr>
+ <td align="left">Language</td>
+ <td align="justify"> The language in which the content of the document is written, usually a ISO-639 language code. Optionally suffixed with a hyphen and an ISO-3166 country code, eg. en-GB, fr-CH.</td>
+ </tr>
+ <tr>
+ <td align="left">Relation</td>
+ <td align="justify"> A reference to a related document, possibly using a formal identifier such as a ISBN or URI.</td>
+ </tr>
+ <tr>
+ <td align="left">Coverage</td>
+ <td align="justify"> The extent or scope of the content of the document, possibly including location, time and jurisdiction ranges.</td>
+ </tr>
+ <tr>
+ <td align="left">Rights</td>
+ <td align="justify"> Information about rights held in and over the document, eg. copyright, patent or trademark.</td>
+ </tr>
+ </tbody>
+</table>
+</body>
+</html>
/Scribus/doc/en/docinfo.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/pagenumber.html
===================================================================
--- Scribus/doc/en/pagenumber.html (nonexistent)
+++ Scribus/doc/en/pagenumber.html (revision 13527)
@@ -0,0 +1,25 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Automatic Page Numbers</title>
+</head>
+<body>
+<h2>Automatic Page Numbering</h2>
+
+<p>Adding automatically incrementing page numbers is a two step process, but, once mastered, quite simple and reliable. There are two different methods which can be used independently or together. The first is to draw a text frame, click to get into edit mode and then go: <strong>Insert > Character > Insert Page Number</strong>. This will only add the page number to the currently selected page. The second uses Master Pages to enable automatic page numbering.</p>
+
+<p>Scribus uses a special place holder within <a href="pagetemplate1.html">Master Pages</a> to indicate page numbers and allows them to be automatically included in your document without concern for moving, importing or deleting pages. </p>
+
+<h4>Step One</h4>
+
+<p>With your chosen document open, go <strong>Edit > Master Pages</strong>. If you have not created any other Master Pages, then there will be just one named "Normal." </p>
+<h4>Step Two</h4>
+<p>Next, create a text frame where you want the page numbers to go. Then, enter the edit mode by double clicking on the text frame and insert a page number as described above. In Scribus versions before 1.3.4, you need to create different master pages for one, two or three digit page numbers, whereas from 1.3.4 on, a single placeholder will suffice. Then save the Master Page by closing the Master Pages dialog and return to the main document.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/pagenumbering.png" title="Inserting Page Number placeholders." alt="Inserting Page Number placeholders" /></td></tr></table>
+
+<p>If you have more than one Master Page, you will need to add these placeholders to each Master Page that is expected to show a page number.</p>
+
+<p>You can also apply styles and direct text formatting as you wish, just like a normal text frame. </p>
+</body>
+</html>
/Scribus/doc/en/pagenumber.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install3.html
===================================================================
--- Scribus/doc/en/install3.html (nonexistent)
+++ Scribus/doc/en/install3.html (revision 13527)
@@ -0,0 +1,59 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Compiling and Installing using autotools</title>
+</head>
+<body>
+<h2>Compiling and Installing using autotools</h2>
+<p><b>These instructions apply to Scribus 1.3.3.x SVN and below</b></p>
+<p>If you have downloaded source from SVN, you will need to start the intial build process:</p>
+
+<pre>
+cd Scribus
+make -f Makefile.svn
+</pre>
+
+<p>In order to compile and install Scribus on your system, type the following
+in the base directory of the Scribus distribution after uncompressing the
+downloaded package:</p>
+
+<pre>
+./configure
+make
+make install
+</pre>
+
+<p>The <code>make install</code> command will have to be done with root access if you have not run the <code>./configure</code> command with a <code>--prefix=[dir]</code> option to specify a different install directory. The following is an example of how to configure and install into your home directory. (For more informaiton than the following line, look at the <a href="/index.php&#063;lang=en&#038;page=parallel-install">Parallel Install</a> section for more on having more than one version of Scribus installed at once)</p>
+
+<pre>
+./configure --prefix=/usr;make;make install prefix=~/scribus/svn
+</pre>
+
+
+<p>If you receive warnings when running <code>./configure</code>, you will need to verify the versions of <code>autoconf</code> and <code>automake</code> by running:</p>
+
+<pre>
+autoconf --version
+automake --version
+</pre>
+
+<p>If they are not at least of the versions mentioned in the <a href=install2.html">Requirements</a> section, you may, depending on your distribution, need to tell it to use a higher version like following:</p>
+
+<pre>
+export WANT_AUTOCONF=&#034;2.5&#034;
+export WANT_AUTOMAKE=&#034;1.7&#034;
+
+</pre>
+
+<p>Having run those two commands, recheck the versions. If they still do not comply to those required, you will need to upgrade those programs, however most distributions contain a high enough version.</p>
+
+<p>Since Scribus uses <code>autoconf</code>, as long as you have the correct developement versions of the libraries, you should have little difficulty compiling it. Should you run into problems please report them to the Scribus mailing list or IRC channel. See <a href="/index.php&#063;lang=en&#038;page=resources">Community Resources</a> section of this manual.</p>
+
+<p>Lastly:</p>
+
+<pre>man scribus</pre>
+
+<p> will list additional info for startup.</p>
+
+</body>
+</html>
/Scribus/doc/en/install3.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox4.html
===================================================================
--- Scribus/doc/en/toolbox4.html (nonexistent)
+++ Scribus/doc/en/toolbox4.html (revision 13527)
@@ -0,0 +1,31 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>GIMP 2.x</title>
+</head>
+<body>
+<h2>GIMP 2.x</h2>
+
+<p>There is not much to say about the best image application for Linux. GIMP 2.x has too many improvements to list. </p>
+
+<p>However, setting up GIMP for print work with Scribus requires some adjustments to the defaults as shown below: </p>
+
+<ul>
+<li>Make sure you have the latest 2.4.x stable version. </li>
+<li>GIMP now can work with CMYK colors. While the color model internally is still RGB plus alpha channels, you can use CMYK measurements and CMYK color definitions. To supplement this, there is a third party plug-in called <a href="http://cue.yellowmagic.info/softwares/separate.html">separate+</a>, which can export CMYK TIFF, using a neat trick with alpha layers. The separate+ plug-in can also embed ICC profiles into the exported TIFF and create duotone TIFF.</li>
+<li>One of the really appreciated improvements is the text handling. GIMP 2.x uses <code>fontconfig</code>, so finding the fonts on your system is much less of an issue. Text can be kept in a separate layer to ease editing and correcting. In the 1.2.x versions certain type of handling were difficult, but there is little to complain about now. It is a pleasure to use the new text controls. In addition, there is also a separate freetype plug-in for GIMP, which allows you to manipulate type in the same means Scribus and Inkscape do. Recommended. You can find this on the ftp.gimp.org site.</li>
+<li>Most recent version of GIMP can export all paths as clipping paths in TIFF files and have much better support for clip paths in TIFF import as well. </li>
+<li>The way that pixels are adjusted (interpolated) in filters and effects are applied use Linear as the default. This is a good compromise for speed vs. accuracy. <b>Lanczos should almost always be the default for print work</b>, but do expect many operations, (re-scaling, filter application) to run slower. Using Lanczos can make sometimes a dramatic difference in the perceived print quality of an image, so make sure GIMP is using it by default.</li>
+</ul>
+
+<table width="100%"><tr><td align="center"><img src="images/gimpoptions1.png" alt="Lanczos Interpolation" /></td></tr></table>
+
+<p>Like most image editors, GIMP's defaults are setup primarily for web site images, meaning waaaay too little resolution for print. So first thing, set the defaults to a <strong>minimum</strong> of 144 DPI in resolution. Remember using these higher resolutions will result in much larger size files, so you might also need to adjust maximum settings for memory usage as well in GIMP preferences. </p>
+
+<table width="100%"><tr><td align="center"><img src="images/gimpoptions3.png" alt="DPI Defaults" /></td></tr></table>
+
+<p>The other notable addition is the beginnings of some very basic color managed "soft proofs" of your images. This is available via LittleCMS also used by Scribus. You can set this in the preferences. Where this will help you is to see how it will look when transformed into a CMYK color space when printed or exported as PDF. </p>
+
+<table width="100%"><tr><td align="center"><img src="images/gimpoptions2.png" alt="Color Management Settings" /></td></tr></table>
+</body>
+</html>
/Scribus/doc/en/toolbox4.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/gsfont.html
===================================================================
--- Scribus/doc/en/gsfont.html (nonexistent)
+++ Scribus/doc/en/gsfont.html (revision 13527)
@@ -0,0 +1,95 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+</head>
+<body>
+<h2>Ghostscript Font Hints for Linux, Unix and MacOSX.</h2>
+<br/>
+<em>These notes thanks to Craig Ringer and Russell Lang, maintainer of GSview.</em>
+
+<p>One of the most common causes of Ghostscript failure to render/import/convert a file is when Ghostscript can't find the fonts it needs to either display an EPS or PS. This not a weakness or flaw in Ghostscript, as <strong>all</strong> EPS/PS interpreters need to be able access the correct fonts listed within the PostScript. This can most definitely affect EPS/PS files you are trying to import into Scribus. Some applications do not properly embed the fonts, so they must be supplied externally. </p>
+
+<p>When Ghostcript can't find a font usually an error message from the console will be something like:</p>
+
+<pre>
+ gs -h
+ AFPL Ghostscript 8.50 (2004-12-10)
+ Copyright (C) 2004 artofcode LLC, Benicia, CA. All rights reserved.
+blah blah bah...
+
+invalidfont
+Current allocation mode is local
+Last OS error: No such file or directory
+and so on...
+</pre>
+
+<p>The <strong>invalidfont</strong> error means a: Ghostscript can't find the font or fonts. b: Ghostscript can't find <strong>any</strong> fonts c: There is a broken or malformed font on your system.</p>
+
+<p>The fix:</p>
+
+<h4>Creating a Fontmap File </h4>
+
+There's a secret gem in the GS source distribution, <pre>$GS_SRC_DIR/toolbin/genfontmap.ps</pre> This can be used to generate a Fontmap file - the same files you see frightening perl scripts for on the 'net. This file may or may not be shipped by your distro, so for this example, we are mentioning the un-tarred source directory for building a parallel GS install.
+
+You should use the <em>genfontmap.ps</em> from the version of Ghostscript you are using. Others may not work correctly. This is another good reason to get a recent version of Ghostscript.
+
+<pre>
+
+ $ gs -q -sFONTPATH=/usr/local/share/fonts/TrueType ${HOME}/build/ghostscript-8.31/toolbin/genfontmap.ps
+
+ % This Fontmap generated by genfontmap.ps
+
+ (AndaleMono) (/usr/local/share/fonts/TrueType/AndaleMo.TTF) ;
+ (Arial-Black) (/usr/local/share/fonts/TrueType/AriBlk.TTF) ;
+ (Arial-BoldItalicMT) (/usr/local/share/fonts/TrueType/Arialbi.TTF) ;
+ (Arial-BoldMT) (/usr/local/share/fonts/TrueType/Arialbd.TTF) ;
+ ... blah blah blah ...
+ (Utopia-Regular) (putr.pfa) ;
+ (Verdana) (/usr/local/share/fonts/TrueType/Verdana.TTF) ;
+ (Verdana-Bold) (/usr/local/share/fonts/TrueType/Verdanab.TTF) ;
+ (Verdana-BoldItalic) (/usr/local/share/fonts/TrueType/Verdanaz.TTF) ;
+ (Verdana-Italic) (/usr/local/share/fonts/TrueType/Verdanai.TTF) ;
+ (Webdings) (/usr/local/share/fonts/TrueType/Webdings.TTF) ;
+ (ZapfChancery-MediumItalic) /URWChanceryL-MediItal ;
+ (ZapfDingbats) /Dingbats ;
+
+ genfontmap completed OK. 42 new fonts added.
+
+</pre>
+
+<p>So you redirect stdout or copy paste everything from the <code>% This Fontmap..</code> line to a text editor to save the Fontmap, copy the generated FontMap into the font directory, then add the directory to your GS_LIB env var:</p>
+
+<p>The exact path may vary.</p>
+
+<pre>
+ $ gs -q -sFONTPATH=/usr/local/share/fonts/TrueType ${HOME}/build/ghostscript-8.50/toolbin/genfontmap.ps > /tmp/Fontmap
+ $ sudo cp /tmp/Fontmap /usr/local/share/fonts/Truetype
+ $ export GS_LIB=/usr/local/share/fonts/TrueType:$GS_LIB
+
+</pre>
+
+<p>Then you can launch Scribus from the same console and GS will find them and will import EPS/PS files without issues.</p>
+
+<p>Alternately, you can edit your GS lib/Fontmap to source the new fontmap or append the new fontmap entries to your main lib/Fontmap.</p>
+
+<h4>Adding User Added TrueType Fonts</h4>
+
+<p>Despite the very best efforts of the Ghostscript documentation to make it appear otherwise, TrueType fonts are well supported in Ghostscript and quite easy to use with it.</p>
+
+<p>Most importantly, the GS_FONTPATH environment var and the -sFONTPATH argument may specify directories containing any supported type of font - not just PostScript fonts as described in the documentation.</p>
+
+<pre>$ export GS_FONTPATH=$MY_FONT_DIR:$HOME/.fonts
+$ scribus</pre>
+
+<h4>Ghostscript Fonts and EPS Import</h4>
+
+<p>EPS import in Scribus is affected by the Ghostscript font path. If GS can't find the fonts, they'll be silently substituted. You really, really want GS to be able to find your fonts.</p>
+
+<p>You are recommend to create Fontmap files for your font directories then add them to the GS_LIB env var, as this will cause GS to load fonts quickly in future.
+
+Testing confirms that once GS has been told where to find the fonts, the EPS import in Scribus happily pulls in local fonts where there is a suitable one to use for a font requested by the EPS, but not embedded.</p>
+
+<p>Note in all of the above, the creation and updating of Fontmap.gs is usually handled automagically, by using Kfontinstaller, as noted here: <a href="fonts2.html" name="Font Installation with KDE">Font Installation with KDE</a></p>
+
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/gsfont.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox12.html
===================================================================
--- Scribus/doc/en/toolbox12.html (nonexistent)
+++ Scribus/doc/en/toolbox12.html (revision 13527)
@@ -0,0 +1,39 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>A little WINE with Scribus</title>
+</head>
+<body>
+<h2>A little WINE with Scribus</h2>
+<h3>Overview</h3>
+<p>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.</p>
+<p>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.</p>
+<p>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:</p>
+<ol><li>Until the recent enhancements to Gnucash, I needed a Windows accounting application to run the books for my own company. </li>
+<li>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. </li>
+<li>I have run VMware in the past and it is superb, but is too resource intensive at times. </li>
+<li>Sadly, many kinds of multimedia on the net needs a Windows based media application. </li></ol>
+<h3>Hints and my experience</h3>
+<p>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:</p>
+<code>./configure &amp;&amp; make &amp;&amp; make install</code>
+<p>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.</p>
+<p>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.</p>
+<p>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.</p>
+<p>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.</p>
+<p>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.</p>
+<p>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 ;))</p>
+<p>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.</p>
+<h2>The Alternatives </h2>
+<h3>Crossover Office from <a href="http://www.codeweavers.com">Codeweavers</a></h3>
+<p>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. <a href="http://www.codeweavers.com">Codeweavers</a> 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.</p>
+<h3>Win4Lin from <a href="http://win4lin.net/content/">Netraverse</a></h3>
+<p><em>Disclaimer: <a href="http://win4lin.net/content/">Netraverse</a> has provided the Scribus Team with in-kind sponsorship.</em> </p>
+<p>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. </p>
+
+<p>I would not discourage anyone from buying either. Both companies have been good citizens in the open source community.</p>
+
+<h3>Success</h3>
+<table width="100%"><tr><td align="center"><img src="images/acroreader5.1.png" alt="Acrobat Reader 5.1 under WINE" /></td></tr></table>
+<p>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.</p>
+</body>
+</html>
/Scribus/doc/en/toolbox12.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install5.html
===================================================================
--- Scribus/doc/en/install5.html (nonexistent)
+++ Scribus/doc/en/install5.html (revision 13527)
@@ -0,0 +1,79 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
+ <title>Compiling and Installing Scribus 1.3.5svn+ On Mac OS X</title>
+</head>
+
+<body>
+ <h2>Compiling and Installing Scribus 1.3.5svn+ On Mac OS X</h2>
+
+ <p>This document outlines the build process for Scribus 1.3.5 or higher from SVN on Mac OS X. This does not currently outline the processs for packaging and bundling Scribus (yet).</p>
+
+ <h3>What you need:</h3>
+
+ <ul>
+ <li>MacPorts installer (renamed from darwinports in version since 1.5)</li>
+
+ <li>Qt 4.3.x from Trolltech</li>
+
+ <li>XCode from Apple, either from the OS X install DVD or downloaded from http://www.apple.com</li>
+
+ <li>Scribus SVN</li>
+ </ul>
+
+ <h3>Building and Installing</h3>
+
+ <p>Steps to build and install Scribus 1.3.5 on OSX/Aqua</p>
+
+ <ul>
+ <li>Install X11 (available on the OSX CDs or from the Apple site)</li>
+
+ <li>Install <a href="http://developer.apple.com/tools/xcode/">XCode</a> (available on the OSX CDs or from the Apple developer site)</li>
+
+ <li>Install MacPorts (downloadable from <a href="http://www.macports.org">www.macports.org</a>)</li>
+
+ <li>Install Qt4 4.3.0+ for OSX (downloadable from <a href="http://www.trolltech.com">www.trolltech.com</a>)</li>
+ </ul>
+
+ <p>Install a few ports from MacPorts. Any other required dependencies will be installed automatically if they are not already. If you have already installed macports for other software, then you should run <code>sudo port selfupdate</code> and <code>sudo port upgrade installed</code> in order that the newest versions of your current ports and libaries are installed.</p>
+
+ <ul>
+ <li>Install CMake (<code>sudo port install cmake</code> ) </li>
+
+ <li>Install freetype2 (<code>sudo port install freetype</code>) The one included with OSX 10.4.9 is not as good as available from darwinports.</li>
+
+ <li>Install lcms (<code>sudo port install lcms</code>). This will also install jpeg, zlib, tiff</li>
+
+ <li>Install cairo (<code>sudo port install cairo</code>). This will install fontconfig too.</li>
+
+ <li>Install libxml2 (<code>sudo port install libxml2</code>).</li>
+
+ <li>Install subversion (<code>sudo port install subversion</code>) OR optionally install subversion from another source.</li>
+
+ <li>Optionally (recommended)<code>sudo port install ghostscript</code></li>
+
+ <li>Make a directory where you want to download to (eg, in Terminal, <code>mkdir -p ~/scribus/135</code>)</li>
+
+ <li>Change to this directory (<code>cd ~/scribus/135</code>)</li>
+ </ul>
+
+ <p>Check out Scribus from SVN</p>
+
+ <ul>
+ <li><code>svn co svn://scribus.info/Scribus/trunk/</code></li>
+
+ <li>Make a build directory <code>mkdir builddir</code></li>
+
+ <li>Change to the build directory (<code>cd builddir</code>)</li>
+
+ <li>Run the cmake command: <code>cmake -DBUILD_OSX_BUNDLE=1 -DWANT_CAIRO=1 -DCMAKE_INSTALL_PREFIX:PATH=/Users/username/Applications/Scribus.App/Contents/ ../trunk/Scribus/</code></li>
+
+ <li><code>make</code></li>
+
+ <li><code>make install</code></li>
+ </ul>
+
+ <p>Now you can run Scribus 1.3.5+ from OSX if all has gone well.</p>
+</body>
+</html>
Index: Scribus/doc/en/mailing_lists.html
===================================================================
--- Scribus/doc/en/mailing_lists.html (nonexistent)
+++ Scribus/doc/en/mailing_lists.html (revision 13527)
@@ -0,0 +1,284 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Mailing Lists</title>
+</head>
+<body>
+<h2>Mailing List Policy and Disclaimers</h2>
+<h3>Introduction</h3>
+<p>
+Scribus is developed by a team whose members are located on every continent
+and often are geographically quite far from each other. Larger Scribus
+Community is even more diverse and geographically distributed. Therefore, IRC
+and e-mail are the preferred ways to discuss Scribus use and development. The
+email communications for the Scribus Developers and the Community are
+supported by Scribus Mailing Lists.
+</p>
+<p>
+Our lists are public, meaning anyone can read everything that is posted, and
+participate in the discussions. Everyone is encouraged to help development of
+Scribus and to spread the word of free software. "scribus" list is intended
+for Scribus usage and general Desktop Publishing discussion, requests for
+help, and announcements. "scribus-dev" list is intended for
+development-related discussion between Scribus Team and interested members of
+the Scribus Community.
+</p>
+<p>
+All Scribus mailing lists are run on using an automatic mail processing
+software called <a href="http://www.list.org">Mailman</a>. All submission,
+subscription and unsubscription messages have to be sent to a particular
+address at this host.
+</p>
+
+<h3>Basic use</h3>
+
+<p>
+Each Scribus mailing list (listname) has a submission address in the form
+listname@lists.scribus.info, a control request address in the form
+listname-request@lists.scribus.info, and a web page at
+<a href="http://lists.scribus.info/mailman/listinfo/">http://lists.scribus.info/mailman/listinfo/</a>.
+</p>
+<p>
+To send an email to a list, simply send it to the submission address
+listname@lists.scribus.info. To subscribe to a list to be able to read
+incoming mails as they arrive, or to unsubscribe from a list, use the control
+request address (see below).
+</p>
+<p>
+The current list of available mailing lists is at <a href="http://lists.scribus.info">http://lists.scribus.info</a>
+presented as an alphabetical list.
+</p>
+
+<h3>Disclaimer / Privacy policy / Legal information</h3>
+
+<p>
+The mailing lists are public forums.
+</p>
+<p>
+All emails sent to the lists are distributed both to the list subscribers and
+copied to the public archive, for people to browse or search without the need
+to be subscribed.
+</p>
+<p>
+Furthermore, you can browse our mailing lists as Usenet newsgroups. It can be
+done using a web interface, like Google or Gmane.
+</p>
+<p>
+There may be other places where lists are distributed — please make sure you
+never send any confidential or unlicensed material to the lists. This includes
+things like e-mail addresses. Of particular note is the fact that spammers,
+viruses, worms etc have been known to abuse e-mail addresses posted to open
+mailing lists.
+</p>
+<p>
+Scribus Team maintains the mailing lists in good faith and will take steps to
+curb all noticed abuse and maintain uninterrupted normal service. At the same
+time, Scribus Team is not responsible for all mailing list posts or anything
+that may happen in relation to them.
+</p>
+<p>
+Please see our disclaimer of responsibility below for more information.
+</p>
+
+<h3>Subscription / Unsubscription</h3>
+
+<p>
+Anyone is able to subscribe/unsubscribe on their own to any mailing list,
+presuming the subscription policy for a particular list is open.
+</p>
+<p>
+You can use simple web forms to subscribe or unsubscribe from individual
+mailing lists, available at their respective web pages at
+<a href="http://lists.scribus.info/">http://lists.scribus.info/</a>.
+</p>
+<p>
+The requests for subscription or unsubscription can also be sent by email, to
+a special control address, which is slightly different from the lists address.
+Subscription or unsubscription messages should NOT be sent to the address of
+the mailing list itself.
+</p>
+<p>
+To subscribe to or unsubscribe from a mailing list, please send mail to
+</p>
+<p>
+listname-REQUEST@lists.scribus.info
+</p>
+<p>
+with the word subscribe or unsubscribe as subject.
+</p>
+<p>
+Please remember the -REQUEST part of the address.
+</p>
+<p>
+As part of the subscription process, the list software will send you an email
+to which you must reply in order to finish subscribing. This is a security
+measure to keep people from subscribing others to the lists without their
+permission.
+</p>
+<p>
+Please remember that an unsubscription request should be sent from the address
+that is subscribed. If that is not possible, the Subject: header should be:
+unsubscribe subscribedaddress@subscribed.domain
+</p>
+<p>
+If you're receiving mail from a mailing list
+but you can't find the address through which you are subscribed, you can use the full headers of the received messages which will include lines like these:
+</p>
+<pre>
+ To: quux@example.com
+ List-Id: <scribus.lists.scribus.info>
+ Sender: scribus-bounces@lists.scribus.info
+</pre>
+<p>
+This tells you reliably that the list in question is called scribus and that the subscribed address is quux@example.com. In this (fictional) case you would send e-mail to scribus-request@lists.scribus.info with unsubscribe quux@example.com in the Subject field.
+</p>
+
+<h4>Member options page</h4>
+
+<ul>
+<li>
+This page is located at http://lists.scribus.info/mailman/options/listname/email (For example, http://lists.scribus.info/mailman/options/scribus/john.doe@example.com)
+</li>
+<li>
+This page can also be accessed by going to the listinfo page (For example, <a href="http://lists.scribus.info/mailman/listinfo/scribus">http://lists.scribus.info/mailman/listinfo/scribus</a>) and entering your email address into the box beside the button marked "Unsubscribe or Edit Options" near the bottom of the page.
+</li>
+<li>
+To log in to your member options page: If you are not already logged in, there will be a box near the top for you to enter your password. Enter your password in the box and press the button. If you do not know your password, click on the "Email My Password To Me" button in the lower left area of the page and check your email for the automated message from the list server software.
+</li>
+<li>
+The member options page allows you to log in/out, change your list settings, unsubscribe, or get a copy of your password mailed to you.
+</li>
+</ul>
+
+<h3>Code of conduct</h3>
+
+<p>
+When using the Scribus mailing lists, please follow these rules:
+</p>
+
+<ul>
+<li>
+Do not send spam; see the advertising policy below.
+</li>
+<li>
+If you can please send all of your list emails in English. You may attempt to use other languages as the Scribus Community consists of people speaking many languages of the world, but you are not guaranteed to receive a response in your native language. Altogether, Scribus Team developers speak English, German, French, Russian, Ukrainian, Finnish, Czech, Swedish, and Luxembourgish languages.
+</li>
+<li>
+Make sure that you are using the proper list. In particular, don't send user-related questions to the scribus-dev development-related mailing list.
+</li>
+<li>
+Wrap your lines at 80 characters or less for ordinary discussion. Lines longer than 80 characters are acceptable for computer-generated output (e.g., ls -l).
+</li>
+<li>Avoid Top Posting: <a href="http://www.blakjak.demon.co.uk/gey_stv0.htm">Here is why.</a> Many list readers get the digest format which really loses readability with top posting. </li>
+<li>
+Do not send automated out-of-office or vacation messages.
+</li>
+<li>
+Do not send subscription or unsubscription requests to the list address itself; use the respective -request address instead.
+</li>
+<li>
+Never send your messages in HTML; use plain text instead
+</li>
+<li>
+Avoid sending large attachments. There is a message size limit for Scribus Lists and your attachments will also be automatically removed from the message and made accessible only through the web interface to the Scribus Lists.
+</li>
+<li>
+Use your subscribed email to communicate with the list. If you use a different email address to send a message to the list your message will be held for moderator approval.
+</li>
+<li>
+Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand.
+</li>
+<li>
+When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied.
+</li>
+<li>
+If you send messages to lists to which you are not subscribed, always note that fact in the body of your message.
+</li>
+<li>
+Do not use foul language; besides, some people may receive the lists via a medium such as packet radio, where swearing is illegal.
+</li>
+<li>
+Try not to flame - it is not polite.
+</li>
+<li>
+Use common sense all the time.
+</li>
+</ul>
+
+<h3>List maintenance and administration</h3>
+
+<p>
+Sometimes our Mailing List Server may be down for maintenance or we could be
+performing upgrades to the mailing list software. Do not be alarmed as we'll
+make everything possible to bring the lists back up as soon as possible.
+</p>
+<p>
+If you're having problems subscribing or unsubscribing, please make sure
+you've followed the proper procedure before trying to contact us. Make sure
+that you have seen the caveats regarding subscription/unsubscription.
+</p>
+<p>
+To contact the list maintainer, send e-mail in English to mailman@lists.scribus.info. Alternatively, you can file a bug report in our Bug Tracking System at <a href="http://bugs.scribus.net">http://bugs.scribus.net</a>.
+</p>
+<p>
+If you were unable to unsubscribe from a mailing list, please include a copy
+of all the headers of an example message that you have received from that list
+in your e-mail.
+</p>
+
+<h3>Scribus mailing list advertising policy</h3>
+
+<p>
+The sending of any kind of unsolicited bulk email (also known as spam) to any
+of the Scribus lists is prohibited. Senders of such messages can get blocked from posting on lists and/or reported to the relevant authorities.
+</p>
+<p>
+The Scribus Listmasters do their best to stop as many such emails as possible from reaching the lists.
+</p>
+<p>
+Many of the rules we use to block spammers and their messages have been reported to us by subscribers. If you wish to help us reduce the amount of spam even more, your help is very much appreciated. To report spam you may send email to mailman@lists.scribus.info with the URL of the message from the mailing list archive. You will get a reply when we act on your submission. Please bear in mind that we will only act on reported spam messages/patterns that have been sent in the last few hours, because there is no point in having out of date filtering rules.
+</p>
+<p>
+Do not allow any emails that you receive from any Scribus mailing lists to be sent to an automated spam reporting system. Doing so is often harmful to all users and will force us to block you from receiving traffic from all Scribus lists until you prove that you will not do so again.
+</p>
+<h3>Disclamer of Responsibility</h3>
+
+<p>
+Disclaimer for the Scribus mailing lists
+</p>
+<p>
+Our mailing lists are public forums, and our mailing list archives are public.
+</p>
+<p>
+By sending an email to such a public forum, you agree to public distribution of your article. All mails sent to any of our mailing lists (and all information submitted to the bug tracking system) will be publicly distributed and archived in our mailing list archives.
+</p>
+<p>
+Any emails sent by any one person directly to the list, or replies by others to those emails sent to the list, are considered published, in accordance with the United States law.
+</p>
+<p>
+Obviously the author still owns the copyright to the content of these emails that they have written. However, that does not mean that the Scribus Team is under obligation to remove them from a list archive once published. Several legal counsels have reviewed this stance for the Debian Project and confirmed that it was correct.
+</p>
+<p>
+The mailing list archives have been public well before you sent a message to that mailing list address. You are responsible for determining who it is you are sending your email to. You cannot send email to arbitrary recipients and expect that they are automatically forced into accepting your terms for receiving your email.
+</p>
+<p>
+Scribus Team accepts no responsibility for the opinions and information posted on its mailing lists by others.
+</p>
+<p>
+Scribus Team disclaims all warranties with regard to information posted on its mailing lists, whether posted by Scribus Team or others; this disclaimer includes all implied warranties of merchantability and fitness. In no event shall Scribus Team be liable for any special, indirect or consequential damages, or damages of any kind whatsoever, resulting from loss of use, data or profits, arising out of or in connection with the use of any information posted on a Scribus mailing list.
+</p>
+<p>
+By posting material, the posting party warrants and represents that it owns the copyright with respect to such material, has received permission from the copyright owner, or that the material is in the public domain. The posting party further warrants and represents that it otherwise has the full and unencumbered right to post such material and that such posting will not infringe any rights or interests of others.
+</p>
+<p>
+Scribus Team does not generally monitor its mailing lists for inappropriate postings, and does not undertake editorial control of postings. We do, however, reserve the right to prevent posting to mailing lists in the event of failure to comply with the mailing list code of conduct.
+</p>
+<p>
+Some spam and virus filtering is applied to every message that goes through Scribus lists.
+</p>
+<h3>License</h3>
+<p>
+<i>This document has been adapted from the Debian Project's Mailing Lists description. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, Draft v1.0 or later, the latest version is usually available at <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).</i>
+</p>
+</body>
+</html>
Index: Scribus/doc/en/faq1.html
===================================================================
--- Scribus/doc/en/faq1.html (nonexistent)
+++ Scribus/doc/en/faq1.html (revision 13527)
@@ -0,0 +1,155 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>General Questions</title>
+</head>
+<body>
+<a name="top"></a>
+<h2>General Questions</h2>
+<ul>
+ <li><a href="#1">How do I contact the Scribus Team or find interactive help?</a></li>
+ <li><a href="#2">Color Management does not appear in the menu.</a></li>
+ <li><a href="#3">How do get I formatted tables in Scribus?</a></li>
+ <li><a href="#4">Help! My palettes have disappeared!</a></li>
+ <li><a href="#5">Scribus is slow to launch. Why ?</a></li>
+ <li><a href="#6">What is the difference between PDF 1.3, PDF 1.4 and PDF 1.5 ?</a></li>
+ <li><a href="#7">Why don't my fonts display properly on Red Hat 8, 9 or Fedora Core-1 ?</a></li>
+ <li><a href="#13">How do you change paper size once the a has been created?</a></li>
+ <li><a href="#14">How do you get a printer to print on a non standard size page?</a></li>
+ <li><a href="#24">I get a &quot;QClipboard: internal error, qt_xclb_wait_for_event recursed&quot; error in the console when dragging and dropping from the KDE Desktop. What causes this?</a></li>
+ <li><a href="#21">The CUPS options do not show up in print options dialog, what is wrong?</a></li>
+ <li><a href="#26">Scribus crashes when launching and searching for fonts. I have updated my freetype2. I upgraded my freetype2 to enable the bytecode interpreter.</a></li>
+ <li><a href="#27">Is there something wrong with the location of the scribus-1.6 RPMs? Whenever I try to download I am unable to get anything - usually the browser (Firefox, Mozilla) will complain it cannot read the source file.</a></li>
+ <li><a href="#28">Scribus seems to hang in an infinite loop when importing EPS or PS files. Why?</a></li>
+ <li><a href="#29">Why don't images print on a HP LaserJet 1xxx series printer from within Scribus or from exported PS/PDF files, but can be viewed in PDFs.</a></li>
+ <li><a href="#30">How do I compile Scribus with debugging enabled ?</a></li>
+ <li><a href="#32">How do I get Arabic text to display correctly with proper glyph shaping and RTL text direction, the most I can get out of Scribus right now is RTL text with no glyph shaping?</a></li>
+</ul>
+
+<h3>Answers</h3>
+
+<ul>
+ <li><a name="1"></a>
+ <p class="faqquestion">How do I contact the Scribus Team or find interactive help?</p>
+ <p>1. There is an active and friendly mailing list details at http://lists.scribus.info/mailman/listinfo/scribus. The archives are also searchable at http://nsj.srem.pl/cgi-bin/search.cgi</p>
+ <p>2. Find the developers on IRC, on the irc.freenode.net network in the #scribus channel.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="2"></a>
+ <p class="faqquestion">Color Management does not appear in the menu.</p>
+ <p>Make sure you have .icc and or .icm profiles in the /scribus/profiles directory, or in the directory that you have set in Settings->Preferences. Ideally, you will have a set of profiles which includes one for your monitor, one for the images and any scanner or input device profiles and profiles for your printer or output device. You need a minimum of 1 RGB color space icc profile and 1 CMYK icc color space profile for the color managment options to be enabled. See the details in Color Management for Scribus for links and info about color profiles.</p>
+ <p>If you install littlecms from an rpm, make sure you have installed the development libraries as well. If not, install the rpm, run ldconfig or /sbin/ldconfig as root, remove config.cache from the source directory, then run ./configure again and recompile.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="3"></a>
+ <p class="faqquestion">How do get I formatted tables in Scribus?</p>
+ <p>Scribus added basic table support in 1.1.6</p>
+ <p>One suggestion for placing formatted tables and sections of spreadsheets is the following:</p>
+ <ul>
+ <li>Create the table in a spreadsheet in either StarOffice or OpenOffice.org 1.1.x (recommended as a first choice). Format the table with the desired fonts, sizing and background colors for the cells.</li>
+ <li>&quot;Print&quot; the file saving as PS, by printing a &quot;file&quot; to the &quot;generic printer&quot;.</li>
+ <li>Open the just created PostScript file in GSView (Version 4.6 or newer recommended)</li>
+ <li>File &gt; Convert &gt; Select Device epswrite</li>
+ <li>Choose 300 or more dpi as the resolution and save. Then, place the image as an EPS. Scribus will print this with the colors, shading and fonts intact. The screen preview may not be perfect, but it will either export as PDF or print just fine.</li>
+ <li>Alternative: Import as an SVG, as outlined: Importing Tricks for Scribus</li>
+ </ul>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="4"></a>
+ <p class="faqquestion">Help! My palettes have disappeared!</p>
+ <p>Close Scribus. Then open ~/.scribus/scribus.rc, a hidden file in your home directory in a text editor. Then look down in the file for the section beginning about 10 lines from the top. ex: MEASUREMENTS YPOS=&quot;-264&quot; XPOS=&quot;-692&quot; VISIBLE=&quot;1&quot;</p>
+ <p>Notice the negative numbers in front of the YPOS and XPOS statements. Remove the minus, set the visible setting to 0 and save. You might find the coordinates too large: (YPOS=&quot;3046&quot; XPOS=&quot;7690&quot;) Either way, these coordinates are screen positions in pixels. They should be within 1024x768 or whatever screen resolution you are running. Restart Scribus and go Tools &gt; and select show for the missing palette. It will reappear like normal.</p>
+ <p>**This has been corrected in the most recent versions of Scribus and should not be a problem in the future.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="5"></a>
+ <p class="faqquestion">Scribus is slow to launch. Why ?</p>
+ <p>For those who are new at desktop publishing, unlike most programs, DTP applications care greatly about which fonts are installed and if the font paths are valid. So, when Scribus launches, one of the things it does is to completely and thoroughly scan your font paths and ensure they are valid. This takes time. If you have a large number of fonts (200+) or more and slow launch times are a problem, reduce the number of fonts or font paths. </p>
+ <p>The other reason is your scrapbook might be filled with complex or large image files. Deleting uneeded items or saving the scrapbook under a different name and then creating a new blank scrapbook will also help reduce the startup time.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="6"></a>
+ <p class="faqquestion">What is the difference between PDF 1.3, PDF 1.4 and recently released PDF 1.5 ?</p>
+ <p>PDF 1.2 = Acrobat 3.0 - relatively obsolete now</p>
+ <p>PDF 1.3 = Acrobat 4.0 - The first version of PDF which truly had all the needed features to support &quot;press-ready&quot; PDFs including color managment, ICC profiles etc. It also added javascript, interactive and multimedia capabilities. This standard is probably the safest to send if you are unsure of the capabilities of the receiver of your file. PDF/X-3 and a number of commercial print work flows are based on PDF 1.3.</p>
+ <p>PDF 1.4 = Acrobat 5.0 - Actually, introduced with Illustrator 9, The main difference to concern Scribus users is PDF 1.4, has both transparency and alpha transparency capabilites, which make a major difference in where a PDF with these features can be printed. It takes wither the latest commerical RIP's or a Level 3 PostScript printer to use these features properly. The latest versions of Ghostscript suport the advanced PDF 1.4 features Scribus can create when exporting PDF.</p>
+ <p>PDF 1.5 = Acrobat 6.0 - Adobe has publicly released the final spec - 1100 pages of light reading :) of PDF 1.5 to accompany the recently released Acrobat 7. Among the most interesting for Scribus users: many improvements for &quot;press-ready&quot; PDF, the capability to have true layering within the PDF, PDF-X &quot;pre-flight&quot; capability, more security and interactive features, like the ability to add comments which are separate from the original doc.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="7"></a>
+ <p class="faqquestion">Why don't my fonts do not display properly on Red Hat 8,9 or Fedora Core-1 ?</p>
+ <p>Upgrade your version of Scribus to 1.1.1 or newer. It has a new font discovery mechanism which works with fontconfig and the new font system in RH 8+</p>
+ <p>The other issue is the startkde script, if you run KDE it causes the font paths to be overridden to inacessable font paths. A bug has been filed against kdebase : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110681</p><a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="13"></a>
+ <p class="faqquestion">How do you change paper size once page has been created?</p>
+ <p>In 1.3.x, you can change the size of the current page or a range of pages in the Page menu, under Manage Page Properties.</p>
+ <p>You can change this for the whole document under File->Document Setup.</p>
+ <p>Scribus 1.3.x allows multiple page sizes per document.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="14"></a>
+ <p class="faqquestion">How do you get printer to print on a non standard size page?</p>
+ <p>It depends:</p>
+ <ol>
+ <li>If you are printing to a local printer which is *not* a PostScript printer, but using CUPS, you can't. It is a limitation, as far as we can tell of CUPS.</li>
+ <li>If you have a &quot;real&quot; PostScript printer, Scribus - with CUPS support - will support any arbitrary page size, as long as the printer support it.</li>
+ </ol>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="24"></a>
+ <p class="faqquestion">I get a &quot;QClipboard: internal error, qt_xclb_wait_for_event recursed&quot; error in the console when dragging and dropping from the KDE Desktop. What causes this ?</p>
+ <p>See: http://bugs.scribus.net/bug_view_advanced_page.php?bug_id=0000045. This is a long standing bug in Qt. SuSE 9.0 users can upgrade to the Qt3 3.3.1-2 or higher. RedHat or Fedora users can upgrade to qt-3.3.1-6 or higher.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="21"></a>
+ <p class="faqquestion">The CUPS options do not show up in print options dialog, What is wrong?</p>
+ <p>See this bug: http://bugs.scribus.net/bug_view_advanced_page.php?bug_id=0000271 for and explanation of how CUPS can be mis-configured.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="26"></a>
+ <p class="faqquestion">Scribus crashes when launching and searching for fonts and I have updated my freetype2. I upgraded my freetype2 to enable the bytecode interpreter.</p>
+ <p>We do not recommend trying to update freetype2, except rebuilding your existing distros Source RPMS or source packages.</p>
+ <ol>
+ <li>Recent versions of freetype have an autohinter which works very well.</li>
+ <li>*Many* packages are compiled against freetype2 (Xfree86,Qt, Gtk etc..), upgrading freetype2, might require recompiling all of these packages or system instability might result.</li>
+ </ol>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="27"></a>
+ <p class="faqquestion">Is there something wrong with the location of the scribus-1.6 RPMs? Whenever I try to download I am unable to get anything - usually the browser (Firefox, Mozilla) will complain it cannot read the source file.</p>
+ <p>It is a Firefox bug as best we can tell. Downloads with Moz 1.6 and Konqueror - even (shudder) IE seem to work fine. We have had over 2000 rpms 1.1.6 downloaded..</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="28"></a>
+ <p class="faqquestion">Scribus 1.1.7+ seems to hang in an infinite loop when importing EPS or PS files. Why?</p>
+ <p>Three possible solutions:</p>
+ <ol>
+ <li>Upgrade Ghostscript to GS 8.15 or GS 8.50. There are notes in the Toolbox section on parallel installs of GS.</li>
+ <li>Reduce the complexity of your EPS/PS file.</li>
+ <li>You do not have enought memory/swap space when importing complex EPS files.</li>
+ </ol>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="29"></a>
+ <p class="faqquestion">Why don't images do not print on a HP LaserJet 1xxx series printer(or other B&amp;W laser)from within Scribus
+or from exported ps/pdf files, but can be viewed in PDFs.</p>
+ <p>One workaround is to export your document to PDF then load it into AcrobatReader and print at PS level 2.</p>
+ <p>Another solution is to create a non PostScript printer (E.g. for a HP LJ 1300 series a printer was set up in CUPS as hplj with lj5gray printer). That works for some apps/docs, too. In general,create a ps2 level printer. Make sure you use the PPD file from the windowsdriver package instead of the cups/foomatic one. You will get better results during the conversion.</p>
+ <p>The reason is Scribus is generating PS3 level objects which the PS interpreter is unable to understand. This is a frequent issue with Black and White laser jets when printing from Desktop Publishing apps - I've seen this with LJ4 and 5, as well as newer HP2xxx printers with Pagemaker, Quark Xpress and Indesign. </p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="30"></a>
+ <p class="faqquestion">How do I compile Scribus with debugging enabled?</p>
+ <p><code>./configure --enable-debug</code></p>
+
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="33"></a>
+ <p class="faqquestion">How do i get Arabic text to display correctly with proper glyph shaping and RTL text direction, the most I can get out of Scribus right now is RTL text with no glyph shapeing?</p>
+ <p>The glyph shaping is a very difficult thing to achieve, we plan to add this in one of the 1.3.x Developers versions.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+</ul>
+</body>
+</html>
/Scribus/doc/en/faq1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install-dpkg.html
===================================================================
--- Scribus/doc/en/install-dpkg.html (nonexistent)
+++ Scribus/doc/en/install-dpkg.html (revision 13527)
@@ -0,0 +1,189 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus on Debian GNU/Linux and Derivatives</title>
+</head>
+<body>
+<h2>How to use the Scribus Debian / Ubuntu Repository</h2>
+<p><em>These notes are kindly provided by our Debian package maintainer, Oleksandr Moskalenko.</em> &#060;malex at tagancha.org&#062;. Please direct questions related to Scribus on Debian to the above email.</p>
+
+<strong>"Debian" name here encompasses Debian proper (unstable/testing/stable also known as sid/etch/sarge) and at least Ubuntu breezy/hoary. Instructions on rebuilding the source package may be applicable to other Debian derivatives and custom distributions.</strong>
+<h3>Preamble</h3>
+
+<p>Currently there are following Scribus-related packages in Debian:</p>
+<ul>
+ <li><a href="http://packages.qa.debian.org/s/scribus.html">scribus</a> (Scribus 1.3.3.x - STABLE) </li>
+ <li><a href="http://packages.qa.debian.org/s/scribus-ng.html">scribus-ng</a> (Scribus 1.3.x - UNSTABLE). scribus-ng package can be installed in parallel with the scribus package. </li>
+
+ <li> <a href="http://packages.qa.debian.org/s/scribus-template.html">scribus-template</a> (Developer and user-contributed additional templates), </li>
+ <li><a href="http://packages.qa.debian.org/s/scribus-doc.html">scribus-doc</a> Scribus 1.2.x documentation, which has to be provided as a separate package due to is non-free nature by the Debian Free Software Guidelines </li>
+ <li><a href="http://packages.qa.debian.org/s/scribus-ng-doc.html">scribus-ng-doc</a> Scribus 1.3.x documentation, which has to be provided as a separate package due to is non-free nature by the Debian Free Software Guidelines </li>
+ <li><a href="http://packages.qa.debian.org/i/icc-profiles.html">icc-profiles</a> - A collection of common ICC profiles to use with Scribus and other color profile-aware software </li>
+
+ <li><a href="http://packages.qa.debian.org/l/lprof.html">lprof</a> Hardware color profiler that can be used to create color profiles for your hardware to be used with Scribus </li>
+</ul>
+
+<p>Scribus team also maintains an unofficial (outside of Debian proper) repository that contains some of the packages mentioned above with the most notable difference being a more frequent update schedule compared to Debian proper. There are a couple reasons for the existence of this upstream repository. Debian development has a limit on how often a scribus package can be updated. It could sometimes take weeks between consecutive uploads as the package could be waiting on other related packages before it can move from Unstable (sid) into Testing (currently etch). Because of that the official packages are usually behind those available in our upstream archives. Packages in our upstream repositories usually follow scribus development fairly closely via svn snapshot builds. For instance, if you discovered a but you are advised to install the most recent package as the bug might have already been fixed and a fixed package is available. This is called "the Scribus magic (TM)". Also, our repositories contain builds for Ubuntu Hoary and Breezy branches (ix86 architecture).</p>
+
+<h3>Debian setup for Scribus repositories</h3>
+<h4>About the repositories</h4>
+<p>We actually maintain two identical repositories to provide bandwidth redundancy and failover capability to our distribution of Debian scribus packages. These repositories contain x86 packages for Debian stable,testing and unstable and Ubuntu hoary and breezy branches. If you are using a different Debian-based distribution or your hardware is not x86-based such as PowerPC or AMD64 you can easily build a Scribus package from our source package, so do not consider it as a strong obstacle to using these packages.</p>
+
+<h3>Repository usage</h3>
+<p>To use our repositories add the appropriate source lines from the following list to your /etc/apt/sources.list file. Note that the lines starting with "deb" are used for installation of the pre-compiled binary packages and the line starting with "deb-src" are for the source package for building a binary package for your distribution (if it has a different set of libraries), hardware (if it's not x86) or compiler optimizations (if you really know you want them).&nbsp;</p>
+
+<h3>Source lines for /etc/apt/sources.list or for Synaptic et al</h3>
+<h4>Debian stable (Sarge): </h4>
+<pre> # debian.scribus.net - Primary repository
+ <br /> deb http://debian.scribus.net/debian/ stable main non-free contrib
+ <br /> deb-src http://debian.scribus.net/debian/ stable main non-free contrib
+ <br /> # debian.tagancha.org - Backup repository
+ <br /> deb http://debian.tagancha.org/debian/ stable main non-free contrib
+ <br /> deb-src http://debian.tagancha.org/debian/ stable main non-free contrib
+ <br />
+</pre>
+<h4>
+ Debian testing (Etch):
+</h4>
+<pre> # debian.scribus.net - Primary repository
+ <br /> deb http://debian.scribus.net/debian/ testing main non-free contrib
+ <br /> deb-src http://debian.scribus.net/debian/ unstable main non-free contrib
+ <br /> # debian.tagancha.org - Backup repository
+ <br /> deb http://debian.tagancha.org/debian/ testing main non-free contrib
+ <br /> deb-src http://debian.tagancha.org/debian/ unstable main non-free contrib
+ <br />
+</pre>
+<h4>
+ Debian unstable (Sid):
+</h4>
+<pre> # debian.scribus.net - Primary repository
+ <br /> deb http://debian.scribus.net/debian/ unstable main non-free contrib
+ <br /> deb-src http://debian.scribus.net/debian/ unstable main non-free contrib
+ <br /> # debian.tagancha.org - Backup repository
+ <br /> deb http://debian.tagancha.org/debian/ unstable main non-free contrib
+ <br /> deb-src http://debian.tagancha.org/debian/ unstable main non-free contrib
+ <br />
+</pre>
+<h4>
+ Ubuntu Hoary:
+</h4>
+<pre> # debian.scribus.net - Primary repository
+ <br /> deb http://debian.scribus.net/debian/ hoary main restricted
+ <br /> deb-src http://debian.scribus.net/debian/ hoary main restricted
+ <br /> # debian.tagancha.org - Backup repository
+ <br /> deb http://debian.tagancha.org/debian/ hoary main restricted
+ <br /> deb-src http://debian.tagancha.org/debian/ hoary main restricted
+ <br />
+
+
+</pre>
+<h4>
+ Ubuntu Breezy:
+</h4>
+<div>
+ Note that Ubuntu breezy package can be also used for Ubuntu "Dapper" branch right now. When Dapper changes enough to require its own scribus or scribus-ng package we will provide it.
+</div>
+<pre> # debian.scribus.net - Primary repository
+ <br /> deb http://debian.scribus.net/debian breezy main restricted
+ <br /> deb-src http://debian.scribus.net/debian breezy main restricted
+ <br /> # debian.tagancha.org - Backup repository
+ <br /> deb http://debian.tagancha.org/debian breezy main restricted
+ <br /> deb-src http://debian.tagancha.org/debian breezy main restricted
+ <br />
+
+
+</pre>
+
+<h3>Using cryptographic repository signatures:</h3>
+<p>Our repositories are cryptographically signed for added security. Add the gpg-keys for our repositories to avoid having to confirm your installation choice to the package manager each time you update a scribus or scribus-ng package.</p>
+
+<pre>
+ root$ gpg --keyserver wwwkeys.eu.pgp.net --recv-keys DA286F326C5F196B
+ root$ gpg --armor --export DA286F326C5F196B | apt-key add -</pre>
+or as a normal user (with an appropriate entry for apt-key in the sudoers file):
+<pre>
+ user$ gpg --keyserver wwwkeys.eu.pgp.net --recv-keys DA286F326C5F196B
+ user$ gpg --armor --export DA286F326C5F196B | sudo apt-key add -</pre>
+
+<h3>Final installation step</h3>
+<p>Once you added the relevant sources lines to your /etc/apt/sources.list you can run:</p>
+ <pre>aptitude install scribus scribus-ng</pre>
+ or
+ <pre>apt-get install scribus scribus-ng</pre>
+
+ <p>in a root terminal or use your favorite graphical apt-get front-end such as synaptic or aptitude. Don't forget to "Reload Package List" in the synaptic. It's the equivalent of "apt-get (or aptitude) update" and has to be done to make new packages from our repositories available to your package management tools.</p>
+
+ <h3>Bug reporting</h3>
+ <p>Please do not file bug reports about the packages from these upstream repositories in the Debian or Ubuntu BTS (Bug Tracking Systems). Use the distribution BTS for the package version that is in that distribution. However, if you cold verify that the bug is present in the package version in Debian, by all means feel free to file a bug report through the Debian BTS. You are encouraged to contact the maintainer <a href="mailto:malextagancha.org">Oleksandr (Alex) Moskalenko</a> directly if you have package installation questions or related Scribus issues that you believe do not belong in Scribus BTS or for comments and suggestions about this document. If you have a Scribus issue that is not related to Debian packaging you may find it easier to just use the scribus BTS at http://bugs.scribus.net for reporting bugs as such issues would be forwarded from the Debian BTS to the Scribus BTS by the maintainer anyway.</p>
+
+ <h3>Step-by-step procedure for new Debian GNU/Linux users</h3>
+ <p>You don't have to log on as root, but you have to have superuser privileges to edit the /etc/apt/sources.list file. Fortunately, on a Linux system you can do that with ease. Please open a root terminal or open a regular terminal and become root through a "su" command. You will have to provide root password when prompted. Then, you can launch your favorite text editor from that terminal and edit the sources.list file as outlined in the http://wiki.scribus.net/index.php/Scribus_on_Debian_GNU/Linux page. Alternatively, you can do a bit more work upfront to achieve a more permanent access to package manipulation system. If you are familiar with the VI editor you can do the following:</p>
+
+ <ul>
+ <li>
+ Open a root terminal.
+ </li>
+ <li>
+ Type "visudo".
+ </li>
+ <li>Type "o" to open a new line (vi command) and type the following line (assuming your login name is "scribusoid"): scribusoid ALL= NOPASSWD: /usr/sbin/synaptic
+ </li>
+ <li> Press "ESC" to leave the editing mode in Vi and return to the command mode. </li>
+
+ <li> Type ":wq!" to exit the editor. </li>
+ </ul>
+ <p>Now you are ready to launch the very nice graphical apt-get front-end Synaptic with a "sudo synaptic" command at any time. If you are a new Linux user, Synaptic will help you get started easier than you probably would with command line tools. Once you launch Synaptic select the "Settings/Repositories" menu entry. Click on the "New" button and type or paste in the appropriate source lines. For example for "Debian Sarge": URI: http://debian.scribus.net/debian/</p>
+ <br />
+ Distribution: stable
+ <br />
+ Section(s): main non-free contrib
+ <br />
+ <p>Don't forget to enable that repository by selecting a checkbox in the leftmost column. Now you can reload repository information by clicking on the "Reload" button in the main Synaptic window. Then you click on the "Search" button and search for "scribus". Once "scribus", "scribus-ng", "scribus-doc", and "scribus-template" packages are found you can mark them for installation by double-clicking on them or by right-clicking and selecting "Mark for installation". When you are done, click on the "Apply" button to proceed with installation. After that you should have the packages installed and may begin to use Scribus.</p>
+ <h3>Building from a source package for other Debian-based distributions</h3>
+ <p>Instructions below have been rendered mostly obsolete for the x86 architecture by the new repositories. If you have non-x86 hardware or would like to build an optimized package you can still use these instructions. You can submit packages for other architectures to me and I will place them into the repository. If you have a non-x86 arch or would like to optimize the packages for your CPT you can achive these goals by a very simple package rebuild. Make sure that you have the deb-src lines for scribus repositories uncommented and run the following commands:</p>
+
+ <p>The cool way (TM) - as root or set up sudo for yourself as a user:</p>
+ <pre>apt-get install apt-build
+ </pre>
+
+ <p>Answer questions about your CPU and stuff - see an excellent document at <a href="http://julien.danjou.info/article-apt-build.html">http://julien.danjou.info/article-apt-build.html</a>)
+ </p>
+ <pre>apt-build update</pre>
+ <pre>apt-build install scribus (or scribus-ng)</pre>
+ <hr />
+
+ <h4>An alternate cool way - as root or see the config setup below:</h4>
+ <ul>
+ <li> Install "apt-src":<pre> apt-get install apt-src<br /></pre></li>
+ <li> Install the dependencies, build and install scribus from source:
+ <pre> apt-src -i install scribus <br /></pre></li>
+ </ul>
+ <h4>To streamline this process and build scribus as a user:</h4>
+ <p><strong>Configure apt-src:</strong> Add the following lines to /etc/apt/apt.conf or ~/.apt-src/config file:
+ </p>
+ <pre>
+ APT::Src::RootCommand su -c;<br />
+ APT::Src::BuildDeps</pre>
+ <p>This is especially convenient if you set up the no-password su to root for yourself through pam. Otherwise you'll likely have to type a password.</p>
+ <hr />
+ <h4>Without apt-build or apt-src - as root:</h4>
+ <pre> apt-get source -b scribus scribus-ng<br /></pre>
+ <pre> apt-get build-dep scribus-ng (or scribus)<br /></pre>
+ <hr />
+ <h4>Another way - as root:</h4>
+ <pre> apt-get install devscripts build-essential fakeroot<br /></pre>
+ <strong>Note:</strong> This creates a minimal build environment.
+ <pre> apt-get source scribus-ng (or "scribus" instead of "scribus-ng")<br /></pre>
+ <pre> apt-get build-dep scribus-ng (or scribus)<br /></pre>
+ <pre> cd scribus.... or scribus-ng...</pre>
+ <p>Use the actual directory names.</p>
+ <pre> debuild -us -uc<br /></pre>
+ <pre> cd .. <br /></pre>
+ <pre> dpkg -i scribus_.... or scribus-ng_....<br /></pre>
+
+
+<p>One thing which sets Scribus apart is the enthusiastic and friendly Scribus community that assists beginner and pro alike. You can take part in many ways: our <a href="http://lists.scribus.info/mailman/listinfo/scribus">mailing list</a>, the <a href="http://docs.scribus.net/index.php?lang=en&page=irc">IRC channel</a>, email, the <a href="http://wiki.scribus.net/">wiki</a>, contracted support and finally the <a href="http://bugs.scribus.net/">bugtracker</A>. These options add to your Scribus experience and we think you will find it very rewarding.</p></
+
+
+</body>
+</html>
/Scribus/doc/en/install-dpkg.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/readme-win32.html
===================================================================
--- Scribus/doc/en/readme-win32.html (nonexistent)
+++ Scribus/doc/en/readme-win32.html (revision 13527)
@@ -0,0 +1,48 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus on Windows</title>
+</head>
+<body>
+<h2>Scribus on Windows - Read Me</h2>
+<h4>What is different about Scribus ?</h4>
+
+<p>First, Scribus was developed first and foremost on Linux and Unix machines, so sometimes the way things work are not always the 'windows way', but a more OS neutral way. Scribus also is natively ported to MacOSX and the behavior changes are mostly in the way the menus work. Second, a great deal of time and effort has been put into Scribus to generate very high quality commercial grade PDF. Provided you follow the recommended workflow in the documentation, you should have few issues with commercial printing.</p>
+
+<h3>Hardware/Software Minimum Requirements:</h3>
+<p>Windows 2000 SP4 or Windows XP are supported. Windows 98 and ME have not been tested and are <strong>not supported</strong>. Any and all bug reports relating to Windows 9X will be closed quickly. </p>
+<p>256 Mb or more system memory - the more the better. 512Mb or more is strongly recommended for larger more complex documents. </p>
+<p>Pentium III or better - 750MHz or better</p>
+<h3>Recommended:</h3>
+<p>XP Themes Disabled - Use the "Windows Classic" theme <strong>is very strongly recommended</strong>. There is a known issue with Custom Themes causing document loading problems. This is especially true with third party themes. </p>
+
+<h3>Before Installing Scribus</h3>
+<ul>
+ <li>Install Ghostscript for Windows - <a href="http://ghostscript.com">Ghostscript 8.60+</a> or newer is recommended. This is important for EPS,PS import and printing. Note: After installing there are two .exe files installed by the installer. The correct .exe name to use in Scribus' preferences for Ghostscript is gswin32c.exe, <strong>not</strong> gswin32.exe. In the large majority of cases <strong>if</strong> Ghostscript is properly installed before installing Scribus, Scribus will automatically detect the location for Ghostscript for you.</li>
+ <li>Scribus is <strong>very</strong> intolerant of poorly constructed or marginal grade fonts. Once installed, please read carefully the font setup section in the help documentation. Scribus may and often will refuse to load fonts which do not follow the True Type and Type 1 specifications properly. What this means in plain English is freeware fonts may work in other programs, but will be rejected by Scribus when starting. Once installed, please read carefully the font setup section in the help documentation. Some of the information is Linux specific, but has detailed explanations why poor quality fonts will cause problems. </li>
+ <li>This is beta software which is undergoing many code changes daily. While it is fairly stable and usable, caution is advised. It is not recommended yet for production use. The underlying file format is undergoing rapid changes and will not be finished until the 1.3.6 or later version is released. </li>
+ </ul>
+ <h3>After Installing</h3>
+ <ul>
+<li>The first launch of Scribus or when a new user launches Scribus will be much longer than usual. This is because Scribus is creating a cache file of your fonts. Later re-starts will be much quicker.</li>
+
+<li>When you select the "Extra Fonts" Option in the installer, this installs two sets of high quality, freely distributable font. One set is the the URW fonts from Ghostscript. This includes 45 type faces which are commonly included with most PostScript printers. The second is the Bitstream Vera font family, widely used on Linux and by many of the included templates.</li>
+ </ul>
+
+<p>Again, Scribus is very particular about font quality. <strong>Use of freeware or shareware fonts is not recommended</strong>. There is an extensive and informative set of notes in the online help about fonts and commercial grade printing. Scribus scans fonts on launch and will disable obviously broken or problematic fonts. Those notes are based on experience both with Scribus and commercial printing.</p>
+<h3>Console Mode for Diagnostics</h3>
+<p>There is a second way to launch Scribus: <strong>Console Mode</strong>. In the <strong>Start > Program Files</strong> menu there is a second short cut <strong>Scribus -console</strong>. This mode merely opens a windows command prompt, but will show line by line, each font and its full path being loaded by Scribus. This will also show any rejected fonts and duplicate fonts Scribus finds, along with other diagnostic info in some cases. Duplicates are not loaded, even if they have different names. One of the font tests Scribus performs on launching is to ensure each font file has a correct PostScript name. </p>
+<p>The Scribus Team is pleased to make available the only open source page layout application which runs natively on all 3 major desktop operating systems; Linux, MacOSX and Windows. Both online and direct commercial support is available for Scribus. There is a very friendly community which has developed around Scribus with the active participation of the developers. Enjoy! </p>
+
+<p><a href="http://docs.scribus.net">Scribus Documentation Site</a> (EN,FR,DE, PL) - http://docs.scribus.net</p>
+<p><a href="http://www.scribus.net/">Scribus Home Page</a> - http://www.scribus.net</p>
+ <p><a href="http://bugs.scribus.net">Scribus Bug Tracker</a> - http://bugs.scribus.net</p>
+ <p><a href="http://wiki.scribus.net">Scribus Wiki</a> (users for users) - http://wiki.scribus.net</p>
+ <p><a href="http://lists.scribus.info/mailman/listinfo/scribus">Mailing list</a> (subscription, archives etc.) -http://lists.scribus.info/mailman/listinfo/scribus </p>
+
+<!-- <p><a href="http://sourceforge.net/project/showfiles.php?group_id=125235">Scribus
+SourceForge Downloads</a></p>
+ <p><a href="devel-docs">Developers Documentation (API)</a></p>
+-->
+</body>
+</html>
/Scribus/doc/en/readme-win32.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/resources.html
===================================================================
--- Scribus/doc/en/resources.html (nonexistent)
+++ Scribus/doc/en/resources.html (revision 13527)
@@ -0,0 +1,33 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Community Resources</title>
+</head>
+<body>
+<h2>Community Resources</h2>
+<p>The <strong>scribus mailing list</strong> is on-line at <a href="http://lists.scribus.info/mailman/listinfo/scribus">http://lists.scribus.info/mailman/listinfo/scribus</a>. There is a multi-lingual interface to the mailing list manager. This list is for end-user support and DTP discussion. </p>
+<p>The <strong>scribus-dev mailing list</strong> is on-line at <a href="http://lists.scribus.info/mailman/listinfo/scribus-dev">http://lists.scribus.info/mailman/listinfo/scribus-dev</a>. There is a multi-lingual interface to the mailing list manager. This list is for Scribus development discussion. </p>
+<h4>Mailing List Etiquette</h4>
+<p>The Scribus mailing list is active and very friendly. Do not be suprised if
+your questions receive several replies within a day. That said, there are a
+few rules we (and most list readers) like folks to follow. Please read our
+<a href="mailing_lists.html">Mailing List policy and disclamers</a></p>
+</p>The mailing list may be searched at this address: <a href="http://search.srem.org/">http://search.srem.org/</a></p>
+<p>The <strong>Bug Tracker</strong> is located at <a href="http://bugs.scribus.net/">http://bugs.scribus.net/</a></p>
+<p>The <strong>Wiki</strong> is located at <a href="http://wiki.scribus.net/">http://wiki.scribus.net/</a></p>
+<p>An IRC channel <strong>#scribus</strong> on <strong>freenode.net</strong> is quite active. There is usually at least one person from the core development team present there. For immediate assistance, this is the best along with the mail list, but does not excuse not searching the docs :-) See: <a href="irc.html">Scribus IRC</a> </p>
+<p>The Scribus Developers maintain a blog at: <a href="http://rants.scribus.net/">http://rants.scribus.net/</a>. This would be of interest to anyone using Scribus. </p>
+<h4>Deutsch</h4>
+<p><a href="http://scribus-forum.de/news.php">http://scribus-forum.de/news.php</a></p>
+<p><a href="http://www.opendtp.de/">Open DTP</a> a German language forum on all things related to page layout and using open source graphics applications. Hosted by long time Scribus user and contributor Thomas Zastrow.</p>
+<p>There is a <a href="http://www.bomots.de/scribus/">German</a> Scribus documentation site, based on an earlier (1.1.x )version of Scribus.</p>
+<h4>Fran&#231;ais</h4>
+<p>Pour les francophones, trois de l'equipe parle fran&#231;ais. Nous vous demandons d'abord d'essayer en anglais, mais en fran&#231;ais marche aussi sur IRC et sur la liste. Il y a plusieurs francophones souvent sur le canal. Il y a aussi un forum dedie pour Scribus sur <a href="http://www.linuxgraphic.org/forums/viewforum.php?f=20">Linuxgraphic.org</a></p>
+<h4>Italiano </h4> <p>There is an introduction to <a href="http://www.freaknet.it/node/496" name="Guida a Scribus" title="Guida a Scribus">Guida a Scribus</a>, thanks to Tommaso Cappello</p>
+<h4>Polish</h4>
+<p>There is a Polish translation of the "Get Started with Scribus" tutorial at :<br /><A href="http://linux.hanski.info/static/scribus/index.html">http://linux.hanski.info/static/scribus/index.html</A></p>
+<p>French, German and Polish versions of the docs are making progress and will be viewable at this address.</p>
+<h4>Russian</h4>
+<p><strong>Русскоязычный</strong> сайт о работе с графикой в Linux: <a href="http://www.linuxgraphics.ru">http://www.linuxgraphics.ru</a></p>
+</body>
+</html>
/Scribus/doc/en/resources.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/topten.html
===================================================================
--- Scribus/doc/en/topten.html (nonexistent)
+++ Scribus/doc/en/topten.html (revision 13527)
@@ -0,0 +1,56 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title> Top <strike>Ten</strike>Twelve Hints - Tips and Tricks to make better documents faster in Scribus</title>
+</head>
+<body>
+<h2>Top <strike>Ten</strike> Twelve Hints - Tips and Tricks to make better documents faster in Scribus</h2>
+
+<p>These are our top ten hints for using Scribus, in (some sort of) order:</p>
+
+<ul>
+<li><strong>Get the latest 7.0.x or 8. Adobe Reader&#174; installed.</strong><br /> Without this, is it impossible to open PDFs from Scribus and see all the features Scribus can create within a PDF. Plus, it renders PDF better than most any other viewer. In the future more documentation for Scribus will be in PDF format, optimized for display in Acro Reader. <a href="toolbox1.html">More details..</a></li>
+<li><strong>Tool Tips</strong><br />When, you are unsure of a function, <strong>use tool tips</strong>. While it is not 100% complete, a great many of the GUI functions have extensive tool tips to guide you about each option for a given function, especially more complex ones. To enable tool tips, make sure <strong>Help &#062; Tooltips </strong>is checked. Then hover your mouse over the check box or GUI option.</li>
+<li><strong>Use guides</strong><br /> to help visually align things in your document. Guides are invisible rulers you can place on the canvas to align different text boxes, as well as centering objects. In almost every document, I create a vertical guide to split the page in two. Then you can use this guide to center objects much easier.</li>
+<li><strong>Use the "nudge" tool.</strong> Select an object and then use the arrow keys to move object a tiny bit at a time - .01 in, or .01 mm. Shift and Ctrl + Shift + Arrow will change the distance per 'nudge'</li>
+<li><strong>Save Paper</strong> - Instead of printing a proof, export a low res PDF and open in Acrobat Reader. A properly setup PDF will display on the screen with a great deal of fidelity to the printed page.</li>
+<li><strong>Use PNG</strong>, in place of jpeg or gif. PNG is a much more versatile image format and it usually prints much better at the same resolution. Most importantly, it uses lossless compression and compresses some types of images really well. Lastly, the<a href="toolbox4.html"> GIMP</a>, which most users have as their primary bitmap editor, does a superb job of handling PNG, as well as compressing them very well.</li>
+<li><strong>Get a good Ghostscript</strong>- The newest 8.5x versions are <strong>much better </strong>at helping Scribus import EPS and generating high quality print previews. Versions 8.5x+ allows the best print previews in Scribus as they enable proper transparency and CMYK previewing.</li>
+<li><strong><a href="fonts2.html">Get good fonts</a></strong> - By good fonts, we mean high quality Type 1 or TrueType fonts from foundries like Adobe Bitstream and Monotype. Luckily, the available MS Web fonts are also pretty reliable in PostScript printing. A good source of fonts is the collection of Bitstream fonts included with most versions of Corel Draw. We know people who have used these fonts for years and can't remember a font problem with these fonts. Most disks have the same font in Type and TrueType versions. Some Adobe applications, like Pagemaker or InDesign include a small collection of useful high quality Type 1 fonts. This will make printing and PDF creation much more reliable.</li>
+<li><strong><a href="pagetemplate1.html">Master Pages</a></strong> can be big time saver. Anytime you have common elements on several pages, add those elements to a template. This also avoids accidently moving or deleting objects.</li>
+<li><strong>Backup your Preferences</strong> - This is more important for users of CVS versions of Scribus. Occasionally - <strong>much less</strong> common now, a program crash caused by a bad image etc., can corrupt your preferences. So, to get a good replacement setup, close Scribus and rename the hidden <code>.scribus</code> folder in your home directory to <code>.scribusbak</code>. Reopen Scribus with no document open and change every setting as you wish and then close Scribus. Now copy the whole directory somewhere else. Then, if you have weird behavior in Scribus, the first thing to do is copy the good <code>.scribus</code> directory over the current one and restart. This is also important if, you have lots of custom keyboard shortcuts.</li>
+<li><strong>A cool trick</strong> for precision adjustments. This may or may not work on your workstation, depending on how your wheel mouse is configured. You can use the mouse wheel with the spin boxes instead of clicking the arrows. For small steps, look carefully at the dialog below where I have put the cursor to the far right.Then spin the mouse wheel up and down to adjust the measurement or setting. This adjusts 10ths of a unit. For larger adjustments, put the cursor to the left side. For extra slow and precise adjustments 100th of a unit, Hold Crtl + Shift keys while moving the wheel mouse up and down. <br /><br /><br />
+<table width="100%"><tr><td align="center"><img src="images/spinbox1.png" title="Place the cursor as indicated by the arrow" alt="Place the cursor as indicated by the arrow" /></td></tr></table><br />
+</li>
+
+<li><strong>Let Scribus do the math for you.</strong>
+Almost every spinbox where you enter values with measurements can magically do math. You can mix and match units as well. Special units are: <em>pageheight, pagewidth, height, width</em></li></ul>
+<br />
+<table bgcolor="#d3d3d3" align="center" summary="* indicates only works when points are the unit" rules="rows" frame="border" cellpadding="5" cellspacing="5" width="85%">
+ <caption>Some Example Calculations</caption>
+ <tbody valign="middle" align="left">
+ <tr>
+ <td>8.5in/3</td>
+ <td>divide 8.5 inches by 3</td>
+ </tr>
+ <tr>
+ <td>pagewidth/4</td>
+ <td>divide the page width by 4 *This only works with points.</td>
+ </tr>
+ <tr>
+ <td>width*2</td>
+ <td>double the width of the selected object</td>
+ </tr>
+ <tr>
+ <td>5in+2p</td>
+ <td>add 2 picas to 5 inches</td>
+ </tr>
+ </tbody>
+</table>
+<br />
+<ul>
+<li><strong>Bonus</strong> - subscribe to the Scribus mailing list. You can get this in digest form daily. The list is active, polite and newbies and experts alike are welcome. Do not be shy to ask questions, Linux gurus might be new to DTP and vice versa. <a href="http://lists.scribus.info/mailman/listinfo/scribus">Scribus Mailing List Info</a> If you have tips you would like to share post them to the list. We will ensure they are considered and credited properly.</li>
+<li><strong>Extra Bonus</strong> - How to ask questions and file bug reports/issues on the mailing list? First, in newer versions go to <strong>Help > About </strong> and include the build info. <a href="menuhelp.html">More details</a> Then, look in the <a href="http://lists.scribus.info/pipermail/scribus/">mailing list archives</a> or on the <a href="http://bugs.scribus.net">Bug Tracker</a>, you might find your answer there. Then, make sure you add relevant details like which distribution, version of Scribus, versions of relevant packages or libraries. e.g. version of X-org if you have video or font issues. This helps the developers and other knowledgable users to respond quicker and more accurately. <strong>Note:</strong> If you are using a CVS version of Scribus, please also include the build date.</li>
+</ul>
+</body>
+</html>
/Scribus/doc/en/topten.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scribuscopyright.html
===================================================================
--- Scribus/doc/en/scribuscopyright.html (nonexistent)
+++ Scribus/doc/en/scribuscopyright.html (revision 13527)
@@ -0,0 +1,17 @@
+<qt>
+<title>Scribus Copyright</title>
+<p>Scribus Copyright 2001-2008 Franz Schmid and rest of the members of the Scribus Team. The "Scribus Team" is informally defined as the following people: Franz Schmid, Peter Linnell, Paul Johnson, Craig Bradney, Petr Vanek, Riku Leino, Craig Ringer, Andreas Vox, Jean Ghali, Hermann Kraus and Christoph Sch&auml;fer.</p>
+
+<p>This program is free software; you can redistribute it and/or modify it under the terms of the <a href=http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>GNU General Public License</a> as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.</p>
+
+<p>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.</p>
+
+<p>You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.</p>
+
+<p>In addition, as a special exception, the listed copyright holders above give permission to link the code of this program with the Trolltech AS Qt3 Commercially Licensed Dynamic Link Libraries (or with modified versions of Trolltech AS Qt3 Commercially Licensed Dynamic Link Libraries that use the same license as Trolltech AS Qt3 Commercially Licensed Dynamic Link Libraries), and distribute linked combinations including the two. You must obey the GNU General Public License in all respects for all of the code used other than Trolltech AS Qt3 Commercially Licensed Dynamic Link Libraries. If you modify this file, you may extend this exception to your version of the file, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.</p>
+
+
+<p>Antiword, which is shipped with the Windows version of Scribus is a separately licensed program under the GPL and the copyright license is included with the program.</p>
+
+<p>The hyphenation dictionaries are covered by their own copyrights and licenses. Those are included with the hyphenation files.</p>
+</qt>
\ No newline at end of file
/Scribus/doc/en/scribuscopyright.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/faq2.html
===================================================================
--- Scribus/doc/en/faq2.html (nonexistent)
+++ Scribus/doc/en/faq2.html (revision 13527)
@@ -0,0 +1,52 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Miscellaneous Questions</title>
+</head>
+<body>
+<a name="top"></a>
+<h2>Miscellaneous Questions</h2>
+<ul>
+ <li><a href="#9">Why is Scribus built with Qt and not some other toolkit?</a></li>
+ <li><a href="#10">Where does the name &quot;Scribus&quot; derive from ?</a></li>
+ <li><a href="#19">Why are there no import filters for Quark, InDesign or other commercial DTP applications?</a></li>
+ <li><a href="#20">So, how can I work with others who might have other page layout applications?</a></li>
+ <li><a href="#31">Is there or will there be a Microsoft Publisher importer ?</a></li>
+</ul>
+
+<h3>Answers</h3>
+
+<ol>
+ <li><a name="9"></a>
+When Franz Schmid launched the project, it was originally written in Python, but for performance reasons he decided to port it to C++. The toolkit with the most complete documentation at the time was Qt 2.2. The first Qt 2 release was 0.3 in 2001. Scribus was ported to Qt 3, after Scribus 0.6 was released.
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="10"></a>
+ <p class="faqquestion">Where does the name &quot;Scribus&quot; derive from ?</p>
+ <p>When Franz Schmid launched the project, the first working name was &quot;Open Page&quot;, but thought to be too generic. Scribus derives from the latin name of the official writers in Roman times, from which we get <i>scribe</i> or writer. This translates well in to many languages besides English. The German word is <i>schrift</i>, for example. Scribus is pronounced 'Skry-bus' long I, like sky. </p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="19"></a>
+ <p class="faqquestion">Why are there no import filters for Quark, InDesign or other commercial DTP applications?</p>
+ <p>There are several reasons why there are no import filters for commercial DTP applications.</p>
+ <ol>
+ <li>DTP file formats are very complex internally - probably the most complex on a PC. Creating import/export filters is a task far more complex than importing a spreadsheet or simpler word processing file formats. An engineer familiar with the internal file format of Pagemaker compared it to a 2m x 3m flow chart diagram with 6 point type. It was not until the arrival of InDesign 2.0 that reliable Pagemaker file import was possible in another DTP application, even though Adobe had the file format specs. Note: Not even InDesign CS can save to InDesign 2.0 format.</li>
+ <li>The file formats are sometimes protected by patents and are not documented publically.</li>
+ <li>So, is it unethical/illegal to apply hexedit to an InDesign file to reverse engineer the file format with hexedit or others for the purpose of creating the export/import plugins for Scribus?<br/>Possibly not, but given its a closed format we would expect to receive a warning from Adobe, as we did from Quark when there was a Quark importer in testing. We do not have the legal resources to challenge large proprietary software companies. Only one developer has been successful at reverse engineering Quark's software and it took a long legal case to succeed.</li>
+ <li>Developer constraints. It is the considered judgement of the development team that efforts to improve Scribus is a more valuable use of time.</li>
+ </ol>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="20"></a>
+ <p class="faqquestion">So, how can I work with others who might have other page layout a applications?</p>
+ <p>Use EPS, SVG or PDF as an exchange format. Scribus created PDFs can be easily imported into a number of commercial applications. SVG import is excellent for vector artwork. Scribus can import EPS files as long as they are conformant to the specs - this includes spot colors in DCS 2.0 files. The documentation has detailed notes covering these subjects. </p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="31"></a>
+ <p class="faqquestion">Is there or will there be a Microsoft Publisher importer ? </p>
+ <p>There is none and very unlikely to be provided by the Scribus Team. As with InDesign and Quark Xpress, these file formats are undocumented. They are difficult and sometimes impossible to reverse engineer. We would note that even users of different versions of Publisher have difficulties saving or opening .pub files on different versions. </p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+</ol>
+</body>
+</html>
/Scribus/doc/en/faq2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripter1.html
===================================================================
--- Scribus/doc/en/scripter1.html (nonexistent)
+++ Scribus/doc/en/scripter1.html (revision 13527)
@@ -0,0 +1,31 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scripting Scribus with Python</title>
+</head>
+<body>
+<h2>Scripting Scribus with Python</h2>
+
+<h4>Overview</h4>
+<p>This is the description how to use the Scripting Plugin for Scribus. The scripter allows you to use the powerful Python Language as a scripting language in Scribus. This can allow you to automate otherwise repetitive tasks among other features. </p>
+
+<p>This manual is the first version, by no means complete or fully accurate. Addtions to the scripter are made frequently, so a short note to the mailing list is in order ifyou have questions.</p>
+
+<p>There are some simple example scripts in the samples subdirectory where Scribus is installed. If you have created scripts which would be useful for other users, please feel free to upload it to www.scribus.net or mail mrdocs at scribus.info with an attachment. We hope to add a plug-in gallery to the main website in the future. </p>
+
+<h3>Using the Plugin</h3>
+
+<table width="100%"><tr><td align="center"><img src="images/Scripter.png" align="center" alt="Running a script" title="Running a script" /></td></tr></table>
+
+<p>To execute a Python Script select "Script-&gt;Execute Script..." Scribus will display a File select Box which allows you to select a Python Script. Below that, there is a menu item "Recent Scripts" where the most recently run scripts are listed. The number listed depends on your preferences setting. </p>
+
+<p>You can use many Python modules with this Plugin. The only exception are scripts who expect parameters from the command Line. They won't work because the plugin gives the Python interpreter an empty command line.</p>
+
+<p>The menu item "Show Console" gives you an interactive Python console, where you can execute commands directly. There is no need to do a "from scribus import *", this has already been done. You can use all the following commands in the Scripter API section directly without any prefix.</p>
+
+<p>You can findsome useful information about any script calling "Script-&gt;About Script...".</p>
+
+<p>You can display the full Scripter reference manual when you select "Help-&gt;Scripter Manual...".</p>
+
+</body>
+</html>
/Scribus/doc/en/scripter1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox16.html
===================================================================
--- Scribus/doc/en/toolbox16.html (nonexistent)
+++ Scribus/doc/en/toolbox16.html (revision 13527)
@@ -0,0 +1,15 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Fontmatrix</title>
+</head>
+<body>
+<h2>Fontmatrix</h2>
+<p>For those users coming from MacOSX or an even older MacOS one of the perceived missing parts on Linux is a nice graphical font manager. Enter <a href="http://fontmatrix.net">Fontmatrix</a>. While it is young, it has all the essentials to manage fonts both individually and in groups via "tags". Fontmatrix also has some nice features to preview not just sample text, but at scalable sizes along with the ability to view individual glpyhs. Even better, Fontmatrix supports Open Type fonts very well and in the future plans are advanced Open Type abilities. </p>
+
+<p>While Fontmatrix does not "activate" fonts on the fly for open applications, it can add and remove fonts quickly without messing with the important system fonts which all applications rely on. So for working with Scribus or other graphics applications, simply preview and add fonts as needed, then restart your application. Lastly, Fontmatrix can create "fontbooks" which are PDFs displaying each font. </p>
+
+<br /><br />
+<table width="100%"><tr><td align="center"><img src="images/fontmatrix.png" alt="Fontmatrix displaying the wonderful Gentium font." /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/en/images/prefsgeneral.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefsgeneral.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/external.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/external.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pdfx3-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pdfx3-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pdfxintent.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pdfxintent.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gsadv1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gsadv1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gsadv2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gsadv2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acroinfo.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acroinfo.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pdfxcolor.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pdfxcolor.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acro1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acro1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acro2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acro2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acro3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acro3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acropass.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acropass.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/toolbar1d.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/toolbar1d.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acrosec.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acrosec.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/toolbar1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/toolbar1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/toolbar3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/toolbar3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gimpoptions1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gimpoptions1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gimpoptions2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gimpoptions2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gimpoptions3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gimpoptions3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontmatrix.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontmatrix.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/kfontinstaller.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/kfontinstaller.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/docheader1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/docheader1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/oochart.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/oochart.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/docheader2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/docheader2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/colormgmtscreen.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/colormgmtscreen.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs6.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefsdisplay.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefsdisplay.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs8.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs8.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/ksnapshot.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/ksnapshot.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/formularz_export_PDF.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/formularz_export_PDF.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/cmsmodify1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/cmsmodify1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/batik1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/batik1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontsampler2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontsampler2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/formularz_pole_num.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/formularz_pole_num.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/layers1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/layers1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/layers2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/layers2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/imageeffects.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/imageeffects.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/wyslij_formularz.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/wyslij_formularz.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/formularz_js_sprawdzanie.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/formularz_js_sprawdzanie.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/colormanager1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/colormanager1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/colormanager2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/colormanager2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/cups1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/cups1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/cups2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/cups2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/scribus2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/scribus2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/ulica.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/ulica.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/printpreview.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/printpreview.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/siatka_jednostki_miar.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/siatka_jednostki_miar.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/siatka_menu.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/siatka_menu.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/oogettext1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/oogettext1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pdfeffect1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pdfeffect1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pdfeffect2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pdfeffect2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fonts2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fonts2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/result.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/result.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/xnview.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/xnview.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pagenumbering.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pagenumbering.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gsadv3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gsadv3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fonts.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fonts.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/scribustru4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/scribustru4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/Scripter_error_string.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/Scripter_error_string.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/scribuscms1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/scribuscms1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/htmlimport.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/htmlimport.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/monprof1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/monprof1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/monprof2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/monprof2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/docinfo2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/docinfo2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontprev.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontprev.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/monprof3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/monprof3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/monprof4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/monprof4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/printer1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/printer1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/printer3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/printer3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/symbole.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/symbole.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/RDF.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/RDF.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/hyphen1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/hyphen1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pstoedit1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pstoedit1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/hyphen2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/hyphen2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/gammagrayscale.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/gammagrayscale.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/hyphen3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/hyphen3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/swmenu.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/swmenu.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs10.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs10.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/docinfo.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/docinfo.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs11.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs11.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs12.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs12.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/htmlstyle.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/htmlstyle.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs15.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs15.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/inkscape.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/inkscape.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/formularz_nowy.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/formularz_nowy.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/wlasciwosci_pola.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/wlasciwosci_pola.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/spinbox1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/spinbox1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontpref1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontpref1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontpref2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontpref2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontpref3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontpref3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/ooeps1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/ooeps1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontpref4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontpref4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/swdialog.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/swdialog.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefs-mac-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefs-mac-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/svg1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/svg1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/lprof.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/lprof.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/printseps.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/printseps.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/formularz_js_skrypt.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/formularz_js_skrypt.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/pagetemplate1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/pagetemplate1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/acroreader5.1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/acroreader5.1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/CMakeLists.txt
===================================================================
--- Scribus/doc/en/images/CMakeLists.txt (nonexistent)
+++ Scribus/doc/en/images/CMakeLists.txt (revision 13527)
@@ -0,0 +1,9 @@
+INCLUDE_DIRECTORIES(
+"${CMAKE_SOURCE_DIR}/scribus"
+)
+
+#Install our image files
+FILE( GLOB SCRIBUS_DOC_EN_IMAGES_FILES *.jpg *.png )
+
+INSTALL(FILES ${SCRIBUS_DOC_EN_IMAGES_FILES} DESTINATION ${DOCDIR}en/images)
+
/Scribus/doc/en/images/CMakeLists.txt
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/images/krita1.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/krita1.jpg
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/automargins.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/automargins.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/after_short_words.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/after_short_words.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/before_short_words.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/before_short_words.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fonts3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fonts3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fonts4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fonts4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/printer2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/printer2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/fontsampler.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/fontsampler.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/Scripter.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/Scripter.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images/prefsblgrid1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
/Scribus/doc/en/images/prefsblgrid1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Index: Scribus/doc/en/images
===================================================================
--- Scribus/doc/en/images (nonexistent)
+++ Scribus/doc/en/images (revision 13527)
/Scribus/doc/en/images
Property changes:
Added: svn:ignore
## -0,0 +1,13 ##
+Makefile
+Makefile.in
+*.la
+*.lo
+*.moc.cpp
+*.moc
+*.o
+.deps
+.libs
+CVS
+scribus
+CMakeFiles
+cmake_install.cmake
\ No newline at end of property
Index: Scribus/doc/en/toolbox1.html
===================================================================
--- Scribus/doc/en/toolbox1.html (nonexistent)
+++ Scribus/doc/en/toolbox1.html (revision 13527)
@@ -0,0 +1,53 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Adobe Reader </title>
+</head>
+<body>
+<h2>Adobe Reader</h2>
+<h4>Using "Hidden" Features with Adobe Reader and Scribus</h4>
+
+<p>Adobe Reader&#174; 8.1+ is in my experience one of the essential tools to have when using Scribus. Although mostly a simple viewer, it has some advanced features which no other PDF viewer has in the Linux,*nix world: full support for JavaScript with a PDF (You did not know a PDF was scriptable? Scribus is unique in the Linux/*nix world for the ability to create scriptable interactive PDF forms) and detailed information which is embedded in the PDF, but viewable only in Adobe Reader.</p>
+
+<p>For MacOSX and Windows users, the above applies, as well. We do not recommend judging colors or correctness in the Mac Preview application either. If you are using Adobe Reader 8.x the settings recommendations apply as well. </p>
+
+<p> Moreover, while PDF is a published standard, Adobe invented PostScript on which PDF is based and has a commercial incentive to promote PDF on all platforms.</p>
+<h3>Hints for Scribus users:</h3>
+<p><strong>We highly recommend upgrading to the latest Adobe Reader 8.1.+ </strong>Simply put, there is nothing else more capable of rendering PDF correctly. Whatever your objections were to older versions (and there were some substantial ones, most notably on Linux), this later versions after 7.0.9 ameliorates the vast majority of them. It is far more stable, bug free and loads quicker than Version 6.x. On Linux it now has a modern look and feel. Versions after 7.0.9 also has direct support for CUPS and allows many extra options for printing. <strong>Any PDF rendering issues with Scribus exported PDF in other viewers should be cross-checked with Reader 7 before reporting bugs to us. </strong>
+<h4>Known Issues:</h4>
+We are aware of color mismatches when viewing PDFs which have some kinds of transparency in PDF 1.4. Yes, this has been duly reported as a bug to Adobe too.</p> <p><strong>Details:</strong> As soon there is an extended graphics state parameter dictionary present which contains any transparency blend space operators, Adobe Reader 7.x switches into CMYK mode showing incorrect colours. My local printer confirmed this strange behaviour even with files not generated by scribus, its clearly a bug from Adobe.</p>
+<h3>Tweaking the Viewer Preferences</h3>
+
+<p>Right away, getting the preferences right in Reader is important to ensure the default preferences to set improve the reliability for our purposes with Scribus. There are a many preferences in Reader 8. The page display part is the most important. </p>
+
+<table width="100%"><tr><td align="center"><img src="images/acro1.png" alt="Acrobat Reader General Preferences" /></td></tr></table>
+<p>This dialog is <strong>very</strong> important to set up properly for optimized viewing Scribus created PDFs.</p>
+
+<p><strong>Display Page to Edge</strong> will give you a larger viewing area to view your PDF.</p>
+
+ <p>Ensure <strong>Smooth Text, Smooth Line Art and Smooth Images</strong> are enabled as they apply a bit of anti-aliasing when viewing. If you send someone a Scribus created PDF and they complain the text or gradients) look like barbed wire or are "banded", advise the user to enable these settings which are commonly available on all later versions of Acrobat Reader - regardless of platform. There are other cross-platform fonts hints in the PDF Export Options section. <strong>Cool Type</strong> is a feature specific for making PDF readable on LCD laptop screens. It is a way of adjusting the anti-aliasing and sub-pixel rendering. Otherwise, leave it unchecked.</p>
+<p>If you are creating Scribus files with transparency effects and export PDF 1.4 (PDF 1.3 does not support transparency), you can enable <strong>Show Transparency Grid</strong>. </p>
+<table width="100%"><tr><td align="center"><img src="images/acro2.png" alt="" title="" /></td></tr></table>
+
+<p>The other options are mostly for the web browser plug-in. I find splash screens a bother, so I leave that unchecked.</p>
+<table width="100%"><tr><td align="center"><img src="images/acro3.png" alt="Acrobat Reader Screen shot" title="Acrobat Reader Screenshot" /></td></tr></table>
+<p>Next, looking at the Reader window above, there are 3 features which can be useful:</p>
+<ol>
+ <li><strong>Thumbnails (which Scribus can optionally embed in the PDF when exporting) are useful for navigating.</strong> </li>
+ <li><strong>The corner triangle</strong> is a short cut to <strong>View &#062; Document Info, Document Fonts, Document Security</strong>.</li>
+ <li><strong>Notes, which are non-printing, can be used to give definitions or hints in a document.</strong> What we care about is document information. Within Scribus <strong>File &#062; Document Setup &#062; Document Information</strong> there is a panel to enter author and title of the document. This shows up in a panel below:</li>
+</ol>
+<table width="100%"><tr><td align="center"><img src="images/acroinfo.png" alt="Acrobat Reader General Info Panel" /></td></tr></table>
+<p>This shows the document size, date of creation and creating application. This information is automatically embedded. Scribus can optionally add author and document title. In addition, this shows Dublin Core RDF (Resource Definition Format) and document security strength.</p>
+<p><strong>Document Security.</strong> Scribus has the ability to encrypt a document with specific user rights. If you enable Security in the PDF export dialog, when you export PDF 1.3, encryption is 40 bit strength.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/acropass.png" alt="Password Dialog for Opening a Protected PDF" title="Password Dialog for Opening a Protected PDF" /></td></tr></table>
+<p>If you export a PDF 1.4 file, encryption is 128 bit strength:</p>
+<table width="100%"><tr><td align="center"><img src="images/acrosec.png" alt="Acrobat Reader Security Panel" /></td></tr></table>
+<p><strong>Annotations</strong> are non-printing notes which Scribus can optionally embed within a PDF. This is really simple. Create a text frame. Then add your notes and right click, select PDF Options and check "Is PDF Annotation".</p>
+<p>For other "hidden" features, read through the online help, which is actually a PDF. Beginning with page 10, there are a number of less well known features, including the command line options. The command line options are specific to Linux/Unix and include some neat options to export PDF into PostScript. There are also hints on settings specific to Acrobat Reader in <code>~/Xdefaults</code>.</p>
+<p><strong>Advanced Settings</strong> - Fortunately, Adobe provided a graphical UI choice for enabling/disabling local fonts. <strong>Document &gt; Use Local Fonts </strong>. What this choice does is enable Acrobat to use locally installed fonts which are named in the PDF, if it can find them in your font path.</p>
+
+<p>I recommend you set this to <strong>disable</strong> for use with Scribus. Why? As is often the case, PDFs you create in Scribus will be sent to other users who are not running on Linux. What you will want in most cases is realistic view <strong>without</strong> your fonts. Thus, the only reliable way of ensuring your doc will view properly anywhere is to embed the fonts. You can convert to outlines in the font preferences panel to save file size. This particularly important when using the Ghostscript fonts, like the Nimbus family. Acrobat Reader does a poor job of simulating them with its own built-in multi-master fonts.</p>
+</body>
+</html>
/Scribus/doc/en/toolbox1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/irc.html
===================================================================
--- Scribus/doc/en/irc.html (nonexistent)
+++ Scribus/doc/en/irc.html (revision 13527)
@@ -0,0 +1,44 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus IRC</title>
+</head>
+<body>
+<h2>Scribus IRC</h2>
+
+Joining (clickable link): <a href="irc://irc.freenode.net/#scribus">irc://irc.freenode.net/#scribus</a>
+
+<h4>Some Hints:</h4>
+<p>One part of the Scribus community is the online one: IRC or Internet Relay Chat. For some, this might be quite unfamiliar as a support channel. However, it works really well we think. Usually, at least one Scribus Team member or knowledgeable user is around. Keep in mind the best time is Central European Time, especially evenings, when it tends to be liveliest. For some, IRC has connotations of flame wars and lots of arguing, but #scribus <strong>is</strong> a friendly congenial place. Flame fests and trolling are just not tolerated in #scribus. A good primer: <a href="http://fnmueller.wordpress.com/2008/02/23/rules-of-engagement-the-ten-commandments-of-irc/">Rules of Engagement - The ten commandments of IRC</a>, also <a href="http://de.opensuse.org/IRC-Einführung">in German </a></p>.
+
+<h4>Don't be shy, just ask.</h4>
+<p></p>
+When joining for the first time, say 'hi' and ask. #scribus (the '#' indicates a channel) is a friendly place. A short introduction is fine. For those who do not speak English, have no fear. First try in English, but there are a number of folks in #scribus who can speak a wide variety of languages. Among the Team Members, we can count at least seven languages spoken well enough to converse in IRC. Other regulars cover probably another half dozen.
+
+<h4>Give Details</h4>
+<p>It helps to know more than, "Something broke and now blah does not work." </p>
+<ul>
+<li>Start by saying which platform you are on and what version of Qt, knowing this immediately is always helpful. Some issues are platform or distribution specific.</li>
+<li>Describe your problem in a way which makes it easy for others to answer. </li>
+<li>Be prepared to answer specific questions about which versions of applications are installed.</li></ul>
+
+<h4>Be Patient</h4>
+
+<p>IRC is wonderful for instant direct nature, but sometimes folks are busy doing other things like coding Scribus :-). On IRC, often regulars and the developers are logged in 24 hours a day. This is called "idling". We might be away from the computer completely. That does not mean you need to wait days for an answer. Also, #scribus has a friendly bot called mrscribe who can relay messages easily. Meet mrscribe below.</p>
+
+<h4>IRC is not an excuse for not reading the documentation.</h4>
+
+<p>At the very least, make sure you have read the FAQ's and read the relevant sections of the docs. If someone replies with an answer (it might be mrscribe), with a link, that means this issue has been asked before - more than once. That also means that info is easily found elsewhere. A lot of time and effort was put into writing the documentation, as imperfect as it may be. They are written to help <strong>you</strong>.</p>
+
+<h4>Meet MrScribe</h4>
+<p>MrScribe is our friendly "bot" Bots are very useful in IRC, as they help automate certain housekeeping tasks. MrScribe also is full of fun facts, which are useful for helping others. You can learn all about MrScribe here: <a href="http://supybot.com/">http://supybot.com/</a>.</p>
+
+<h4>Some IRC Client Suggestions</h4>
+<p>Given that we have IRC chat clients running 7/24 on our PC's, a couple we can recommend:</p>
+<ul>
+ <li><a href="http://X-chat.org">X-Chat</a> - a mature GTK based client which runs on Linux and Windows. The Windows version also is alternatively available from: <a href="http://www.psyon.org/projects/xchat-win32/">http://www.psyon.org/projects/xchat-win32/</a> or <a href="http://xchataqua.sourceforge.net/twiki/bin/view/Main/WebHome">X-Chat For Aqua on MacOSX</a> </li>
+ <li><a href="http://konversation.kde.org/">Konversation</a> - Very stable, full featured IRC client which is easy to use for newbies. </li>
+ </ul>
+<h4>Lounging</h4>
+<p>Once you have your answer in hand, you are not obligated to disappear. #scribus is not just for hard core developers. Newbies with Scribus are just as welcome. Often, you can recognize the developers easily, as they usually have "operator" status. IRC is where we learn as developers, where people are struggling with some feature or where something is confusing in the GUI. Lounging is a good way to learn lots of tidbits about the newest features, as well as learn some good usage tricks from gurus. So, when the mood strikes, pull up a chair, kick up your feet and enjoy. </p></body>
+</html>
\ No newline at end of file
/Scribus/doc/en/irc.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox2.html
===================================================================
--- Scribus/doc/en/toolbox2.html (nonexistent)
+++ Scribus/doc/en/toolbox2.html (revision 13527)
@@ -0,0 +1,12 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+<title>Other PDF/PS Viewers</title>
+</head>
+<body>
+<h2>Other PDF Viewers</h2>
+<p>Another useful PDF viewer to use with Scribus is GSview which is a graphical viewer/front end to Ghostscript. The latest version (4.9) with Ghostscript 8.5+ work very nicely together allow you to convert PS to PDF, as well as view and convert EPS, PS and PDF files among other tools. GSview runs natively on Linux/Unix. OS/2 and Windows. More details are in <a href="gsview.html">GSview and Scribus</a>.</p>
+<p><strong>Kpdf 3.5+ / <a href="http://www.foolabs.com/xpdf/">Xpdf</a> </strong> The most recent Kpdf in KDE 3.4 shows me the the developers "get it". Based on Xpdf 3.x it has many nice touches and seems to be a pretty fast renderer. I say this not as a KDE fanboy, but based on using quite a bit in comparison to the larger Adobe Readers. One other note, look through Settings and enable "aggressive" in the performance options. If you have the required memory, enabling this makes a big difference in loading larger or complex documents. You still might want Xpdf 3.02+ from Foolabs, as it includes some command line tools for converting PDFs to PS. To display properly embedded fonts with Xpdf in all PDFs, not just Scribus ones, you should read the Xpdf man page about setting up the fonts paths correctly via the .xpdfrc file. Otherwise, embedded fonts may not display properly. One known limitation is the inability to display transparency in Scribus generated PDFs.</p>
+<p>In KDE 4, <a href="http://okular.kde.org/">Okular</a>, the sucessor to KPDF is a versatile PDF viewer which also can view a number of different image formats like Tiff and PSD. </p>
+</body>
+</html>
/Scribus/doc/en/toolbox2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox15.html
===================================================================
--- Scribus/doc/en/toolbox15.html (nonexistent)
+++ Scribus/doc/en/toolbox15.html (revision 13527)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Krita</title>
+</head>
+<body>
+<h2>Krita</h2>
+<p>Seemingly rising from the ashes, <a href="http://koffice.org/krita/">Krita</a>, a part of the <a href="http://koffice.org/">KDE Office</a> suite, has become a wonderful application focused on natural painting. Using a brushes metaphor on screen, it has some innovative and quite interesting features like the ability to emulate the way watercolors dry on canvas, a filters gallery to display previews of each filter, adjustment layers, layer groups and tools to precisely manipulate brush strokes. That alone would be worth adding it to your publishing toolbox for the occasional artwork.</p><p> The bonus for Scribus users is its versatile handling of a large number of formats and color spaces. Not only RGB, but CMYK, Greyscale (up to 16 bit) and L*a*b are handled using the same littlecms color engine as Scribus. Krita fully supports RGB to CMYK conversion needs in a simple easy to use manner, but can also convert 16 bit images into 8 bit to import into Scribus. (Scribus will support 16-bit images and possibly higher in the future.)</p>
+
+<p><strong>Notes:</strong></p>
+<ul>
+ <li>There is one limitation in the current 1.6.x Krita in the way resolution works when Krita writes an image to disk. Thus, Scribus will always interpret the resolution as 72 DPI, which is not usually high enough for good quality print, so rescaling may need to be done within Scribus. </li>
+ <li>Krita is only available on BSD, Linux, MacOSX (via fink) and Unix. Krita 2 is expected to be available as a native Win32 application. </li>
+ <li>For importing into Scribus, exporting Tiff from Krita with LZW compression should yield good results and Krita reliably embeds ICC profiles into the images to make color matching from print to screen much easier.</li>
+ </ul>
+
+<br /><br />
+<table width="100%"><tr><td align="center"><img src="images/krita1.jpg" alt="Krita showing a color managed CMYK image." /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/en/pdflavor.html
===================================================================
--- Scribus/doc/en/pdflavor.html (nonexistent)
+++ Scribus/doc/en/pdflavor.html (revision 13527)
@@ -0,0 +1,30 @@
+<qt>
+
+ <title>PDF Flavors</title>
+<h2>PDF Flavor - Which one is best for you ?</h2>
+
+<p>Answering that question, brings up many questions and bears some discussion of what are the differences. A higher version does not presume a "better" PDF and in some cases works against you.</p>
+<h4>What is the difference between versions PDF 1.2 to PDF 1.7 ?</h4>
+<p>Each version roughly parallels the release of a major version of Adobe Acrobat. The short overly simple answers:
+</p>
+<ul>
+<li>PDF 1.2 = Acrobat 3.0 - relatively obsolete now
+</li>
+<li>PDF 1.3 = Acrobat 4.0 - The first version of PDF which truly had all the needed features to support "press-ready" PDF's including color management, ICC profiles etc. It also added javascript, interactive and multimedia capabilities. This standard is probably the safest to send if you are unsure of the capabilities of the receiver of your file. PDF/X-3 and a number of commercial print work flows are based on PDF 1.3.</li>
+<li>PDF 1.4 = Acrobat 5.0 - Actually, introduced with Illustrator 9. The main difference to concern Scribus users is both transparency and alpha transparency capabilites. This makes a major difference in where a PDF with these features can be printed. It takes either the latest commercial RIPs or certain Level 3 PostScript printers to use these features properly. Moreover, not all Level 3 PostScript printers will handle transparency. The latest versions of Ghostscript support the advanced PDF 1.4 features Scribus can create when exporting PDF.<strong>The most distinguishing feature of PDF 1.4 for Scribus is the ability to export true transparency in PDF. </strong>Note: Often, the only way you will be able to print exactly the transparency features viewed on-screen is to export PDF 1.4 and print from Acrobat Reader 5.x or newer. </li>
+<li>PDF 1.5 = Acrobat 6.0 - Among the most interesting for Scribus users: many improvements for "press-ready" PDF, the capability to have true layering within the PDF, PDF-X "pre-flight" capability, more security and interactive features, like the ability to add comments which are separate from the original doc. Scribus can support many PDF 1.5 features in the 1.3.x development version. PDF 1.5 can also support more sophisticated compression options for images using JPEG 2000. </li>
+<li>PDF 1.6 = Acrobat 7.0 - Refinements of the 1.5 features and more extensive use of PKI and digital signing for document control, as well as, extended commenting for group collaboration. Where it concerns Scribus, nothing of importance, except the release of Adobe Reader 7.0 for Linux. </li>
+<li>PDF 1.7 = Acrobat 8.x - Added 3D capabilities</li>
+</ul>
+<p>In deciding which version you choose for export, you need to consider the following: </p>
+<ul>
+<li><strong>Where am I ultimately printing ?</strong> - If you are planning to have your files printed commercially, always try to ask the printer first.</li>
+<li><strong>Does my document have transparency features ?</strong> - See above and ensure the rest of your equipment or workflow can support PDF 1.4. </li>
+<li><strong>I am exporting PDF forms. How do I know end receivers of my file can use it ?</strong> - Do you know the version of Acro Reader your users will have ? The safest is to use PDF 1.3 or 1.4.</li>
+<li><strong>Do I need layers ?</strong> - Only PDF 1.5 supports this and only in the 1.3.x version of Scribus. Be aware support for PDF 1.5 is not complete in most open source viewers. Ghostscript 8.5x does support some, but not all PDF 1.5 features. </li>
+</ul>
+<p></p>
+<h4>What about other kinds of PDF I have read about, like PDF-X and PDF-A ?</h4>
+<p>PDF marked as any of the following: PDF/X-1:2001, X-1a:2001 and 2003; X-2:2003; X-3:2002 and 2003 are all different flavors of PDF-X, which is a way of creating a PDF with certain criteria for pre-press. Scribus supports the latest PDF-X-2:2003. Support for other versions of PDF/X is planned. </p>
+<p>PDF-A is an ISO standard based on PDF 1.4 for long term storage of public documents in an open format.</p>
+</qt>
\ No newline at end of file
/Scribus/doc/en/pdflavor.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-select.html
===================================================================
--- Scribus/doc/en/scripterapi-select.html (nonexistent)
+++ Scribus/doc/en/scripterapi-select.html (revision 13527)
@@ -0,0 +1,37 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Selecting Objects</title>
+</head>
+<body>
+<h2>Selecting Objects</h2>
+
+<dl>
+
+<dt><a name="-deselectAll"><strong>deselectAll</strong></a>(...)</dt>
+<dd><code>deselectAll()</code>
+<p>Deselects all objects in the whole document.</p></dd></dt>
+
+<dt><a name="-getSelectedObject"><strong>getSelectedObject</strong></a>(...)</dt>
+<dd><code>getSelectedObject([nr]) -&gt; string</code>
+<p>Returns the name of the selected object. "nr" if given indicates the number of the selected object, e.g. 0 means the first selected object, 1 means the second selected Object and so on.</p></dd>
+
+<dt><a name="-moveSelectionToBack"><strong>moveSelectionToBack</strong></a>(...)</dt>
+<dd><code>moveSelectionToBack()</code>
+<p>Moves the current selection to the back.</p></dd>
+
+<dt><a name="-moveSelectionToFront"><strong>moveSelectionToFront</strong></a>(...)</dt>
+<dd><code>moveSelectionToFront()</code>
+<p>Moves the current selection to the front.</p></dd>
+
+<dt><a name="-selectionCount"><strong>selectionCount</strong></a>(...)</dt>
+<dd><code>selectionCount() -&gt; integer</code>
+<p>Returns the number of selected objects.</p></dd>
+
+<dt><a name="-selectObject"><strong>selectObject</strong></a>(...)</dt>
+<dd><code>selectObject("name")</code>
+<p>Selects the object with the given "name".</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-select.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-object.html
===================================================================
--- Scribus/doc/en/scripterapi-object.html (nonexistent)
+++ Scribus/doc/en/scripterapi-object.html (revision 13527)
@@ -0,0 +1,141 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Creating and Destroying Objects</title>
+</head>
+<body>
+<h2>Creating and Destroying Objects</h2>
+
+<dl>
+
+<dt><a name="-createCharStyle"><strong>createCharStyle</strong></a>(...)</dt>
+<dd><code>createCharStyle(...)</code>
+<p>Creates a character style. This function takes the following keyword parameters:
+<ul>
+<li>"name" [required] -> name of the char style to create</li>
+<li>"font" [optional] -> name of the font to use</li>
+<li>fontsize [optional] -> font size to set (double)</li>
+<li>"features" [optional] -> nearer typographic details can be defined by a string that might contain the following phrases comma-seperated (without spaces!):
+<ul>
+ <li>inherit</li>
+ <li>bold</li>
+ <li>italic</li>
+ <li>underline</li>
+ <li>underlinewords</li>
+ <li>strike</li>
+ <li>superscript</li>
+ <li>subscript</li>
+ <li>outline</li>
+ <li>shadowed</li>
+ <li>allcaps</li>
+ <li>smallcaps</li>
+</ul>
+</li>
+<li>"fillcolor" [optional], "fillshade" [optional] -> specify fill options</li>
+<li>"strokecolor" [optional], "strokeshade" [optional] -> specify stroke options</li>
+<li>baselineoffset [optional] -> offset of the baseline</li>
+<li>shadowxoffset [optional], shadowyoffset [optional] -> offset of the shadow if used</li>
+<li>outlinewidth [optional] -> width of the outline if used</li>
+<li>underlineoffset [optional], underlinewidth [optional] -> underline options if used</li>
+<li>strikethruoffset [optional], strikethruwidth [optional] -> strikethru options if used</li>
+<li>scaleh [optional], scalev [optional] -> scale of the chars</li>
+<li>tracking [optional] -> tracking of the text</li>
+<li>"language" [optional] -> language code</li>
+</ul>
+</p>
+</dd>
+
+<dt><a name="-createBezierLine"><strong>createBezierLine</strong></a>(...)</dt>
+<dd><code>createBezierLine(list, ["name"]) -&gt; string</code>
+<p>Creates a new bezier curve and returns its name. The points for the bezier curve are stored in the list "list" in the following order: [x1, y1, kx1, ky1, x2, y2, kx2, ky2...xn. yn, kxn. kyn] In the points list, x and y mean the x and y coordinates of the point and kx and ky meaning the control point for the curve. The coordinates are given in the current measurement units of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used. May raise ValueError if an insufficient number of points is passed or if the number of values passed don't group into points without leftovers.</p></dd>
+
+<dt><a name="-createEllipse"><strong>createEllipse</strong></a>(...)</dt>
+<dd><code>createEllipse(x, y, width, height, ["name"]) -&gt; string</code>
+<p>Creates a new ellipse on the current page and returns its name. The coordinates are given in the current measurement units of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further referencing of that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.</p></dd></dt>
+
+<dt><a name="-createImage"><strong>createImage</strong></a>(...)</dt>
+<dd><code>createImage(x, y, width, height, ["name"]) -&gt; string</code>
+<p>Creates a new picture frame on the current page and returns its name. The coordinates are given in the current measurement units of the document. "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.</p></dd>
+
+<dt><a name="-createLine"><strong>createLine</strong></a>(...)</dt>
+<dd><code>createLine(x1, y1, x2, y2, ["name"]) -&gt; string</code>
+<p>Creates a new line from the point(x1, y1) to the point(x2, y2) and returns its name. The coordinates are given in the current measurement unit of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.</p></dd>
+
+<dt><a name="-createParagraphStyle"><strong>createParagraphStyle</strong></a>(...)</dt>
+<dd><code>createParagraphStyle(...)</code>
+<p>Creates a paragraph style. This function takes the following keyword parameters:
+<ul>
+<li>"name" [required] -> specifies the name of the paragraphstyle to create</li>
+<li>linespacingmode [optional] -> specifies the linespacing mode; possible modes are:
+<ul>
+ <li>fixed linespacing: 0</li>
+ <li>automatic linespacing: 1</li>
+ <li>baseline grid linespacing: 2</li>
+</ul>
+</li>
+<li>linespacing [optional] -> specifies the linespacing if using fixed linespacing</li>
+<li>alignment [optional] -> specifies the alignment of the paragraph
+<ul>
+ <li>left: 0</li>
+ <li>center: 1</li>
+ <li>right: 2</li>
+ <li>justify: 3</li>
+ <li>extend: 4</li>
+</ul>
+</li>
+<li>leftmargin [optional], rightmargin [optional] -> specify the margin</li>
+<li>gapbefore [optional], gapafter [optional] -> specify the gaps to the heading and following paragraphs</li>
+<li>firstindent [optional] -> the indent of the first line</li>
+<li>hasdropcap [optional] -> specifies if there are caps (1 = yes, 0 = no)</li>
+<li>dropcaplines [optional] -> height (in lines) of the caps if used</li>
+<li>dropcapoffset [optional] -> offset of the caps if used</li>
+<li>"charstyle" [optional] -> char style to use</li>
+</ul>
+</p>
+</dd>
+
+<dt><a name="-createPathText"><strong>createPathText</strong></a>(...)</dt>
+<dd><code>createPathText(x, y, "textbox", "beziercurve", ["name"]) -&gt; string</code>
+<p>Creates a new pathText by merging the two objects "textbox" and "beziercurve" and returns its name. The coordinates are given in the current measurement unit of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.
+May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if one or both of the named base object don't exist.</p></dd>
+
+<dt><a name="-createPolyLine"><strong>createPolyLine</strong></a>(...)</dt>
+<dd><code>createPolyLine(list, ["name"]) -&gt; string</code>
+<p>Creates a new polyline and returns its name. The points for the polyline are stored in the list "list" in the following order: [x1, y1, x2, y2...xn. yn]. The coordinates are given in the current measurement units of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used. May raise ValueError if an insufficient number of points is passed or if the number of values passed don't group into points without leftovers.</p></dd>
+
+<dt><a name="-createPolygon"><strong>createPolygon</strong></a>(...)</dt>
+<dd><code>createPolygon(list, ["name"]) -&gt; string</code>
+<p>Creates a new polygon and returns its name. The points for the polygon are stored in the list "list" in the following order: [x1, y1, x2, y2...xn. yn]. At least three points are required. There is no need to repeat the first point to close the polygon. The polygon is automatically closed by connecting the first and the last point. The coordinates are given in the current measurement units of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further access to that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used. May raise ValueError if an insufficient number of points is passed or if the number of values passed don't group into points without leftovers.</p></dd>
+
+<dt><a name="-createRect"><strong>createRect</strong></a>(...)</dt>
+<dd><code>createRect(x, y, width, height, ["name"]) -&gt; string</code>
+<p>Creates a new rectangle on the current page and returns its name. The coordinates are given in the current measurement units of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name to reference that object in future. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.</p></dd>
+
+<dt><a name="-createText"><strong>createText</strong></a>(...)</dt>
+<dd><code>createText(x, y, width, height, ["name"]) -&gt; string</code>
+<p>Creates a new text frame on the actual page and returns its name. The coordinates are given in the actual measurement unit of the document (see UNIT constants). "name" should be a unique identifier for the object because you need this name for further referencing of that object. If "name" is not given Scribus will create one for you.</p>
+<p>May raise <a href="scripterapi.html#NameExistsError">NameExistsError</a> if you explicitly pass a name that's already used.</p></dd>
+
+<dt><a name="-deleteObject"><strong>deleteObject</strong></a>(...)</dt>
+<dd><code>deleteObject(["name"])</code>
+<p>Deletes the item with the name "name". If "name" is not given the currently selected item is deleted.</p></dd>
+
+<dt><a name="-getAllStyles"><strong>getAllStyles</strong></a>(...)</dt>
+<dd><code>getAllStyles() -&gt; list</code>
+<p>Return a list of the names of all paragraph styles in the current document.</p></dd>
+
+<dt><a name="-objectExists"><strong>objectExists</strong></a>(...)</dt>
+<dd><code>objectExists(["name"]) -&gt; bool</code>
+<p>Test if an object with specified name really exists in the document. The optional parameter is the object name. When no object name is given, returns True if there is something selected.</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-object.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-doc.html
===================================================================
--- Scribus/doc/en/scripterapi-doc.html (nonexistent)
+++ Scribus/doc/en/scripterapi-doc.html (revision 13527)
@@ -0,0 +1,162 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Document related Commands</title>
+</head>
+<body>
+<h2>Document related Commands</h2>
+
+<dl>
+
+<dt><a name="-closeDoc"><strong>closeDoc</strong></a>(...)</dt>
+<dd><code>closeDoc()</code>
+<p>Closes the current document without prompting to save.</p>
+<p>May throw <a href="#NoDocOpenError">NoDocOpenError</a> if there is no document to close</p></dd>
+
+<dt><a name="-docChanged"><strong>docChanged</strong></a>(...)</dt>
+<dd><code>docChanged(bool)</code>
+<p>Enable/disable save icon in the Scribus icon bar and the Save menu item. It's
+useful to call this procedure when you're changing the document, because Scribus
+won't automatically notice when you change the document using a script.</p></dd>
+
+<dt><a name="-getUnit"><strong>getUnit</strong></a>(...)</dt>
+<dd><code>getUnit() -&gt; integer (Scribus unit constant)</code>
+<p>Returns the measurement units of the document. The returned value will be one of the UNIT_* constants: UNIT_INCHES, UNIT_MILLIMETERS, UNIT_PICAS, UNIT_POINTS.</p></dd>
+
+<dt><a name="-haveDoc"><strong>haveDoc</strong></a>(...)</dt>
+<dd><code>haveDoc() -&gt; bool</code>
+<p>Returns true if there is a document open.</p></dd>
+
+<!--<dt><a name="-importSVG"><strong>importSVG</strong>(...)</a></dt>
+<dd><code>importSVG("string")</code>
+<p>The "string" must be a valid filename for a SVG image. The text must be UTF8 encoded or 'unicode' string(recommended).</p></dd> -->
+
+<dt><a name="-loadStylesFromFile"><strong>loadStylesFromFile</strong></a>(...)</dt>
+<dd><code>loadStylesFromFile("filename")</code>
+<p>Loads paragraph styles from the Scribus document at "filename" into the current document.</p></dd>
+
+<dt><a name="-masterPageNames"><strong>masterPageNames</strong>(...)</a></dt>
+<dd><code>masterPageNames()</code>
+<p>Returns a list of the names of all master pages in the document.</p></dd>
+
+<dt><a name="-newDoc"><strong>newDoc</strong></a>(...)</dt>
+<dd><code>newDoc(size, margins, orientation, firstPageNumber, unit, facingPages, firstSideLeft) -&gt; bool</code>
+<p>WARNING: Obsolete procedure! Use <a href="#-newDocument">newDocument</a> instead.</p>
+<p>Creates a new document and returns true if successful. The parameters have the
+following meaning:</p>
+<ul>
+ <li>size = A tuple (width, height) describing the size of the document. You can use predefined constants named PAPER_&lt;paper_type&gt; e.g. PAPER_A4 etc.</li>
+ <li>margins = A tuple (left, right, top, bottom) describing the document margins</li>
+ <li>orientation = the page orientation - constants PORTRAIT, LANDSCAPE</li>
+ <li>firstPageNumber = is the number of the first page in the document used for page numbering. While you'll usually want 1, it's useful to have higher numbers if you're creating a document in several parts.</li>
+ <li>unit: this value sets the measurement units used by the document. Use a predefined constant for this, one of: UNIT_INCHES, UNIT_MILLIMETERS, UNIT_PICAS, UNIT_POINTS.</li>
+ <li>facingPages = FACINGPAGES, NOFACINGPAGES</li>
+ <li>firstSideLeft = FIRSTPAGELEFT, FIRSTPAGERIGHT</li>
+ </ul>
+<p>The values for width, height and the margins are expressed in the given unit for the document. PAPER_* constants are expressed in points. If your document is not in points, make sure to account for this.</p>
+<p>example: <a href="#-newDoc">newDoc</a>(PAPER_A4, (10, 10, 20, 20), LANDSCAPE, 1, UNIT_POINTS, FACINGPAGES, FIRSTPAGERIGHT)</p></dd>
+
+<dt><a name="-newDocument"><strong>newDocument</strong>(...)</a></dt>
+<dd><code>newDocument(size, margins, orientation, firstPageNumber,
+ unit, pagesType, firstPageOrder, numPages) -&gt; bool</code>
+<p>Creates a new document and returns true if successful. The parameters have the
+following meaning:
+<ul>
+<li>size = A tuple (width, height) describing the size of the document. You can
+use predefined constants named PAPER_&lt;paper_type&gt; e.g. PAPER_A4 etc.</li>
+<li>margins = A tuple (left, right, top, bottom) describing the document
+margins</li>
+<li>orientation = the page orientation - constants PORTRAIT, LANDSCAPE</li>
+<li>firstPageNumer = is the number of the first page in the document used for
+pagenumbering. While you'll usually want 1, it's useful to have higher
+numbers if you're creating a document in several parts.</li>
+<li>unit: this value sets the measurement units used by the document. Use a
+predefined constant for this, one of: UNIT_INCHES, UNIT_MILLIMETERS,
+UNIT_PICAS, UNIT_POINTS.</li>
+<li>pagesType = One of the predefined constants PAGE_n. PAGE_1 is single page,
+PAGE_2 is for double sided documents, PAGE_3 is for 3 pages fold and
+PAGE_4 is 4-fold.</li>
+<li>firstPageOrder = What is position of first page in the document.
+Indexed from 0 (0 = first).</li>
+<li>numPage = Number of pages to be created.</li>
+</ul>
+<p>The values for width, height and the margins are expressed in the given unit
+for the document. PAPER_* constants are expressed in points. If your document
+is not in points, make sure to account for this.</p>
+<p>example: newDocument(PAPER_A4, (10, 10, 20, 20), LANDSCAPE, 7, UNIT_POINTS,
+PAGE_4, 3, 1)</p>
+<p>May raise ScribusError if is firstPageOrder bigger than allowed by pagesType.</p>
+</dd>
+
+<dt><a name="-openDoc"><strong>openDoc</strong></a>(...)</dt>
+<dd><code>openDoc("name")</code>
+<p>Opens the document "name".</p>
+<p>May raise ScribusError if the document could not be opened.</p></dd>
+
+<dt><a name="-placeEPS"><strong>placeEPS</strong>(...)</a></dt>
+<dd><code></code>
+<p>placeEPS("filename", x, y) Places the EPS "filename" onto the current
+page, x and y specify the coordinate of the topleft corner of the EPS
+placed on the page If loading was successful, the selection contains
+the imported EPS</p></dd>
+
+<dt><a name="-placeODG"><strong>placeODG</strong>(...)</a></dt>
+<dd><code></code>
+<p>placeODG("filename", x, y) Places the ODG "filename" onto the current
+page, x and y specify the coordinate of the topleft corner of the ODG
+placed on the page If loading was successful, the selection contains
+the imported ODG</p></dd>
+
+<dt><a name="-placeSVG"><strong>placeSVG</strong>(...)</a></dt>
+<dd><code></code>
+<p>placeSVG("filename", x, y) Places the SVG "filename" onto the current
+page, x and y specify the coordinate of the topleft corner of the SVG
+placed on the page If loading was successful, the selection contains
+the imported SVG</p></dd>
+
+<dt><a name="-placeSXD"><strong>placeSXD</strong>(...)</a></dt>
+<dd><code></code>
+<p>placeSXD("filename", x, y) Places the SXD "filename" onto the current
+page, x and y specify the coordinate of the topleft corner of the SXD
+placed on the page If loading was successful, the selection contains
+the imported SXD</p></dd>
+
+<dt><a name="-saveDoc"><strong>saveDoc</strong></a>(...)</dt>
+<dd><code>saveDoc()</code>
+<p>Saves the current document with its current name, returns true if successful. If the document has not already been saved, this may bring up an interactive save file dialog. If the save fails, there is currently no way to tell.</p></dd>
+
+<dt><a name="-saveDocAs"><strong>saveDocAs</strong></a>(...)</dt>
+<dd><code>saveDocAs("name")</code>
+<p>Saves the current document under the new name "name" (which may be a full or
+relative path).</p>
+<p>May raise ScribusError if the save fails.</p></dd>
+
+<dt><a name="-setInfo"><strong>setInfo</strong></a>(...)</dt>
+<dd><code>setInfo("author", "info", "description") -&gt; bool</code>
+<p>Sets the document information. "Author", "Info", "Description" are strings.</p></dd>
+
+<dt><a name="-setMargins"><strong>setMargins</strong></a>(...)</dt>
+<dd><code>setMargins(lr, rr, tr, br)</code>
+<p>Sets the margins of the document, Left(lr), Right(rr), Top(tr) and Bottom(br) margins are given in the measurement units of the document - see UNIT_&lt;type&gt; constants.</p></dd>
+
+<dt><a name="-setDocType"><strong>setDocType</strong></a>(...)</dt>
+<dd><code>setDocType(facingPages, firstPageLeft)</code>
+<p>Sets the document type. To get facing pages set the first parameter to FACINGPAGES, to switch facingPages off use NOFACINGPAGES instead. If you want to be the first page a left side set the second parameter to FIRSTPAGELEFT, for a right page use FIRSTPAGERIGHT.</p></dd>
+
+<dt><a name="-setUnit"><strong>setUnit</strong></a>(...)</dt>
+<dd><code>setUnit(type)</code>
+<p>Changes the measurement unit of the document. Possible values for "unit" are defined as constants UNIT_&lt;type&gt;.</p>
+<p>May raise ValueError if an invalid unit is passed.</p></dd>
+
+<dt><a name="-scrollDocument"><strong>scrollDocument</strong>(...)</a></dt>
+<dd><code>scrollDocument(x,y)</code>
+<p>Scroll the document in main GUI window by x and y.</p></dd>
+
+<dt><a name="-zoomDocument"><strong>zoomDocument</strong>(...)</a></dt>
+<dd><code>zoomDocument(double)</code>
+<p>Zoom the document in main GUI window. Actions have whole number
+values like 20.0, 100.0, etc. Zoom to Fit uses -100 as a marker.</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-doc.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-page.html
===================================================================
--- Scribus/doc/en/scripterapi-page.html (nonexistent)
+++ Scribus/doc/en/scripterapi-page.html (revision 13527)
@@ -0,0 +1,110 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Page related Commands</title>
+</head>
+<body>
+<h2>Page related Commands</h2>
+
+<dl>
+
+<dt><a name="-closeMasterPage"><strong>closeMasterPage</strong>(...)</a></dt>
+<dd><code>closeMasterPage()</code>
+<p>Closes the currently active master page, if any, and returns editing
+to normal. Begin editing with <a href="#-editMasterPage">editMasterPage()</a>.</p></dd>
+
+<dt><a name="-createMasterPage"><strong>createMasterPage</strong>(...)</a></dt>
+<dd><code>createMasterPage(pageName)</code>
+<p>Creates a new master page named pageName and opens it for editing.</p></dd>
+
+<dt><a name="-currentPage"><strong>currentPage</strong></a>(...)</dt>
+<dd><code>currentPage() -&gt; integer</code>
+<p>Returns the number of the current working page. Page numbers are counted from 1 upwards, no matter what the displayed first page number of your document is.</p></dd>
+
+<dt><a name="-deleteMasterPage"><strong>deleteMasterPage</strong>(...)</a></dt>
+<dd><code>deleteMasterPage(pageName)</code>
+<p>Delete the named master page.</p></dd>
+
+<dt><a name="-deletePage"><strong>deletePage</strong></a>(...)</dt>
+<dd><code>deletePage(nr)</code>
+<p>Deletes the given page. Does nothing if the document contains only one page. Page numbers are counted from 1 upwards, no matter what the displayed first page number is.</p>
+<p>May raise IndexError if the page number is out of range</p></dd>
+
+<dt><a name="-editMasterPage"><strong>editMasterPage</strong>(...)</a></dt>
+<dd><code>editMasterPage(pageName)</code>
+<p>Enables master page editing and opens the named master page
+for editing. Finish editing with <a href="#-closeMasterPage">closeMasterPage()</a>.</p></dd>
+
+<dt><a name="-getAllObjects"><strong>getAllObjects</strong></a>(...)</dt>
+<dd><code>getAllObjects() -&gt; list</code>
+<p>Returns a list containing the names of all objects on the current page.</p></dd>
+
+<dt><a name="-getHGuides"><strong>getHGuides</strong></a>(...)</dt>
+<dd><code>getHGuides() -&gt; list</code>
+<p>Returns a list containing positions of the horizontal guides. Values are in the
+document's current units - see UNIT_&lt;type&gt; constants.</p></dd>
+
+<dt><a name="-getPageType"><strong>getPageType</strong>(...)</a></dt>
+<dd><code>getPageType() -&gt; integer</code>
+<p>Returns the type of the Page, 0 means left Page, 1 is a middle Page and 2 is a right Page</p></dd>
+
+<dt><a name="-getVGuides"><strong>getVGuides</strong></a>(...)</dt>
+<dd><code>getVGuides()</code>
+<p>See <a href="#-getHGuides">getHGuides</a>.</p></dd>
+
+<dt><a name="-getPageItems"><strong>getPageItems</strong></a>(...)</dt>
+<dd><code>getPageItems() -&gt; list</code>
+<p>Returns a list of tuples with items on the current page. The tuple is: (name, objectType, order) E.g. [('Text1', 4, 0), ('Image1', 2, 1)] means that object named 'Text1' is a text frame (type 4) and is the first at the page...</p></dd>
+
+<dt><a name="-getPageMargins"><strong>getPageMargins</strong></a>(...)</dt>
+<dd><code>getPageMargins()</code>
+<p>Returns the page margins as a (top, left, right, bottom) tuple in the current units. See UNIT_&lt;type&gt; constants and <a href="#-getPageSize">getPageSize</a>().</p></dd>
+
+<dt><a name="-getPageSize"><strong>getPageSize</strong></a>(...)</dt>
+<dd><code>getPageSize() -&gt; tuple</code>
+<p>Returns a tuple with page dimensions measured in the document's current units. See UNIT_&lt;type&gt; constants and <a href="#-getPageMargins">getPageMargins</a>()</p></dd>
+
+<dt><a name="-gotoPage"><strong>gotoPage</strong></a>(...)</dt>
+<dd><code>gotoPage(nr)</code>
+<p>Moves to the page "nr" (that is, makes the current page "nr"). Note that gotoPage doesn't (curently) change the page the user's view is displaying, it just sets the page that script commands will operates on.</p>
+<p>May raise IndexError if the page number is out of range.</p></dd>
+
+<dt><a name="-importPage"><strong>importPage</strong>(...)</a></dt>
+<dd><code></code>
+<p>importPage("fromDoc", (pageList), [create, imortwhere, importwherePage]) Imports a set of pages (given as a tuple) from an existing document (the file name must be given). This functions maps the "Page-&gt;Import" dropdown menu function. fromDoc: string; the filename of the document to import pages from pageList: tuple with page numbers of pages to import create: number; 0 to replace existing pages, 1 (default) to insert new pages importWhere: number; the page number (of the current document) at which import the pages importWherePage: number; used if create==1; 0 to create pages before selected page; 1 to create pages after selected page; 2 (default) to create pages at the end of the document</p></dd>
+
+<dt><a name="-newPage"><strong>newPage</strong></a>(...)</dt>
+<dd><code>newPage(where [,"masterpage"])</code>
+<p>Creates a new page. If "where" is -1 the new Page is appended to the document, otherwise the new page is inserted before "where". Page numbers are counted from 1 upwards, no matter what the displayed first page number of your document is. The optional parameter "masterpage" specifies the name of the master page for the new page.</p>
+<p>May raise IndexError if the page number is out of range</p></dd>
+
+<dt><a name="-pageCount"><strong>pageCount</strong></a>(...)</dt>
+<dd><code>pageCount() -&gt; integer</code>
+<p>Returns the number of pages in the document.</p></dd>
+
+<dt><a name="-redrawAll"><strong>redrawAll</strong></a>(...)</dt>
+<dd><code>redrawAll()</code>
+<p>Redraws all pages.</p></dd>
+
+<dt><a name="-savePageAsEPS"><strong>savePageAsEPS</strong></a>(...)</dt>
+<dd><code>savePageAsEPS("name")</code>
+<p>Saves the current page as an EPS to the file "name".</p>
+<p>May raise ScribusError if the save failed.</p></dd>
+
+<dt><a name="-setHGuides"><strong>setHGuides</strong></a>(...)</dt>
+<dd><code>setHGuides(list)</code>
+<p>Sets horizontal guides. Input parameter must be a list of guide positions measured in the current document units - see UNIT_&lt;type&gt; constants.</p>
+<p>Example: <a href="#-setHGuides">setHGuides</a>(<a href="#-getHGuides">getHGuides</a>() + [200.0, 210.0] # add new guides without any lost<br>
+<a href="#-setHGuides">setHGuides</a>([90,250]) # replace current guides entirely</p></dd>
+
+<dt><a name="-setRedraw"><strong>setRedraw</strong></a>(...)</dt>
+<dd><code>setRedraw(bool)</code>
+<p>Disables page redraw when bool = False, otherwise redrawing is enabled. This change will persist even after the script exits, so make sure to call <a href="#-setRedraw">setRedraw</a>(True) in a finally: clause at the top level of your script.</p></dd>
+
+<dt><a name="-setVGuides"><strong>setVGuides</strong></a>(...)</dt>
+<dd><code>setVGuides()</code>
+<p>See <a href="#-setHGuides">setHGuides</a>.</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-page.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox7.html
===================================================================
--- Scribus/doc/en/toolbox7.html (nonexistent)
+++ Scribus/doc/en/toolbox7.html (revision 13527)
@@ -0,0 +1,95 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Advanced Ghostscript and GSview Hints</title>
+</head>
+<body>
+<h2>Advanced Ghostscript and GSview Hints</h2>
+<p>One of the frustrations for users of RPM-based or commercially created distributions, is the lack of availability of the latest versions of Ghostscript(GS). Because of the differences in licensing between the GPL Ghostscript and AFPL Ghostscript, GPL Ghostscript releases usually follow by about a year, the release of the most up to date AFPL GS. Because, there are certain restrictions in AFPL, most Linux distributions ship an older and heavily patched version of GPL Ghostscript.</p>
+<p>As the current GS 8.x resource configuration (where it looks for fonts and fontmaps) is new, simply dropping in the latest GS tarball and rebuilding the RPM does not quite work. Lord knows I've tried on Red Hat and I consider myself to be pretty well versed in RPM building. If you have ever seen the Red Hat or Suse rpm spec file for GS, you will know what I mean. ;)</p>
+<p>So, why do I want to go to the trouble of worrying about having the absolute latest version of GS? Not so difficult.</p>
+<ol><li>There are real substantial improvements in the ability of GS 8.5+ to handle EPS and PDF files which have the kinds of advanced features Scribus and other DTP applications can create. This can in some cases directly affect the quality of EPS and PS imports into Scribus. </li>
+<li>You can build it with full on compiler optimization, which speeds up print and separation previews in Scribus. Many distributions only compile it with i386 instructions. This is probably more beneficial to older workstations compared to newer ones. Image processing programs are one area where compiler optimizations do make a difference. </li>
+<li>Having the latest GS, makes GSview (and Scribus) more capable and more robust at handling both EPS files and a special kind of EPS called DCS 2.0. </li>
+<li>Both Scribus and GSview have the ability in their preferences settings to use alternative locations for GS and GS libraries.</li> </ol>
+<p>So, how does one get the latest GS for Scribus and GSview - without breaking your existing distribution printing setup? The secret: a parallel build of GS.</p>
+<p><strong>Disclaimer:</strong> This works for me. It could wreck your system, catch your hair on fire and other nastiness. </p>
+<p>First Steps:</p>
+<ul><li>Get the latest GS from here: <a href="http://sourceforge.net/project/showfiles.php?group_id=1897&package_id=108733">Ghostscript Downloads</a> </li>
+<li>You can manually tweak the make files the old way or </li>
+<li>Use the new configure script with the following options (and optionally <code>-with-jasper</code> and <code>-with-rinkj</code> with very latest versions): </li></ul>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>./configure --enable-compile-inits -with-x</pre></td></tr></table>
+</blockquote>
+
+<p>By default, '<code>make install</code>' will install all the files in '<code>/usr/local/bin</code>', '<code>/usr/local/lib</code>' etc. You can specify an installation prefix other than '<code>/usr/local</code>' using '<code>--prefix</code>', for instance '</p>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>--prefix=$HOME</pre></td></tr></table>
+</blockquote>
+<p>This default usually works fine and keeps the two sets of GS libs separated.</p>
+<p>Second Steps:</p>
+<p>There is a second step to compile Ghostscript as a shared library, which GSview needs:</p>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>make so</pre></td></tr></table>
+</blockquote>
+<p>and as root:</p>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>make soinstall</pre></td></tr></table>
+</blockquote>
+<p>Now, let&#039;s check briefly:</p>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>/usr/local/bin/gs -h</pre></td></tr></table>
+</blockquote>
+<p>You should have an output something like this:</p>
+<blockquote>
+<table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+AFPL Ghostscript 8.51 (2005-04-18)
+Copyright (C) 2005 artofcode LLC, Benicia, CA. All rights reserved.
+Usage: gs [switches] [file1.ps file2.ps ...]
+Most frequently used switches: (you can use # in place of =)
+ -dNOPAUSE no pause after page | -q 'quiet', fewer messages
+ -g&#060;width&#062;x&#060;height&#062; page size in pixels | -r&#060;res&#062; pixels/inch resolution
+ -sDEVICE=&#060;devname&#062; select device | -dBATCH exit after last file
+ -sOutputFile=&#060;file&#062; select output file: - for stdout, |command for pipe,
+ embed %d or %ld for page #
+Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PostScriptLevel3 PDF
+Default output device: x11
+Available devices:
+ bbox bit bitcmyk bitrgb bj10e bj200 bjc600 bjc800 bmp16 bmp16m bmp256
+ bmp32b bmpgray bmpmono bmpsep1 bmpsep8 cdeskjet cdj550 cdjcolor cdjmono
+ cljet5 cljet5c deskjet devicen djet500 epswrite faxg3 faxg32d faxg4 ijs
+ jpeg jpeggray laserjet lj5gray lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d
+ ljetplus nullpage pbm pbmraw pcx16 pcx24b pcx256 pcxcmyk pcxgray pcxmono
+ pdfwrite pgm pgmraw pgnm pgnmraw pj pjxl pjxl300 pkm pkmraw pksm pksmraw
+ png16 png16m png256 pngalpha pnggray pngmono pnm pnmraw ppm ppmraw
+ psdcmyk psdrgb psgray psmono psrgb pswrite pxlcolor pxlmono spotcmyk
+ tiff12nc tiff24nc tiffcrle tiffg3 tiffg32d tiffg4 tifflzw tiffpack
+ uniprint x11 x11alpha x11cmyk x11gray2 x11gray4 x11mono xcf
+Search path:
+ . : /home/peter/.fonts : /usr/local/share/ghostscript/8.51/lib :
+ /usr/local/share/ghostscript/8.51/Resource :
+ /usr/share/ghostscript/fonts</pre></td></tr></table>
+</blockquote>
+
+<p>The key thing here is:</p>
+<ol><li>You see the correct version of GS. Otherwise, you might need to adjust your <code>$PATH</code> settings</li>
+<li>You have <code>pngalpha</code> and the <code>x11</code> devices listed, along with <code>bitcmyk</code> for cmyk preview, and <code>png16m</code>.</li>
+<li>There is a reasonable search path for fonts, so GS can find your fonts. You will get errors in Scribus, when attempting to import EPS files or using the print preview, if this path is not set correctly and GS cannot find fonts. GS determines where to find fonts in a file called Fontmap. Setting this option is explained in the GS documentation.</li> </ol>
+<p>If you are concerned about messing about with your existing packaging setup, you could use: <code>checkinstall</code> or <code>Xstow</code>. These programs will keep track of applications which are outside of your normal packaging system. I have used checkinstall with good luck in these kinds of situations on Red Hat systems.</p>
+<p>Next,if installed, open up GSview and go to <strong>Options.. &#062; Advanced Configure</strong>. Then, make sure the &#034;Ghostscript Shared Object&#034; is pointing at the correct libgs.so. Below is how I have setup GSview on my system.: </p>
+<table width="100%"><tr><td align="center"><img src="images/gsadv1.png" alt="GSview - Advanced Options Panel" align="middle" title="GSview - Advanced Options Panel" /></td></tr></table>
+
+<p>Next, we need to tell Scribus where to find the newer GS. Go <strong>Edit..&#062; Preferences.. &#062;General</strong>. Then in External Tools, add the path for the new Ghostscript under PostScript Interpreter.</p>
+<table width="100%"><tr><td align="center"><img src="images/gsadv2.png" alt="Scribus External Tools Preferences" align="middle" title="Scribus External Tools Preferences" /></td></tr></table>
+<p>Another tool which is available with GSview is <code>epstool</code>. An older version is shipped with the current GSview 4.6, but a newer one is available on the GSview home page. This is a great command line tool, which can perform advanced EPS/DCS 2.0 conversion. This is very useful when someone sends you an EPS file from other DTP applications - even those created on Macs. Upgrading this to work with GSview gives you excellent support on Linux to handle EPS files from all platforms. Recommended.</p>
+<p>Lastly, one other tool which works as a plug-in with GSview is <code>pstoedit</code> This is a command line tool for converting bitmap images into vectors and PostScript, which then, depending on the nature of the image, can be edited in a vector drawing tool like Inkscape or Skencil. See the section Import Hints for hints on how I used this to convert the Scribus logo into SVG and then a native Scribus file. GSview uses this as a plug-in to convert files into vector format. </p>
+<p>GSview has been, in my experience, the most reliable and versatile EPS/PS viewer on Linux. How good is it ? Well, the best example is letting you know this usually installed on every Windows DTP workstation I support for clients. For DTP with Scribus, I consider it essential.</p>
+
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/toolbox7.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install2.html
===================================================================
--- Scribus/doc/en/install2.html (nonexistent)
+++ Scribus/doc/en/install2.html (revision 13527)
@@ -0,0 +1,80 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Requirements</title>
+</head>
+<body>
+<h2>Requirements</h2>
+<p>The programs you will need to compile Scribus 1.3.5+ are:</p>
+<ol>
+ <li><strong>For Scribus 1.3.x+ GCC 3.x+ is required, GCC 3.3+ is strongly recommended</strong>. The Scribus Team has tested compiling with GCC 4.1, 4.2 and 4.3. We recommend the newest stable GCC 4.x release for the performance benefits.</li>
+ <li>GNU make</li>
+</ol>
+The dependencies for compilation, and also to run Scribus are:
+<ol>
+<li>Qt 4.3.0+, both the runtime libraries and development libraries. Qt 4.2.x is not supported as 1.3.5+ relies on functions only in 4.3.x. Qt3 is no longer required or supported with Scribus 1.3.5 or higher.</li>
+<li>Python and python-devel libraries 2.3+. Python 2.2 is not supported.</li>
+<li>Freetype2 2.1.7+. Due to various freetype2 bugs, we recommend, if your distribution/OS allows, to use 2.3.x</li>
+<li>cairo 1.4.x <strong>We recommend 1.4.10+</strong>for performance reasons.</li>
+<li>libxml2 2.6+.</li>
+<li>Ghostscript 8.15+ or GPL Ghostscript 8.60+ is highly recommended. Ubuntu users in particular are urged to update to a newer version if possible.</li>
+<li>PostScript-Fonts. TrueType Fonts. Scribus also can support OpenType fonts, both TrueType and Type 1 Outline OpenType Fonts.</li>
+<li>Littlecms - also known as lcms in some distributions. Minimum 1.12, 1.17+ recommended. lcms 1.12+ has support for black point compensation. 1.3.4+ requires littlecms.</li>
+<li>libtiff 3.6.0+</li>
+<li>libjpeg</li>
+</ol>
+<h3>Optionally:</h3>
+<ul>
+<li>CUPS development libraries - Scribus directly supports printing with CUPS.(Linux/Unix only).</li>
+<li>tkinter - for the font sampler script</li>
+<li>python-imaging libaries for font sampler script preview</li>
+<li>openssl-devel (Some linux distributions enable ssl support for CUPS, notably SUSE Linux)</li>
+<li>fontconfig-devel - for auto discovery of fonts on Linux, MacOSX and Unix. Not needed on Windows.</li>
+<li>antiword - this is not needed at compile time for MS Word import. Scribus will detect this at run time however.</li>
+<li>Podofo 0.5 (svn does not currently work) - used to enhance the Adobe Illustrator importer.</li>
+</ul>
+<p>Scribus will run under most any window manager and does not require KDE itself. However, drag and drop functionality will be lost without KDE. One of the Scribus developers runs Gnome. The author of this documentation has made a point of testing each release of Scribus under Blackbox as well. This has shown no incompatibilities or problems for Scribus, except for the loss of drag and drop functionality.</p>
+<p>If color management does not work, you also need at least one RGB profile and one CMYK profile installed or the color preferences and options will not appear in the menus. Scribus installs one RGB and one CMYK profile simply to enable color management, but some distributions, notably Debian, because of licensing issues provides icc profiles in separate packages.</p>
+<p>Testing suggests setting the correct &#034;-march=&#034; CXXFLAGS has a very beneficial effect on Scribus performance. For example, if you have a Duron or Athlon processor, using <code>export CXXFLAGS=&#034;-march=athlon&#034;</code> would be of benefit. Check if your distribution sets these for you and how they are set, and for further information see:
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>man gcc</pre>
+</td></tr></table></blockquote>
+for detailed options</p>
+<p>There are detailed notes in the BUILDING file and packagers should look at the PACKAGING file in the sources for more details.</p>
+<h4>Using CMake</h4>
+<p>In 1.3.3.6+, we have added support for using CMake as an alternative for traditional autotools. For 1.3.5+ it is now mandatory. Currently, Linux and MacOSX are working reliably. Please see <a href="install4.html">CMake instructions</a> for instructions.</p>
+
+<p>You can launch Scribus from the command line with the following options:</p>
+
+<pre>
+scribus --help
+</pre>
+
+<p>Output:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>scribus -h
+
+Scribus, Open Source Desktop Publishing
+---------------------------------------
+Homepage: http://www.scribus.net
+Documentation: http://docs.scribus.net
+Wiki: http://wiki.scribus.net
+Issues: http://bugs.scribus.net
+
+Usage: scribus [option ... ] [file]
+Options:
+ -h, --help Print help (this message) and exit
+ -l, --lang Uses xx as shortcut for a language, eg `en' or `de'
+ -la, --langs-available List the currently installed interface languages
+ -fi, --font-info Show information on the console when fonts are being loaded
+ -ns, --no-splash Do not show the splashscreen on startup
+ -v, --version Output version information and exit
+ -sb, --swap-buttons Use right to left dialog button ordering (eg. Cancel/No/Yes instead of Yes/No/Cancel)
+ -pr, --prefs filename Use filename as path for user given preferences
+ -pi --profile-info Lists the installed profiles Scribus can access and diagnostics on loading them.
+</pre>
+</td></tr></table></blockquote>
+<p>The default location for the Scribus executable is located in <code>/usr/local/bin</code>. Documentation is located in <code>/usr/local/lib/scribus/doc</code></p>
+<p>In addition for Linux/Unix desktops, there is a <code>desktop.config</code> file named <code>scribus.desktop</code> which can be used for a menu shortcut or desktop shortcut. Simply copy this from the base directory of the installation source directory to your KDE desktop and this will launch Scribus. After dragging this to the desktop, right click and make sure the execute check box is checked. This file conforms to the latest <a href="http://www.freedesktop.org">www.freedesktop.org</a> specifications.</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/install2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/about2.html
===================================================================
--- Scribus/doc/en/about2.html (nonexistent)
+++ Scribus/doc/en/about2.html (revision 13527)
@@ -0,0 +1,52 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Basics</title>
+</head>
+<body>
+
+<h2>Scribus Basics</h2>
+<h3>Why Page Layout is different from Word Processing</h3>
+
+<p>What can you do with Scribus ? What is a &quot;page layout&quot; program ? </p>
+<p>Fundamentally, Scribus is <strong>not a word processor</strong>. This is a very important concept to understand. Scribus belongs to the family of applications known as page layout programs or more commonly known as Desktop Publishing programs. Scribus gives users great flexibility in placing objects like photos, logos, text frames and shapes in the exact place where you want them. This short guide is meant to give a first time user a sense of what Scribus can do. It is not meant to cover every feature, just a simple over view to get you started and being productive.</p>
+
+<p>With Scribus you can:</p>
+<ul>
+<li>Create great looking documents including things like CD covers, greeting cards, company brochures, newsletters and posters. </li>
+<li>Create files which will print easily at your commercial printer.</li>
+<li>Create interactive PDF forms and presentation documents. What is interactive PDF? <!--Your looking at one.--> Interactive PDFs have special features like hyperlinks, annotations (non-printing notes), bookmarks &ndash; a kind of an automatically created index for your PDF, as well as special navigation features &ndash; just like a web browser.</li>
+<li>Create logos and drawings with Scribus' easy to use tools including the ability to create neat font effects.</li>
+<li>Import photos and other artwork with precise color control for high fidelity printing. </li>
+</ul>
+<h4>First the Theory &ndash; The Right Approach</h4>
+<p>First time users of page layout applications like Scribus can find starting out quite frustrating. The interface seems approachable and familiar enough, but when you make your beginning steps things often do not quite work as expected. Do not make the mistake of launching Scribus, opening a new document and expect to start typing. Making the most of an application like Scribus, requires a bit of understanding of the concepts of &quot;workflow&quot; in the page layout world. It might seem a bit arcane at first, but will pay off in the end.</p>
+<p>Part of the challenge of learning Scribus is you are often not just trying to learn a program, but learning page layout, which has its own sometimes subtle rules. There are stark differences from word processors or other text editors. Fortunately, Scribus comes with its own built-in Story Editor (SE). Using this instead of editing on the canvas, understanding the setup and application of styles will greatly enhance your productivity, as well as providing you with more consistent, easier to edit documents.</p>
+<p><i>Workflow</i>, means in the page layout world a way of assembling both the files to be used, but also some forethought on where and how your document will be printed or used. If for example, you were planning on creating a brochure for your business, you certainly would want to have it commercially printed. Thus, you would be sadly mistaken if you thought you could take the low resolution JPEG from your website and use them in Scribus directly. Web and print have two different objectives. <b><i>Graphics used on a website are almost always unusable for commercial printing.</i></b> You need <b>much</b> higher resolution graphics. File size should almost always be secondary to image quality when considering commercial print needs. A typical website image is 72&ndash;96 DPI , where for good print results, you need 200&ndash;300 DPI. Scribus can export PDF at <em>4000</em> DPI</p>
+<p>A Simple Page Layout Workflow:</p>
+<ol>
+<li>Make a simple sketch on paper of the basic layout. This helps to visualize how to mix text, artwork and images.</li>
+<li>Get images collected as needed, preferably high 200 DPI or higher saved as TIFFs or PNG. Get your artwork (illustrations or line art in a suitable import format. SVG or EPS are usually the best option.</li>
+<li>Write out the text in a word processor or text editor. Spell check, double check grammar, etc.</li>
+<li>Collect all these files in a project directory and start building your document in Scribus.</li>
+</ol>
+<p>In a commercial setting, this might be far more complex. In my experience, using similar methods will allow the planning and structure to make sense and greatly enhances productivity.</p>
+<p>Lastly, Workflow similarly takes into consideration the many options when exporting PDF or printing. There are extensive notes about this in the chapter <a href="pdflavor.html">PDF Export</a>. Scribus has many advanced printing features, which are atypical of desktop applications. Make sure <b>tooltips</b> are enabled, to get general guidance and/or read the <a href="print1.html">Printing Section</a> carefully to understand the options.
+</p>
+<p><!--For first time users, I would encourage you to launch Scribus while looking -->When reading through the parts of the documentation, especially some of the sections on more advanced topics,<!-- . Read everything once thoroughly. M-->make notes on what you do not understand, then post your questions to the mailing list or IRC.</p>
+<p>Before diving into a project, sometimes the best thing is to put the computer aside, get out a sketch pad and make a simple drawing how you want the doc to appear. I too have rediscovered pen and paper. On a recent vacation, lacking a computer at times, I discovered my lack of writing by hand has lead to very poor penmanship. Results, I wrote 8 complete pages in an afternoon, more than I might have written in three nights. Why? Because, I could only concentrate on content. I suggest you do the same. Scribus's real magic is the ability to assemble all the bits <i>at the end</i> to create your masterpiece.
+</p>
+<p>So, if text is going to be a big part of your document, start your favorite text editor or word processor and compose the text first. This way you can concentrate on content. This is where word processors sometimes work against you&nbsp; Note how often you can be distracted by editing done to affect the look, instead of the content. (I'm guilty too) I need not preach to the choir and explain the benefits of saving plain unformatted text. This, in the UNIX world is a given, but for migrating Windows/Mac users may not be the usual habit. Save plain text, you will be happy about this some day. Alternatively, you can import OpenOffice.org.org 1.x and 2.x (OASIS) text and or MS Word documents.</p>
+<p>Next, you will need to consider drawings, photos, tables etc., which might be a part of your doc.</p>
+
+<h4>Bitmap Images</h4>
+<p>Like photos that come from the GIMP, Krita, Adobe Photoshop or similar. They could also be images from a digital camera program like <a href="http://www.digikam.org/">digiKam</a> or a scanner application like <a href="http://www.xsane.org/">Xsane</a> or <a href="http://kooka.kde.org/">Kooka</a>. Bitmap images are composed of pixels or dots, typically compressed in a file format like JPEG, TIFF, PNG or bmp. For images in Scribus, I prefer and recommend either PNG for things like screen captures or TIFFs. TIFFs are generally very reliable in DTP and should be chosen for any kind of high resolution photos.</p>
+<h4>Vector Drawings or illustrations</h4><p>come from applications like Inkscape, OpenOffice.org Draw, Adobe Illustrator, CorelDraw, Sketch, or Xfig. These generate line drawings and other artwork which is kept in a vector format inways which preserve their appearance at any scale. It should be mentioned that vector files don't save dots, but coordinates which <em>describe</em> mathematically where to draw the lines or fill shapes. That's the reason why they can be scaled endlessly without loss of quality. The preferred way to import them into Scribus is via EPS (Encapsulated Post Script) or via SVG (Scalable Vector Graphics). The advantage of SVG is Scribus imports this into native editable objects and can re-edit almost every features in SVG. <!--The importer can import almost every type of SVG from the W3C test suite, excepting multimedia features and scripted actions for Win32 plug-ins in a browser.--></p>
+<h4>EPS/PS Importing</h4>
+<p>One of the reasons we recommend the latest Ghostscript is to enable the best possibility of importing EPS and PS vector files, which can then be edited natively as Scribus objects. This can be very useful for imports which need further changes and you do not have the original source files. </p>
+<h4>Importing PDF</h4>
+<p>One other way you can import files into Scribus is via PDF. Scribus will use Ghostscript to create a high resolution image with a lower resolution file for preview on screen. This is more appropriate for drawings and images versus text. If you need just the text from a PDF, you can open the file in Adobe Acrobat Reader or KPDF and copy and paste from the clipboard. Note: you can only import one page of a PDF at a time, and you cannot yet edit imported PDFs. </p>
+<p>Once you have assembled all these bits, it is time to begin working in Scribus. For previous users of desktop publishing, launching Scribus for the first time will seem comfortable and familiar.
+</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/about2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/download.html
===================================================================
--- Scribus/doc/en/download.html (nonexistent)
+++ Scribus/doc/en/download.html (revision 13527)
@@ -0,0 +1,30 @@
+<qt>
+<title>Scribus Downloads</title>
+<h3>Scribus Downloads</h3>
+
+<hr />
+
+
+<h4>Getting Scribus 1.3.x:</h4>
+
+<p>Windows 2000/XP:<a> <a href="http://windows.scribus.net">http://windows.scribus.net</a></a>
+</p>
+<p>MacOSX: <a href="http://aqua.scribus.net">http://aqua.scribus.net</a></p>
+
+<p>Debian and Ubuntu Packages </b><a href="http://debian.scribus.net">apt-get setup</a> Note: We do not have 64-bit Ubuntu Packages available in our repo.</p>
+
+<p>You can:<br />
+Download source tarballs and document templates and some rpms from
+our :
+<a href="http://sourceforge.net/project/showfiles.php?group_id=125235">Sourceforge Download page</a></p>
+
+<h4>RPM Distros</h4>
+<p>Thanks to the <a href="http://en.opensuse.org/Build_Service">Open Suse Build Service</a>, we are pleased offer a <a href="http://download.opensuse.org/repositories/home:/mrdocs/">Scribus RPM Repository</a>. The repository with both 32-bit and 64-bit rpms has updated 1.3.3.x stable and for the more adventurous, 1.3.x-devel versions of Scribus. These rpms are updated regularly with svn snapshots for Fedora 5-7, Mandrake 2007 and Suse 10.+. This includes SLED 10 (Suse Enterprise Desktop 10). The only limitation at the moment is we cannot provide Scribus development versions for all distributions as they may not have shipped with the latest versions of libraries which our development version may require. Currently, Qt 4.3 is only available for Suse on the Build Server, thus 1.3.5svn is only available for the latest versions of Suse.
+<br />You can use these repositories with <a href="http://en.opensuse.org/Add_Package_Repositories_to_YaST">Yast</a>, <a href="http://linux.duke.edu/projects/yum/">Yum</a> or <a href="http://opensuse-community.org/Smart">Smart</a> easily, as they provide rpm metadata. We use the same build server to provide the rpms for normal releases. For stable releases, the 1.3.3.x rpms have been tested a fair amount and do not vary significantly from the rpms which ship with the distro. If you have any issues with the rpms, please file a bug on http://bugs.scribus.net. </p>
+<p>In addition, there are a number of packages in this repository which are built to complement Scribus like GSview, ICC profiles, fonts and some other useful tools and utilities which are not packaged for other distributions. </p>
+
+<!--<li><b>Extra Document Templates</b> - http://www.scribus.org.uk/downloads/1.2.2/scribus-temp-all-1.2.2.tar.bz2</li>
+<!--<li><b>Translation source files</b> (not needed for Scribus usage) - http://www.scribus.org.uk/downloads/1.2.2/scribus-po-files.tar.bz2</li>-->
+<h4>Downloading SVN</h4>See: <a href="install1.html">SVN Checkout Instructions</a>
+
+</qt>
\ No newline at end of file
/Scribus/doc/en/download.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/print1.html
===================================================================
--- Scribus/doc/en/print1.html (nonexistent)
+++ Scribus/doc/en/print1.html (revision 13527)
@@ -0,0 +1,38 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Printing in Depth</title>
+</head>
+<body>
+<h2>Printing in Depth</h2>
+<p>One of the challenges of an advanced DTP application like Scribus, is the ability to generate what I refer to as "high-level" PostScript or PDF features. By <em>high level</em>, this is meant to describe things like transparency, blends, masks and gradients, usually created by professional grade DTP applications and illustration programs. <strong>Always</strong> make sure you have the newest updated versions of CUPS and Ghostscript available for your distribution. Newer versions of CUPS and Ghostscript are much better at supporting the kinds of high level PS3 and PDF features Scribus can create.</p>
+<h3>Basic Options:</h3>
+<ul>
+<li>Print to your default printer with the defaults set either by kprinter, CUPS or Lprng, depending on your specific installation. You can also specify printing in gray scale, as well as reverse the order of printing, which makes the pages stack in correct order on many ink jet printers.</li>
+<li>You can also use an external print command example. XPP, or kprinter.</li>
+</ul>
+
+<h3>Advanced Options:</h3>
+<ul>
+<li>&#034;Print&#034; a separation as shown below. This enables you to create a 4 color separation of the CMYK inks used in process printing. Each of the inks will print on a separate page. This can also be saved to a PostScript file for later processing.</li>
+</ul>
+<table width="100%"><tr><td align="center"><img src="images/printseps.png" alt="Printing Separations from Scribus" title="Printing Separations from Scribus" /></td></tr></table>
+
+<ul>
+<li>&#034;Print&#034; a PostScript file, which can be later &#034;distilled&#034; or transferred for processing by a printer or service bureau.</li>
+<li>If you have the <strong>Gimp Print</strong> modules, selecting Options will bring up a panel similar to the one below. The exact contents will vary with the capabilities of the printer - one very good reason for having CUPS-Gimp Print. These modules are much less &quot;generic&quot; than many other printer drivers. When installed correctly, they enable you to use all the options your printer is capable of handling such as: different paper types, duplex modes, color printing modes etc. Scribus directly supports <strong>Gimp-Print</strong> drivers with CUPS, These high quality drivers are optimized for printing high resolution prints from ink-jet printers. The specific details are here: <a href="cups.html">CUPS and Gimp-Print</a>.</li>
+</ul>
+<table width="100%"><tr><td align="center"><img src="images/printer1.png" alt="Setup Printer Dialog" title="Advanced CUPS Options in Scribus"/></td></tr></table>
+
+<ul>
+ <li>&#034;Mirrored&#034; Printing - this option enables you to mirror pages on the printer. This is useful when printing things like card layouts, calendars or brochures to compensate for folds and cuts or when duplexing prints.</li>
+</ul>
+<table width="100%"><tr><td align="center"><img src="images/printer2.png" alt="Advanced Options" title="Advanced Printing Options"/></td></tr></table>
+
+<ul>
+ <li>Color Managed Printing - When color management is enabled Scribus can apply ICC profiles to the print output. This option can be used to make simple simulations of CMYK press conditions. This can also be used if have special profiles of your printer for special papers like glossy photo paper or specially coated stock paper for color laser printers. More details are found in <a href="cms.html">Scribus and littlecms</a>.</li>
+</ul>
+
+
+</body>
+</html>
/Scribus/doc/en/print1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/translation_howto.html
===================================================================
--- Scribus/doc/en/translation_howto.html (nonexistent)
+++ Scribus/doc/en/translation_howto.html (revision 13527)
@@ -0,0 +1,43 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>How to create or update a translation of Scribus</title>
+</head>
+<body>
+<h2>How to create or update a translation of Scribus</h2>
+
+<p>Scribus is available in over 20 languages thanks to the many willing souls out there who have spent the time translating. This is no small task, but to be honest, not a very difficult one technically. This page outlines the requirements and procedures for creating or updating such a translation.</p>
+
+<p>Please note, there are many willing contributors to the Scribus project and there may already be a translation in progress for the language you wish to help for. It would be worthwhile asking on the mailing list to see if someone has started. This is also a courtesy matter. At this point we don't really have any &#034;official&#034; translators but perhaps you can work together, or take over an old translation if the previous translator no longer has the time to keep it up-to-date. So, here we go...</p>
+
+<h3>Requirements</h3>
+<ul>
+<li>The Scribus source from CVS. Please see the <a href="install.html">Installation</a> section for details on how to checkout CVS if you aren't up with that yet. Its not too hard so don't be dismayed. By working with the CVS source, you know you will be working with the latest Scribus source and therefore will get the most up-to-date set of files to translate.</li>
+<li>KBabel or Qt Linguist. Both of these are available in their respective development packages. The choice of which one to use is more a user preference, the result is the same.</li>
+<li>You will need to make sure you have the <strong><code>lupdate</code></strong> and <strong><code>lrelease</code></strong> programs which are a part of Qt, or perhaps a part of a Qt development package, depending on your distribution.</li>
+<li>If you use create .mo for .po files you need the <strong><code>msg2qm</code></strong> program to convert them to .qm files. Debian users will need to install: <a href="http://packages.debian.org/stable/devel/qt3-dev-tools-compat">http://packages.debian.org/stable/devel/qt3-dev-tools-compat</a> to obtain this tool.</li>
+</ul>
+
+<h3>Procedure for creating or updating a translation file</h3>
+<ol>
+<li>Check out CVS as per instructions on this page.</li>
+<li>Move into the <code>Scribus</code> directory.</li>
+<li>Run <code>qmake -project</code>.</li>
+<li>Edit the <code>Scribus.pro</code> file to have the language listed at the bottom that you wish to translate for. For example,
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+ <pre>TRANSLATIONS += scribus/po/scribus.en_GB.ts</pre>
+</td></tr></table></blockquote>
+Of course, replace the <code>en_GB</code> in this example with the language code you are working with.</li>
+<li>Run <code>lupdate Scribus.pro</code>.</li>
+<li>Start KBabel or QT Linguist and load the <code>scribus/po/scribus.en_GB.ts</code> file.</li>
+<li>Perform the translations.</li>
+<li>Save the <code>.ts</code> file.</li>
+<li>Run <code>lrelease scribus/po/scribus.en_GB.ts -qm scribus/qm/scribus.en_GB.qm</code>. this can be simplified by just running <code>lrelease scribus/po/scribus.en_GB.ts</code> and the qm will be created for you in the <code>scribus/po</code> directory. The previous command allows a <code>make &#038;&#038; make install</code> with the translations in their correct places.</li>
+<li>Copy the <code>.qm</code> file to the <code>/usr/local/lib/scribus</code> directory (or appropriate Scribus installation directory on your PC).</li>
+<li>Run Scribus with the language code from the command line like: <code>scribus -lang en_GB</code>.</li>
+<li>Once you are happy with this, please open your web browser to the <a href="http://bugs.scribus.net">Scribus Bugs Website</a> and submit a new bug with Title of &#034;British English Translation Update&#034; and Category of &#034;Translation&#034; and upload the new <code>.ts</code> AND <code>.qm</code> into the bug system. If you can, please make a <code>tar.bz2</code> file of the two to save some space on the bugs site.</li>
+<li>That's it! When the next CVS release is made, your new translation will be added by the team.</li>
+</ol>
+<p>So that's it really! Enjoy Scribus in your favourite language!</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/translation_howto.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/workspace1.html
===================================================================
--- Scribus/doc/en/workspace1.html (nonexistent)
+++ Scribus/doc/en/workspace1.html (revision 13527)
@@ -0,0 +1,71 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus' Workspace</title>
+</head>
+<body>
+<h2>Scribus' Workspace</h2>
+
+<p>Once you have assembled all the bits to create your first layout, it is time to begin working in Scribus. For previous users of page layout applications, launching Scribus for the first time will seem comfortable and familiar. </p>
+
+<p> Scribus has three different icon tool bars.</p>
+<h4>1) File Tools </h4>
+<table width="100%"><tr><td align="left"><img src="images/toolbar1.png" title="Scribus Tool Bar" alt="Scribus Tool Bar" /></td></tr></table><br />
+<p>Left to Right: File New, File Save, Close File, Print and Export PDF.</p>
+<p><strong>File New</strong> will bring up the new document dialog with the default preferences, shown further below. <strong>File Save, Close File and Print</strong> all work as expected and the last <strong>Export PDF</strong> launches the <A href="pdfexport2.html">PDF Export</A> window.</p>
+
+<h4>2) Edit/Selection Tools</h4>
+<table width="100%"><tr><td align="center"><img src="images/toolbar1d.png" title="Scribus Tool Bar" alt="Scribus Tool Bar" /></td></tr></table><br />
+<p></p>
+
+<h4>3) PDF Form Tools.</h4>
+<table width="100%"><tr><td align="left"><img src="images/toolbar3.png" title="Scribus Tool Bar" alt="Scribus Tool Bar" /></td></tr></table><br />
+
+
+<p>Scribus toolbars are floatable and dockable in that they can move from the main window and float over the canvas or they can be "docked" below the menus or either side of the canvas. </p>
+<table width="100%"><tr><td align="left"><img src="images/toolbar1c.png" title="Scribus Tool Bar" alt="Scribus Tool Bar" /></td></tr></table><br />
+
+
+
+
+
+
+<p><strong>File > New</strong> brings up a dialog which has a number of options, the default is set in the preferences dialog under Edit - Preferences. Lets open the default and have a begin with importing text. Text in a Scribus layout is an object, so it can moved and manipulated very precisely. </p><br />
+
+<table width="100%"><tr><td align="center"><img src="images/newdoc1.png" title="See Automatic Text Frames is checked." alt="See Automatic Text Frames is checked" /></td></tr></table><br />
+
+<p>Selecting <strong>Automatic Text Frames</strong> will create one text frame per page with the borders of the text frame determined by the page margins. You can also make the text within the text frame multi-colum, commonly used in newspaper and magazine layouts.</p>
+
+
+
+<h4>Manually Creating Text Frames</h4>
+
+<p>Now to create a text frame, click the Insert Text Box button on the top. Move the cursor to the upper left hand corner of the page canvas and left click drag to enlarge the frame. You can now either double click the frame or select the Text Cursor to begin editing. Scribus has its own built-in <a href="storyeditor.html">Story Editor</a>, which is essentially a small built in text editor. The other way and the I recommend is to import your text directly. But before set the font, size and alignments first - then import the text - this saves editing time.
+</p>
+<p>You can further modify text frames by the Right Click, which brings up a context menu or using the measurements palette via Tools > Show Measurements. Both panels share many of the same editing features. The modify option adds some PDF and color options, which are not available on the measurements palette.</p>
+
+<strong>Edit Mode vs. Select Mode</strong>
+
+<p>Switching between modes at the beginning can be confusing to new users - learning drawing programs can cause similar frustration. You select something, but you cannot do anything with it directly. It is doubly confusing, because while you are in select mode, you can move a text or image frame. How you can tell and how can you switch?</p>
+
+<p>There are a couple of basic ways which you can use and select tools and objects.
+To enable edit mode - simply double click the object, any object when double clicked will be in edit mode. The cursor will change from the cross, which is for moving selecting objects to the hand/text cursor. To exit, click the page canvas without touching other objects. This puts you back in select mode. Select mode is what you want when you want to move, delete, copy or resize. Edit mode is when you want to edit the contents of the frame.
+</p>
+<p>Moving the cursor near the border or corner of an object frame the cursor will change to a double arrow. This will resize an object frame in one direction. When resizing with the mouse, holding Shift, will <em>constrain</em> or retain the same shape. Holding the Control key will retain the object's proportion as well.</p>
+
+<p>When you select a image or text frame, the red squares are grab handles. For text frames, the corner squares can be used to resize the frame. The top and bottom squares in the middle are for resizing vertically by dragging. </p>
+
+<p><strong>Text Frames</strong> - Scribus has many different features for text handling, including support for right to left languages such as Hebrew and Arabic. Moreover, Scribus has a built in hyphenation engine based on the same one used in Open Office -it works well and many languages are supported. There is also the ability to adjust tracking or spacing between letter pairs. You can squeeze text or spreeaaad it apart. Text boxes can be rotated, flipped and you can add them to paths, like following the arc of a circle.
+</p>
+
+<h4>The Basics:</h4>
+
+<p>Click the text icon and drag a new frame on the page. Then Right Click > Properties from the contect menu. From there you can adjust the defaults. Including borders, the fill color and column gap, spacing of text from the text frame edge and others.</p>
+
+<!--<table width="100%"><tr><td align="center"><img src="images/proppalette1.png" title="Text Tab of Properties Palette" alt="Text Tab of Properties Palette" /></td></tr></table><br />-->
+
+<table width="100%"><tr><td align="center"><img src="./images/proppalette1.png" title="Text Tab of Properties Palette" alt="Text Tab of Properties Palette" /></td></tr></table><br />
+
+<p>In the palette above, note the Styles drop down button. Using Styles is strongly recommended for efficient text layout and styling. With properly used styles, you can change the entire look of a document with a few clicks. </p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/workspace1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-extensions.html
===================================================================
--- Scribus/doc/en/scripterapi-extensions.html (nonexistent)
+++ Scribus/doc/en/scripterapi-extensions.html (revision 13527)
@@ -0,0 +1,41 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scripter Extensions API</title>
+</head>
+<body>
+<h2>Scripter Extensions API</h2>
+
+<p>See <a href="scripter-extensions.html">Scripter Extensions</a> for the
+theoretical background of these procedures and functions.</p>
+
+<dl>
+
+<dt><a name="-getChild"><strong>getChild</strong>(...)</a></dt>
+<dd><code>getChild(object, childname, ofclass=None, recursive=True)</code>
+<p>Return the first child of `object' named `childname', possibly restricting the search to children of type name `ofclass'. If `recursive' is true, search recursively through children, grandchildren, etc.</p></dd>
+
+<dt><a name="-getChildren"><strong>getChildren</strong>(...)</a></dt>
+<dd><code>getChildren(object, ofclass=None, ofname=None, regexpmatch=False, recursive=True)</code>
+<p>Return a list of children of `object', possibly restricted to children of class named `ofclass' or children named `ofname'. If `recursive' is true, search recursively through children, grandchildren, etc. See QObject::children() in the Qt docs for more information.</p></dd>
+
+ <dt><a name="-getProperty"><strong>getProperty</strong>(...)</a></dt>
+<dd><code>getProperty(object, property)</code>
+<p>Return the value of the property `property' of the passed `object'. The `object' argument may be a string, in which case the named PageItem is searched for. It may also be a PyCObject, which may point to any C++ QObject instance. The `property' argument must be a string, and is the name of the property to look up on `object'. The return value varies depending on the type of the property.</p></dd>
+
+<dt><a name="-getPropertyCType"><strong>getPropertyCType</strong>(...)</a></dt>
+<dd><code>getPropertyCType(object, property, includesuper=True)</code>
+<p>Returns the name of the C type of `property' of `object'. See getProperty() for details of arguments. If `includesuper' is true, search inherited properties too.</p></dd>
+
+<dt><a name="-getPropertyNames"><strong>getPropertyNames</strong>(...)</a></dt>
+<dd><code>getPropertyNames(object, includesuper=True)</code>
+<p>Return a list of property names supported by `object'. If `includesuper' is true, return properties supported by parent classes as well.</p></dd>
+
+<dt><a name="-setProperty"><strong>setProperty</strong>(...)</a></dt>
+<dd><code>setProperty(object, property, value)</code>
+<p>Set `property' of `object' to `value'. If `value' cannot be converted to a type compatible with the type of `property', an exception is raised. An exception may also be raised if the underlying setter fails. See getProperty() for more information.</p></dd>
+
+</dl>
+
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/scripterapi-extensions.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/cms.html
===================================================================
--- Scribus/doc/en/cms.html (nonexistent)
+++ Scribus/doc/en/cms.html (revision 13527)
@@ -0,0 +1,47 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Color management with Scribus, an Introduction</title>
+</head>
+<body>
+<h2>Color management with Scribus, an Introduction</h2>
+
+<h4>Activating Color Management</h4>
+<p>For color management to function properly you need the following to be installed to be active and usable:</p>
+<ul><li>Littlecms libraries installed and Scribus compiled with lcms support. You can tell by looking at <strong>Help > About Scribus</strong> and looking for C-C-T. The first C means Scribus is compiled with littlecms support. This is standard with MacOSX and Windows.</li>
+<li>You need a <strong>minimum</strong> of 1 RGB and 1 CMYK profile. Scribus provides two basic profiles to ensure CMS can be enabled immediately. In practical terms, you need more. One sRGB for most RGB colors and one for each color device. One for your monitor which is created with monitor profiling tools. Several CMYK profiles for printing. Some CMYK profiles are known as "press-standards", in that they represent common commercial print standards used in North America and Europe. The best bet is to download the "Windows" version of the Adobe ICC profile package and unzip it into a directory like $home/.colors/icc. Linux users can also download freely distributable profiles from the <a href="http://www.scribus.net/modules.php?op=modload&name=Downloads&file=index&req=viewdownload&cid=16">ICC downloads</a> section on <a href="http://www.scribus.net">www.scribus.net</a> </li>
+<li>Scribus, by default on Linux, will look in:
+ <pre>$home/.color/icc</pre> and <pre>/usr/share/color/icc/</pre>
+for both personal icc profiles or system wide ones. There is a small, but growing collection of freely available icc profiles for download on <a href="http://www.scribus.net">www.scribus.net</a>. Look in the Downloads > ICC section. Scribus on Windows or MacOSX will look in the default system directories. Earlier versions of Scribus will look in the directory specified in preferences.</li>
+<li>If you are new to color management, please look over the <A href="http://www.scribus.net/index.php?name=Web_Links&req=viewlink&cid=4" id="links and documentation" onclick="links and documentation">links and documentation</A> on color management listed on www.scribus.net. These explain the theory and concepts far better than I could here.</li></ul>
+<h4>Overview</h4>
+<p>The objective of a color management system is to reduce the differences between the on-screen colors and final printing, as well as showing colors which are out of gamut, beyond the color range of your selected printer. The caveat is you need to provide a profile of the printer and one for your monitor which is reasonably accurate. For users of other applications, the default settings and descriptions can be quite confusing to new users. Without prior knowledge of the terminology, it is <strong>very</strong> easy to choose the wrong settings. This can often makes images look worse on screen or print. Then, the first time user simply says enough and disables color management.</p>
+
+<p>In a word <strong>don't</strong>. Once you understand some basic concepts and know your final print destination, you will be able to predict - and - control more reliably how your document will look when printed. This is especially helpful when you will be sending files for later reproduction with four color printing or sending hi-resolution PDFs. The type of color management support within Scribus, I believe, is the first for an open source program. Future enhancements will bring even more exact control over color reproduction. The latest CUPS versions since 1.1.15+ now have support for true CMYK color printing. The newest version of little cms 1.15 has many new features which enhance the capabilities of Scribus to more accurately display color, along with much better performance. .</p>
+
+<p>The steps to making color management work reliably (what you see on screen is what you print) :</p>
+
+<ol>
+ <li>Learn a little bit about color management concepts and terminology. </li>
+ <li>Get the profiles setup properly. Below is a listing of color tools available for Linux. The most important is getting a good accurate monitor profile. The prof profilers do an excellent job at creating monitor profiles. <a href="moncal.html">Here</a> is a how to for creating ICC profiles for your monitor with the lprof profile tools. <strong>Without a properly created monitor profile, enabling color management will give you unsatisfactory results in printing and inaccurate previews on screen.</strong> </li>
+ <li>Embed the image profiles properly in image editing applications where possible.</li>
+
+</ol>
+
+<p>The color management system within Scribus is designed foremost for enabling color managed "soft proofs" of the images within the document. Scribus can also show "out of gamut" warnings for colors which might not be accurately reproduced by printing. (Most printers, have a narrower range of colors which can be printed, when compared to most monitors.) It does not embed or alter the profiles within your images. Some image files, png and Tiff, helpfully, can have an embedded ICM or ICC profile within the file header - also known as <strong><em>tagged</em></strong>, with a color profile. Later on, we will describe how and when it might be appropriate to use littlecms or Photopaint to apply a <strong>tag</strong> or embed a profile. If a file is <strong>tagged</strong>, Scribus will work with littlecms to read that profile within the image and use that profile to more accurately display the colors within an image. If an image does not have a tag but you know the device profile which should be assigned to the image, you can still use the CMS settings to preview with the profile temporarily assigned within the document. Caution is advised not to assign the wrong profile unless you are absolutely sure of the image source.</p>
+
+<p>The <strong>littlecms</strong> package has developed into a stable mature library. Independent tests vouch for its accuracy and littlecms is used within the printer firmware of some the most exotic and high end printers available. Given that this has come from a very small group of folks is really remarkably accurate considering the amount of development work done by large companies such as Kodak, Adobe, Agfa and others. </p>
+
+<p><strong>What are color or device profiles?</strong></p>
+
+<p><strong>ICC</strong> or <strong>ICM</strong> profiles are a special type of file which describes the color characteristic of a device like a scanner, monitor or printer - basically any device which can create or display manipulate the color of a digital image. There are also color profiles which are known as <strong>device independent</strong> or <strong>working space</strong> profiles. These special files can be thought of as translators which are used to convert from one type of color profile to another. An icc or icm file is a set of tables which describes the mathematical values by which devices measure and describe color. Fortunately, these are set by open international standards and work the same way on a Mac, Windows PC, Linux or Solaris.</p>
+
+<p><strong>Device Profiles</strong> - are separate files which describe the way a device creates (scanner or digital camera), displays (monitor) or outputs (printer) colors. Users of of Photoshop will be familiar with the choice of <strong>Working Profiles</strong> or <strong>Working Space</strong> - which are color profiles not related to a particular device, but to assist in the conversion of color from one device to another. Well known RGB "working spaces" Include sRGB, Adobe&#174; RGB 1998, Colormatch,Bruce RGB or CIERGB. Users of Photoshop or other color may be wondering if this is a missing feature, but littlecms uses its own internal color conversion process to make the transformation between color spaces. One less setting to worry about!</p>
+
+<table width="100%"><tr><td align="center"><img src="images/cmsmodify1.png" align="center" title="Color Management Preferences" alt="Color Management Preferences"/></td></tr></table>
+
+<table width="100%"><tr><td align="center"></td></tr></table>
+<p>Why "soft proofing" ? With the proper setup of device profiles, Scribus can adjust the colors of your monitor to more accurately represent how your document will actually look when finally printed., This can be doubly helpful if you are sending it to be printed commercially or for service bureau output. Moreover, each image can be individually modified by Scribus to assign profiles in an image, so that it can be properly color managed in document production, such as preparing film, a PDF/X-3 or direct to plate technologies. This does not however, alter the image file internally. Preview profiles <strong>assigned</strong> to an image are part of the setting retained in a Scribus document or in the creation of a PDF. There is also are command line tools in littlecms to embed profiles with <strong>tifficc</strong> and <strong>jpegicc</strong>. See the littlecms docs for exact options. You can also embed ICC profiles using Cinepaint, Imagemagick, Krita along with Adobe Photoshop.</p>
+<br />
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/cms.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripter-extensions.html
===================================================================
--- Scribus/doc/en/scripter-extensions.html (nonexistent)
+++ Scribus/doc/en/scripter-extensions.html (revision 13527)
@@ -0,0 +1,360 @@
+<html>
+<head>
+ <title>Scripter: Extension Scripts</title>
+</head>
+<body>
+</head>
+<body>
+
+<h2>Scripter: Extension Scripts</h2>
+
+<p>Author: Craig Ringer</p>
+
+<p>The Scribus Python plugin offers some additional features for
+extending Scribus with new capabilities and features, as opposed
+to automating tasks. In particular, it is possible to use 'extension scripts'
+to create new palettes and dockable windoes that can be used just like
+they were a part of Scribus.</p>
+
+<h3>Extension scripts</h3>
+
+<p>Extension scripts are mostly like normal Python scripts for Scribus.
+They're written somewhat differently so that they can be run with the
+"extension script" feature, giving them access to PyQt support and
+some other special features of the scripter. The most fundamental
+differences between normal scripts and extensions scripts are that:
+</p>
+
+<ul>
+
+ <li>Extension scripts can create Python objects that continue to exist
+ after the script exits. Objects will only continue to exist if a reference
+ to them still exists, most commonly because there's a name in the global
+ namespace that refers to them. This means that Python functions can be
+ called by Scribus - for example, as PyQt slots, or as callback functions on
+ an event.</li>
+
+ <li>Extension scripts can create code that runs without blocking the
+ execution of scribus, so you can create floating palettes that can be
+ present while the user works normally with Scribus (ie non-modal
+ palettes).</li>
+
+ <li>PyQt works correctly in extension scripts, unlike normal scipts.</li>
+
+ <li>Extension scripts can make changes to the Python environment that will
+ affect scripts run after it. Modules imported by one script can be seen by
+ another, settings changed by one may stay changed, etc. This means you have
+ to be somewhat more careful when writing extension scripts. In particular,
+ global names bound by one extension script can be overwritten by another,
+ causing the objects associated with those names to be cleaned up by the
+ interpreter. In other words, you can have name conflicts and interactions
+ between scripts, which you can't with normal scripts.</li>
+
+</ul>
+
+<h4>The technical bit</h4>
+
+<p>Normal scripts get run in a new Python sub-interepter that's used just for
+that script then cleaned up. This means that whatever Python objects they
+create and whatever Python settings they change get automatically reset when
+the script exits. Because Scribus takes care of cleaning up your script, you
+don't have to worry about memory, conflicting with other scripts, etc and can
+just get on with the business of writing the script.</p>
+
+<p>Extension scripts, by contrast, are run in a single Python interpreter that
+is started up when the script plugin loads. This interpreter keeps on running
+until the script plugin is unloaded when Scribus quits. When Scribus runs an
+extension script, it loads it into the running interpreter - much like
+<code>execfile</code> loads a Python script in another Python script. This lets
+extension scripts create new objects as they run, then exit to return control
+to Scribus without having the objects they created destroyed. If another script
+is then run, it can see all the objects created by the first script.</p>
+
+<p>There are several situations where being able to create objects from Python
+that hang around after the script exits is useful. The most signficiant is
+graphical programming with PyQt, where PyQt objects are created when the script
+runs and become functional only after the script exits, returning control to
+the Scribus event loop. Another possible use is for macros, event callbacks,
+and timers, where Scribus would need to be able to call Python code. You can
+do all these with PyQt right now, but there is no direct support for timers
+and callbacks in Scribus yet.</p>
+
+<p>There are some downsides to having objects persist after the script exits.
+Scripts can potentially interact in ways not thought of by their authors, which
+is often good but can also cause unexpected and surprising bugs. Script authors
+must also consider the effect of their code on the memory consumption of
+Scribus.<p>
+
+<h4>Building graphical add-ons in Python</h4>
+
+<p>Building new palettes and dialogs in PyQt is a fairly easy way to
+extend Scribus's user interface and provide extra facilities for
+advanced scripts. Python is well suited to getting data into and out of
+databases, content management systems, and other external repositories,
+and being able to build your own interfaces for this can be very
+helpful.</p>
+
+<p>In most ways, PyQt works the same when running within Scribus as it
+does when used in a stand-alone Python interpreter. There are
+differences, however, and it is important to understand these.</p>
+
+<ul>
+
+ <li>An instance of <code>QApplication</code> already exists, and attempting
+ to create one will have undesired consequences. You can access the existing
+ <code>QApplication</code> instance as <code>qt.qApp</code> if you need
+ it.</li>
+
+ <li>Scribus runs the Qt event loop. Entering the Qt event loop in PyQt will
+ probably prevent further execution of Scribus until your code exists, and
+ may have other undesired behaviour. The following documentation will cover
+ the correct approach to integrating your code into the event loop. In
+ brief, however, you simply create all your instances, show your windows,
+ and let your script exit. Qt will automatically integrate your windows into
+ its event loop and everything will "just work" - even Python slots and
+ Python widgets. In general, anything you want to keep around should be put
+ in the global namespace (as explained above). </li>
+
+</ul>
+
+<h4>The Basics - Converting Hello World</h4>
+
+<p>The first PyQt tutorial is the classic Hello World application. As
+an example of the differences between PyQt and Scribus, we'll convert
+that program to run in Scribus. Here's the original:</p>
+
+<pre>
+#!/usr/bin/env python
+import sys
+import qt
+
+a = qt.QApplication(sys.argv)
+
+hello = qt.QPushButton("Hello world!", None)
+hello.resize(100, 30)
+
+a.setMainWidget(hello)
+hello.show()
+sys.exit(a.exec_loop())
+</pre>
+
+<p>First, we need to disable the creation of <code>QApplication</code> since in
+Scribus a <code>QApplication</code> instance already exists, and only one is
+allowed per application. PyQt provides us with access to the
+<code>QApplication</code> that was created by Scribus when it starts up as
+<code>qt.qApp</code>. So, we simply replace:</p>
+
+<pre>
+a = qt.QApplication(sys.argv)
+</pre>
+
+<p>with</p>
+
+<pre>
+a = qt.qApp
+</pre>
+
+<p>and we're done with that change.</p>
+
+<p>Next, we need to prevent the script from trying to run its own event
+loop. Because Scribus has an event loop, if the script starts its own
+it will disrupt Scribus until it exits. Qt is smart enough to hook any
+windows you create into the existing event loop, so there's not much to
+do. While your script is running, Scribus is under the control of
+Python, so what we need to do is do all our setup (in this case, create
+a simple window and show it) but then <i>let our script exit</i>
+instead of running the event loop. Because all extension scripts run in
+the same Python interpreter, the objects you create are not destroyed
+when your script exits. It's a bit like loading a module. When your
+script exists, Scribus takes control and resumes running the Qt event
+loop. Because your windows are Qt widgets, the Scribus event loop looks
+after them and they work like a normal part of Scribus. When a Python
+slot is triggered or a Python function is called, PyQt automatically
+takes care of running the Python function then returning to Scribus.</p>
+
+<p>The only hitch with this scheme is that when your script terminates, all
+objects you create inside a function or other local scope will be cleaned up by
+Python as the scope is left (eg when leaving main()). This means that you need
+to keep a reference to everything at the global level so that it's not cleaned
+up. Support for PyQt in Scribus is very new, and there's no clear "right" way
+to do this yet. Options
+include:</p>
+
+<ul>
+ <li>Creating everything you want to keep in the global namespace. Caution
+ is required if your script is run multiple times.</li>
+
+ <li>Storing objects you wish to keep in a dictionary or class in the global
+ namespace. Most of the same problems exist with this as with storing the
+ objects directly as global names.</li>
+
+ <li>Putting your script in a module, then having the script the user runs
+ simply import the module and run a function in it. This looks like it'll be
+ the favoured approach. Note that the module body is not reloaded with every
+ import, so you should generally put any code you want run each time in a
+ function inside the module instead of the module top level. Alternately, you
+ could check if the module is already loaded and reload() it instead of
+ importing it anew.</li>
+</ul>
+
+<p>For now, because this script already creates everything as a global
+we're going to do things that way. Larger scripts should be written as
+modules.</p>
+
+<p>Given that the objects we need will already hang around when the
+script exits, all we need to do is prevent the script from entering the
+event loop. That's easy - just comment out the last line:</p>
+
+<pre>
+# sys.exit(a.exec_loop())
+</pre>
+
+<p>and we're nearly done. The script will run now, but when you
+close it it'll have a rather unintended effect - it'll close down
+Scribus. That's probably not what you want. This happens because a Qt
+application normally exits when its main widget ('main window') is
+closed. We call <code>qt.setMainWidget(...)</code> to make our new window the
+main widget, so when it's closed, Scribus goes with it. To prevent this, just
+comment out <code>qt.setMainWidget</code>.</p>
+
+<p>The new script looks like:</p>
+
+<pre>
+#!/usr/bin/env python
+import sys
+import qt
+
+a = qt.qApp
+
+hello = qt.QPushButton("Hello world!", None)
+hello.resize(100, 30)
+
+#a.setMainWidget(hello)
+hello.show()
+#sys.exit(a.exec_loop())
+</pre>
+
+<p>You'll find that script already saved as <code>pyqt_tut1.py</code> in the
+scripter examples directory. Try running it as an extension script. You should
+get a hello world button. Notice that you can keep working in Scribus as normal
+while it's there, and that when you close the hello world window it politely
+goes away without affecting Scribus.</p>
+
+<p>If you have a look at the sample copy of this tutorial script,
+you'll notice it has a few small additions. They are accompanied
+by some explanatory comments, so they won't be explored more here.</p>
+
+<h4>Fun with global names and shared interpreters</h4>
+
+<p>You may remember that I mentioned 'issues' with storing objects you
+want to keep as globals earlier? Unsurprisingly, I was dodging
+something I didn't want to have to explain right away.</p>
+
+<p>Storing objects as global names works fine ... until the user runs
+your script again, or runs another script that uses the same names.
+Python uses reference counting - an object continues to exist while one
+or more names refer to it. When the global name you created earlier is
+overwritten by another script or by another run of your script, there
+are no more references to that object (which might be a window the user
+is still using). Python does its job and helpfully deletes it for you -
+it doesn't know it might still be being displayed, or might be a slot
+that one of your windows is using. In many cases this will simply result
+in a window unexpectedly vanishing, but it can have nastier consequences
+too.</p>
+
+<p>Try this now. Run the hello world script (using "Load Extension
+Script...") and without closing the "Hello world" window, run the
+script again. The original window should vanish and be replaced with
+the new one.</p>
+
+<p>There aren't really any good solutions to this yet, and the right
+behavour depends on what exactly you want to do. I'd like to have some
+clearer recommendations to give, but for that I need use cases. If
+you're running into this issue, please post a description of your
+project on the Scribus mailing list and I or someone else will try to
+give you a few suggestions.</p>
+
+<p>The best solution so far is to use a simple wrapper script to run
+your script and put your real script in a module. The wrapper script
+imports your module then runs a function from the module to show the
+windows. Since the module is only run the first time it's imported, the
+window(s) will be displayed if they're not already visible, but won't
+be disrupted if they are still visible. You can reload() the module
+if you really want to re-run it, possibly after running some
+cleanup code.</p>
+
+<p>Better suggestions would be much appreciated. Feel free to post questions
+and ideas on the mailing list.</p>
+
+<h4>Other tricks</h4>
+
+<p>Even if you're not building a custom graphical user interface, it's
+possible to make use of extension scripts. For example, you can use
+PyQt to run a function on a timer. One use might be to check for
+updates to an article in a database and perhaps ask the user if they
+wish to update their document with the new text (or see the
+differences). You can find a very simple exmaple of setting up a timer
+with PyQt in the examples directory, called <code>pyqt_timer.py</code>.</p>
+
+<p>Another idea, as suggested by someone on the mailing list, was to
+write an XML-RPC server to expose the scripter API to external
+programs. This should be possible by using the PyQt classes for
+networking and event handling.</p>
+
+<h4>Other sources of information</h4>
+
+<p>This document isn't a PyQt or Qt tutorial. Good sources of information on Qt and PyQt are:
+
+</p><ul>
+ <li>The PyQt tutorial and examples from the PyQt documentation</li>
+ <li><a href="http://www.opendocs.org/pyqt/">Graphical Programming with Python - Qt Edition</a></li>
+ <li><a href="http://doc.trolltech.com/">TrollTech's Qt documentation (C++)</a></li>
+ <li>The <a href="http://www.digitalfanatics.org/projects/qt_tutorial/">Independent Qt Tutorial</a></li>
+ <li><a href="http://www.qtforum.org/">QtForum.org</a></li>
+</ul>
+
+<h3>Cleanly handling being run outside Scribus</h3>
+
+<pre>
+try:
+ import scribus
+except ImportError:
+ print "This script can only be run as an extension script from Scribus"
+ sys.exit(1)
+</pre>
+
+<p>This tries to load the Scribus scripter interface, and if it fails
+assumes it is not running under Scribus and complains. It's a good idea
+to do this in all your scripts so that you don't confuse users who try
+to run them with the standalone Python interpreter. Try running the
+script with <code>python pyqt_tut1.py</code> and note how it tells the user why
+it won't work then exits. This is much nicer than an import error or bizarre
+behaviour.</p>
+
+<h3>Unanswered questions and missing features</h3>
+
+<p>Support for extending Scribus from Python is still very much a work
+in progress. Lots works fine, but there are lots of unexplored corners.
+Feedback, suggestions, requests, ideas and offers of help would be much
+appreciated and can be directed to the mailing list or to the author(s)
+of this document.</p>
+
+<p>Note that in particular there is no support for:
+</p><ul>
+ <li>Using PyQt from normal scripts (as opposed to extension scripts)</li>
+ <li>Using PyGtk or wxPython</li>
+ <li>Threading (PyQt threads might work within the limits of Qt's threading support)</li>
+ <li>Hooking into the right-click menu (yet!)</li>
+ <li>Triggering scripts on certain events (being considered)</li>
+ <li>Easily and reliably hooking into the menus</li>
+ <li>Extending Scribus dialogs</li>
+ <li>Using Scribus custom widgets and classes</li>
+ <li>Anything that requires you to hand over control to its event loop without returning (these will work, but block Scribus).</li>
+</ul>
+
+<p>Some of these are just not done yet, some are extremely difficult, and some
+we don't know how to do at all or don't plan to attempt.</p>
+
+</body>
+
+</html>
/Scribus/doc/en/scripter-extensions.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox14.html
===================================================================
--- Scribus/doc/en/toolbox14.html (nonexistent)
+++ Scribus/doc/en/toolbox14.html (revision 13527)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>LProf</title>
+</head>
+<body>
+<h2>LProf</h2>
+<p>For those running BSD, Linux or Unix <a href="http://lprof.sourceforge.net/">LProf</a> is an essential tool for making color management work reliably in Scribus. Why so?</p>
+
+<h3>LProf is like visiting your eye doctor.</h3>
+
+<p>LProf is the only graphical tool available on Linux and Unix capable of creating ICC monitor profiles or scanner profiles. It also works on Windows and, soon, Mac&nbsp;OS&nbsp;X. Very simply LProf is a tool for creating an ICC profile of your monitor which helps make color managed previews more accurate. Think of a monitor profile as a set of glasses which magically transform your eyes to see with perfect color balance. Within Scribus a correct monitor profile can make a big difference in viewing accurately how your print or PDF will appear on a PostScript printer or when printed commercially. Without an individual profile of your monitor&nbsp;&mdash; no two monitors are alike&nbsp;&mdash; you have no real assurance the color transforms will be anywhere near close, when you are for example sending PDFs to a printer. </p>
+<p>LProf has a simple step by step method to walk you through creating a profile of your monitor which then can be used in Scribus. You should take the 5 minutes it takes to create a profile and then add this to your Scribus Color management preferences. LProf can also create profiles for your scanner or digital camera. A look at the LProf's documentation will give you a more detailed understanding of its capabilities. </p>
+<p>Currently available released version (0.11.4) doesn't allow using calibration devices yet. Adding this feature is a work in progress and quite successful one: with the next version of LProf you will be able to use devices like X-Rite DTP94, EyeOne Display 2 and EyeOne Display LT to measure your display on both Windows and Linux.</p>
+
+<p>On Mac&nbsp;OS&nbsp;X, you can also use the native built in ColorSync applet to create a monitor profile. On Windows, if you have installed Photoshop, Indesign or Illustrator, Adobe Gamma performs a similar, if more simplistic method of creating a monitor profile.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/lprof.png" alt="LProf creating a profile." /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/en/gsadv.html
===================================================================
--- Scribus/doc/en/gsadv.html (nonexistent)
+++ Scribus/doc/en/gsadv.html (revision 13527)
@@ -0,0 +1,109 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Advanced Ghostscript and GSview Hints</title>
+</head>
+<body>
+<h2>Advanced Ghostscript and GSview Hints</h2>
+<p>One of the frustrations for users of RPM-based or commercially created distros, is the lack of availability of the latest versions of Ghostscript(GS). Because of the differences in licensing between the GPL Ghostscript and AFPL Ghostscript, GPL Ghostscript releases usually follow by about a year, the release of the most up to date AFPL GS. Because, there are certain restrictions in AFPL, most Linux distros ship an older and heavily patched version of GPL Ghostscript.</p>
+<p>As the current GS 8.x resource configuration is new, simply dropping in the latest GS tarball and rebuilding the RPM does not quite work. Lord knows I've tried on Red Hat and I consider myself to be pretty well versed in RPM building. If you have ever seen the Red Hat or SuSE rpm spec file for GS, you will know what I mean. ;)</p>
+<p>So, why do I want to go to the trouble of worrying about having the absolute latest version of GS? Easy.</p>
+
+<ol>
+ <li>There are real substantial improvements in the ability of GS 8.x to handle EPS and PDF files which have the kinds of advanced features Scribus and other DTP applications can create. <strong>This can in some cases directly affect the quality of EPS and PS imports into Scribus.</strong></li>
+ <li>You can build it with full on compiler optimization, which speeds up print and separation previews in Scribus. This is probably more beneficial to older workstations, compared to newer ones. My alternative GS is compiled with:
+ <blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+ <pre>--march=i686 -fomit-frame-pointer -O2.</pre>
+ </td></tr></table></blockquote>
+ Image processing programs are one area where compiler optimizations <strong>do</strong> make a difference.</li>
+ <li>Having the latest GS, makes GSview (and Scribus) more capable and more robust at handling both EPS files and a special kind of EPS called DCS 2.0.</li>
+ <li>Both Scribus and GSview have the ability in their preferences settings to use alternative locations for GS and GS libraries.</li>
+</ol>
+<p>So, how does one get the latest GS for Scribus and GSview - without breaking your existing distro printing setup ? The secret: a parallel build of GS.</p>
+<p><b><i>Disclaimer:</i></b> This works for me. It could wreck you system, catch your hair on fire and other nastiness. </p>
+
+<p>First Steps:</p>
+<ul>
+ <li>Get the latest GS from here: <a href="http://ghostscript.com/doc/AFPL/" >http://ghostscript.com/doc/AFPL/</a></li>
+ <li>You can manually tweak the make files the old way or</li>
+ <li>Use the new configure script with the following options (and optionally <code>-with-jasper</code> and <code>-with-rinkj</code> with very latest versions): </li></ul>
+</ul>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>./configure --enable-compile-inits --with-x</pre>
+</td></tr></table></blockquote>
+<p>By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>--prefix=$HOME</pre>
+</td></tr></table></blockquote></p>
+
+<p>This default usually works fine and keeps the two sets of GS libs separated.</p>
+<p>Second Steps:</p>
+<p>There is a second step to compile Ghostscript as a shared library, which GSview needs:</p>
+<p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>make so</pre>
+</td></tr></table></blockquote>
+and as root:
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>make soinstall</pre>
+</td></tr></table></blockquote>
+</p>
+
+<p> Now, let's check briefly:</p>
+<p><blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>/usr/local/bin/gs -h</pre>
+</td></tr></table></blockquote>
+</p>
+<p>You should have an output something like this:</p>
+
+<p></p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>AFPL Ghostscript 8.51 (2005-04-18)
+Copyright (C) 2005 artofcode LLC, Benicia, CA. All rights reserved.
+Usage: gs [switches] [file1.ps file2.ps ...]
+Most frequently used switches: (you can use # in place of =)
+ -dNOPAUSE no pause after page | -q `quiet', fewer messages
+ -g&#060;width&#062;x&#060;height&#062; page size in pixels | -r&#060;res&#062; pixels/inch resolution
+ -sDEVICE=&#060;devname&#062; select device | -dBATCH exit after last file
+ -sOutputFile=&#060;file&#062; select output file: - for stdout, |command for pipe,
+ embed %d or %ld for page #
+Input formats: PostScript PostScriptLevel1 PostScriptLevel2 PostScriptLevel3 PDF
+Default output device: x11
+Available devices:
+ bbox bit bitcmyk bitrgb bj10e bj200 bjc600 bjc800 bmp16 bmp16m bmp256
+ bmp32b bmpgray bmpmono bmpsep1 bmpsep8 cdeskjet cdj550 cdjcolor cdjmono
+ cljet5 cljet5c deskjet devicen djet500 epswrite faxg3 faxg32d faxg4 ijs
+ jpeg jpeggray laserjet lj5gray lj5mono ljet2p ljet3 ljet3d ljet4 ljet4d
+ ljetplus nullpage pbm pbmraw pcx16 pcx24b pcx256 pcxcmyk pcxgray pcxmono
+ pdfwrite pgm pgmraw pgnm pgnmraw pj pjxl pjxl300 pkm pkmraw pksm pksmraw
+ png16 png16m png256 pngalpha pnggray pngmono pnm pnmraw ppm ppmraw
+ psdcmyk psdrgb psgray psmono psrgb pswrite pxlcolor pxlmono spotcmyk
+ tiff12nc tiff24nc tiffcrle tiffg3 tiffg32d tiffg4 tifflzw tiffpack
+ uniprint x11 x11alpha x11cmyk x11gray2 x11gray4 x11mono xcf
+Search path:
+ . : /home/peter/.fonts : /usr/local/share/ghostscript/8.51/lib :
+ /usr/local/share/ghostscript/8.51/Resource :
+ /usr/share/ghostscript/fonts
+</pre>
+</td></tr></table></blockquote>
+<br />
+<p>The key thing here is:</p>
+<ol>
+ <li>You see the correct version of GS</li>
+ <li>You have pngalpha and the x11devices listed</li>
+ <li>There is a reasonable search path for fonts, so GS can find your fonts. You will get errors in Scribus, when attempting to import EPS files or using the print preview, if this path is not set correctly and GS cannot find fonts. GS determines where to find fonts in a file called Fontmap. Setting this option is explained in the GS documentation.</li>
+</ol>
+<p>If you are concerned about messing about with your existing packaging setup, you could use: <a href="http://asic-linux.com.mx/~izto/checkinstall/">checkinstall</a> or <a href="http://xstow.sourceforge.net/">Xstow</a>. These programs will keep track of applications which are outside of your normal packaging system. I have used checkinstall with good luck in these kinds of situations on RedHat systems.</p>
+<p>Next,if installed, open up GSview and go to <strong>Options.. > Advanced Configure.</strong> Then, make sure the "Ghostscript Shared Object" is pointing at the correct libgs.so. Below is how I have setup GSview on my system.: </p><br />
+<table width="100%"><tr><td align="center"><img src="images/gsadv1.png" alt="GSview - Advanced Options Panel" align="middle" title="GSview - Advanced Options Panel" /></td></tr></table>
+<p>Next, we need to tell Scribus where to find the newer GS. Go <strong>Edit..> Preferences.. >General.</strong> Then in <strong>External Tools</strong>, add the path the new GS.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/gsadv2.png" alt="Scribus External Tools Preferences" align="middle" title="Scribus External Tools Preferences" /></td></tr></table>
+
+<p>Another tool which is available with GSview is <strong>epstool</strong>. An older version is shipped with the current GSview 4.7, but a newer one is available on the GSview home page. This is a great command line tool, which can perform advanced EPS/DCS 2.0 conversion. This is very useful when someone sends you an EPS file from other DTP applications - even those created on Macs. Upgrading this to work with GSview gives you excellent support on Linux to handle EPS files from all platforms. Recommended.</p>
+<p>Lastly, one other tool which works as a plug-in with GSview is <a href="http://pstoedit.net">pstoedit</a> This is a command line tool for converting bitmap images into vectors and PostScript, which then, depending on the nature of the image, can be edited in a vector drawing tool like Inkscape or Skencil. See the section <a href="importhints.html">Import Hints</a> for hints on how I used this to convert the Scribus logo into SVG and then a native Scribus file. GSview uses this as a plug-in to convert files into vector format. </p>
+
+<p>GSview has been, in my experience, the most reliable and
+versatile EPS/PS viewer on Linux. How good is it ? Well, the best example is letting you know this usually installed on every Windows DTP workstation I support for clients. For DTP with Scribus, I consider it essential.</p>
+</body>
+</html>
/Scribus/doc/en/gsadv.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/importhints4.html
===================================================================
--- Scribus/doc/en/importhints4.html (nonexistent)
+++ Scribus/doc/en/importhints4.html (revision 13527)
@@ -0,0 +1,56 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Notes on Importing HTML into Scribus</title>
+</head>
+<body>
+<h2>Notes on Importing HTML into Scribus</h2>
+
+<p>Scribus has an HTML importer which can import clean, well formed HTML and retain much of the layout and and formatting, provided the formatting or styling is basic HTML <strong>in the HTML markup</strong>, not via css style sheets. CSS support will come in the future.</p>
+<h4>So what kind of HTML is supported and how does it work ?</h4>
+<p>Upon import, the importer will create paragraph styles which correspond to the html markup. Bold, Italics and monospace text and alignment are also supported. Below is a listing of the HTML markup supported - both upper and lower case tags. </p>
+<ul>
+<li>body, div, a - Text must be within the &#060;body&#062; tags.</li>
+<li>p and br - Corresponding to paragraph and line breaks.</li>
+<li>H1 to H4 - Correspond to Heading Sizes 1 to 4.</li>
+<li>ol,ul,li - Corresponding to ordered or unordered lists.</li>
+<li>pre and code - Corresponding to preformatted text and source code listings. These will be converted to text using the fixed pitch font Courier.</li>
+<li>www. style web links are converted to text with blue coloring to highlight them in the same manner as most web browsers do in their default settings.</li>
+<li>b, u, i, em, strong,sub.sup,del,u - Text formatting is converted to the corresponding font styles. Note, your default font should have all of these variants available to Scribus. </li>
+</ul>
+Hence the following section of html will display and create paragraph styles in Scribus as demonstrated below.
+<pre>
+&#060;?xml version="1.0" encoding="utf-8"?&#062;
+&#060;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&#062;
+&#060;html xmlns="http://www.w3.org/1999/xhtml"&#062;
+&#060;head&#062;
+&#060;title&#062;&#060;/title&#062;
+&#060;meta http-equiv="Content-Type" content="text/html; charset=utf-8" /&#062;
+&#060;/head&#062;
+&#060;body&#062;
+&#060;h1&#062;H1 Text&#060;/h1&#062;
+&#060;h2&#062;H2 Text&#060;/h2&#062;
+&#060;h3&#062;H3 Text&#060;/h3&#062;
+&#060;h4&#062;H4 Text&#060;/h4&#062;
+&#060;ol&#062;
+&#060;li&#062;Ordered List Item 1 &#060;/li&#062;
+&#060;li&#062;Ordered List Item 2 &#060;/li&#062;
+ &#060;/ol&#062;
+ &#060;ul&#062;
+&#060;li&#062;Un-Ordered List Item 1 &#060;/li&#062;
+ &#060;li&#062;Un-Ordered List Item 2 &#060;/li&#062;
+ &#060;/ul&#062;
+ &#060;code&#062;code listings&#060;/code&#062;
+ &#060;p&#062;&#060;b&#062;Bold Paragraph Style&#060;/b&#062;&#060;/p&#062;
+ &#060;p&#062;&#060;i&#062;Italic Paragraph Style&#060;/i&#062;&#060;/p&#062;
+ &#060;p align="center"&#062;Centered Text&#060;/p&#062;
+&#060;/body&#062;
+&#060;/html&#062;</pre>
+<p>Below the imported styles from the file above. </p>
+<table width="100%"><tr><td align="center"><img src="images/htmlstyle.png" alt="HTML Styles imported into Scribus" title="HTML Styles imported into Scribus " /></td></tr></table>
+<p>Below is the imported text displayed on the canvas:</p>
+<table width="100%"><tr><td align="center"><img src="images/htmlimport.png" alt="HTML imported into Scribus" title="HTML imported into Scribus " /></td></tr></table>
+<p>Not all applications export HTML with high fidelity to the W3C specifications. You can use htmltidy to clean up and make conformant HTML text you need to import. See : <a href=" http://w3c.org"> http://w3c.org</a>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/importhints4.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/cms4.html
===================================================================
--- Scribus/doc/en/cms4.html (nonexistent)
+++ Scribus/doc/en/cms4.html (revision 13527)
@@ -0,0 +1,36 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Color management with Scribus, an Introduction Part 4</title>
+</head>
+<body>
+<h2>Color management with Scribus, an Introduction Part 4</h2>
+<h4>PDF/X-3 and Color Management</h4>
+<p>Above, we covered the basics of getting color management working and configured properly. Now, let's consider using PDF/X-3 to optimize our output for commercial printing. PDF/X-3 is the latest and most advanced ISO standard for PDF files and Scribus fully supports it, as well as being the first DTP app to be able to directly export PDF/X-3 conforming files.</p>
+
+<p>The principal benefit of PDF/X-3 is the typically more accurate color conversion from RGB to a printer's CMYK output. The accuracy comes from working in RGB colors until very late in the printing process when the printer's own RIP does the RGB >CMYK conversion. The downside is only the latest and most updated RIPs support PDF/X-3, although others may support earlier PDF/X-x standards. As the RIP engine has detailed knowledge of the exact color range and capabilities, it is thought to offer, in most cases, a more accurate conversion. PDF/X-3 does not preclude using CMYK images, but is ideal for maintaining your colors in RGB as long as possible in the process. </p>
+<p>The major downsides to working in PDF/X-3 are twofold: You cannot use transparency natively. PDF/X-3 is based on PDF 1.3, which does not support transparency. The second is the limited, but growing number of printers who can support it. If in doubt, inquire. My testing show very reliable results with a minimum of color shifting. </p>
+<p></p>
+<p>The other issue is which printer profile should I use. There are two strategies: The first is to have an actual ICC profile from your print for the matching paper type. The second is to use a well-known printing standard as SWOP, ECI or others. Using PDF/X-3 requires cooperation from your printer, but can really improve your print color matching. As always, a short visit to your printer <strong>in advance</strong> is strongly recommended. If answers are not forthcoming, try another one. Printing is a competitive business and alternatives almost always can be found.
+
+
+<p><strong>Real World Experiences</strong></p>
+
+<p>The author has been testing Scribus with a variety of images with color management enabled in Scribus. These high resolution RGB and CMYK TIFFs were prepared using the latest color management tools with Windows 2000, Photoshop 6 with hardware calibrated and profiled professional DTP monitors, then later proofed with Level 3 PostScript printers. Using images have been used as cover photos for a magazine with a circulation of over one million per annum. Using the same printer profiles that are used in the production of the magazine, littlecms and Scribus can create previews which are remarkably accurate given the relative newness of littlecms and Scribus. The accuracy of littlecms has improved in every version of 1.1x, especially with absolute colorimetric intents. littlecms 1.11+ has Black Point Compensation, which can be used by Scribus if lcms 1.11+ is installed. This helps to improve contrast in photos.</p>
+
+
+
+<p><strong>Conclusions</strong></p>
+
+<p>So, by example, we have simply described a color managed strategy for our document. Take the image from the source, properly apply profiles and then choose correct rendering intents for conversions to another color model. In our example, Scribus, by checking the simulate printer box, tells littlecms to make a two step conversion so your monitor represents with reasonable accuracy how your images and color will print.</p>
+
+<p>Attempting to incorporate a simple, but effective color management system within Scribus is an ambitious, and the author believes first serious open source attempt to provide the end user with color management. These type of tools are more typically only found in high end professional pre-press applications. As this is uncharted territory for open source, your comments and suggestions on this document,as well as your experience using color management are most welcome. The reader should also know color management is still being perfected by the graphics industry.</p>
+
+<p><strong>Have Patience</strong> - color management is a new and improving part of DTP. It takes quite a bit of time to understand the theory, which then brings practical results. </p>
+
+<p>Acknowledgments:</p>
+
+<p>Mart&iacute; Maria; Developer of little cms, without which this would not be possible.</p>
+
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/cms4.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/install.html
===================================================================
--- Scribus/doc/en/install.html (nonexistent)
+++ Scribus/doc/en/install.html (revision 13527)
@@ -0,0 +1,29 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Installation of Scribus</title>
+</head>
+<body>
+<h2>Installation of Scribus</h2>
+
+<p>The installation process of Scribus depends on the distribution of Linux/Unix that you are using. This is the case just like it is for any program you may wish to install. The following are examples for how to install Scribus on various distributions:</p>
+<table border="1">
+ <tr bgcolor="#dddddd"><td>Linux Distribution</td><td>Install Method</td></tr>
+ <tr bgcolor="#eeeeee"><td>Debian</td><td><code>apt-get install scribus</code> or preferably use one of the graphical front-ends such as &#034;Synaptic&#034; that handle &#034;Recommends&#034; correctly. For further information please read <a href="install-dpkg.html">How to use the Scribus Debian Repository</a></td></tr>
+ <tr bgcolor="#eeeeee"><td>Gentoo</td><td><code>emerge scribus</code></td></tr>
+ <tr bgcolor="#eeeeee"><td>PLD</td><td><code>poldek -i scribus</code></td></tr>
+ <tr bgcolor="#eeeeee"><td>RedHat/Fedora</td><td><code>rpm -Uvh ./scribus-1.x.rpm</code></td></tr>
+ <tr bgcolor="#eeeeee"><td>Slackware</td><td>Install from source, until 1.2 is part of Slackware</td></tr>
+ <tr bgcolor="#eeeeee"><td>SuSE</td><td>Use Yast2 for installation, OR, <code>rpm -Uvh ./scribus-1.x.rpm</code></td></tr>
+ <tr bgcolor="#dddddd"><td>Other OS</td><td>Install Method</td></tr>
+ <tr bgcolor="#eeeeee"><td>FreeBSD</td><td><code>cd /usr/ports/print/scribus; make install</code></td></tr>
+ <tr bgcolor="#eeeeee"><td>Mac OSX</td><td>Please refer to the <a href="cross-platform.html">Cross Platform</a> section</td></tr>
+ <tr bgcolor="#eeeeee"><td>Windows&#8482;</td><td>Please refer to the <a href="cross-platform.html">Cross Platform</a> section</td></tr>
+</table>
+
+<p>Depending on the version of your distribution, there is the possiblity that you may need to upgrade various dependencies of Scribus and the above commands should make sure the required packages are installed.</p>
+<p>For example, to access the font files you want to use in Scribus, Scribus relies on FreeType. For getting the best results we recommend using FreeType version 2.1.9 or later. Without having certain levels of software, we cannot guarantee correct operation of Scribus, or guarantee you achieve the results you are trying to get. If the above commands do not upgrade all the dependencies on your system, please refer to the <a href="install2.html">Requirements</a> page to make sure you have them.</p>
+<p>For those who wish to install a more recent version of Scribus than that is included in their distribution, please check you have all the <a href="install2.html">Requirements</a> and continue into the <a href="install1.html">Scribus Source</a> section.</p>
+
+</body>
+</html>
/Scribus/doc/en/install.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/fonts5.html
===================================================================
--- Scribus/doc/en/fonts5.html (nonexistent)
+++ Scribus/doc/en/fonts5.html (revision 13527)
@@ -0,0 +1,48 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+
+ <title>Basic Font Tests - Part 2</title>
+</head>
+<body>
+ <h2>Basic Fonts Tests - Part 2</h2>
+
+<h4>A second quality check for fonts.</h4>
+<p>Included with Scribus is a wonderful and very powerful example of what the python scripter in Scribus can do. The font sampler script, written by Steve Callcott, is a tool to create a nicely laid out catalog of your existing font, which you can print and bind, as well as make a PDF for reference. It also happens to make it easy to spot broken fonts or fonts which are missing needed glyphs which might pose a problem when printing, especially high end or commercial printing.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/fontsampler.png" alt="Font Sampler with all fonts selected" title="Font Sampler with all fonts selected"/></td></tr></table>
+
+
+
+<p>Using this scripter module requires:
+<ul>
+<li>tkinter - which provides the Graphical UI for Python Scripts</li>
+<li>Optionally, python-imaging, which is a set of python libraries for image handling and provides the nice preview above.</li>
+<li>Obviously, python support built in Scribus.</li>
+</ul>
+</p>
+<p>Running is easy enough:</p>
+
+<table width="100%"><tr><td align="center"><img src="images/Scripter.png" alt="Launching the Font Sampler" "title="Launching the Font Sampler"/></td></tr></table>
+
+<p>Now, depending on the number of fonts, kinds of fonts and speed/memory of your machine, it might take a while for the script to run. Approximately, 700 plus fonts on a P4 might will take a few minutes, but also remember the script is not only scanning all your fonts, but also automagically adding pages and laying them out too. If memory is short or you have lots of fonts, in the order of 1000 plus, you might want to split the job in parts.</p>
+
+
+
+<h4>Results: </h4>
+
+<table width="100%"><tr><td align="center"><img src="images/fontsampler2.png" alt="Scripter output showing broken font" title="Scripter output showing broken font"/></td></tr></table>
+
+<p>Note the output on the left and the right. The left side is a known high quality Type 1 font. The right side shows a freeware font from a bug report. Note, the lack of glyphs above, does not always indicate a broken font. Some specialty fonts like symbol fonts, dingbats and some non-Latin fonts may show the same results, but for a normal font, the results above are usually an indication of possible trouble.</p>
+
+
+<h4>Looking in the console</h4>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>Font /usr/X11R6/lib/X11/fonts/URW/p052023l.pfb is broken, discarding it
+Font /usr/X11R6/lib/X11/fonts/URW/p052023l.pfb is broken, discarding it
+Font /usr/X11R6/lib/X11/fonts/URW/p052023l.pfb is broken, discarding it....
+</pre>
+</td></tr></table></blockquote>
+When running the console, Scribus will indicate fonts which are dropped on loading and then again when used if specific glyphs are missing or broken. The same font might be listed several times as Scribus is using freetype to scan for available glyphs. <strong>This is a Good Thing &#8482;</strong> Bad fonts cause crashes in Scribus and other nastiness down the line when you export or print.
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/fonts5.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/settings1.html
===================================================================
--- Scribus/doc/en/settings1.html (nonexistent)
+++ Scribus/doc/en/settings1.html (revision 13527)
@@ -0,0 +1,147 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Settings and Preferences Panels</title>
+</head>
+<body>
+<h2>Settings and Preferences Panels</h2>
+
+<p>The settings panels are the heart of changing the default behaviors of Scribus and give you considerable flexibility in setting document and program defaults. If you are new to page layout, some of these terms might not be familiar, but there is a multi-lingual glossary on <a href="http://wiki.scribus.net">http://wiki.scribus.net</a> compiled by a group of Scribus users, as well as the included documentation. </p>
+
+
+
+<h4>Where Are the Preferences Files ?</h4>
+<p>Scribus' preferences are kept in a hidden directory <code>.scribus</code>. The location of which is as follows:
+<ul>
+<li><strong>Linux:</strong> Under your $home directory, %username/.scribus</li>
+<li><strong>MacOSX:</strong> Under User/%username/.scribus</li>
+<li><strong>Windows:</strong> Documents and Settings/%username/.scribus</li>
+</ul>
+ Within the directory is a <code>.scribus13.rc</code> file, a <code>scribusfont.rc</code> file which preserves your font preferences and a <code>prefs13.xml</code>. These files are stored in XML format, so you can inspect its contents with a text editor. If you have installed the scripter plug-in, there will also be a <code>scripter.rc</code> file which lists most recently used scripts. There might also be several directories, which are configuration or history files. If you are troubleshooting starting Scribus, <strong>rename</strong>, do not delete these files and directories. If you rename the directory, on re-starting Scribus, the launch time will be somewhat longer, as Scribus creates a cache of installed fonts. On the second re-start of Scribus, it will be much quicker. </p>
+
+<p>You can change the Document Setup preferences while a document is open and those preferences will remain only for the currently open doc. When you change the application preferences, any new documents will inherit these preferences and default settings.</p>
+
+<p>Within these panels below, you can change many of the defaults for Scribus, many of which can be changed or overridden in with a menu or right click context menu on an object while editing or in the measurements palette.</p>
+
+<p><strong>Note: The screen captures below are on Windows 2000, Linux and MacOSX may vary slightly.</strong></p>
+
+<h3>General Tab</h3>
+<p>You can change the default theme with Scribus to include themes like Liquid or the new themes based on KDE plug-ins. Scribus will inherit KDE themes and decorations if you have KDE running. If you do not have KDE installed, you can also tune the look of your Qt programs separately with <strong><code>qtconfig</code></strong> from the command line. Simply open a console window and type <code>qtconfig</code>. The configuration panels in Qtconfig are pretty self explanatory. I would advise not increasing the font size above 12 points, as some buttons in Scribus menus might be obscured. In this example, the fonts have been changed to TrueType fonts at 12 points and Scribus is using the default theme inherited from KDE.</p>
+
+<p>On MacOSX and Windows, you do not need to access qtconfig as it inherits the styles from the operating system. However, changing the default to Platinum or other style, may not appear so attractive and these styles are primarily for Linux and Unix systems.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs.png" align="center" alt="Edit Style Dialog" title="General Preferences" /></td></tr></table>
+
+<p>Note also that the "Languages" drop down can be blank. This merely means Scribus will use the system's default language.</p>
+
+<h3>Mouse settings</h3>
+<p>If you have a wheel mouse, one of the nice defaults of Scribus is using this to scroll through a Document. Wheel jump changes the number of lines for each scroll of the mouse wheel. <strong>Grab Radius</strong> defines how much distance is allowed to select an object. Smaller numbers mean more
+precise, but sometimes more difficult selection of smaller objects.</p>
+
+<h3>Paths</h3>
+<p>These are user selectable paths for your documents, ICC color profiles and python scripts. Changing them is simply clicking on your preferred location. Note: hidden directories are not viewed by default, but can be seen by right clicking the file selector widget and choosing. "Show Hidden".</p>
+
+<h3>Document</h3>
+<p>This panel sets the defaults for paper size, page margins and Auto save options. Auto-save enables Scribus to save your file with a backup file with <code>.sla.bak</code> extension. The section "Preset Layouts" will offer you a choice of standard margin settings, depending on wether you are creating a book, magazine or other document. You can also choose to have the left or right page first as well.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs2.png" align="center" alt="Default Document Settings" title="Default Document Settings" /></td></tr></table>
+
+<h3>Guides</h3>
+<p>This panel sets the default distances and colors, as well as the snap to settings. <strong>Baseline Grids</strong> is the set of horizontal guides which forces text in multiple columns to align horizontally, as shown below. Settings for the distances for baselines are in Paragraph Styles, as well as the next panel <strong>Typography</strong></p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs3.png" alt="Guides and Baseline Grid Settings" align="middle" title="Guides and Baseline Grid Settings" /></td></tr></table>
+
+<h3>Typography</h3>
+<p>Here you can change options for typographic features including subscript, superscript, automatic line spacing and scaling of small capitals. <strong>Disp.:</strong> means displacement or difference in distance above/below normal text. <strong>Baseline Grids</strong> are non-printing grids which align text across multiple columns on the page. <strong>Baseline Offset</strong> is the distance from the top of the page where the topmost baseline is placed.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefsblgrid1.png" alt="Baseline Grids"title="Baseline Grids" /></td></tr></table>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs4.png" align="center" alt="Typography Tab Panel" /></td></tr></table>
+
+<h3>Tools</h3>
+<p>In the Tools tab you can change the defaults for many common tasks and tools: font, size and color, text frame defaults, image frame defaults and zoom defaults. Most all of these can be overridden or changed with the the right click context menu or in the Properties Palette when selecting an object.You can also override these in the Document Setup dialog.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs5.png" alt="Tools Tab Panel"/></td></tr></table>
+
+<h3>Polygon objects</h3>
+<p>You can make stars, triangles and convex polygons with intuitive controls. You can also apply gradient colors to all of these shapes within the measurements panel. </p>
+
+<h3>Hyphenation</h3>
+<p>Hyphenation details are described here: <a href="hyphenator.html">Hyphenation in Scribus</a>.</p>
+
+<h3>Fonts</h3>
+<p>Selecting and installing fonts correctly is one of the most important configuration items with Scribus and an extensive set of notes is here: <a href="fonts1.html">Fonts and Scribus</a>. If there is one part of the documentation you really must read, it is this one.</p>
+
+<h3>Color Management Settings</h3>
+<p>Note in this dialog, the setting of sRGB is <strong>incorrect</strong> for a monitor profile. There are detailed notes on <a href="cms.html"> Color Management under Scribus</a> and <a href="moncal.html">Creating a Monitor Profile with Littlecms</a>. MacOSX and Windows users can use commercially available tools like Monaco's Color Tools, Eye-One, Adobe Gamma and Scribus can use them along side other color savvy applications. MacOSX users can use any of the profiles available to Color Sync. Scribus will automatically discover any system profiles installed.</p>
+<table width="100%"><tr><td align="center"><img src="images/prefs10.png" alt="Setting the PDF Preferences for Scribus" title="Setting the PDF Preferences for Scribus" /></td></tr></table>
+<p><strong>Note: </strong>PDF/X-3 preferences are disabled if color management is disabled. CMS must be enabled to use PDF/X-3.</p>
+
+<h3>PDF Export Options</h3>
+<p> For more info on PDF look at <a href="pdfexport1.html">PDF Export Options</a> and <a href="pdfx3.html">PDF/X-3 and Scribus</a>.. This section of the preferences has extensive tool tips as well.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs11.png" alt="Setting the PDF Preferences for Scribus" title="Setting the PDF Preferences for Scribus" /></td></tr></table>
+
+<h3>Documents Items and Table of Contents</h3>
+<p>This new functionality is explained here: <a href="http://wiki.scribus.net/index.php/Creating_a_Table_of_Contents">http://wiki.scribus.net/index.php/Creating_a_Table_of_Contents</a></p>
+
+<h3>Keyboard Short-Cuts</h3>
+
+<table width="100%"><tr><td align="center"><img src="images/prefs12.png" alt="Setting the Keyboard Shortcuts for Scribus" title="Setting the Keyboard Shortcuts for Scribus" /></td></tr></table>
+
+<p>Scribus gives you complete flexibility with respect to keyboard shortcuts. Moreover, once customized, you can export them into a separate XML file which can be exported and saved separately, along with making it portable to other machines. The default file suffix is .ksxml. The XML is a unicode file and should not have issues being transported across platforms, with the only caveat that Macs have an option and command meta key, where Linux and Windows share common keyboards.</p>
+
+<h3>Scrapbook</h3>
+<p>With scrapbooks, you can <em>right button</em> drag and drop frequently used items, including pictures, images and text files for quick placement. Scrapbooks can be saved with a file or independently of a document, as a separate scrapbook which can be loaded use with many different Documents. Separate scrapbooks are kept with a <code>.scs</code> designation. This panel sets the defaults for the thumbnail size in the scrapbook palette and if scrapbooks should be saved automatically when changed.</p>
+<h3>Display</h3>
+<p>This panel sets the defaults and options for margin colors, frame display, page background and you have the option to display unprintable areas in the selected margin color. You can also enable page side by side or also known in DTP lingo as &#034;reader spreads&#034;. The Adjust Display Size enables you to adjust the screen sizing in order that 1 inch on the screen actually measures 1 inch. Just take an accurate ruler and place it on the screen and adjust the slider until it matches your ruler</p>
+
+<table width="100%"><tr><td align="center"><img src="images/prefsdisplay.png" alt="Global Color Management Preferences for Scribus" title="Global Color Management Preferences for Scribus" /></td></tr></table>
+
+<h3>External Tools</h3>
+<p>This panel enables you to change the default settings for the location of Ghostscript and your preferred image editing tool. If you have installed Ghostscript on Windows before installing Scribus, it is usually automatically detected.If you receive an error message on Windows indicating EPS files cannot be used. This is where the settings can be changed to allow Scribus to find the correct location of Ghostscript.</p>
+<p><strong>On Linux:</strong></p>
+<table width="100%"><tr><td align="center"><img src="images/gsadv2.png" alt="External Tools Settings" title="External Tools Settings" /></td></tr></table>
+<p> In the example above, a parallel build of Ghostscript 8.53 has been installed in <code>/usr/local/bin/</code> for better results with EPS,PS and PDF importing, as well as speedier print-previews. Linux and Unix users should see the hints in <a href="toolbox7.html" title="Advanced Setup of Ghostscript">Advanced Ghostscript.</a></p>
+<p>You can use any available image editor including cinepaint, krita and even Photoshop with wine. With Crossover, you would use (with quotes) in the dialog something like this :
+
+<pre>"/opt/cxoffice/bin/wine" --workdir "C://Adobe" --check --cx-app "C:////Adobe////Photoshp.exe"</pre>
+ You can copy the exact settings from the desktop shortcut from the menu editor in KDE.</p>
+<p> One other important note, when using the GIMP as your image editor, <strong>you must close GIMP completely before, control will return to Scribus.</strong> The workaround for this is to use <strong>gimp-remote</strong>
+<p><strong>On MacOSX</strong></p>
+<p>Depending on the language settings, the Preferences menu entry appears under Edit->Preferences or under Scribus->Preferences.
+If <strong>both</strong> entries are present, the one under Scribus->Preferences will <strong>not</strong> work. This is a limitation in the Qt3 libraries.
+</p>
+<table width="100%"><tr><td align="center"><img src="images/prefs-mac-1.png" alt="External Tools Settings" title="External Tools Settings" /></td></tr></table>
+<p>Above are the recommended settings, provided you are using GIMP and/or if you have installed the Ghostscript.framework from <a href="http://aqua.scribus.net">http://aqua.scribus.net</a>.</p>
+<p><strong>On Windows:</strong></p>
+
+<p><em>Note the correct .exe name for Ghostscript is gswin32c.exe, <strong>not</strong> gswin32.exe.</em></p>
+<table width="100%"><tr><td align="center"><img src="images/prefs15.png" alt="External Tools Settings" title="External Tools Settings" /></td></tr></table>
+
+<p>To use GIMP as your image editor on Windows , <strong>you must close GIMP completely before control will return to Scribus.</strong> The workaround for this is to use <strong>c:\path to\gimp-remote.exe gimp-2.2.exe</strong> as shown instead.<br /> The default on windows is:<br /> <code>C:/Program Files/GIMP-2.0/bin/gimp-win-remote.exe gimp-2.2.exe</code> This will then either start a new instance of gimp or use the currently running version of gimp. </p>
+
+<p></p>
+
+
+<h3>Miscellaneous</h3>
+<ul>
+ <li><strong>Clip to Page Margins</strong> - This option prevents any object which in not within the page margins from either printing or being exported to PDF. The content of an object within the margins will still print or export. </li>
+ <li><strong>Under Color Removal</strong> - This option changes the way grays are composed when printing. This is most often used with newsprint or other low gamut media. </li>
+ <li><strong>Always ask before replacing fonts</strong> - This option will prompt you to choose replacement fonts when they are missing from your system when a document uses them in a layout.</li>
+ <li><strong>Preview </strong>of current style when editing paragraph styles, is an option to have a preview of your paragraph including the font used, font size and alignment using Lorem Ipsum (dummy) text. </li>
+ <li><strong>Show Startup Dialog</strong> - If you disabled the startup dialog, you can re-enable this here. </li>
+<li><strong>Lorem Ipsum</strong> - Lorem Ipsum is actually Latin text of a famous speech by Cicero, which has been used in page layout for a long time. This allows a designer to make a layout with dummy text which few people can actually read and moreover it uses most of the Roman alphabet. When inserting sample text into a text frame, you can choose the language and number of paragraphs. This option enforces the same settings for all documents.</li>
+ </ul>
+
+<h3>Plugins</h3>
+<p>This panel controls the loading and displays the type of plugins available to Scribus. Normally, you should not need to touch this panel.</p>
+
+<h3>Short Words</h3>
+<p>Short Words is a plug-in to assist adding non breaking spaces to short words like Jr. measurements like km Details on configuration and use are here: <a href="short-words.html">Short Words in Scribus</a>. </p>
+
+<h3>Scripter</h3>
+<p>Scripter Extensions are special scripter module or scripts which are loaded at startup to modify the abilities of the python scripter plug-in within Scribus. Details are here: <a href="scripter-extensions.html">Scripter Extensions Howto</a>. The console tab is for choosing syntax highlighting colors within the scripter console.</p>
+<br />
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/settings1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox11.html
===================================================================
--- Scribus/doc/en/toolbox11.html (nonexistent)
+++ Scribus/doc/en/toolbox11.html (revision 13527)
@@ -0,0 +1,22 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Tracing Tools - Converting Bitmap into Vector</title>
+</head>
+<body>
+<h2>Tracing Tools - Converting Bitmap into Vector</h2>
+
+<p>The programs below are known as tracing tools of various types. I recommend if you are working a lot with scanned images, you might want all of them. They share common features in their ability to open bitmap files and convert them into vector format. This can very desirable if you have artwork, which needs to be replicated or reproduced with high fidelity. The reason I suggest all is they use different algorithms for performing conversions.</p>
+
+<p><strong>Autotrace / FrontLine</strong> - can use Imagemagick to convert to many different formats. Frontline is a GTK gui front end to access the many command line options.</p>
+
+<p><strong>Delineate</strong> - A java based front end to both Autotrace and Potrace. The neat thing is it converts directly into SVG.</p>
+
+<p><strong>Potrace</strong> - works in black and white, but does have a very good tracing routine. Potrace also has a GUI front end written for Qt 3.x</p>
+
+<p><strong>Pstoedit</strong> - is slightly different in that it specializes in the conversion of PostScript in to vector using Ghostscript. It works as a plug-in for GSview. </p>
+
+<p>The thing to keep in mind when using these is there are many options when performing traces and some experimentation is sometimes required, especially more complex artwork. Don't expect perfection. The first time, it took me a bit of experimenting when I converted the Scribus logo from an EPS with a bitmap embedded into pure SVG, which then imported in Scribus.</p>
+
+</body>
+</html>
/Scribus/doc/en/toolbox11.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/intro.html
===================================================================
--- Scribus/doc/en/intro.html (nonexistent)
+++ Scribus/doc/en/intro.html (revision 13527)
@@ -0,0 +1,24 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Preface</title>
+</head>
+<body>
+<h2>Preface</h2>
+
+<p>This document is a semi-ambitious attempt to create something quite different in technical documentation. The aim is to give the reader a new and different way of learning about a software program, but also using the very tools of the program - while it is being developed to create this modest tome. This documentation is ideally in printed form and also in electronic form using the features of the freely available Adobe Acrobat Reader.</p>
+
+<p>That I am writing this at all is a perfect example of chance in life. Maybe, even worthy of a little story. On the suggestion of a friend in IT, I started tinkering with Red Hat Linux in a part time attempt to broaden my world beyond desktop PC's. When one explores a new world, one often looks for things which are common with the old, even if just for comparison. So, once I discovered Gnome and KDE and even learned how to compile programs, I thought this is not so difficult. </p>
+
+<p>A quick hop on Google, yielded a home page with Scribus 0.3.6, a Quark-like DTP program which had just started to be developed. So, download, do the ./configure bit and splat: Scribus won't compile. I fire off a quick e-mail with the gobbly-gook error message I had yet to understand and surprisingly just 20 minutes later a polite reply explaining the error of my ways. Good sign...</p>
+
+<p>A few e-mails later over the course of a few weeks, Scribus had a documenter who had very little understanding of application development, nor how to write even the most basic html. However, I knew and liked desktop publishing and had that sixth sense Scribus was and could be something really special. </p>
+
+<p>In the open source world, there are some great programs which are wholly lacking in any kind of documentation. There are also great programmers who are abysmal at documenting things. (Franz despite having English as a second language is excellent at explaining things.)</p>
+
+<p>Thus, the following, is my modest attempt at adding some help to a great program.</p>
+
+<p>More to come... </p>
+
+</body>
+</html>
/Scribus/doc/en/intro.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-constants.html
===================================================================
--- Scribus/doc/en/scripterapi-constants.html (nonexistent)
+++ Scribus/doc/en/scripterapi-constants.html (revision 13527)
@@ -0,0 +1,203 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Predefined Constants</title>
+</head>
+<body>
+<h2>Predefined Constants</h2>
+
+<p>There are some Constants defined to help using the Commands: </p>
+
+<h4>Scribus Version:</h4>
+ <p>The script interface provides two variables containing the current Scribus version in the <code>scribus</code> module. Scripts can use these variables to check that they're running under the version of Scribus they expect, and to report information about incompatibilities to the user. These two variables, <code>scribus_version</code> and <code>scribus_version_info</code>, were added in 1.2.1 and 1.3.0svn and will not be present in earlier versions. If you need to, you can check for their presence with <code>hasattr(scribus, 'scribus_version')</code>.</p>
+ <p><code>scribus_version</code> contains the current Scribus version as a string. It will usually look like <code>'1.2.1svn'</code> or <code>'1.3.0'</code>, for example, but is not guaranteed to always follow that format. This variable is useful when you need to display the version to the user, for example when reporting an incompatibility. Do not parse or compare this variable, that is what <code>scribus_version_info</code> is for.</p>
+ <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)<code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
+<pre>
+if scribus.scribus_version_info[:3] &lt; (1,2,2):
+ messageBox("Scribus - Python script",
+ "This script requires Scribus 1.2.2 or newer. "+\
+ "You're running %s." % scribus.scribus_version,
+ ICON_CRITICAL)
+ sys.exit()
+</pre>
+
+<h4>Unit Enumeration Constants: </h4>
+<dl>
+ <dt>UNIT_POINTS</dt>
+ <dd>Measurement Unit Point = 0</dd>
+ <dt>UNIT_MILLIMETERS</dt>
+ <dd>Measurement Unit Millimeter = 1</dd>
+ <dt>UNIT_INCHES</dt>
+ <dd>Measurement Unit Inch = 2</dd>
+ <dt>UNIT_PICAS</dt>
+ <dd>Measurement Unit Pica = 3</dd>
+</dl>
+
+<h4>Unit Conversion Constants</h4>
+
+<p>These conversion factors can be used to convert units to and from points.
+Thus, to convert inches to points, you can simply write 'value/inch', to
+convert points to inches you write 'value*inch', and to convert inches to mm
+you write 'value*mm/inch' .</p>
+
+<dl>
+ <dt>pt</dt>
+ <dd>points in 1 pt</dd>
+ <dt>inch</dt>
+ <dd>inches in 1 pt</dt>
+ <dt>p</dt>
+ <dt>pica in 1 pt</dt>
+ <dt>cm<dt>
+ <dt>centimetres in 1 pt</dt>
+ <dt>mm</dt>
+ <dt>millimetres in 1 pt</dt>
+ <dt>...</dt>
+ <dt>Other constants will be provided if the Scribus core knows about them.</dt>
+</dl>
+
+<h4>Page Orientation Definitions: </h4>
+<dl>
+ <dt>PORTRAIT</dt>
+ <dd>Pageformat Portrait = 0</dd>
+ <dt>LANDSCAPE</dt>
+ <dd>Pageformat Landscape = 1</dd>
+</dl>
+
+<h4>Definitions for Page Formats: </h4>
+<dl>
+ <dt>PAPER_A0</dt>
+ <dd>Paperformat A0 = 2380 x 3368 Points</dd>
+ <dt>PAPER_A1</dt>
+ <dd>Paperformat A1 = 1684 x 2380 Points</dd>
+ <dt>PAPER_A2</dt>
+ <dd>Paperformat A2 = 1190 x 1684 Points</dd>
+ <dt>PAPER_A3</dt>
+ <dd>Paperformat A3 = 842 x 1190 Points</dd>
+ <dt>PAPER_A4</dt>
+ <dd>Paperformat A4 = 595 x 842 Points</dd>
+ <dt>PAPER_A5</dt>
+ <dd>Paperformat A5 = 421 x 595 Points</dd>
+ <dt>PAPER_A6</dt>
+ <dd>Paperformat A6 = 297 x 421 Points</dd>
+ <dt>PAPER_A7</dt>
+ <dd>Paperformat A7 = 210 x 297 Points</dd>
+ <dt>PAPER_A8</dt>
+ <dd>Paperformat A8 = 148 x 210 Points</dd>
+ <dt>PAPER_A9</dt>
+ <dd>Paperformat A9 = 105 x 148 Points</dd>
+ <dt>PAPER_B0</dt>
+ <dd>Paperformat B0 = 2836 x 4008 Points</dd>
+ <dt>PAPER_B1</dt>
+ <dd>Paperformat B1 = 2004 x 2836 Points</dd>
+ <dt>PAPER_B2</dt>
+ <dd>Paperformat B2 = 1418 x 2004 Points</dd>
+ <dt>PAPER_B3</dt>
+ <dd>Paperformat B3 = 1002 x 1418 Points</dd>
+ <dt>PAPER_B4</dt>
+ <dd>Paperformat B4 = 709 x 1002 Points</dd>
+ <dt>PAPER_B5</dt>
+ <dd>Paperformat B5 = 501 x 709 Points</dd>
+ <dt>PAPER_B6</dt>
+ <dd>Paperformat B6 = 355 x 501 Points</dd>
+ <dt>PAPER_B7</dt>
+ <dd>Paperformat B7 = 250 x 355 Points</dd>
+ <dt>PAPER_B8</dt>
+ <dd>Paperformat B8 = 178 x 250 Points</dd>
+ <dt>PAPER_B9</dt>
+ <dd>Paperformat B9 = 125 x 178 Points</dd>
+ <dt>PAPER_B10</dt>
+ <dd>Paperformat B10 = 89 x 125 Points</dd>
+ <dt>PAPER_C5E</dt>
+ <dd>Paperformat C5E = 462 x 649 Points</dd>
+ <dt>PAPER_COMM10E</dt>
+ <dd>Paperformat Comm10E = 298 x 683 Points</dd>
+ <dt>PAPER_DLE</dt>
+ <dd>Paperformat DLE = 312 x 624 Points</dd>
+ <dt>PAPER_EXECUTIVE</dt>
+ <dd>Paperformat Executive = 542 x 720 Points</dd>
+ <dt>PAPER_FOLIO</dt>
+ <dd>Paperformat Folio = 595 x 935 Points</dd>
+ <dt>PAPER_LEDGER</dt>
+ <dd>Paperformat Ledger = 1224 x 792 Points</dd>
+ <dt>PAPER_LEGAL</dt>
+ <dd>Paperformat Legal = 612 x 1008 Points</dd>
+ <dt>PAPER_LETTER</dt>
+ <dd>Paperformat Letter = 612 x 792 Points</dd>
+ <dt>PAPER_TABLOID</dt>
+ <dd>Paperformat Tabloid = 792 x 1224 Points</dd>
+</dl>
+
+<h4>Definitions for Document Layout:</h4>
+<dl>
+ <dt>FACINGPAGES</dt>
+ <dd>Layout with facing Pages.</dd>
+ <dt>NOFACINGPAGES</dt>
+ <dd>Normal Layout of the Document.</dd>
+ <dt>FIRSTPAGELEFT</dt>
+ <dd>The first Page of the Document is a left Page.</dd>
+ <dt>FIRSTPAGERIGHT</dt>
+ <dd>The first Page of the Document is a right Page.</dd>
+</dl>
+
+<h4>Alignment Definitions </h4>
+<dl>
+ <dt>ALIGN_LEFTK</dt>
+ <dd>Text is aligned to the Left.</dd>
+ <dt>ALIGN_CENTERED</dt>
+ <dd>The Text is centered in the Textframe.</dd>
+ <dt>ALIGN_RIGHT</dt>
+ <dd>The Text is aligned to the Right Side of the Textframe</dd>
+ <dt>ALIGN_FORCED</dt>
+ <dd>The Text has forced Alignment</dd>
+ <dt>ALIGN_BLOCK</dt>
+ <dd>The Text has block Alignment</dd>
+</dl>
+
+<h4>Line related Definitions: </h4>
+<dl>
+ <dt>LINE_DASH</dt>
+ <dt>LINE_DASHDOT</dt>
+ <dt>LINE_DASHDOTDOT</dt>
+ <dt>LINE_DOT</dt>
+ <dt>LINE_SOLID</dt>
+ <dt>JOIN_BEVEL</dt>
+ <dt>JOIN_MITTER</dt>
+ <dt>JOIN_ROUND</dt>
+ <dt>CAP_FLAT</dt>
+ <dt>CAP_ROUND</dt>
+ <dt>CAP_SQUARE</dt>
+</dl>
+
+<h4>Fill related Definitions: </h4>
+<dl>
+ <dt>FILL_NOG</dt>
+ <dd>No gradient, plain color</dd>
+ <dt>FILL_HORIZONTALG</dt>
+ <dt>FILL_VERTICALG</dt>
+ <dt>FILL_DIAGONALG</dt>
+ <dt>FILL_CROSSDIAGONALG</dt>
+ <dt>FILL_RADIALG</dt>
+</dl>
+
+<h4>Dialog Buttons</h4>
+<dl>
+ <dt>BUTTON_ABORT</dt>
+ <dt>BUTTON_CANCEL</dt>
+ <dt>BUTTON_IGNORE</dt>
+ <dt>BUTTON_NO</dt>
+ <dt>BUTTON_NONE</dt>
+ <dt>BUTTON_OK</dt>
+ <dt>BUTTON_RETRY</dt>
+ <dt>BUTTON_YES</dt>
+</dl>
+
+<h4>Dialog Icons</h4>
+<dl>
+ <dt>ICON_CRITICAL</dt>
+ <dt>ICON_INFORMATION</dt>
+ <dt>ICON_NONE</dt>
+ <dt>ICON_WARNING</dt>
+</dl>
+
+</body>
+</html>
/Scribus/doc/en/scripterapi-constants.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/pdfexport4.html
===================================================================
--- Scribus/doc/en/pdfexport4.html (nonexistent)
+++ Scribus/doc/en/pdfexport4.html (revision 13527)
@@ -0,0 +1,35 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Creating PDF Presentations</title>
+</head>
+<body>
+<h2>Creating PDF Presentations</h2>
+<h3>Presentation PDFs</h3>
+<p>Creating Presentation PDFs in Scribus, is not only easy, they work great. Using PDF in place of traditional "presentation" applications does have some advantages:</p>
+
+<ol>
+ <li>They are portable. You can create a presentation PDF with Scribus and display it on almost any computer with Acrobat Reader. Other types, usually require the application to be installed, and few are cross-platform.</li>
+ <li>You can use all the drawing, text manipulation and image handling tools in Scribus, which are in many cases superior to those in other presentation applications. Few can import SVG or EPS files really well.</li>
+ <li>You will have more precise typographic control of text.</li>
+ <li>Because they are created in Scribus, you can export them with a higher resolution and they will print beautifully.</li>
+<li>Unlike other presentation tools, with use of the powerful form and javascript capabilties in Scribus you can make truly interactive PDFs which can take counts, ask questions with dialogs and more. You are only limited by your imagination and scripting skills. </li>
+</ol>
+
+<h4>Hints:</h4>
+<ul>
+ <li>Down-sample all images to 72-96dpi. Depending on the resolution of the displaying device, you might go as high as 120dpi, but higher will not gain you sharpness. But do this in an image editing program like the GIMP. Then import them into Scribus.</li>
+ <li>Embed all fonts. This ensures the spacing and layout will remain the same no matter which platform you are using.</li>
+ <li>You can use US Letter or A4 in landscape mode for your layout. This will most closely match the screen output of Acrobat Reader in Full Screen mode.</li>
+ <li>When displaying images like photos or screen shots, use a black or dark background on your page. They will make the colors more vibrant and give your viewers more contrast to see all the details in your slides.</li>
+ <li>Use RGB colors for your images and always use Screen/Web for Export.</li>
+ <li>One trick I have learned from using PDF for presentation. Load the PDF and run through each page once before giving the presentation, so the file is loaded in memory. This will make for smoother transitions on the screen.</li>
+</ul>
+<h4>Settings and Options</h4>
+<p>Presentation effects and settings fall into two categories. The first is controlling the transition between pages when running a presentation PDF for example like you would when on stage. There are a variery of effects which are in the drop down boxes and they are often not only supported in Adobe Reader, but in other PDF viewers like KPDF or Xpdf for example. Moreover, each page can its own transition, different from the others. </p>
+<table width="100%"><tr><td align="center"><img src="images/pdfeffect1.png" title="PDF Effects" alt="PDf Effects"/></td></tr></table>
+<p>Viewer Options are the second and gives you control over how the viewing application is opened. These mostly will only work in Adobe Reader alone as they are based on javascript commands in the PDF. <strong>Special Actions</strong> are more advanced ways of controlling the viewer on opening, but requires custom javascript to work.</p>
+<table width="100%"><tr><td align="center"><img src="images/pdfeffect2.png" title="PDF Effects" alt="PDf Effects"/></td></tr></table>
+
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/pdfexport4.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/importhints1.html
===================================================================
--- Scribus/doc/en/importhints1.html (nonexistent)
+++ Scribus/doc/en/importhints1.html (revision 13527)
@@ -0,0 +1,58 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Notes on Importing EPS/PS into Scribus</title>
+</head>
+<body>
+<h2>Notes on Importing EPS/PS into Scribus</h2>
+
+<p>To better your chances of successfully importing EPS/PS files it helps to have three ingredients:</p>
+ <ul>
+<li>An EPS/PS file which is conformant to the published specs. Not all applications export EPS files with the same level of fidelity, nor do all embed fonts properly.</li>
+<li>The latest Ghostscript available for your platform.</li>
+<li>Where an EPS file has fonts embedded, ensuring Ghostscript's font paths are setup correctly. See: <a href="gsfont.html">Ghostscript Fonts</a> for hints. This is mostly for folks using Linux or Unix with X-Windows. Windows and MacOSX users will not need to worry so much about font configuration with Ghostscript.</li></ul>
+<p>There are two basic methods of importing EPS files and both have pluses and minuses. The first and most often preferred method is to import the EPS into Scribus as native objects. Both have trade-offs, partly because of the inherent nature of EPS files. Like PDF, most, if not all EPS are not meant to be edited, but EPS is more of an an exchange format. However, importing them as native Scribus objects can allow some editing of some of the content, as well as re-scaling them without loss of resolution. </p>
+
+<p>The second is simply importing the EPS file into an image frame, much like the methods used by the GIMP or Photoshop. That is <em>rasterize</em>, or turn the EPS/PS file into a bitmap like a tiff or JPEG. This method may be the only possibility if the EPS file has embedded images. </p>
+<h4>Importing Hints:</h4>
+<p>One of my preferred ways to import EPS/PS files in to Scribus is to simply create a new document via File > Open > Select EPS/PS from the drop down in the file dialog. Then directly import the EPS/PS file. This creates a new document in which the page size is automatically calculated from the EPS bounding box. Save this temporarily under a file name.</p><p> Then, re-open the target document for import. Create a new layer and then use the page import function to import your newly created document into the new layer in your existing document. This prevents any of the imported elements from disturbing existing objects and allows you to place with precision where you want the file.</p>
+<h4>Other EPS/PS Hints:</h4>
+<ul>
+ <li>Users saving from Adobe Illustrator 9.0+ are urged to "backsave" to Illustrator version 7 or less. Why ? Illustrator 9.0+ actually uses PDF as a native format and embeds quite a bit of Adobe specific info in the EPS which can cause issues when importing. (Scribus is not alone with this issue.) </li>
+ <li>Photoshop can export EPS natively, but these are mostly raster objects within the EPS, with some Photoshop specific features with layers and blend modes. Photoshop also can export a special type of EPS called DCS (Desktop Color Separations). These type of EPS files are best imported into an image frame, where Scribus will detect and enable extended image editing/displaying capabilities. <a href="psd.html">More hints for Photoshop files.</a></li>
+<li>You are well advised if possible to separate images from vector and import only the vector artwork as EPS. See below.</li>
+ <li>Scribus can import multipage PS files via File > Open. Scribus will create as many pages as the PostScript file contains, but for Postscript files which are purely text this is not recommended. Currently, text is converted to outlines on import. If you need the text contained within the Postscript file you can use GSview to extract the text or the command line tool ps2ascii which comes with Ghostscript. This tool works on Windows and OSX as well. </li>
+<li>If your platform supports it, GSview is recommend above all other PostScript viewers for diagnosing and previewing Postscript. While the display is not color managed, it will generally help to diagnose issues with importing in Scribus. Simply typing <strong>M</strong> will give you a window with sometimes helpful diagnostic info.</li>
+<li>When exporting EPS or PostScript files, if possible fully embed the fonts if the option is given.</li>
+ </ul>
+<h4>Importing EPS files with Embedded Raster Graphics</h4>
+<p>Scribus can import EPS files which contain embedded raster graphics (bitmaps). However, this works far better with Ghostscript 8.50+ and there are some limitations:</p>
+<ul>
+<li>Imagemask doesn't work correctly</li>
+<li>Clipping paths are ignored</li>
+<li>Importing will create one file (A Tiff) for each bitmap and there can be many within an EPS.</li>
+</ul>
+<h3>Importing EPS as an Image</h3>
+<p>When you wish to import an EPS into Scribus and it has a mix of text, images and vector, this is the only real option. Importing in this manner, provided the fonts are correctly embedded, usually works very reliably and will maintain fidelity to the CMYK colors defined in the EPS. On initial import Scribus will ignore any embedded preview tiff or pict and will generate its own low resolution preview of the EPS. If nothing displays this is a hint something is not working correctly in the import and needs closer inspection. When exporting to PDF, the EPS is rerun through Ghostscript as it is embedded into the PDF, so do not be surprised about long PDF export times or high memory usage.
+</p>
+<p>To import EPS as an image:</p>
+<ul>
+ <li>Select the Insert Picture Tool </li>
+ <li>Left Click Drag the frame to your chosen size.</li>
+ <li>Right click the new Image Frame and select <strong>Get Picture..</strong> </li>
+ </ul>
+<h3>Importing EPS as Native Scribus Objects.</h3>
+<p>Importing EPS as Scribus native objects, when possible, does have some advantages. First, they are all vector, so file size and exported PDF size are relatively small. It makes them resolution independent, so they can be re-scaled without losing crispness in printing. The bonus is you can edit the graphical elements like lines, polygons and curves natively.</p>
+<p>To import an EPS as a native Scribus Object:</p>
+<ul>
+ <li><strong>File > Import > Import EPS/PS</strong> </li>
+ <li>Select the EPS. if you have previews enabled in the file chooser, large complex EPS file may take some time to render. </li>
+ <li>Left Click to Drop the Cursor where you want to place the file. Once dropped on the canvas, the EPS file objects are grouped. You will need to ungroup them to edit individual objects. To scale an imported EPS, select the lower right corner and Ctrl + Left Click Drag up or down as needed. This will scale your EPS proportionately.</li>
+ </ul>
+
+
+<h4>Troubleshooting EPS Import </h4>
+<p>As mentioned above, EPS export quality from other applications can vary widely. Some applications like to add their own ingredients to the sauce - unfortunately. The first step for testing a failed import is open the file in <a href="toolbox6.html">GSview</a>, then press <strong>M</strong> to watch the messages from Ghostscript as it attempts to open the file. When you have a failure in GSview, the messages can be sometime cryptic, but they are a helpful pointer to see what is the problem.</p>
+<p></p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/importhints1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/gsview.html
===================================================================
--- Scribus/doc/en/gsview.html (nonexistent)
+++ Scribus/doc/en/gsview.html (revision 13527)
@@ -0,0 +1,34 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>GSview and Scribus</title>
+</head>
+<body>
+<h2>GSview and Scribus</h2>
+<p><strong>Parts of this section are thanks to Russell Lang, author and maintainer of GSview, epstool and Ghostscript for his hints and patiently answering my questions about GSview and Ghostscript. It has allowed the Scribus Team to use some of the more advanced features of Ghostscript in Scribus. </strong></p>
+<p>First off, It is in my very strong opinion, <strong>a superior replacement for ghostview, gv and derivatives.</strong> Although Acrobat Reader&#174; is in my experience sometimes a better pure viewer for PDF, I also consider GSview one of the most essential tools to have when using Scribus. GSview has a handful of extremely useful functions. For those unfamiliar, it provides an easy to use &quot;front end&quot; to
+Ghostscript, as well as <code>pstoedit</code> for converting bitmaps into vector files. For those coming from the Windows/Mac world, it also has the functionality of Distiller with a graphical front end for those applications which do not export PDF natively.</p>
+<p>Second ensure you have the latest version 4.7+. (GSview migrated from the Windows world, where it has been excellent since the 4.x versions.)</p>
+<p>For use with Scribus, GSview has the following features:</p>
+<ul>
+ <li>With the help of <a href="http://pstoedit.net">pstoedit</a>, you can convert bitmap images or PDF content back into SVG and other scalable vector file formats.</li>
+ <li>The ability to preview, convert and add previews (Tiff recommended) for raw EPS (Encapsulated PostScript Files).</li>
+ <li>The ability to extract text from a PDF.</li>
+ <li>The ability to preview, convert and add previews for raw PostScript files. An easy to use interface for creating PDF's in applications without the high level of export capabilities of Scribus. (You are still recommended to use the Export to PDF Scribus, as it is optimized for Scribus files.)</li>
+ <li>As an easy to use front end to Ghostscript's less well known features such as image conversion and re-sampling. The example below uses the <strong>epswrite</strong> &quot;device&quot;. There are others in Ghostscript including: converting between TIFF formats, changing the color depth of at TIFF, JPEG or the color space of an image.</li>
+</ul>
+<p>One example where I use GSview with Scribus is for troubleshooting/fixing EPS files which do not display correctly within Scribus. Although many applications can generate EPS files, some add their own quirks into the EPS, which can cause problems when used in other applications (like Scribus).</p>
+<p>So, if you find difficulty with an EPS or PDF you wish to use in Scribus, open the EPS in GSview. Then, use the key command <strong>M</strong> to display messages from Ghostscript. The messages can indicate problems which cause display or printing errors. You can also use the <strong>epswrite</strong> &quot;device&quot; to re-save the EPS, which can help to strip out or fix issues with an EPS.</p>
+<p>You can also <em>rasterize</em> an EPS image like this, by converting to PNG or TIFF and then resize, adjust colors etc with an image program like GIMP or Corel Photoshop. I did this with a troublesome EPS and converted it to a 600DPI PNG, which would then display and print perfectly from Scribus. Sometimes when working with images and DTP there are several different ways to accomplish the same task - in my example, it was getting a complex EPS file from Illustrator to display and print properly from Scribus. The fact that there problem displaying the EPS, was not a bug in Scribus, but some non-standard PostScript info in the file, which by using Ghostscript as a back end to GSview I could strip out and then display properly in Scribus.</p>
+<p> Note: GSview uses the <code>libgs.so</code> shared library to access Ghostscript. Not all Linux distributions ship this, so the hints for compiling Ghostscript with a paralell install really apply here. </p>
+<h4>Getting Gsview:</h4>
+<p>Not all Linux distributions offer GSview. However, for those with rpm based systems, a simple rpm command will have you with an easy to install rpm. The GSview tarball already has a built-in spec file. A simple: </p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+rpmbuild -tb ./gsview-4.7.tar.gz
+</pre></td></tr></table></blockquote>
+<p>Will get you started. Windows has a convetional setup.exe installer. Unfortunately, it is not yet available for MacOSX. </p>
+<p>GSview since about 4.3, has been, in my experience, the most reliable and versatile PDF viewer along with Acrobat Reader on Linux. For DTP with Scribus, I consider it essential.</p>
+<p>Now, for advanced hints with GSview and Ghostscript, see: <a href="toolbox7.html">Advanced Ghostscript and GSview Hints</a></p>
+</body>
+</html>
/Scribus/doc/en/gsview.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/fonts2.html
===================================================================
--- Scribus/doc/en/fonts2.html (nonexistent)
+++ Scribus/doc/en/fonts2.html (revision 13527)
@@ -0,0 +1,48 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Fonts in Depth</title>
+</head>
+<body>
+<h2>Fonts in Depth</h2>
+
+<p>Fonts are often where the trouble starts and often ends in page layout. They are in my experience one of the leading troubles in pre-press in general and one of the sources of constant questions on the mailing list and IRC. A rough guess is 50% of the bug reports which are font related are problems with the fonts themselves. A typical question or complaint on IRC is: "Scribus won't use font X, but application blah and blahblah use it just fine. Why is this?"</p>
+
+<p>Fundamentally, Scribus is <strong>really really</strong> fussy about fonts. This is a feature and not a bug. Certainly, on Linux no other application is less tolerant of fonts with defects than Scribus. This is a Good Thing &#8482;! Preventing the use of possibly defective fonts is without question essential for reliable output. This has caused some minor annoyance or confusion for end users. Rest assured, this avoids many potential problems down the road. Like a PDF which crashes when you are printing 200,000 magazine covers because the imagesetting machine crashes or refuses to output a file. That, in the real world can cost thousands or millions in your local currency.</p>
+
+<p>Scribus uses the freetype2 libraries for accessing font internals. Scribus also does some error checking upon loading to verify the quality of the fonts. Not all fonts are up to the task for use in DTP. Why ?</p>
+<p>High quality fonts are essential for reliable output, no matter which platform. Call me a font snob, but I <b>never ever</b> use freely downloaded shareware fonts. Experience has shown us some freeware fonts do not follow normal font specifications for things like having a proper encoding, a missing or incorrectly formatted PostScript name, broken curves in individual glyphs and other defects. </p>
+
+<p>
+Scribus does an initial "self-defense" test when starting to see if the available fonts have usable encodings, is scalable and has a correctly embedded PostScript name. Then, loading a document, Scribus uses freetype2 to do a more extensive check of the requested fonts to ensure freetype2 can access all the glyphs within the font. If freetype2 cannot read the glyphs correctly, then usage of that particular font is disabled by Scribus.</p>
+
+
+
+<h3>Trustworthy Fonts</h3>
+
+<p>The the fonts I use and trust below: (in no particular order) :</p>
+<ul>
+ <li>The latest Ghostscript fonts. Preferably, if you have no need for non-Latin, You can get an alternative set of these in TrueType form, from the Artifex site. These alternatives also come with some extra font families and are good usable fonts. </li>
+ <li>Any of the Adobe or Bitstream fonts from Xfree86 or X.org: Charter, Luxi and Utopia are excellent fonts from this package. The PDF version of this doc is set using Utopia for the main body text.</li>
+ <li>Any of the Lucida fonts from the Sun Java Packages.</li>
+ <li>MS Web fonts - the exception: Wingdings can cause problems in DTP, not just for Scribus (fixed in 1.2.2). This particular font has a unusual encoding scheme unlike most other fonts.</li>
+ <li>Lido CE family is an alternative to Times Roman and is a very well made font, by a highly regarded foundry.</li>
+ <li>Gentium - an ambitious effort to create a freely available Unicode font which works well with most Latin scripts.</li>
+ <li>Bitstream Vera Family - These were donated to the Gnome foundation and are packaged by most distributions. The Vera Serif is in particular a rarity, a really easy to read on screen serifed font. </li>
+ <li>Any of the Bitstream Fonts from Corel Draw. I have clients who have used these for years in professional pre-press without a single problem.</li>
+ <li>Any Adobe font. Adobe fonts are some of the best and if you have them, the new OpenType fonts are terrific. Scribus is one of the rare applications to support them well, including making them work well with PDF so they print properly from PDF.</li>
+ <li>Any of the fonts packaged with StarOffice 6.0+. These are replacements for the default Windows fonts in some cases and include other font faces. These are all high quality fonts licensed from Agfa Monotype and should work fine in Scribus.</li>
+</ul>
+<p>You can find links for all the downloadable fonts noted above on the Scribus web site under Web Links > Fonts. </p>
+
+<p>Some Linux distributions package some free fonts and shareware fonts under various package names. I avoid them and have removed them from some installs without missing them. Windows users should be equally suspect downloading any site which has "free" and "font" in the domain name. </p>
+
+<p>Do not be surprised when shareware or clone TrueType fonts downloaded from the Internet disappoint when printed. Sometimes shareware TrueType fonts do not follow proper the proper encoding specs, so they are unreliable in a PostScript environment. Making good reliable fonts in the PostScript sense is not easy and requires extensive QA testing. An example: Verdana from the MS web font collection took almost a year to create.</p>
+
+<p>Also, do not be put off by the lack of a great screen preview with the URW fonts - they are excellent printer fonts. Font faces like Palladio and Utopia for example, are not really attractive on screen, but they are excellent fonts for easy to read printed documents. There is a reason service bureaus and printers spend literally thousands of dollars for high quality font libraries. </p>
+
+<p>On Linux, installation, if you use <code>$home/.fonts</code> directory for adding fonts, Scribus should find them just fine. For those leery of messing around with the command line tools for font installation, KDE 3.2+ includes an improved version of Keith Drummond's kfontinstaller program. The one in KDE 3.3+ works superbly and you can even preview fonts within Konqueror. In my opinion, it is one of the most user friendly font installers I have seen on any platform. It also automatically will create Ghostscript Fontmap files for use with GSview and Ghostscript. Highly recommended. </p>
+
+<p>Scribus also makes it easy to add additional font paths. Simply, close all documents, then select Settings > Fonts > Additional Paths. Select the new path and click OK. If fonts, still do not show up, you may need to add these to either your <code>$home/.fonts.conf</code> file or other method depending on your distribution. If some still fail to show up, it is possibly Scribus's font checking mechanism has disabled them. You can make some basic checks by following the hints in: <a href="fonts4.html">Basic Font Tests</a> </p>
+</body>
+</html>
/Scribus/doc/en/fonts2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/cross-platform.html
===================================================================
--- Scribus/doc/en/cross-platform.html (nonexistent)
+++ Scribus/doc/en/cross-platform.html (revision 13527)
@@ -0,0 +1,14 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Cross Platform Hints and Issues</title>
+</head>
+<body>
+<h2>Cross Platform Hints and Issues</h2>
+<p>One thing that exposure has taught me is DTP is one of those areas where cross-platform issues come into play more than most types of applications. PDF does help, but sooner or later, something will pop-up. </p>
+<p>Have a look through the <a href="http://www.scribus.net/modules.php?op=modload&name=Web_Links&file=index">Web Links</a> for cross-platform tools and downloads.</p>
+<p><a href="machints1.html">Mac OSX/Fink Hints</a></p>
+<h2>Scribus on Windows</h2>
+<p>For those interested in running Scribus on Windows 2000 or Window XP, there is a native version: <a href="http://windows.scribus.net">http://windows.scribus.net</a>.</p>
+</body>
+</html>
/Scribus/doc/en/cross-platform.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/plugin_howto.html
===================================================================
--- Scribus/doc/en/plugin_howto.html (nonexistent)
+++ Scribus/doc/en/plugin_howto.html (revision 13527)
@@ -0,0 +1,322 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>How to write a Scribus Plugin</title>
+</head>
+<body>
+<h2>How to write a Scribus Plugin</h2>
+
+<h3>Preface</h3>
+
+<p>This article shows you how to write plugins for Scribus. Plugins are
+libraries that are loaded into the main application at run-time. Plugins can
+extend and to an extent modify the behavior of the application without having
+to edit and recompile the core application. They are useful for adding extra tools,
+extra import and export functions, and for various more advanced uses.</p>
+
+<p>This document assumes some basic knowledge of C++. You're assumed to know
+what a header file is, how include files work, know about classes an
+inheritance, and have some general familiarity with the language. Some
+familiarity with Qt - mainly QString and QObject - will also help. Issues like
+virtual and pure virtual functions, "extern C" declarations, the details of
+memory management, etc are glossed over and avoided in this document. You don't
+have to know about them, but it'll help you follow what's going on better if
+you do.</p>
+
+<p>We're not going to try to explain the details of how the Scribus plugin
+system works here. This is just about how to write a plugin. The documentation
+in the <code>scplugin.h</code> and <code>pluginmanager.h</code> help explain
+how the system works.</p>
+
+<p>For any reasonable plugin idea, you will receive encouragement and assistance from the Scribus Team.
+As rule, we do not do a lot of planning or development discussion by e-mail, but by <a href="irc.html">IRC</a>. Probably 99% of
+the planning and project discussions take place there. You will find #scribus usually lively during parts of each day. The team is mostly resident in Europe, so Central European Time evenings is when it is busiest. </p>
+
+<h3>Where do I find Scribus Plugins?</h3>
+
+<p>Scribus ships with a number of standard plug-ins. These will be installed
+along with the Scribus program and its other files. On UNIX, plug-ins will be
+installed in the same prefix as the main app. In Mac OS X they're included in
+the .app bundle. If you want to know what these plug-ins do, the easiest way to
+find out is to to fire up Scribus and go into <code>Edit-&gt;Preferences</code>
+and click on the "plugins" icon. From there you will see a list of what
+plug-ins are installed, what type of plug-in they are, and where the files
+are.</p>
+
+<p>In addition to the plug-ins shipped as standard with Scribus, it is possible
+to build and install plug-ins you obtain from elsewhere, or to write and add
+your own.</p>
+
+<h3>Before you start coding</h3>
+
+<p>Let's suppose you've got a great idea to improve Scribus and you cannot wait
+to start writing some excellent C++ code. <b>Hold on for just a few minutes</b>
+and read this section; you might save yourself some time and trouble.</p>
+
+ <h4>Important</h4>
+
+ <p>Maybe you are at the edge of "reinventing the wheel" - that is, writing
+ something you don't have to because someone else has already done it. You
+ should probably join the mailing-list and post about your idea, or join the
+ <code>#scribus</code> channel on <code>irc.freenode.net</code>. Your topic will
+ be discussed and you will probably get some help and ideas from the developers
+ and from other users. As Scribus is freely licensed, you're welcome to work
+ on your own, but at least an introductory chat on IRC, or a mail to the
+ mailing list may save hours of work and head banging. We want to make
+ writing plug-ins as painless as possible for those who're interested.
+
+ <h4>Compatability</h4>
+
+ <p>Scribus does not have a fixed C++ API for plugins to use. Releases are not
+ binary compatible, and unstable versions frequently break source compatibility.
+ Source compatibility is not currently guaranteed even across stable releases
+ if changes are required to fix a problem. We hope to improve this so we can
+ provide a stable C++ API for external code in the future. For now, if possible
+ you should try to bundle the core of your plugin's functionality into a
+ separate module that knows as little about the innards of Scribus as
+ possible.</p>
+
+ <p>This document covers implementing a plugin for Scribus 1.3.x. It is
+ dramatically different to what was required for the 1.2.x series. Future
+ changes should be smaller.</p>
+
+
+<h3>Quick Start</h3>
+
+<p>It's not too hard to jump in and start writing a plugin. The documentation
+below describes the implementation of a plugin in some detail, with references
+to places where you can find out more if you need it. A "plugin template" is
+provided for your use, so if you like you can get started by making a copy of
+that and getting hacking. Some basic instructions are included in the file, and
+if you get confused you can refer back to this document.</p>
+
+<p>We'll build the plugin as a part of Scribus. That's the easiest way to get
+started, though you'll probably want to start distributing it separately later
+on (see later). To start work on an Action plugin:</p>
+
+<p>We use <a href="http://cmake.org">CMake</a>, as support for autotools has been
+deprecated and moving forward it will be the only one used in 1.3.5+</p>
+
+<ul>
+ <li>Copy <code>scribus/plugins/myplugin</code>
+ to <code>scribus/plugins/pluginname</code>
+ (where "pluginname" is what you want to call your plugin).
+ pluginname must be a valid C identifier - I suggest
+ sticking to nothing but lower case characters.</li>
+
+ <li>Edit <code>scribus/plugins/CmakeLists.txt</code> and add
+ "pluginname" to it by adding the subdirectory to the others. This tells Scribus's build
+ system to compile your plugin.</li>
+
+ <li>rename all the files in <code>scribus/plugins/pluginname/</code>
+ from <code>myplugin</code> to <code>pluginname</code>, eg
+ <code>myplugin.h</code> to <code>pluginname.h</code>.
+ </li>
+
+ <li>rename <code>myplugin</code> wherever it appears in the files to
+ <code>pluginname</code>, e.g. <code>myplugin_getPluginAPIVersion()</code>
+ to <code>pluginname_getPluginAPIVersion()</code>. Do the same for
+ <code>MyPlugin</code> and <code>MYPLUGIN</code>. On UNIX, you can use this
+ command:<br/>
+ <code>sed -i -e "s/myplugin/pluginname/g" -e "s/MyPlugin/PluginName/g" -e "s/MYPLUGIN/PLUGINNAME/g" myplugin*</code><br/>
+ (all on one line, run from <code>scribus/plugins/pluginname/</code>).
+ </li>
+</ul>
+
+<p>You're now ready to start work on your plug-in. First, you need to fill
+out some information about your plug-in in <code>pluginname.cpp</code>:</p>
+
+<ul>
+ <li>In <code>PluginName::languageChange()</code>:
+ <ul>
+ <li>Change <code>m_actionInfo.text</code> to the text of the menu item
+ you want to trigger your plugin.</li>
+ <li>Change <code>m_actionInfo.menu</code> to the name of the menu you
+ want the menu item to go in. See <b><i>FIXME where????
+ FIXME</i></b> for a list of menu names.</li>
+ <li>If you want your plugin to have a keyboard shortcut, uncomment
+ <code>m_actionInfo.keySequence</code> and set it to your preferred
+ shortcut. The example there should show you how that works.</li>
+ </ul>
+ </li>
+
+ <li>Change the name in <code>PluginName::fullTrName()</code>
+ to the name of your plugin as you want it to appear in the Help-&gt;About Plugins dialog
+ box and in the Plugin Manager pane in the preferences.</li>
+
+ <li>If you want your plugin to have information such as author info and a
+ description when the user looks at it in Help-&gt;About Plugins, fill out
+ as much as you want of the about info by assigning members of
+ <code>about</code>. You can see what information can be provided by looking
+ at the definition of <code>AboutData</code> in
+ <code>scplugin.h</code>.</li>
+</ul>
+
+<p>You've finished setting up the plugin, and can now start programming. Your
+code should go in <code>pluginnameimpl.cpp</code> and
+<code>pluginnameimpl.h</code>. The existing code should display a message
+dialog box.</p>
+
+<p>To compile the plugin, you can simply re-run <code>cmake with your usual options. </code>,
+and <code>make</code> in the top-level Scribus directory. You may need to remove CmakeCache.txt,
+but this is becoming a rarer necessity in newer versions of CMake.
+When the compile completes, run <code>make install</code> and fire up Scribus.
+Your plugin should now appear in the plugin manager (in the preferences), and
+should have a menu item. If you press the menu item, a dialog box should appear.</p>
+
+<h3>Building plugins outside the Scribus tree</h3>
+
+<h4>Quick and dirty using QMake</h4>
+
+ <p><strong>Warning</strong></p>
+
+ <li>Beware - a qmake project easy to use but isn't necessarily the most standard
+ way to distribute software on the Linux platform. Scribus runs natively on Linux/Unix, MacOSX, OS/2 and
+ Windows. This process is an example
+ only for development. When you create your bug-free functional package then
+ make time to prepare a full featured distributon as described in the next section.</li>
+
+ <li>Let's compile it, but it isn't so easy as typing in <code>gcc
+ myplugin.cpp</code> ;). One easy way to build it - Qt qmake (because some
+ people really really hate autoconf and automake in their complexity. We've been know to
+call it worse things more than once. ). Note: you
+ will need to create an empty <code>config.h</code> file before running these
+ steps</li>
+ <li>On Linux or OSX systems where Qt3 and Qt4 are installed parallel, you may need to
+provide the full path: e.g. <code>/usr/lib/Qt4/qmake</code></li>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+$qmake -project
+</pre>
+</td></tr></table></blockquote>
+
+<p>Now the project file is created and we'll make just a few changes into it.</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+######################################################################
+# Automatically generated by qmake (1.06c) Sun Dec 14 13:32:11 2003
+######################################################################
+
+#change TEMPLATE = app. We aren't working on application just plugin
+TEMPLATE = lib
+INCLUDEPATH += .
+#As working with Scribus, we need Scribus includes too.
+INCLUDEPATH += /home/subzero/devel/Scribus/include/Scribus/
+#And Scribus have to use freetype2.
+#So we should link it too. Use paths returned from
+##freetype-config --cflags and --libs
+INCLUDEPATH += /usr/include/freetype2
+LIBS += -lfreetype -lz
+
+# Input
+#create empty config.h file
+HEADERS += myplugin.h config.h
+SOURCES += myplugin.cpp
+</pre>
+</td></tr></table></blockquote>
+
+ <p>After these changes you're ready to compile</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+$qmake
+$make
+</pre>
+</td></tr></table></blockquote>
+
+ <p>Running Qmake creates the Makefile and by running make you compile your
+ plugin.</p>
+
+ <p>Then just copy *so* files into Scribus plugin directory and run Scribus.
+ You'll see "Do Nothing Plugin" in the Extras menu.</p>
+
+ <p>It is clear that you have to use some other way to distribute your
+ source code to others - some use autogenerated qmake pro files, other use
+ the autoconf/automake combination.</p>
+
+ <h4>Distribute it! (a.k.a. Compile it! 2nd edition)</h4>
+
+ <p>Qmake is user frendly and useful for rapid development, but traditionally there has been
+ one standard way to compile/distribute software for Linux, *BSD etc. - autoconf
+ and automake. Lets call these two programs by the automagic acronym in the
+ following text.</p>
+
+ <p>To use automagic successfully you'll need chalk drawn to the north
+ oriented pentagram on the floor (Carrefour, 2&#8364;), red-black daemonic
+ dress (Hugo Boss, 2000&#8364;) and a sacrificed penguin on the home altar
+ (one hour of fear in your local zoo). Err, only joking.. dont harm any
+ nice little penguins, you wont need to. We strongly prefer the simpler and
+easier to use CMake build system.</p>
+
+ <p>Download the <code>donothingplugin-1.0.tar.gz</code> example from
+ http://docs.scribus.net, unpack it and browse it.</p>
+
+
+<h3>Learning More</h3>
+
+<p>To go on from here, you should probably read <code>scplugin.h</code> and ensure
+you understand that. There is an explanation of the way the plugin system works
+in more detail <a href="WHERE">here</a>. Above all else, though, you'll learn how
+to get things done by reading the other plugins and the core Scribus code.</p>
+
+ <h4>Storing your plugin's preferences:</h4>
+
+ <p>Scribus provides a preferences api for plugin writers to store data between
+ Scribus launches. There are two types of storage formats available: key-value
+ pairs and tables.</p>
+
+ <p>First you will need to get the <code>PrefsContext</code> object for your
+ plugin. Then you can query <code>PrefsContext</code> to get the value for a
+ specific key or you can ask for a <code>PrefsTable</code> by it's name. Here is
+ a short example using key-value pairs.</p>
+
+<pre>
+#include &lt;prefsfile.h&gt;
+#include &lt;prefscontext.h&gt;
+
+extern PrefsFile* prefsFile;
+
+PrefsContext *myPluginPrefs = prefsFile-&gt;getPluginContext("MyPlugin");
+
+// default value -1 will be used if "i" doesn't already exist
+int i = myPluginPrefs-&gt;getInt("i");
+
+// default value "dog" will be used if "s" doesn't already exist
+QString s = myPluginPrefs-&gt;get("s", "dog");
+
+myPluginPrefs-&gt;set("i", 221);
+myPluginPrefs-&gt;set("s", "cat");
+</pre>
+
+ <h4>Scribus Object Model</h4>
+
+ <p>Scribus's source code is lightly documented. There is a significant
+ effort to correct this, but given the size of the codebase it's taking
+ quite some time. Please do try to follow what's going on based on the
+ header files and the code. If you're unable to sort it out, feel free to
+ drop in on IRC or ask on the mailing list, and someone may well be able to
+ help you. Try to be patient - we're not always on IRC or available, and it
+ can take time to answer a message if everybody's busy.</p>
+
+ <p>If you feel like improving the documentation or fixing the doxygen api
+ docs generation, the praise will be endless.</p>
+
+ <p>One important thing to understand is that the core Scribus application
+ can be accessed via the static global pointer <code>ScApp</code>, declared
+ in <code>scribus.h</code>. Confusingly, this is a QMainWindow subclass.
+ You can also get to the QApplication subclass used as <code>ScQApp</code>
+ from <code>scribusapp.h</code>.</p>
+
+ <p>Some major subsystems are singleton classes that are accessible via
+ ClassName::instance() . Examples include <code>PluginManager</code>,
+ <code>ScPaths</code>, and growing numbers of others. The advantage
+ of this is that you can interact with these classes without having to
+ delve into the guts of ScApp.</p>
+
+<h3>Plugin related links</h3>
+<a href="http://doc.trolltech.com/">Qt documentation from Trolltech</a><br />
+<a href="http://doc.trolltech.com/3.3/qmake-manual.html">QMake documentation from Trolltech</a><br />
+<!--<a href="http://www.murrayc.com/learning/linux/automake/automake.shtml">Automake/autoconf example</a>--><br />
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/plugin_howto.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/print3.html
===================================================================
--- Scribus/doc/en/print3.html (nonexistent)
+++ Scribus/doc/en/print3.html (revision 13527)
@@ -0,0 +1,33 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Prepping files for Commercial Printing</title>
+</head>
+<body>
+<h2>Prepping files for Commercial Printing</h2>
+<p>If you have never dealt with printers, nothing will assure a worry free experience for printing files commercially better than talking to your printer well in advance. Preventing mis-understandings and making them well aware in advance of your goals will more than likely prevent 90% of the mistakes. If you do not get satisfactory answers shop around. The printing business is competitive. The best offer both technical savvy and good service. </p>
+
+
+<h3>Ask questions:</h3>
+
+<h4>If they accept PDF, which level ?</h4>
+
+<p> PDF 1.3 (Acrobat 4), PDF 1.4 (Acrobat 5) or PDF/X-3 (ISO Standard) ? If they accept PDF/X-3, consider yourself lucky. This type of PDF is the most advanced for commercial printing.
+PDF/X is expressly designed to assure good color fidelity between systems. If they can recommend specific ICC profiles to use, then even better.</p>
+
+<h4>Will they be converting the PDF to other formats like EPS? </h4>
+
+<p>Be aware, not all page layout applications are capable of supporting some of the advanced PS3 or PDF 1.4 features Scribus supports. Unless the printer's systems are using PDF 1.4, this is <strong>not</strong> a recommended solution.</p>
+
+<h4>Can they provide an ICC profile of their printer if color fidelity is critical?</h4>
+
+<h4>What is the PS level of their RIP ?</h4>
+
+<p>This can be a determining factor in how you prepare the files. If their RIP is 3015.xxx+, you can be sure their RIP can handle 100% of the features of Scribus. They might not be able to directly answer that, but... </p>
+
+<p>Consult <a href="prepress.html">The Pre-Press Notes</a> and you can even take a printed copy of the PDF with you if the printer has not heard of Scribus. We have an online a listing of printers who support Scribus. See: <a href="scprinters.html">Scribus Printers</a></p>
+
+<p>If there remains unanswered issues, ask on the mailing list or on IRC. Usually, there is someone knowledgable who can answer your questions.</p>
+
+</body>
+</html>
/Scribus/doc/en/print3.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/importhints.html
===================================================================
--- Scribus/doc/en/importhints.html (nonexistent)
+++ Scribus/doc/en/importhints.html (revision 13527)
@@ -0,0 +1,54 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Notes on Importing Issues with Scribus</title>
+</head>
+<body>
+<h2>Notes on Importing Issues with Scribus</h2>
+<p>Although Scribus imports most common DTP image formats like TIFF and EPS, over time one of the more difficult tasks in DTP is getting stuff into your layout. Unlike some other DTP programs where printing can be finicky, Scribus print and PDF export has always been very reliable. I can think of
+a handful of times when I had crashes or could not get the desired print or PDF from Scribus. With correctly prepared images and files, the output from Scribus matches proprietary layout programs.</p>
+<p>In my experience, the key to this are using the right format for the right type of image. Whenever possible, import your images as vector via SVG, EPS or PDF. The other is I am <strong>really</strong> picky about fonts. You will see this noted through the docs; when you are working with high-end DTP tools like Scribus, font quality matters. In professional DTP, it matters <strong>a lot</strong>. Probably the number one reason PostScript output fails, whether to a printer or PDF export, is a dodgy or corrupted font.</p>
+
+<h3>TIFF, JPEG, PNG what is the difference?</h3>
+<p>Hints (or) avoiding some issues which can baffle a beginner:</p>
+
+<h3>If it looks good on screen it will look good on paper</h3>
+<p>Nope, sorry. One of the most common beginner mistakes is to assume a nice looking JPEG from website will print nicely on paper. Most websites use JPEGs, gifs or sadly, less commonly, PNGs. JPEGs, by their design, are lossy compression. In the process of compressing a JPEG, data is discarded and permanently lost. Moreover, there is a type of JPEG called progressive which is pure poison in a PostScript work-flow. A progressive JPEG is the type that partially displays as it is downloading in a web browser. <strong>Avoid these at all costs.</strong> Scribus will not load, nor export progressive jpegs. Lastly, remember, most web page graphics have a resolution of 72-96 DPI. Scribus can generate PDFs with 4000 dpi.</p>
+<p>For high-level PostScript printing there are three kinds of file formats that work well for images like photos and anything that is made up of pixels and have been time tested: TIFF, tif and Tiff.</p>
+<p>No matter which way you spell it, a Tagged Image File Format is the file format for bitmap images. Period. End of story. Don't give me any arguments: I'll win.</p>
+
+<h3>Why?</h3>
+<ol>
+ <li>It is a &#034;lossless&#034; format. The compression scheme does not reduce quality.</li>
+ <li>For your purpose of working with Scribus, the GIMP does a fine job of exporting or saving them from the native XCF format.</li>
+ <li>It handles ICC profiles without problems. You can &#034;tag&#034; it with the little cms utility tifficc or embed an ICC profile in Photoshop, Photopaint and other bitmap editors.</li>
+ <li>It supports CMYK colors better than almost any other bitmap format.</li>
+ <li>Every high end DTP application can support them, including Scribus.</li>
+ <li>TIFF files, if they are prepared properly in the GIMP or Photoshop are extremely reliable when printed commercially. Rarely do PostScript devices have problems with them.</li>
+</ol>
+
+<h3>Caveats</h3>
+<p>There are more than fifty different flavors of TIFF. Not every image editor saves them with the same fidelity to the standards. GIMP through its use of libtiff, shared with Scribus, does a fine job of supporting Tiffs. The way I work with files from GIMP is to save the original file in the native GIMP xcf format and then, once edited to your satisfaction, re-save as a tiff or with screen shots meant for the web, PNG.</p>
+<p>Now the exception to that rule is PNG, especially for application screen shots. PNG has a lot of advanced features, like ICC color support and real alpha transparency, which are often not supported well by some applications (a certain leading browser comes to mind). PNG also compresses very well. The only time I prefer Jpeg to PNG is for photos with high dynamic range, mostly for reasons of size on a web page. For creating PDFs with screen shots, PNG is superb and will print well, as long as you do not make any scaling adjustments which reduce the image size. So if you have a screen shot which is typically at 72-96dpi, but you need to shrink it, do so by scaling the image in the GIMP or within Scribus. Whenever you are scaling screen shots disable re-sampling in any image editor. With screen-shots you should never reduce the number of pixels or you will lose sharpness quickly.</p>
+
+<h3>If it looks bad on screen, it will print terribly</h3>
+<p>EPS files or Encapsulated PostScript files. EPS files natively have no screen preview at all. EPS files are really a special subset of postscript instructions. They typically look just plain awful on screen if they have a TIFF or PICT preview embedded or are just a simple gray box. EPS have two important virtues: They print well to both high resolution printers or when creating PDFs. EPS files can be resolution independent and are the only file you can (sometimes) safely scale larger than 100% than its native size without degrading image sharpness.</p>
+<p>The one issue you might find with EPS files is while a lot of applications can generate EPS files, not all do so with the same fidelity to high-quality printing, nor do all apps follow the EPS specs properly. One way to test an EPS for use with Scribus, is to open the EPS in GSview and look in the message box, by pressing Shift M. This will show the output messages from Ghostscript. Ghostscript is correctly quite fussy about EPS files. So, if you are trying to import EPS files and they do not work properly in Scribus and GSview/Ghostscript is spitting lots of error messages, try using a different application to generate them.</p>
+<p>One reason for the ubiquity of EPS files in DTP is there is another DTP application which historically had poor support for TIFF and other bitmap image files, but does have good support for EPS import. So, many DTP users habitually create EPS files from bitmap images from Photoshop or others. Unfortunately, this can have the side effect of receiving image files which may need adjustment, but without the original image file - impossible. EPS is ideal for receiving vector artwork like maps, mixed with text. The caveat is the fonts should be embedded in the EPS properly
+to print properly from Scribus.</p>
+<p>Fortunately, Scribus automatically creates a low resolution preview image which is handy for placing and adjusting sizing on the page. When importing an EPS, Scribus generates a 72dpi PNG preview of the EPS, so do not be concerned if it does not look sharp right away. Printing or exporting a PDF will generate the high resolution image in the file.</p>
+<p>Skeptical about the difference between a vector and a bitmap image file ? Here is an example that you can see for yourself. Go to: <a href="http://www.isc.tamu.edu/~lewing/linux">http://www.isc.tamu.edu/~lewing/linux</a></p>
+<p>Get the linked PostScript, which is an EPS version of Tux and then right click and download one of the gifs. They are about the same in file size. Now create a new doc in Scribus with 2 regular size pages. Place the gif on one page and then the eps file on another. Export a PDF at 600+dpi.
+Open in Acro Reader. Zoom in 200-400 %. Now you see the difference...</p>
+<p>Why the difference? Scribus creates and Acrobat Reader renders something called PostScript operators - another fancy name for using math in drawing curves on screen and when printed. A gif, or JPEG is just a bunch of pixels, literally dots to create the image.</p>
+
+<h3>My New Favorite File Format</h3>
+<p>With the recent addition of SVG import, this gives users one more excellent way of importing images and artwork. SVG - Scalable Vector Graphics. Scalable is great because well it is scalable, meaning you can in theory enlarge the the graphic to the size of the side of a house and it would retain its sharpness. Vector is how it does it, vectors meaning the shapes are drawn by mathematical commands to greatly simplify. More on the next page on some neat importing tricks.</p>
+
+<h3>Think About Fonts When Importing Too</h3>
+<p>A similar issue is the fonts look good on screen, but do not print well. Usually, this is the case of freeware TrueType fonts, downloaded from the web. TrueType fonts, on average will look better on screen, but may not print with the intended results. However, it takes a huge amount of time and QA to create high-quality fonts, especially correctly hinting TrueType fonts. Notice that there are very few high-quality fonts which have been developed in open source. There are a few, but sadly not with the regularity which we see new apps pop up on Freshmeat.</p>
+<p>Conversely, the Type 1 fonts included with Ghostscript are not optimized for on-screen appearance, but they usually make excellent printer fonts. The fonts actually were made by URW++, a well regarded type foundry and were donated to the Ghostscript distribution by Artifex. The only issue is when the Nimbus fonts - their true PostScript names are often aliased to Times, Helvetica and Courier. This results in a user thinking it is not necessary to embed these fonts as they come standard with Acrobat Reader. Unfortunately, if they are not embedded Acro Reader does a particularly
+poor job of emulating these with its built-in multi-master fonts. With Scribus, you will not have this worry, as Scribus uses the correct PostScript name embedded in the font.</p>
+<p>The Bitstream fonts included with Xfree86 like Charter and the new Vera fonts are fine fonts for printing. I also like the Utopia family which is actually an Adobe Type 1 font donated by IBM. When creating Scribus docs in PDF form, I pretty much use this family exclusively.</p>
+</body>
+</html>
/Scribus/doc/en/importhints.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/machints1.html
===================================================================
--- Scribus/doc/en/machints1.html (nonexistent)
+++ Scribus/doc/en/machints1.html (revision 13527)
@@ -0,0 +1,49 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Mac OSX Hints and Notes</title>
+</head>
+<body>
+<h2>Mac OSX Hints and Notes</h2>
+
+<p><strong>Editor's Note:</strong> These notes are based on advice and notes kindly provided by Martin Costabel. He has done a terrific job of maintaining the Scribus fink package, as well as, providing assistance to fink users on the mailing list. Some of these hints are directed to DTP users who might not have much experience with the vagaries of X11 or its font handling.</p>
+
+<h3>Installing Scribus Binaries</h3>
+
+<p>There are two ways - equally simple:</p>
+<ul>
+ <li>If you have Fink Commander select it from the list and <strong>right click</strong> ><strong> install binaries</strong>.</li>
+ <li>From a terminal window:
+ <blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+ <pre>sudo fink install scribus</pre>
+ </td></tr></table></blockquote>
+ </li>
+</ul>
+<p>Depending on what you already have installed and your Internet speed, this could be just a few short minutes or a long download to install the needed support libraries. The Depends will automatically be installed by Fink if you install Scribus binaries. The Recommends will not be so if you want them you will need to ask Fink to install them for you.</p>
+
+<p>Scribus Depends on the following:</p>
+<ul>
+ <li>x11</li>
+ <li>Ghostscript</li>
+ <li>qt3-shlibs</li>
+ <li>libjpeg-shlibs</li>
+ <li>libjpeg-bin</li>
+ <li>lcms-shlibs</li>
+ <li>libart2-shlibs</li>
+ <li>libpng3-shlibs</li>
+ <li>libtiff-shlibs</li>
+ <li>freetype2-shlibs or freetype2-hinting-shlibs</li>
+</ul>
+<p>Recommended, but not absolutely necessary:</p>
+<ul>
+ <li>applesystemfonts</li>
+ <li>msttcorefonts</li>
+ <li>ghostscript-fonts - Note the "unstable" 8.11 fonts are actually of better quality.</li>
+ <li>x-ghostscript-fonts</li>
+</ul>
+<p>I would avoid using the gimp-freefonts package in Scribus, while they might be fine in other applications.</p>
+<p>In addition, Scribus supports OpenType Fonts, but not in the DFONT format that MacOSX uses. You can use <a href="http://fondu.sourceforge.net/">fondu</a>, a tool to convert fonts with resource forks, into a format which can be understood by X11. You are recommended to convert OpenType fonts into TrueType/ OpenType fonts, to preserve all the glyphs. (Type 1 fonts are limited to 256 gylphs per font.) </p>
+<p>Newer X windows system with the so-called <strong>fontconfig</strong> system have the concept of a personal fonts directory, usually in a hidden directory named <code>.fonts</code>. Scribus can add this and any other directories which contain Type 1 (PC) or TrueType / OpenType fonts. Scribus does not need the <code>.afm</code> files for a Type 1 font, just the <code>.pfm</code> files. Scribus obtains the font metrics via freetype2.</p>
+<p>To build the latest greatest CVS version, look here: <a href="machints2.html">Mac OSX/Fink &#038; CVS</a></p>
+</body>
+</html>
/Scribus/doc/en/machints1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-font.html
===================================================================
--- Scribus/doc/en/scripterapi-font.html (nonexistent)
+++ Scribus/doc/en/scripterapi-font.html (revision 13527)
@@ -0,0 +1,26 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Font Related Commands</title>
+</head>
+<body>
+<h2>Font Related Commands</h2>
+
+<dl>
+
+<dt><a name="-getFontNames"><strong>getFontNames</strong></a>(...)</dt>
+<dd><code>getFontNames() -&gt; list</code>
+<p>Returns a list with the names of all available fonts.</p></dd>
+
+<dt><a name="-getXFontNames"><strong>getXFontNames</strong></a>(...)</dt>
+<dd><code>getXFontNames() -&gt; list of tuples</code>
+<p>Returns a larger font info. It's a list of the tuples with: [ (Scribus name, Family, Real name, subset (1|0), embed PS (1|0), font file), (...), ... ]</p></dd></dl>
+
+<dt><a name="-renderFont"><strong>renderFont</strong></a>(...)</dt>
+<dd><code>renderFont("name", "filename", "sample", size, format="PPM") -&gt; bool</code>
+<p>Creates an image preview of font "name" with given text "sample" and size. If "filename" is not "", image is saved into "filename". Otherwise image data is returned as a string. The optional "format" argument specifies the image format to generate, and supports any format allowed by QPixmap.save(). Common formats are PPM, JPEG, PNG and XPM.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the specified font can't be found. May raise ValueError if an empty sample or filename is passed.</p></dd></dl>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-font.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/short-words.html
===================================================================
--- Scribus/doc/en/short-words.html (nonexistent)
+++ Scribus/doc/en/short-words.html (revision 13527)
@@ -0,0 +1,69 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Short Words for Scribus</title>
+</head>
+<body>
+<h2>Short Words for Scribus</h2>
+
+<h4>What the Short Words Plug-in Does:</h4>
+<p>Short Words for Scribus is a special plug-in for adding non-breaking spaces before or after, so called, short words.</p>
+<p>These short words are specific to every language's typography rules, e.g. according to Czech, Polish, and Slovak typographical standards it is not allowed to leave one letter conjunctions at line ends, if the line contains more than 25 signs. A common issue are measure and weight units, where for obvious reasons non-breaking spaces should be put in-between the preceding numbers and the units. Last but not least, there are plenty of abbreviated academic degrees, military ranks etc, which should not be separated from their owners.</p>
+<p>Although Scribus team cannot individually address every one of these national standards, one of the Scribus core team developers, Petr Van&#283;k, decided to provide Scribus users with a plug-in, that can be easily customized to meet their specific needs.</p>
+
+<h4>How it Works</h4>
+<p>The screen shot below shows a sample text containing a short word before applying non-breaking spaces.</p>
+<p><b>Text sample before executing Short Words</b></p>
+<table width="100%"><tr><td align="center"><img src="images/before_short_words.png" alt="Text sample before executing Short Words" title="Text sample before executing Short Words " /></td></tr></table>
+
+<p>The same text after applying non-breaking spaces. The red encircled word Mr jumped to the next line, because the normal space between Mr and Justice has been replaced by a non-breaking space.</p>
+<p><b>Text sample after executing Short Words</b></p>
+<table width="100%"><tr><td align="center"><img src="images/after_short_words.png" alt="Text sample after executing Short Words" title="Text sample after executing Short Words " /></td></tr></table>
+<h4>How to execute Short Words</h4>
+<p>If you successfully installed the plug-in, go to the <code>Extras</code> menu and choose the <code>Short Words...</code> option:</p>
+<p><b>Calling Short Words for Scribus</b></p>
+<table width="100%"><tr><td align="center"><img src="images/swmenu.png" alt="Calling Short Words for Scribus" title="Calling Short Words for Scribus " /></td></tr></table>
+
+<p><b>Short Words dialog window</b></p>
+<!--<center><img src="images/" alt="" /></center>-->
+<table width="100%"><tr><td align="center"><img src="images/swdialog.png" alt="Short Words dialog window" title="Short Words dialog window " /></td></tr></table>
+<ul>
+<li><strong>Selected frames</strong> - Apply non-breaking spaces to selected text frames</li>
+<li><strong>Active page</strong> - Apply non-breaking spaces to all frames of the current page.</li>
+<li><strong>All items </strong> - Apply non-breaking spaces to the whole document.</li>
+<li><strong>Replace defaults by user config</strong> - When the user config file exists you can choose if you want to append your config to the global configuration by unchecked button. You can replace predefined values with yours with checked button too.</li>
+</ul>
+<h4>Configuration</h4>
+<p>Short Words for Scribus provides a system wide configuration file <code>scribus-short-words.rc</code>, which is usually located in the <code>$prefix/lib/scribus/plugins</code> directory (the actual directory depends on where you or your distribution installed Scribus). This configuration file is self explanatory, basically it contains a list of short words for a given language, preceded or followed by a space and separated by commas. The position of the space, before or after a short word, indicates to the plug-in, where the non-breaking space should be put. Every line with configuration settings has to start with the language it is meant for, e.g. en for English or cs for Czech:
+</p>
+<pre>
+# English stuff START here
+en=Dr. ,Dr ,Mr. ,Mr ,Mrs. ,Mrs ,Ms. ,Ms ,Prof. ,Prof ,Rev. ,Rev ,
+en= Kg, kg, g, mg, oz, lb, cwt, km, Km, m, cm, mm,
+
+# Czech short words START here
+## hanging conjunctions
+cs=K ,k ,S ,s ,V ,v ,Z ,z ,O ,o ,U ,u ,I ,i ,A ,
+## physics and math
+cs= kg, g, m, cm, mm, l, hl, s, %,
+</pre>
+<p>If you want to use self defined short words, e.g. for a new language, create your own configuration file with your own short words, and save the file as <code>scribus-short-words.rc</code> in the <code>~/.scribus</code> directory. <em>You can choose the plugin appends your configuration into the system one or just to replace and use it only itself.</em></p>
+
+<h3 class="title">Important</h3>
+<p>The author is eager to extend the global configuration file to meet your needs, let him know about the short words and standards specific to your language.</p>
+
+<h3 class="title">Short Words Copyright</h3>
+<p>Short Words for Scribus Copyright 2003, 2004 Petr Van&#283;k, &lt;<a href="mailto:petr@yarpen.cz">petr@yarpen.cz</a>&gt;</p>
+<p>This program is free software; you can redistribute it
+and/or modify it under the terms of the GNU General Public License as
+published by the Free Software Foundation; either version 2 of the
+License, or (at your option) any later version.</p><p>This program is distributed in the hope that it will be
+useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+General Public License for more details.</p><p>You should have received a copy of the GNU General Public
+License along with this program; if not, write to the Free Software
+Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.</p>
+<p>Document Copyright © 2004 Petr Van&#283;k, Maciej Hanski, under the opencontent.org license included with these documents with Elected Option IV</p></p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/short-words.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/pdfexport1.html
===================================================================
--- Scribus/doc/en/pdfexport1.html (nonexistent)
+++ Scribus/doc/en/pdfexport1.html (revision 13527)
@@ -0,0 +1,24 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>PDF Exporting from Scribus</title>
+</head>
+<body>
+<h2>PDF Exporting from Scribus</h2>
+
+<h3>Overview</h3>
+
+<p>The power and versatility with the PDF Export in Scribus is one of its notable features. Documenting all its features requires almost a chapter by itself. I encourage you to read this introductory part thoroughly to become familiar with all the PDF features and options, along with viewing some of the PDFs created with Scribus on-line at <a href="http://www.scribus.net">www.scribus.net</a> in the download section.</p>
+<p>The platform neutral nature of PDF enables Scribus users to overcome a number of potential barriers to Linux and DTP. Scribus reliably exports high quality, "press-ready" PDF including advanced PDF 1.4 features, ISO compliant PDF/X-3 and ICC color managed PDFs, thanks to <a href="http://www.littlecms.com">little cms</a>. If your printer is skeptical, point them to <a href="prepress.html">Scribus Pre Press</a>. This is a downloadable PDF which outlines pre-press tests on Scribus, along with other supplementary info.</p>
+<p>If Scribus only created high resolution commercial grade PDFs, that alone would make Scribus a great application. The bonus is all the easy to use versatility such as: creating presentations &#225; la Powerpoint or creating web-enabled PDF interactive forms which can be used with electronic document exchange, the ability to use JavaScript to control elements within the PDF. Scribus provides other user friendly touches like annotations, bookmarks and optionally, document security, if needed.</p>
+<p>While PDF in one sense is a proprietary standard, it is also widely available on most every computing platform. It is also extremely well documented. The PDF 1.5 reference manual is a <em>mere</em> 1100 pages. The PDF abilities in Scribus enables for <strong>repurposing</strong> a document. One document can be produced for printing, web download or for presentation like StarOffice Impress or MS Power point. That this is a future trend in publishing is indicated by the same strategy in Adobe's InDesign 2.0+ and the new PDF capabilities in Quark Xpress 6 and Adobe Illustrator 10+. In electronic publishing and pre-press production, both have seen many enhancements to PDF, which often overcome the limitations of HTML and traditional PostScript, respectively.</p>
+<p>Your best viewing / printing results will be with the newest version of Acrobat Reader 5.0.10 or Adobe Reader 7.0.8 for Linux and version 6.0+ on other platforms, where it is available. Please also note, <strong>gv and derivatives are not suitable viewers</strong> for Scribus EPS or PDFs. Similarly, Adobe Reader on MacOSX is given preference over the built-in Preview app.</p>
+<p>One of the challenges with PDF and EPS viewers on Linux, is that Scribus creates high end PS level 3 and PDF 1.4, with capabilities beyond most of the open source viewers. Some of these features are only supported in commercial pre-press or DTP tools. Moreover, none of the open source viewers are capable of correctly interpreting color managed PDF. Two plus years of working with Scribus has led me to the current conclusion that the following three viewers are the most reliable at displaying PS/EPS/PDF created by Scribus:</p>
+<ul>
+<li><strong>Adobe Reader 5.0.10+ for Linux</strong> - The best and sometimes the only choice for PDF viewing. Detailed notes and hints: <a href="toolbox1.html">Adobe Reader</a>.</li>
+<li><strong>GSview 4.8+</strong> - with the latest version of Ghostscript available. This combination is your best choice for viewing EPS files, PS files and most PDFs. In addition, GSview has many other very useful capabilities with add-ons like <code>pstoedit</code> and <code>epstool</code>. For more detailed notes and hints: <a href="toolbox6.html">GSview</a>. I consider it an essential tool for DTP on Linux.</li>
+<li><strong>Kpdf 3.5+</strong> - This updated PDF viewer from KDE 3.5 has a new rendering engine and is capable of viewing PDF 1.5 files.</li>
+</ul>
+<p><strong>If any other PDF or EPS viewer you choose cannot display PDFs from Scribus, but they do view properly in Acrobat Reader, file a bug with the upstream author. In virtually all cases I have tested, it is a limitation of the viewing application. Scribus PDFs are tested daily with specialist pre-press software to validate their adherence to the published PDF specifications.</strong></p>
+</body>
+</html>
/Scribus/doc/en/pdfexport1.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/otherinfo.html
===================================================================
--- Scribus/doc/en/otherinfo.html (nonexistent)
+++ Scribus/doc/en/otherinfo.html (revision 13527)
@@ -0,0 +1,13 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Other Information</title>
+</head>
+<body>
+<h2>Other Information</h2>
+
+<p>Scribus has a small development team, surrounded by regular contributors and translators. The userbase is steadily growing and a large number of users are in constant contact with the development group, using Scribus and contributing in their own way to the project.</p>
+<p>This section contains information on the Scribus community, how to get in contact with the development team and the users at large. Copyright information is also provided here.</p>
+
+</body>
+</html>
/Scribus/doc/en/otherinfo.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/readme-os2.html
===================================================================
--- Scribus/doc/en/readme-os2.html (nonexistent)
+++ Scribus/doc/en/readme-os2.html (revision 13527)
@@ -0,0 +1,44 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus on OS/2 &#174; and eComStation&#8482; </title>
+</head>
+<body>
+<h2>Scribus on OS/2- Read Me</h2>
+<p>Scribus v1.3.3.7 beta for OS/2 & eComStation</p>
+<p>
+Scribus is an open-source program that brings award-winning
+professional page layout to Linux/Unix, MacOS X and Windows
+desktops with a combination of "press-ready" output and
+new approaches to page layout.</p>
+
+<p>Underneath the modern and user friendly interface, Scribus
+supports professional publishing features, such as CMYK color,
+separations, ICC color management and versatile PDF creation.</p>
+
+<p>The Scribus Team is very pleased to welcome a release on the OS/2 & eComStation platform. We would like to thank Paul Smedley who has taken the time to port Scribus itself, and those who have ported the other supporting libraries to OS/2. We will endeavour to find and resolve issues specific to the platform when they are discovered,specifically relating to levels of supporting libraries such as Qt.</p>
+
+<strong>Supports OS/2 Warp4(R) and eComStation(TM)<p></p></strong>
+
+<p>Requires libc061.dll - which is available from ftp://ftp.netlabs.org/pub/gcc/libc-0.6.1-csd1.zip</p>
+
+<p>GhostScript is a recommended installation as per the standard Scribus install instructions. Set the PostScript interpreter in Scribus' preferences to point to your installation. Example: the AFPL GhostScript executable from their gs854os2.zip is gsos2.exe. This package includes install instructions (note the GS_LIB environment variable}.</p>
+
+<p>Known issues:</p>
+<ul><li>The Qt released on OS/2 is quite old and issues may arise due to
+ this fact.</li>
+<li>Printing support is not complete, but PDF export is, you can easily print
+via Acrobat Reader or another PDF viewer as a temporary workaround.</li></ul>
+
+<p>General feedback can be provided to paul@smedley.info and via the normal Scribus communications methods (IRC, mailing list etc), bug reports should go to http://bugs.scribus.net. </p>
+<p>Porter's Note</p>
+<p>If you like this software and want to support continued OS/2 ports,
+please consider donating via PayPal via the link at http://smedley.info/os2ports,
+or via the Mensys online store at http://www.mensys.net/os2ports</p>
+
+<p>Cheers,</p>
+<p>Paul Smedley<br />
+Adelaide, Australia<br />
+January, 2007<br />
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/readme-os2.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-layer.html
===================================================================
--- Scribus/doc/en/scripterapi-layer.html (nonexistent)
+++ Scribus/doc/en/scripterapi-layer.html (revision 13527)
@@ -0,0 +1,109 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Layer related Commands</title>
+</head>
+<body>
+<h2>Layer related Commands</h2>
+
+<dl>
+
+<dt><a name="-createLayer"><strong>createLayer</strong></a>(...)</dt>
+<dd><code>createLayer(layer)</code>
+<p>Creates a new layer with the name "name".</p>
+<p>May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-deleteLayer"><strong>deleteLayer</strong></a>(...)</dt>
+<dd><code>deleteLayer("layer")</code>
+<p>Deletes the layer with the name "layer". Nothing happens if the layer doesn't exists or if it's the only layer in the document.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-getActiveLayer"><strong>getActiveLayer</strong></a>(...)</dt>
+<dd><code>getActiveLayer() -&gt; string</code>
+<p>Returns the name of the current active layer.</p></dd>
+
+<dt><a name="-getLayers"><strong>getLayers</strong></a>(...)</dt>
+<dd><code>getLayers() -&gt; list</code>
+<p>Returns a list with the names of all defined layers.</p></dd>
+
+<dt><a name="-getLayerBlendmode"><strong>getLayerBlendmode</strong>(...)</a></dt>
+<dd><code>getLayerBlendmode("layer") -&gt; int</code>
+<p>Returns the "layer" layer blendmode, May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-isLayerFlow"><strong>isLayerFlow</strong>(...)</a></dt>
+<dd><code>isLayerFlow("layer") -&gt; bool</code>
+<p>Returns whether text flows around objects on layer "layer", a value of True means that text flows around, a value of False means that the text does not flow around.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-isLayerLocked"><strong>isLayerLocked</strong>(...)</a></dt>
+<dd><code>isLayerLocked("layer") -&gt; bool</code>
+<p>Returns whether the layer "layer" is locked or not, a value of True means that the layer "layer" is editable, a value of False means that the layer "layer" is locked.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-getLayerTransparency"><strong>getLayerTransparency</strong>(...)</a></dt>
+<dd><code>getLayerTransparency("layer") -&gt; float</code>
+<p>Returns the "layer" layer transparency, May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-isLayerOutlined"><strong>isLayerOutlined</strong>(...)</a></dt>
+<dd><code>isLayerOutlined("layer") -&gt; bool</code>
+<p>Returns whether the layer "layer" is outlined or not, a value of True means that the layer "layer" is outlined, a value of False means that the layer "layer" is normal.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-isLayerPrintable"><strong>isLayerPrintable</strong></a>(...)</dt>
+<dd><code>isLayerPrintable("layer") -&gt; bool</code>
+<p>Returns whether the layer "layer" is printable or not, a value of True means that the layer "layer" can be printed, a value of False means that printing the layer "layer" is disabled.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-isLayerVisible"><strong>isLayerVisible</strong></a>(...)</dt>
+<dd><code>isLayerVisible("layer") -&gt; bool</code>
+<p>Returns whether the layer "layer" is visible or not, a value of True means that the layer "layer" is visible, a value of False means that the layer "layer" is invisible.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-sentToLayer"><strong>sentToLayer</strong></a>(...)</dt>
+<dd><code>sentToLayer("layer" [, "name"])</code>
+<p>Sends the object "name" to the layer "layer". The layer must exist. If "name" is not given the currently selected item is used.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setActiveLayer"><strong>setActiveLayer</strong></a>(...)</dt>
+<dd><code>setActiveLayer("name")</code>
+<p>Sets the active layer to the layer named "name".</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerBlendmode"><strong>setLayerBlendmode</strong>(...)</a></dt>
+<dd><code>setLayerBlendmode"layer", blend)</code>
+<p>Sets the layers "layer" blendmode to blend. May raise NotFoundError if the layer can't be found.</p>
+<p>May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerFlow"><strong>setLayerFlow</strong>(...)</a></dt>
+<dd><code>setLayerFlow"layer", flow)</code>
+<p>Sets the layers "layer" flowcontrol to flow. If flow is set to true text in layers above this one will flow around objects on this layer.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerLocked"><strong>setLayerLocked</strong>(...)</a></dt>
+<dd><code>setLayerLocked("layer", locked)</code>
+<p>Sets the layer "layer" to be locked or not. If locked is set to true the layer will be locked.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerOutlined"><strong>setLayerOutlined</strong>(...)</a></dt>
+<dd><code>setLayerOutlined"layer", outline)</code>
+<p>Sets the layer "layer" to be locked or not. If outline is set to true the layer will be displayed outlined.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerPrintable"><strong>setLayerPrintable</strong></a>(...)</dt>
+<dd><code>setLayerPrintable("layer", printable)</code>
+<p>Sets the layer "layer" to be printable or not. If is the printable set to false the layer won't be printed.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerTransparency"><strong>setLayerTransparency</strong>(...)</a></dt>
+<dd><code>setLayerTransparency"layer", trans)</code>
+<p>Sets the layers "layer" transparency to trans.</p>
+<p>May raise NotFoundError if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+<dt><a name="-setLayerVisible"><strong>setLayerVisible</strong></a>(...)</dt>
+<dd><code>setLayerVisible("layer", visible)</code>
+<p>Sets the layer "layer" to be visible or not. If is the visible set to false the layer is invisible.</p>
+<p>May raise <a href="scripterapi.html#NotFoundError">NotFoundError</a> if the layer can't be found. May raise ValueError if the layer name isn't acceptable.</p></dd>
+
+</dl>
+</body>
+</html>
/Scribus/doc/en/scripterapi-layer.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/javascriptpdf.html
===================================================================
--- Scribus/doc/en/javascriptpdf.html (nonexistent)
+++ Scribus/doc/en/javascriptpdf.html (revision 13527)
@@ -0,0 +1,17 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Enhancing Scribus PDF with JavaScript</title>
+</head>
+<body>
+<h2>Enhancing Scribus PDF with JavaScript</h2>
+<p>Scribus has very complete support for adding interactive features to PDF. Perhaps, no other application can offer more in the area of PDF forms, presentations or other interactive elements than Acrobat Pro itself. This is enabled via dialog boxes in the field properties and by adding JavaScript based functions attached to PDF buttons and text fields. The best way to demonstrate this is via a PDF tutorial which has these features:</p>
+
+<p>The "JavaScripting PDF " from http://docs.scribus.net is a step by step guides for beginning to enhance PDF with JavaScript.</p>
+<p>Direct Link: </p><a href="http://docs.scribus.net/content/en/pdfs/javascriptpdf.pdf">http://docs.scribus.net/content/en/pdfs/javascriptpdf.pdf</a></p>
+<p>After reading this PDF tutorial, the next section, PDF Web Forms walks you through the step by step creation of a web based PDF form with a sample .php snippet to read the submitted data.</p>
+<p>This is best viewed by Acrobat Reader 5.x downloaded and run outside of a browser. You can typically right click the links to the PDF and <em>Save As.*</em>. to save the file locally. Other PDF viewers do not have the JavaScript support to view this properly.</p>
+
+<p>Lastly, a good link for with code examples: <a href="http://www.accesspdf.com/article.php/20050510131850979#comments">http://www.accesspdf.com/article.php/20050510131850979</a> for using the pdftk utilities to allow using html as a front end to filling in PDF forms.</p>
+</body>
+</html>
/Scribus/doc/en/javascriptpdf.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/developers.html
===================================================================
--- Scribus/doc/en/developers.html (nonexistent)
+++ Scribus/doc/en/developers.html (revision 13527)
@@ -0,0 +1,14 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>For Developers</title>
+</head>
+<body>
+<h2>For Developers</h2>
+
+<p>Wanting to help Scribus develop even faster? Want to get your hands dirty with some coding? Got a great idea for new addon functionality for Scribus?</p>
+
+<p>Information related to the development of Scribus is here! You have come to the right place. Contact the team to discuss our plans and what we need some help with.</p>
+
+</body>
+</html>
/Scribus/doc/en/developers.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox9.html
===================================================================
--- Scribus/doc/en/toolbox9.html (nonexistent)
+++ Scribus/doc/en/toolbox9.html (revision 13527)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Inkscape</title>
+</head>
+<body>
+<h2>Inkscape</h2>
+<p><em>Disclaimer: I am technically one of the Inkscape Team members, though mostly to liaise with them and build rpms. However, I would not bother a: If Inkscape was not such a terrific application with a really bright future. b: The Inkscape Team was not a really great bunch to work with. Inkscape&#039;s development is an excellent model for OSS developers to follow.</em></p>
+
+<p>That said, Inkscape is rapidly becoming the leading OSS SVG vector drawing or &#034;illustration&#034; tool. The Inkscape Team has made a lot of effort to faithfully adhere to the W3C SVG specs. The most recent version has made a lot of progress and has new import/export options. Some more experimental than others. </p>
+
+<p>In its favor: A very friendly user interface, with extensive tool tips and a couple of really well done short tutorials on vector drawings. Almost every function can be handled by keyboard short cuts (the list of shortcuts is almost 10 pages). Like Scribus, the Inkscape Team is quick with bug fixes and is very open minded about feature requests and enhancements.</p>
+
+<p>The best part of Inkscape though it is its fidelity to SVG specs. No, it is not perfect, no application is, however. Inkscape SVG seems to work well with other SVG applications better than most, even some expensive commercial ones. </p>
+
+<p>For the most part, Inkscape SVG artwork will import into Scribus easily. There are some SVG features which are not yet supported by Scribus (patterns), however 99% of the time, It Just Works TM. If a file does not seem to import correctly into Scribus, try saving as &#034;Plain SVG&#034; within Inkscape. One other hint for working with Inkscape SVG is the SVG model for working with text is far different than the PDF/PostScript model. (One of the few weak spots in the spec in my opinion.) Save text input and text effects for Scribus. Scribus does a very good job of offering you a multitude of text effects and it will output them faithfully. Scribus uses the freetype2 libraries and this gives you a wide range of effects.</p>
+
+<p>That does not mean Inkscape does it wrong. Only that the way it is done in SVG and within a PostScript oriented application are sometimes very different and difficult to translate from one to the other. Actually, Inkscape does an excellent job of support for SVG font features including kerning and other advanced features.</p>
+</body>
+</html>
/Scribus/doc/en/toolbox9.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/hyphenator.html
===================================================================
--- Scribus/doc/en/hyphenator.html (nonexistent)
+++ Scribus/doc/en/hyphenator.html (revision 13527)
@@ -0,0 +1,31 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Hyphenation - Type Hints</title>
+</head>
+<body>
+<h2>Hyphenation - Type Hints</h2>
+<h3>Introduction</h3>
+<p>This feature adds sophisticated hyphenation control for text formatting within Scribus. Based on code from both Tex and OpenOffice.org, it has a time tested algorithm for selecting syllables within words.</p>
+
+<h3>Usage</h3>
+<p>Hyphenation. Select a text frame, Adjust the text alignment you wish and then select Hyphenation &#062; Hyphenate Text from the menu. Automatic, means just that - select a text frame and Hyphenate &#062; Hyphenate Text sets this very similarly to applying a Style. Changing the font, kerning or font size will automatically redraw the text and reapply the hyphenation automatically.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/hyphen1.png" align="center" alt="Hyphenator Settings Dialog" /></td></tr></table>
+
+<p>For most purposes, the settings can be left at the default - Automatic - and then you can simply apply hyphenation by selecting the text box and then Hyphenation &#062; Hyphenate Text from the menu. You can also allow Scribus to automatically hyphenate as you type.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/hyphen2.png" align="center" alt="Possible Hyphenation Dialog" title="Possible Hyphenation Dialog" /></td></tr></table>
+
+<p>When set to manual, you also have the option to over ride possible hyphenation word by word, as shown in figure below.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/hyphen3.png" align="center" alt="Possible Hyphenation Dialog" title="Possible Hyphenation Dialog" /></td></tr></table>
+
+<p>There is a sample document included with the documentation <code>hyphen.scd.gz</code> which gives a short demo of the differences when you layout a columns of text.</p>
+
+<p>You will probably have the best appearance from formatting your text as <strong>Block(justified)</strong>.</p>
+
+<p>Currently, there are hyphenation dictionaries in Catalan, Czech, Danish, English, Finnish
+French, German, Greek, Irish (Gaelic), Italian, Hungarian, Lithuanian, Polish, Portuguese, Russian, Slovak, Slovenian, Spanish, Swedish and Ukrainian.</p>
+</body>
+</html>
/Scribus/doc/en/hyphenator.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/toolbox13.html
===================================================================
--- Scribus/doc/en/toolbox13.html (nonexistent)
+++ Scribus/doc/en/toolbox13.html (revision 13527)
@@ -0,0 +1,18 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Xnview</title>
+</head>
+<body>
+<h2>Xnview</h2>
+<p>There are loads of image previewer/thumb nailing applications from some web based - even Konqueror and Nautilus have some of these features. </p>
+
+<h3>So why do I pick Xnview? </h3>
+
+<p>Its ugly. It uses old, Motif type libraries, but it has two very redeeming qualities: </p>
+<ol><li>Its very fast, as fast or faster than some similar proprietary apps. </li>
+<li>It handles a wide array of image formats with very good conversion capabilities. There are some real obscure file formats Xnview can open and convert. It's probable that only Imagemagick can handle more. I've found it very stable and worth at least adding to your toolbox.</li></ol>
+
+<table width="100%"><tr><td align="center"><img src="images/xnview.png" alt="Xnview" /></td></tr></table>
+</body>
+</html>
/Scribus/doc/en/toolbox13.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/faq3.html
===================================================================
--- Scribus/doc/en/faq3.html (nonexistent)
+++ Scribus/doc/en/faq3.html (revision 13527)
@@ -0,0 +1,46 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Development Questions</title>
+</head>
+<body>
+<a name="top"></a>
+<h2>Development Questions</h2>
+<ul>
+ <li><a href="#16">Packaging Scribus rpms,debs or plug-ins - What should I do ?</a></li>
+ <li><a href="#12">I have a great idea for adding something to Scribus. How can I write a plug-in?</a></li>
+ <li><a href="#18">I am interested in contributing. Is there documentation on coding style or other reference?</a></li>
+</ul>
+
+<h3>Answers</h3>
+
+<ul>
+ <li><a name="16"></a>
+ <p class="faqquestion">Packaging Scribus rpms, debs or plug-ins - What should I do?</p>
+ <p>Downstream packagers are asking for and may soon demand GPG signed tarballs. For Fedora, this is not a requirement, but does ease acceptance of packages. It also shows we are doing &quot;The Right Thing&quot;. md5sums are not foolproof.</p>
+ <p>To create a gpg signed tarball: <br/>
+ <code>$gpg -u package&#114;&#064;&#102;oo.net --armor --output tarball.sig --detach-sig tarball.tar.gz </code></p>
+ <p>To verify : <br/>
+ <code>$gpg --verify ./tarball.asc ./tarball.tar.gz</code></p>
+
+ <p><strong>Packaging plug-ins:</strong></p>
+ <p>Plug-ins should be named <i>scribus-something</i>. This helps packagers deal with revisions and obsoletes when upgrading.</p>
+ <p><strong>Signing your package,deb,tar etc.</strong></p>
+ <p>First, you need to have a public/private keypair. This can be generated with GPG using &lt;code&gt;gpg --gen-key&lt;/code&gt;</p>
+ <p>To add a signature to an existing package, use the command <code>rpm --addsign /path/to/package.rpm</code> To sign in the process of building a package, use <code>rpmbuild -bb --sign</code></p>
+ <p>To check the signature on a package, use <code>rpm --checksig</code></p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="12"></a>
+ <p class="faqquestion">I have a great idea for adding something to Scribus. How can I write a plug-in?</p>
+ <p>Thanks to Petr Vanek, there is nicely done article: <a href="plugin_howto.html">Scribus Plug-in Howto</a> online.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+ <li><a name="18"></a>
+ <p class="faqquestion">I am interested in contributing. Is there documentation on coding style or other reference?</p>
+ <p>Glad you asked. There is a <a href="codingstandards.html">Scribus Coding section</a> which outlines coding style and recommendations for code submissions.</p>
+ <a href="#top">Back to top</a><hr/>
+ </li>
+</ul>
+</body>
+</html>
/Scribus/doc/en/faq3.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scprinters.html
===================================================================
--- Scribus/doc/en/scprinters.html (nonexistent)
+++ Scribus/doc/en/scprinters.html (revision 13527)
@@ -0,0 +1,21 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Friendly Printers</title>
+</head>
+<body>
+ <h2>Scribus Friendly Printers</h2>
+ <p>Once you have your masterpiece created, sometimes the next step is getting is your file commercially printed.</p>
+ <h4>What defines a "Scribus Friendly Printer" ?</h4>
+ <p>First and foremost the ability to handle PDF directly without conversion to other formats. Conversion for placement into other page layout applications is <strong>not</strong> recommended and may result in reduced print quality. Ideally, a printer can handle a Scribus file natively, but is not a necessity. The most important is the ability to handle correctly newer versions of PDF without further alteration.</p>
+ <p>This list is by no means comprehensive, but are printers who have been involved in developing Scribus and or have expressed a willingness to handle Scribus files natively or as PDF: </p>
+
+ <h3>North America / Canada</h3>
+ <p><a href="http://www.mardigrafe.com/index.html">Mardigrafe</a> Based in Montreal - Capable of working with native Scribus files. Can work with English, French, German, Italian, Russian and Spanish texts.</p>
+ <h3>North America / USA</h3>
+ <p><a href="http://ecape.com/mediakit/print_dsn_index.shtml">Cape Cod Ink</a> based in Massachusetts. Can handle a range of printing needs including short run color print jobs. Can handle native Scribus files on request.</p>
+ <h3>Europe / Germany</h3>
+<p> <a href="http://digital-print-center.com/">Digital Print Center</a> based in Konstanz - Specialist in Digital Copy and database publishing. </p>
+<p>If you know of printers who should be added to this list, please mail mrdocs at scribus.info.</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/scprinters.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/pdf_form.html
===================================================================
--- Scribus/doc/en/pdf_form.html (nonexistent)
+++ Scribus/doc/en/pdf_form.html (revision 13527)
@@ -0,0 +1,106 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>How To Create Your First PDF Web Form with Scribus</title>
+</head>
+<body>
+<h2>How To Create Your First PDF Web Form with Scribus</h2>
+<p><em><strong>With many thanks to Maciej Hanski</strong>, who kindly translated this from the Polish original, licenced under the FDL.</em></p>
+<p><strong>The sample files, <code>scribusformphp.tar.gz</code>, a tarball of a php file and a sample doc, are available from http://docs.scribus.net</a></p>
+
+<p>One of the biggest advantages of Scribus is the possibility to create PDF forms with embedded JavaScript scripts (in Adobe's own version, as described in the Adobe JavaScript Reference at http://partners.adobe.com/asn/developer/pdfs/tn/5186AcroJS.pdf</p>
+
+<p>Its rather simple to create a new form with Scribus. We start with clicking on the "New Document" icon or choosing <strong>New</strong> from the <strong>File</strong> menu.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/formularz_nowy.png" alt="Create a new doc" title="Create a new doc" /></a></td></tr></table>
+
+<br />
+<p>Let us activate the grid then (menu <strong>View</strong> -> <strong>Show Grid</strong>), it will help us to correctly locate our form fields on the page. We need some text frames to make a nice title and field descriptions - a few clicks on the <strong>[ab]</strong> icon and all the text frames are there in no time.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/siatka_menu.png" border="0" alt="null" /></td></tr></table>
+
+<p>Having filled our frames with text, we can change their properties with the <strong>Properties</strong> palette, which can be found in the <strong>Tools</strong> menu.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/siatka_jednostki_miar.png" alt="" /></td></tr></table>
+
+
+<br />
+
+<div>Now we can start adding form elements: some text fields and one button for submitting our form to an URL. To add a field simply click on the arrow on the right side of the <strong>OK</strong> icon and select a type from the displayed options: button, text field, check box, combo box, and list box.</div>
+
+<br />
+<table width="100%"><tr><td align="center"><img src="images/symbole.png" alt="null" /></td></tr></table>
+
+<p>The current active element of the form has a red frame border; you can activate an element in choosing the "Select" icon (the one with crossed arrows) and clicking on the item to be chosen.</p>
+<br />
+
+<table width="100%"><tr><td align="center"><img src="images/ulica.png" alt="null" /></td></tr></table>
+
+<br />
+
+<p>The right click on an element activates a new menu. We choose <strong>Field Properties</strong> and define field names (we will need the field names in our PHP script, to which we'll send the form), types (e.g., number, time, date), and actions to be performed on different events (Mouse Enter, Mouse Exit, On Blur, and so on).</p>
+
+<br /><br />
+
+<table width="100%"><tr><td align="center"><img src="images/wlasciwosci_pola.png" alt="null" border="0" /></td></tr></table>
+
+<br />
+
+<p>Here we are defining the <strong>No</strong> field as a number. Acrobat Reader won't accept anything else as a valid entry, then.</p>
+
+<br />
+
+<table width="100%"><tr><td align="center"><img src="images/formularz_pole_num.png" border="0" alt="null" /></td></tr></table>
+
+<br />
+
+<p>Here, we are defining a custom validation script for the <strong>Name</strong> field - after changing the field contents there will be a beep sound and an alert will be showed (not very sophisticated, I know, but it still demonstrates the possibilities of PDF). Scribus has its own simple text editor, which enables us to save the script to a separate file. Custom scripts can be defined not only on the form field level, but as global scripts as well (<strong>Edit</strong> -&#062; <strong>JavaScripts</strong>).</p>
+
+<br />
+
+<table width="100%"><tr><td align="center"><img src="images/formularz_js_skrypt.png" alt="null" /></td></tr></table>
+<br />
+
+<p>After saving the script and closing the editor, the script contents is shown in the <strong>Field Properties</strong>.</p>
+<br />
+
+<table width="100%"><tr><td align="center"><img src="images/formularz_js_sprawdzanie.png" border="0" alt="null" /></td></tr></table>
+
+<br />
+
+<p>We have still to define, to which URL the form contents will be sent (there is a simple PHP script at the destination address, which will format and display the received form data). We choose in the button properties as the action type <strong>Submit form</strong> and enter the address of our PHP script: <strong>scribus_test.php</strong>. We match the <strong>Submit Data as HTML</strong> option to end with (the other option would be the FDF data, but this is a very different story) and we are done now.</p>
+
+<br />
+
+<table width="100%"><tr><td align="center"><img src="images/wyslij_formularz.png" alt="null" /></td></tr></table>
+
+<br />
+
+<p>The only thing else to do is to export the document to PDF: menu <strong>File -&#062; Export... -&#062;; Export to PDF...</strong>.<br />We select <strong>Acrobat 5.0</strong> as the file format and save the file.</p>
+
+<br />
+<table width="100%"><tr><td align="center"><img src="images/formularz_export_PDF.png" border="0" alt="null" /></td></tr></table>
+<br />
+
+<p>The result of our work can be downloaded from http://docs.scribus.net and tested. In order to submit the form we must open it from within a browser, Netscape 4.* or Mozilla are the safe choices (check the Mozilla plug-ins to see, if the Acrobat Reader plug-in is enabled. If not, you have to symlink it into the Mozilla's plug-in directory. In my particular case, the Mozilla's plug-in directory is <strong>/usr/lib/mozilla-1.3/plug-in</strong>, and the plug-in to be symlinked into it is <strong>/usr/local/Acrobat5/Browsers/intellinux/nppdf.so</strong>).</p>
+
+<p><strong>My very own impression:</strong> Scribus as a tool for working with PDF forms seems to be more comfortable in use than Adobe Acrobat 5.0 (the only version, I've worked with). It's a lot easier to layout documents with Scribus, since Acrobat only allows you to edit existing documents, but not to create a new document from scratch. Scribus provides us with the full control over the final results and allows us much more freedom in changing the document's layout. More over, Scribus files can be edited even with a simple text editor, since its file format is entirely XML
+based.</p>
+<p><em>Maciej Hanski</em> - 22:10:2003</p>
+
+<p><strong>Some useful PDF/JavaScript Links:</strong></p>
+<ul>
+ <li><a href="http://www.planetpdf.com/mainpage.asp?WebPageID=229" target="_blank">Planet PDF</a></li>
+ <li><a href="http://partners.adobe.com/asn/developer/pdfs/tn/5186AcroJS.pdf" target="_blank">Acrobat JavaScript Object Specification</a></li>
+ <li><a href="http://ahnews.music.salford.ac.uk/scribus/documentation/pdfs/javascriptpdfa4.pdf" target="_blank">JavaScript and Scribus</a></li>
+</ul>
+
+<p><strong>Some useful CGI/PHP links:</strong></p>
+<ul>
+ <li><a href="http://www.cgi101.com/book/ch4/text.html">http://www.cgi101.com/book/ch4/text.html</a></li>
+ <li><a href="http://www.cgi101.com/book/ch4/post-cgi.html">http://www.cgi101.com/book/ch4/post-cgi.html</a></li>
+ <li><a href="http://www.mkaz.com/reference/php/setup_linux.html">http://www.mkaz.com/reference/php/setup_linux.html</a></li>
+</ul>
+
+</body>
+</html>
/Scribus/doc/en/pdf_form.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/docchanges.html
===================================================================
--- Scribus/doc/en/docchanges.html (nonexistent)
+++ Scribus/doc/en/docchanges.html (revision 13527)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Changelog of Documentation</title>
+</head>
+<body>
+<h2>Changelog of Documentation</h2>
+
+<ul>
+ <li>28 08 2004 : Launch of docs.scribus.net with Scribus 1.2 release.</li>
+</ul>
+<ul>
+ <li>01 09 2004 : Addition of <a href="fonts2.html">Fonts in Depth</a>
+ </li>
+ <li>02 09 2004 : Updated <a href="scripter1.html">Scripter</a> and <a href="scripterapi.html">Scripter API</a> files</li>
+ <li>08 09 2004 : Addition of <a href="print3.html">Preparing for Press</a> </li>
+ <li>25 09 2004 : Addition of <a href="fonts3.html">Non-Latin Fonts</a> </li>
+</ul>
+</body>
+</html>
/Scribus/doc/en/docchanges.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/doccopyright.html
===================================================================
--- Scribus/doc/en/doccopyright.html (nonexistent)
+++ Scribus/doc/en/doccopyright.html (revision 13527)
@@ -0,0 +1,78 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Copyright Notice and Publication License</title>
+</head>
+<body>
+<h2>Copyright Notice and Publication License</h2>
+
+<p>This copyright notice concerns the online and packaged version of: Scribus Help Manual, by Peter Linnell with the assistance of Franz Schmid, the main programmer of Scribus. Further additions by the rest of the Scribus team composed of Craig Bradney, Paul Johnson, Riku Leino, Petr Vanek). Original site design based on site design of the <a href="http://www.inkscape.org">Inkscape</a> website.</p>
+
+<p>The FreedomYug tutorial on docs.scribus.net, and "PDF Forms and PHP" page are licensed under the Free Documentation License which can be viewed by going to the first page of the FreedomYug tutorial section and clicking on the FDL link. The FDL applies ONLY to this section of the documentation.</p>
+
+<p>The help manual (excluding the aforementioned FreedomYug tutorial and "PDF Form and PHP" page) is distributed under the Open Publication License guidelines described at <a href="http://www.opencontent.org">www.opencontent.org</a>.</p>
+
+<p>The following is the text of the license as it applies to this work:</p>
+
+<h3>I. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS</h3>
+
+<p>This on-line help manual "Scribus Help Manual" may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference is displayed in the reproduction.
+
+<p>Proper form for an incorporation by reference is as follows:
+
+<p>Copyright (c) 2006 Peter Linnell and Franz Schmid, 2006 The Scribus Team. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).
+
+<p>The reference must be immediately followed with the elected options (see section VI).
+
+<p>Commercial redistribution of Open Publication-licensed material is permitted.
+
+<h3>II. COPYRIGHT</h3>
+
+<p>The copyright is owned by Peter Linnell and Franz Schmid, and the Scribus team.</p>
+
+<h3>III. SCOPE OF LICENSE</h3>
+
+<p>Mere aggregation of this work or a portion of this work with other works or programs on the same media shall not cause this license to apply to those other works. The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice.</p>
+
+<p>SEVERABILITY. If any part of this license is found to be unenforceable in any jurisdiction, the remaining portions of the license remain in force.</p>
+
+<p>NO WARRANTY. Open Publication works are licensed and provided "as is" without warranty of any kind, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose or a warranty of non-infringement.</p>
+
+<h3>IV. REQUIREMENTS ON MODIFIED WORKS</h3>
+
+<p>All modified versions of documents covered by this license, including translations, anthologies, compilations and partial documents, must meet the following requirements:</p>
+
+<p>1) The modified version must be labeled as such.</p>
+
+<p>2) The person making the modifications must be identified and the modifications dated.</p>
+
+<p>3) Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices.</p>
+
+<p>4) The location of the original unmodified document must be identified.</p>
+
+<p>5) The original author's name may not be used to assert or imply endorsement of the resulting document without the original author's (or authors') permission.</p>
+
+<h3>V. GOOD-PRACTICE RECOMMENDATIONS</h3>
+
+<p>In addition to the requirements of this license, it is requested from and strongly recommended of redistributors that:</p>
+
+<p>1) If you are distributing Open Publication works on hardcopy or CD-ROM, you provide email notification to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze, to give the authors time to provide updated documents. This notification should describe modifications, if any, made to the document.</p>
+
+<p>2) All substantive modifications (including deletions) be either clearly marked up in the document or else described in an attachment to the document.</p>
+
+<p>Finally, while it is not mandatory under this license, it is considered good form to offer a free copy of any hardcopy and CD-ROM expression of an Open Publication-licensed work to its author.</p>
+
+<h3>VI. ELECTED OPTIONS</h3>
+
+<p>1) Distribution of the work or derivative of the work in any standard (paper) book form is prohibited unless prior permission is obtained from the copyright holder. Other forms of distribution including CD-ROM, electronic, and magnetic media are permitted.</p>
+
+<ul>
+<li>Adobe, Adobe Reader, Adobe Acrobat are trademarks of Adobe Corporation in the United States, other countries or both.</li>
+<li>Linux is a trademark of Linus Torvalds in the United States, other countries or both.</li>
+<li>Mac, Mac OS and Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries.</li>
+<li>Microsoft, Windows, Windows NT, Visual Studio and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.</li>
+<li>Motif is a registered trademark of The Open Group in the United States, other countries, or both.</li>
+<li>UNIX is a registered trademark of The Open Group in the United States and other countries.</li>
+<li>All other company, product, or service names may be trademarks or service marks of others and are the property of their respective owners.</li></ul>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/doccopyright.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/contributions.html
===================================================================
--- Scribus/doc/en/contributions.html (nonexistent)
+++ Scribus/doc/en/contributions.html (revision 13527)
@@ -0,0 +1,36 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Contributions to the documentation<</title>
+</head>
+<body>
+<h2>Contributions to the documentation</h2>
+
+<p>This documentation website is the third generation of the Scribus documentation. The initial documents that these were developed from were written by Peter Linnell with help from Franz Schmid. As the Scribus team has grown, and the various contributions from other people has also grown, we have seen a number of additions and updates. The following table attempts to list in alphabetical order the main contributors to the documentations. Hopefully we dont miss any of you out (if so, please contact us and we will add you in):
+</p>
+
+<table border="1">
+ <tr bgcolor="#dddddd"><td>Name</td><td>Contribution(s)</td></tr>
+ <tr bgcolor="#eeeeee"><td>Niyam Bhushan</td><td>Get Started with Scribus tutorial</td></tr>
+ <tr bgcolor="#eeeeee"><td>Craig Bradney</td><td>Site implementation, management and documentation verification</td></tr>
+ <tr bgcolor="#eeeeee"><td>Maciej Ha&#324;ski</td><td>PHP form document</td></tr>
+ <tr bgcolor="#eeeeee"><td><a href="http://www.inkscape.org">Inkscape team</a></td><td>Original site layout code</td></tr>
+ <tr bgcolor="#eeeeee"><td>V&#225;clav Hlobil</td><td>Title graphics</td></tr>
+ <tr bgcolor="#eeeeee"><td>Paul Johnson</td><td>Coding Standards document</td></tr>
+ <tr bgcolor="#eeeeee"><td>Riku Leino</td><td>Get Text Plugin Howto</td></tr>
+ <tr bgcolor="#eeeeee"><td>Peter Linnell</td><td>Main documentation</td></tr>
+ <tr bgcolor="#eeeeee"><td>Franz Schmid</td><td>Scribus :) and documentation verification</td></tr>
+ <tr bgcolor="#eeeeee"><td>Petr Van&#283;k</td><td>Scripter and Plugin documentation</td></tr>
+ <tr bgcolor="#eeeeee"><td>Craig Ringer</td><td>Scripter documentation</td></tr>
+</table>
+<h4>Document Translators</h4>
+<table border="1">
+ <tr bgcolor="#dddddd"><td>Name</td><td>Language(s)</td></tr>
+ <tr bgcolor="#eeeeee"><td>Frederic Dubuy</td><td>French</td></tr>
+ <tr bgcolor="#eeeeee"><td>Johannes R&#252;schel</td><td>German</td></tr>
+ <tr bgcolor="#eeeeee"><td>Louis Desjardin</td><td>French</td></tr>
+ <tr bgcolor="#eeeeee"><td>Volker Ribbert</td><td>German</td></tr>
+ <tr bgcolor="#eeeeee"><td>François Lanctôt, thanks to <A href="http://grics.qc.ca">GRICS</A></td><td>French</td></tr>
+</table>
+</body>
+</html>
/Scribus/doc/en/contributions.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/prepress.html
===================================================================
--- Scribus/doc/en/prepress.html (nonexistent)
+++ Scribus/doc/en/prepress.html (revision 13527)
@@ -0,0 +1,15 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Pre-Press and Service Bureau Considerations with Scribus PDF</title>
+</head>
+<body>
+<h2>Pre-Press and Service Bureau Considerations with Scribus PDF</h2>
+<p>For service bureaus, printers, magazine publishers and other pre-press providers who are unfamiliar with Scribus, the notes available in the Pre-Press and Scribus PDF from <a href="http://docs.scribus.net" name="http://docs.scribus.net">http://docs.scribus.net</a> are meant to address your concerns.</p>
+
+</p>
+<a>Direct Link: <a href="http://docs.scribus.net/content/en/pdfs/pre-press.pdf">http://docs.scribus.net/content/en/pdfs/pre-press.pdf</a></p>
+<p>This is currently an updated working draft, but it has much relevant information on Scribus created PDFs. This will updated with more information and test results as we have more information on hand.</p>
+<p>Moreover, members of the Scribus Team offer commercial support for printers, pre-press bureaus and other institutions who are implementing Scribus in their production. You can contact them at <a href="http://scribus.biz">http://scribus.biz</a></p>
+</body>
+</html>
/Scribus/doc/en/prepress.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/importhints3.html
===================================================================
--- Scribus/doc/en/importhints3.html (nonexistent)
+++ Scribus/doc/en/importhints3.html (revision 13527)
@@ -0,0 +1,60 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus and OpenOffice.org</title>
+</head>
+<body>
+<h2>Scribus and OpenOffice.org</h2>
+<h4>Overview</h4>
+<p>The open and XML based file formats (.sxw and .odt etc.) used by OpenOffice.org in all versions, share some common traits with Scribus. The clear documentation and specs have helped the Scribus Team to create very useful import features. Expect more enhancements in the future. One of the pleasant surprises to see in the OpenOffice.org version 2 releases is the improved EPS exporter. The 1.1.x version sometimes had difficulties exporting correctly. The exporter in V 2.x in testing here seems to create better, more conformant files, which Scribus imports with little difficulties. Except for OpenOffice.org Writer files, the magic trick to get high quality imports into Scribus depends on using OO.org Draw. Almost any type of OpenOffice.org file can be imported into Scribus with high fidelity, provided you export from Draw as EPS. Native Draw files can usually be imported directly into Scribus. </p>
+<h4>Importing from OpenOffice.org Writer</h4>
+<p>The importer for Writer imports <strong>only</strong> the text contained in your document. Images and drawings need to be saved separately outside of the Writer document and then each drawing or image is then imported individually. Thus, a compound Writer document with tables of charts will not import the tables or charts. Tables, charts or other embedded objects, need to be placed into their own Draw file and exported by the methods described below.</p>
+<p>The singular most important issue to take into consideration for hassle free OO.org Writer import is well chosen usage and correctly applying styles in OO.org. Doing so will greatly reduce the amount of time needed within Scribus to format and style text. Any special paragraph styles in your Writer file will automatically be imported into your existing Scribus document.</p>
+<h4>Step by Step:</h4>
+<ul>
+<li>Select the text frame.</li>
+<li>Right Click > Get Text.. </li>
+<li>Select your OO.org document. The importer is smart enough to know recognize the type of OO.org file.</li>
+ </ul>
+
+<p>This will import <strong>all</strong> the text in your document, so ensure there is enough space in your frames or link extra text frames on subsequent pages. You can comfortably import 10, 20 or even 50 pages of text in one go. In testing the importer we have imported 600 pages. However, the practical limit is probably not more than a chapter's (15&#8211;30 pages) worth of text for performance reasons.</p>
+
+<p> When importing text from OO.org there are three important options which need to be carefully considered:</p>
+
+<table width="100%"><tr><td align="center"><img src="images/oogettext1.png" alt="Import Options for OO.org Writer and OASIS (Open Document) files." align="middle" title="Import Options for OO.org Writer and OASIS (Open Document) files." /></td></tr></table>
+
+<ul>
+ <li><strong>Update Paragraph Styles</strong> This option will tell Scribus to change the formatting of any created styles in your Scribus document to follow those in the OO.org document. </li>
+ <li><strong>Merge Paragraph Styles</strong> This option looks at the actual attributes (fonts, size) of the OO.org and merges style which have common attributes. This can help to eliminate differently named, but similar styles.</li>
+ <li><strong>Use Document Name as a prefix for paragraph styles </strong> - is self-explanatory, but can be useful for sorting styles when importing from several documents. </li>
+<li><strong>Do Not Ask Again</strong> - <strong>Caution</strong> This last option will make this permanent until you completely remove your preferences files. This will be fixed in a future release. <!--reset it in File &#062; Preferences &#062; permanent these options.--></li>
+ </ul>
+
+
+
+<h4>Importing Charts and Tables from Calc </h4>
+<p>This is a special case which needs to be done carefully. After you have created your Chart or Table in Calc, then <strong>Copy > Paste Special </strong> and embed the chart <strong>not</strong> as a GDI image, but as a linked object into a Draw Document, like below:</p>
+
+<table width="100%"><tr><td align="center"><img src="images/oochart.png" alt="Embedding a Chart in to OO.org Draw" align="middle" title="Embedding a Chart in to OO.org Draw" /></td></tr></table>
+
+<p>After placing the linked object, import using one of the two methods below.</p>
+
+<h4>Importing Native OO.org Draw Files</h4>
+<p>There are two methods: First is to use the native importer. For most drawings this works very well and I have tested very complex Draw files which imported flawlessly. In some cases, especially with gradients, it may be preferable to test exporting EPS, with the settings further down. The second method is to export EPS from OO.org. You should test both methods of export for best quality not only on screen, but by exporting a PDF and then zooming with Adobe Acrobat Reader is a recommended quality check.</p>
+
+<ul>
+ <li> It is important to note Draw 3D objects do not export well, as they are limited to screen resolution. They do not print well in most cases and will appear pixellated at print resolutions. </li>
+ <li>Not all shapes in OO.org Draw 2.x are supported. Contours and callouts do not currently work natively. The workaround is to go <strong>Edit > Select All</strong> in Draw and then right click the selection, then choose <strong>Convert to Curves or Convert to Polygons</strong> depending on the kind of content.</li>
+ <li>Most curves, polygons and bezier shapes are imported without issues. The same applies for star shapes, ellipses and markers - a type of line with arrows. </li>
+ <li>Text effects should be avoided in preference to doing them natively in Scribus which has very versatile text effects. </li>
+ </ul>
+
+<h4>Importing Formulas</h4>
+<p>The most reliable way I have found is to save your formula as desired and Close Math. Then open OO.org Draw and create a new file. Then, <strong>Insert Object > Formula</strong>. You will have a tiny embedded square on Draw's canvas. Then, right click the embedded object > <strong>Edit Object</strong>. Then, Draw will launch Math. In Math, select <strong>Tools > Import Formula</strong> and browse to your saved formula. Then save to close the file and the embedded formula is now scalable in Draw with the context menus. Save this Draw file, then export as EPS and import into Scribus. The formulas and text will import as a grouped objects as scalable vector items. Any text is imported as outlines as well. This will result in formulas which will print with <strong>very</strong> high quality and little worries when exported as PDF. Saving the Draw file and attempting to import the Draw file with embedded objects will fail, as Scribus cannot access those object directly.</p>
+<h4>Export Settings from OO.org Draw</h4>
+<p>Below are the recommended EPS export settings for all versions of OO.org Draw.</p>
+<table width="100%"><tr><td align="center"><img src="images/ooeps1.png" alt="Recommended EPS Export Settings" align="middle" title="Recommended EPS Export Settings" /></td></tr></table>
+
+<p>Using the settings above and a recent Ghostscript (8.50+), I have encountered only minor difficulties importing files from OpenOffice.org. Even then, ungrouping the import and minor touching up is easily done. The most noticeable issue I have found is some lines on charts or freehand lines are too thin when viewed as imported EPS in Scribus and a quick adjustment of the size of the line with the Properties Palette sets things right.</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/importhints3.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/cms3.html
===================================================================
--- Scribus/doc/en/cms3.html (nonexistent)
+++ Scribus/doc/en/cms3.html (revision 13527)
@@ -0,0 +1,39 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Color management with Scribus, an Introduction Part 3</title>
+</head>
+<body>
+<h2>Color management with Scribus, an Introduction Part 3</h2>
+<p ><strong>Rendering Intents</strong></p>
+
+<p>The other puzzler for newcomers to color management is <strong><em>rendering intents</em></strong>. Your choice of rendering intents is a way of telling littlecms how you want colors mapped from one color space to another.</p>
+
+<p><strong>Perceptual</strong> - This rendering intent maps color "smoothly", preserving relationships between similar colors. This prevents "gamut clipping" with its potential loss of detail and "tonal banding" problems. Gamut "clipping" happens when two or more colors that are different in the input image appear the same when printed. Perceptual rendering intent makes small adjustments throughout the image to preserve color relationships. It sacrifices some precision of colors in order to ensure pleasing results. For photographic images and scans, this is usually the best choice for a default setting.</p>
+
+<p>Perceptual intent will produce the most predictable results when printing from a wide range of image sources, for example, when printing RGB images on CMYK devices, or when trying to match CMYK devices that are radically different from each other. Consider this "foolproof" setting to be best for users who handle the wide variety of images that commonly enter large format printing facilities.</p>
+
+<p><strong>Saturation</strong> stands for logos, spot colors, etc. It tends to preserve the amount of, or vividness of colors. But it can make photos look ugly. If you were working with logos with a specific shade, saturation will bring better color matching, as far as you give more importance to the color than to the image.</p>
+
+<p><strong>Absolute Colorimetric: </strong>When a color is not printable within the "gamut "of the output device, this rendering intent simply prints the closest match. It reproduces in-gamut colors without compromise, as faithfully as possible. This produces the most accurate matching of spot colors. Unfortunately, it can also result in "gamut clipping" where two colors that are different in the original are identical on the print. White points are similarly clipped, then causing color relationship problems in the highlights of images. This type of clipping, and the resultant problems, typically make this rendering difficult to use with anything but <!--<a href="./lcms/spot.html">-->spot colors<!--</a>-->. Some users will be disconcerted with a yellowish cast in their image, but this
+ intent is measured in highly controlled lighting conditions with a D50 light box. This often has a "warmer" temperature than more typical viewing conditions. This rendering intent is almost exclusively used when a corporate logo or color must be matched exactly regardless of media. Kodak yellow would be a good example.</p>
+
+<p><strong>Relative Colorimetric:</strong> When a color is not printable within the gamut of the output device, this rendering intent prints the closest match along with an adjustment that maps white to the paper of the output. This mapping of "white point" prevents the problems of "Absolute Colorimetric" with images that will not be printed with spot colors. When producing color proofs on RGB ink jet printers, while simulating CMYK printing presses you can use this intent, if you know the intended precise profile. Users of Adobe Press Ready will understand this concept quite well. This approach works well when you have accurate embedded profiles in images being converted to CMYK space with printer profiles that have been very precisely profiled with color measurement devices. These are typically scanner or more rarely in digital cameras, and is most likely when someone has spent a lot of time and effort to finely calibrate and profile their equipment. It takes sophisticated ($$$) color calibration equipment to measure the printer under fairly well controlled conditions.</p>
+
+<h4>Other CMS Options</h4>
+
+
+
+<p><strong>Mark Colors Out of Gamut</strong> is a setting which will show colors in your document which may be outside the gamut, or printable color range of your printer. Note, this is only a warning, as the current ICC specs do not define this uniformly. This is a function available from littlecms.</p>
+
+<p><strong></strong></p>
+
+<h4>Final Printing with Scribus</h4>
+
+<p>For Scribus users, there are a couple of options for printing with a color managed intent.</p>
+
+<p>When printing, Scribus can optionally apply the printing profile you have chosen in the color management panel. This can be very useful, if you want to simulate a commercial printer profile with your ink-jet printer via CUPS. </p>
+
+<p>PostScript Output - This would require having your images tagged before being placed in Scribus files when outputting a Scribus document either: as pure postscript or as individual EPS files. Scribus uses level 3 postscript.Level 2 and Level 3 postscript can read and use icc profiles within an image. Most color postscript devices will read the embedded profiles and use them to render color within the postscript using something called a rendering dictionary.</p>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/cms3.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scripterapi-ImageExport.html
===================================================================
--- Scribus/doc/en/scripterapi-ImageExport.html (nonexistent)
+++ Scribus/doc/en/scripterapi-ImageExport.html (revision 13527)
@@ -0,0 +1,65 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Python: class ImageExport</title>
+</head>
+<body>
+<h2>Python: class ImageExport</h2>
+<p>
+<a name="ImageExport">class <strong>ImageExport</strong></a>(object)
+</p>
+<hr />
+
+<h2>Image export</h2>
+<p>Class ImageExport() provides the bitmap graphics exporting for Python scripting as you know it from Export/Save as Image menu. See related class PDFfile() and procedure savePageAsEPS().</p>
+<p>Example:<br/>
+<code>
+i = ImageExport()<br/>
+i.type = 'PNG' # select one from i.allTypes list<br/>
+i.scale = 200 # I want to have 200%<br/>
+i.name = '/home/subik/test.png'<br/>
+i.save()<br/>
+</p>
+<p>Last two lines should be replaced with: <code>i.saveAs('/home/subik/test.png')</code></p>
+
+<h3>Methods defined here</h3>
+
+<dl>
+ <dt><strong>__init__(...)</strong></strong></dt>
+ <dd><p>x.__init__(...) initializes x; see x.__class__.__doc__ for signature</p></dd>
+
+ <dt><strong>save(...)</strong></dt>
+ <dd>save() -> boolean
+ <p>Saves image under previously set 'name'.</p></dd>
+
+ <dt><strong>saveAs(...)</strong></dt>
+ <dd>saveAs('filename') -> boolean
+ <p>Saves image as 'filename'.</p></dd>
+</dl>
+
+<h3>Data and other attributes defined here</h3>
+
+<dl>
+ <dt><strong>__new__ = &lt;built-in method __new__ of type object&gt;</strong></dt>
+ <dd><p>T.__new__(S, ...) -> a new object with type S, a subtype of T</p></dd>
+
+ <dt><strong>allTypes = &lt;attribute 'allTypes' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>Available types. Read only list of strings.</p></dd>
+
+ <dt><strong>dpi = &lt;member 'dpi' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>This value will be used for export as DPI. Read/write integer.</p></dd>
+
+ <dt><strong>name = &lt;attribute 'name' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>Filename of the image. With or without path. Read/write string.</p></dd>
+
+ <dt><strong>quality = &lt;member 'quality' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>Quality/compression: minimum 1 (poor), maximum 100 (qaulity). Read/write integer.</p></dd>
+
+ <dt><strong>scale = &lt;member 'scale' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>This is the scaling of the image. 100 = 100% etc. Read/write iteger.</p></dd>
+
+ <dt><strong>type = &lt;attribute 'type' of 'ImageExport' objects&gt;</strong></dt>
+ <dd><p>Bitmap type. See allTypes list for more info. Read/write string.</p></dd>
+
+</body>
+</html>
/Scribus/doc/en/scripterapi-ImageExport.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/scribus-svg.html
===================================================================
--- Scribus/doc/en/scribus-svg.html (nonexistent)
+++ Scribus/doc/en/scribus-svg.html (revision 13527)
@@ -0,0 +1,57 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus SVG Import/Export</title>
+</head>
+<body>
+<h2>Scribus SVG Import/Export</h2>
+<p>Scribus includes SVG import/export plug-ins, which enables you to export Scribus pages or objects as SVG. The import plug-in allows you to import SVG drawings and documents from illustration programs like Inkscape, Skencil and Adobe Illustrator.</p>
+<p>These plug-ins have the capability to import and export SVG 1.0/1.1 standards 2D graphics primitives and text, which can then be displayed in web browsers with SVG capability, within SVG viewers or further edited with SVG capable vector editors, like Skencil, Inkscape or Adobe Illustrator.
+</p>
+<h4>Exporting using the Plug-in:</h4>
+<p>Export the whole page is simply have the page you want to be exported open, and use <strong>File > Export > Export Page as SVG..</strong></p>
+<h4>Importing using the Plug-in:</h4>
+<p>Go <strong>File..>Import SVG Image</strong> When you import an SVG image or drawing, it will appear like an object from the Scrapbook. Drag the cursor where you want to place the SVG image. </p>
+
+<h4>SVG Importing Hints:</h4>
+<p>Scribus can handle most of the SVG features which can be created in Inkscape and Sketch, two well known vector drawing programs for Linux. The biggest issue I have observed is sometimes the paths when interpreted do not show up as closed. So parts of the SVG file look empty upon import. The simple fix is to ungroup the elements and then select the empty looking objects, then double click to bring up the editing palette for drawing objects and click on the close path button. Typically, then the invisible object will appear.</p>
+<p>I <strong>strongly recommend against</strong> creating special text effects in SVG, unless a: It cannot be done in Scribus and Scribus has very versatile text effect tools. b: The text effects are converted to outlines before importation. Why ? Scribus uses a PostScript model for handling fonts and text, where SVG uses a model much like html. In the case where you need to create them in another program, converting the text to outlines will be far more satisfactory.</p>
+
+<h3>Scribus - SVG Q and A</h3>
+<h4>What is an SVG?</h4>
+<p>SVG (Scalable Vector Graphics) is a W3C recommended standard for vector graphics like line drawings, maps and logos. </p>
+<h4>Why add SVG Export to Scribus?</h4>
+<p>Increasingly, Scribus has more sophisticated drawing tools, which are both familiar and easy to use. End users might like to use Scribus created objects in other applications like web design. Many other applications can import SVG and export an SVG object into other file formats. This also makes it easy for your print and web objects to be created from the same source.</p>
+<h4>What features can I export with the plug-in?</h4>
+<p>Basic 2D graphics and text. Text on a path works sometimes with other applications, sometimes not. Adobe Illustrator and Inkscape (increasingly) both do a good job of importing Scribus SVG. Almost all features in a Scribus doc can be exported as SVG. Images within a page are converted to PNG. The Amaya Web browser will also display Scribus SVG. More and more browsers have native SVG rendering built in.</p>
+<h4>What features are not supported</h4>
+<p>The current version of the SVG-Import Plug-in has the following limitations:</p>
+<ol>
+ <li>Text isn't supported fully yet.</li>
+ <li>Not all gradient styles are fully supported.</li>
+ <li>No support for masking and clipping</li>
+ <li>Embedded SVG-Images aren't supported.</li>
+ <li>The SVG should be well formed, with all tags and structures should be correct. Corrupted SVGs could crash the plug-in.</li>
+ <li>Animations, multi-media and "extensions" or proprietary tags within SVG, which can only be viewed with certain viewers.</li>
+</ol>
+
+<h4>Why SVG?</h4>
+<p>SVG as a file format has many advantages:</p>
+<ul>
+ <li>Easy to implement. The SVG file format is based on XML and has many similarities to Scribus' native file format.</li>
+ <li>SVG is a scalable vector graphics, so graphics do not become pixellated when zoomed.</li>
+ <li>They are in XML format, text based and quick to load - much smaller than bitmap images. A typical SVG file is under 10k.</li>
+ <li>SVG is an open XML-based standard from the W3 consortium</li>
+ <li>It is platform neutral</li>
+ <li>Can be scripted for user interaction and control. Also has support for ICC color spaces so color display accurately, even within a browser.</li>
+ <li>SVG can also be color managed and supports a well defined way to specify ICC profiles.</li>
+</ul>
+
+<h4>What about browser support?</h4>
+<p>Firefox 1.5+, Konqueror 3.4.0+, Opera and Safari support SVG natively.</p>
+<h4>Where can I learn more?</h4>
+<p><a href="http://www.svgx.org/">SVG Foundation</a> has a wealth of links and news.</p><p>Other links are listed in the <a href="http://www.scribus.net/index.php?name=Web_Links&req=viewlink&cid=7">Links page</a></p>
+<h4>A Scribus page displayed in a browser:</strong></h4>
+<table width="100%"><tr><td align="center"><img src="images/svg1.png" title="Scribus Page Exported as SVG in Browser" alt="Scribus Page Exported as SVG in Browser" /></td></tr></table>
+</body>
+</html>
\ No newline at end of file
/Scribus/doc/en/scribus-svg.html
Property changes:
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+Author Date Id Revision
\ No newline at end of property
Index: Scribus/doc/en/codingstandards.html
===================================================================
--- Scribus/doc/en/codingstandards.html (nonexistent)
+++ Scribus/doc/en/codingstandards.html (revision 13527)
@@ -0,0 +1,433 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Coding Standards</title>
+</head>
+<body>
+<h2>Scribus Coding Standards</h2>
+
+<p>
+Initial document: Paul F. Johnson, 26 Feb. 2004, Version: 0.04<br/>
+Revised: Craig Ringer, 16 Aug. 2005, Version: 0.05 (text encodings, exceptions, who to send patches to)<br />
+Revised: Peter Linnell, 06 Sept. 2005, Version: 0.06 (more text encodings stuff from recent discussions)</p>
+
+<p>This document is intended as a guide to all Scribus developers and contributors. It is aimed to be simple to use, as well as to keep the source code simple to understand and maintain.</p>
+
+<h3>Code Documentation</h3>
+
+<p>All code should be documented clearly.</p>
+
+<p>Prior to any method, the following should be there</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+/*!
+ \fn functionName::functionName()
+ \author Authors Name
+ \date
+ \brief Constructor for class
+ \param None
+ \retval None
+ */
+</pre>
+</td></tr></table></blockquote>
+
+<p>There should be something similar prior to the class definitions.</p>
+
+<p>In preference, all details should be in English. This includes comments.</p>
+
+<p>Unless a comment occupies a single line, <code>//</code> should be used in preference to <code>/* */</code></p>
+
+<h3>Code</h3>
+
+<h4>Variable naming conventions</h4>
+<p>All variables should begin in lower case letters. If the variable has more than one part to it, then the second part should begin in a capital letter. For example <code>int foo</code> and <code>int fooBar</code>. </p>
+<p>Variables should be clear in their naming. The exception to this is in a for loop. In preference, these should be in English. We are in the process of converting and altering the current ones to fit in with this.</p>
+<p>Any temporary variables (such as those used in a <code>for</code> loop or those only used within a scope), should only be declared where they are needed and not used in a global scope. If there is a condition at the start of a method, any variables required should be declared, but nothing else. For example</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+void foo::bar(f *b)
+{
+ int j;
+ string g = b-&gt;passed_in;
+ double fg, m, c;
+ which_string(g, &amp;j);
+ if (j == true)
+ return;
+ // rest of the code
+}
+</pre>
+</td></tr></table></blockquote>
+<p>should not have the double variables declared. It is arguable if g should be declared, but in this example, it doesn't matter.</p>
+
+<p>If a variable is not required, don't create it. In the example above, there is no requirement for g to be used.</p>
+
+<h4>Tabbing convention</h4>
+<ol>
+ <li>
+ <p>In class definitions</p>
+ <p>With the exception of the access declarations, a single tab should be used prior to all method and variable definitions. There should be no tabs prior to access declarations. There is a tab prior to <code>Q_Object</code>.</p>
+ </li>
+ <li>
+ <p>In the main code</p>
+ <p>There should be a tab at the start of every line. With any conditional line, there should be an opening brace by itself. On the next line down, there should be another tab prior to any code. The close brace should be underneath the open brace.</p>
+ </li>
+</ol>
+
+<h4>Conditionals</h4>
+<p>Always make a conditional logical. This may sound silly, but look at the following example</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+int foobar(bool m)
+{
+ if (m == true)
+ {
+ somethingA(1);
+ somethingB(1);
+ somethingC(1);
+ }
+ else
+ {
+ somethingA(0);
+ somethingB(0);
+ somethingC(0);
+ }
+}
+</pre>
+</td></tr></table></blockquote>
+
+<p>This can be re-written to make things clearer</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+int foobar(bool m)
+{
+ int c = m == true ? 1 : 0;
+ somethingA(c);
+ somethingB(c);
+ somethingC(c);
+}
+</pre>
+</td></tr></table></blockquote>
+<p>A lot simpler to see and will usually optimize far better.</p>
+
+<p>Ternary conditionals (?) should be used in preference to <code>if</code> / <code>else</code>. These are usually far quicker to process the code once compiled.</p>
+
+<p>Depending on what is being performed, switch statements should be avoided. There is usually a simpler way to avoid them. For example</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+int b;
+string s;
+switch (f)
+{
+ case 1 :
+ b = 4;
+ s = "four";
+ break;
+ case 2 :
+ b = 8;
+ s = "eight";
+ break;
+ case 3 :
+ b = 12;
+ s = "twelve";
+}
+</pre>
+</td></tr></table></blockquote>
+<p>can be re-written as</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+int b = f * 4;
+char *number[] = {"four", "eight", "twelve"};
+size_t no = sizeof(number) / sizeof(*number);
+s = number(f);
+</pre>
+</td></tr></table></blockquote>
+<p>The switch has gone and the code generated runs far faster and as the conditions don't need to be created, will optimize far better. Note: when using the <code>QObject::tr()</code> function, this method of using char* may not always work properly. An alternative is to use <code>QString number[] = {"four", "eight", "twelve"};</code> etc.
+
+<p>Obviously for more complex switch conditions, the above can't be used.</p>
+
+<h4>Conditionals formatting</h4>
+
+<p>Formatting should look like this:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+if (fred == 5)
+{
+ // something
+ // something
+}
+</pre>
+</td></tr></table></blockquote>
+<p>Switch formatting should look like this:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+switch (f)
+{
+ case 0:
+ if (fred == 1)
+ {
+ // something
+ // more
+ // ok
+ }
+ else
+ {
+ if (jimmy == 0)
+ {
+ // hi
+ // code
+ }
+ // something here
+ }
+ break;
+}
+</pre>
+</td></tr></table></blockquote>
+<p>Simple to read and simple to see where the conditional ends.</p>
+<p>Under NO circumstances should you have a line such as:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+if (foo == bar) { somethingA(0); }
+</pre>
+</td></tr></table></blockquote>
+<p>This should be written as:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+if (foo == bar)
+ somethingA(0);
+</pre>
+</td></tr></table></blockquote>
+<p>If braces are not required, don't use them. For example, braces wouldn't be needed here</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+for (int j = 0; j &lt; 10; ++j)
+ cout &lt;&lt; j &lt;&lt; &quot;\n&quot;?;
+</pre>
+</td></tr></table></blockquote>
+<h4>Pre or post increments</h4>
+
+<p>In for loops, preincrements should be used (++a rather than a++). Under ARM processors and x64 processors (not sure about ia64) ++a requires half the number of clock cycles than the post processor style. In some circumstances, ++a is far more efficient under ia32. It is even more efficient when used with iterators. Post increments should be used in the following sort of code:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+if (b == true)
+{
+ m-&gt;wibble(c);
+ m-&gt;wobble(c++);
+}
+</pre>
+</td></tr></table></blockquote>
+
+<h4>Spacings</h4>
+<p>There should be a space after:</p>
+<ul>
+ <li>All commas and semi-colons (in a for condition)</li>
+ <li>Between any conditional (<code>if (a == true)</code> - there is a space either side of the <code>==</code> conditional)</li>
+ <li><p>Prior to an open bracket or after a close bracket:</p>
+ <ul>
+ <li>A space should not be used immediately inside or at the end of a bracket</li>
+ <li>Do not use spaces at the beginning of lines. You must use a tab. A tab will always be a finite number of spaces, the number of spaces can vary when hand inputted.</li>
+ </ul>
+ </li>
+</ul>
+
+<h4>Use of templates</h4>
+
+<p>Templates for both types and classes are fine to be used. The project recommends using g++ 3.x which fully support templates and template classes. Please remember the overhead involved in using templates!</p>
+<p>When using templates, please remember the following:</p>
+<ul>
+ <li>The final binary will be larger</li>
+ <li>To use them correctly. It is very easy to say "I can just whizz that over to a template" when actually, it would be far better to construct (say) a generic template class which inherits the base Qt classes in question.</li>
+ <li>In some places, a template will not be as efficient as a standalone call.</li>
+</ul>
+
+<h4>Optimization</h4>
+
+<p>Unless you really know what you're doing and more over, what the code is doing, do not attempt to do any code optimization. In a lot of respects, optimization is a "black art".</p>
+<p>Code such as <code>a = b = c = 0;</code> is more efficient (through the compiler) than <code>a=0; b=0; c=0;</code></p>
+<p>Careful thought about how the code works is usually far more beneficial than attempting any of the "tricks" currently employed.</p>
+<p>Any large scale changes should be approved of first. Sometimes a small change can have large side effects.</p>
+<p>Multiple separate lines containing calls to Qt methods are far less efficient than multiple calls contained in a for loop.</p>
+
+<h4>Initialization</h4>
+
+<p><code>QString fred = QString("bob")</code> is not the same as <code>QString fred("bob")</code>. The first one creates an additional temporary that's then thrown away. That's slow, and should generally be avoided.</p>
+
+<p>In constructors, it is somewhat faster to use:</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+Fred::Fred() : ParentClass(),
+ argument1("initialValue"),
+ argument2(INITIAL_VALUE)
+{
+}
+</td></tr></table></blockquote>
+
+<p>than</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+Fred::Fred() : ParentClass()
+{
+ argument1 = "initialvalue";
+ argument2 = INITIAL_VALUE;
+}
+</td></tr></table></blockquote>
+
+<p>for much the same reasons as outlined above. It's best to initialize the members in the same order that they're listed in the class declaration.</p>
+
+<h4>Memory checking</h4>
+
+<p>Due to the unavailability of exceptions (see below), we're using <code>Q_CHECK_PTR</code> to check allocations. This means that you get an abort with a useful message when an allocation fails, rather than an unexplained segfault.<p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+int *m = new int[2048];
+Q_CHECK_PTR(m);
+</td></tr></table></blockquote>
+
+<h5>Exceptions</h5>
+
+<p>All calls to <code>new</code> should ideally be trapped. This is not currently implemented in current releases. The preferred method would be:</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+#include &lt;new&gt;
+
+try
+{
+ m = new int[2048];
+}
+
+catch(bad_exception)
+{
+ cout &lt;&lt; "memory allocation to m failed - &lt;method name&lt;" &lt;&lt; endl;
+ exit(EXIT_FAILURE);
+}
+</pre>
+</td></tr></table></blockquote>
+<p>As there are many calls in Scribus to new, these will have a wrapper around.</p>
+<p>For users of Qt who compile their own, they will need to include in the <code>./configure</code> script that they want to throw C++ exceptions. Failure to do so will result in the catches not catching and possibly Scribus failing to run.</p>
+<p>Currently (for v3.2 - v3.4), KDE recommend Qt is compiled without exceptions. This is a bad idea as it means trapping bad memory allocations cannot be caught using the preferred method. As most distributions follow this recommendation, that means we (Scribus) can't expect to be able to rely on exceptions.</p>
+
+<h4>Text encodings</h4>
+
+<p>Text encodings need to be handled carefully. Strange errors can result if you treat UTF-8 text as latin-1, for example. These issues are often hard to track down, so careful coding is important. A detailed treatment of text encodings won't fit here, but some information will be provided elsewhere in the documentation. This is an early version of this part of the text; feedback would be appreciated.</p>
+
+<p>The first thing you need to understand is that Qt's <code>QString</code>, and most other Qt classes, know their own encoding and take care of text encoding issues for you, so they can be treated as "just text" when passing them around inside Scribus and to other Qt classes. It's only at the interfaces between byte-oriented and "text"-oriented code that care is required. These interfaces can be tricky to spot (the implicit conversion of a <code>QString</code> to a <code>QCString</code> or <code>char*</code>, for example, is easily missed) so caution and careful reading of API documentation is required.</p>
+
+<p>While there is no real substitute for <i>understanding</i> text encodings, some of the most important rules to follow are:</p>
+
+<p>Always construct a <code>QString</code> from a byte string using one of the <code>QString::fromblah(...)</code> methods. You should never use <code>QString(char*)</code> or <code>QString(QCString)</code>. You need to determine what encoding the byte string you're working with is in and use the correct call, by examining the documentation for the system / library you are calling. There is generally no way to tell what encoding a string is in by examining the string - at best this is guesswork. <b>Do not</b> assume a string is utf-8 or latin-1, since even if it works for you, in some locales it will not. For data read from the OS or C libraries, you generally want <code>QString::fromLocal8Bit(...)</code>. If in doubt, ask somebody.</p>
+
+<p>Similarly, you should always use the appropriate <code>QString</code> conversion methods when converting <code>QString</code>s to byte strings (e.g. <code>QCString</code>, <code>QByteArray</code>, or <code>char*</code>). Note that such conversions may happen automatically, so watch out for implicit conversions. If sending data to system calls or C libraries you'll generally want <code>QString::local8Bit()</code> but you should check to confirm that's correct for the specific call you're making. Some win32 calls, for example, expect UCS-2 (wchar) data, and some C libraries will expect UTF-8 strings to be passed to some methods.</p>
+
+<p>You should absolutely never do this:</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+QString blah = anotherQString.utf8();
+</td></tr></table></blockquote>
+
+<p>The above code:</p>
+<ul>
+ <li>Converts anotherQString from its internal UCS-2 encoding to a UTF-8 byte string stored in a <code>QCString</code>; then</li>
+ <li>Passes it to the <code>QString(QCString)</code> constructor for blah;</li>
+ <li><code>QString(QCString)</code> decodes the passed <code>QCString</code> <i>according to the default byte string locale set in qt</i> which is usually latin-1 (don't rely on that; it should change to depend on locale at some point.).</li>
+</ul>
+
+<p>Thus, you end up doing a lot of pointless work encoding and decoding the string, and to top it off probably mangle it by decoding a utf-8 string as latin-1. You usually won't notice this, because you probably only send ASCII data thorough, and thus the bug will only turn up much later from people in other locales who use other text encodings. These issues tend to be a pain to track down.</p>
+
+<p>For similar reasons, when you're reading or writing a <code>QTextStream</code>, remember to call <code>QTextStream::setEncoding(...)</code> before reading/writing any data. Use <code>operator&lt;&lt;</code> with <code>QString</code>s, but <code>WriteRawBytes(...)</code> when writing byte strings that are already in the correct encoding. Byte strings in other encodings should be converted to <code>QString</code> or transcoded using <code>QTextCodec</code>. <b>Do not</b> just assume the <code>QTextStream</code> should write out UTF-8. The correct encoding will depend on where the data is going / coming from. For example, a plain text file for the user to edit should be in their local text encoding. If you're not sure, ask someone.</p>
+
+<p>Don't convert a QString to a byte string when writing to a QTextStream - the QTextStream does that for you in operator&lt;&lt; . For example:</p>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+QTextStream ts(&amp;file);
+// In this case we know we want to write out UTF-8 to this file, not write in
+// the local 8-bit byte string encoding.
+ts.setEncoding(QTextStream::UnicodeUTF8);
+ts &lt;&lt; someQString.utf8();
+</td></tr></table></blockquote>
+
+<p>as that's the same error as in the previous example, just written a different way. Instead, you should omit the <code>.utf8()</code>.</p>
+
+<p>The best way to handle text encodings is to convert 8-bit byte strings to <code>QString</code> or another "safe" class as early as possible in input, and convert to 8-bit byte strings as late as possible on output. Above all else, do it only once and watch out for implicit conversions. You should think about encodings whenever passing text across any interface that wants byte-oriented strings rather than <code>QString</code>s. Remember to <b>read the documentation</b> of the APIs you're using to determine how they behave with text encodings, and if you're not sure, <i>ask somebody</i>.</p>
+
+<p>It is strongly recommended that you read <a href="http://doc.trolltech.com/3.3/i18n.html">http://doc.trolltech.com/3.3/i18n.html</a> for more coverage of this issue, especially the section "Support for Encodings". You should also read <a href="http://doc.trolltech.com/qq/qq05-achtung.html">Achtung! Binary and Character data</a>.</p>
+
+<h4>Translation Hints - Encoding Issues</h4>
+<p>Please use:</p>
+<pre> "&#060;qt&#062;" + tr("text for translation") + "&#060;/qt&#062;"</pre>
+<p>not this:</p>
+<pre> tr("&#060;qt&#062;text for translation&#060;/qt&#062;")</pre>
+<p>it's really annoying to translators.</p>
+
+<p>If you are writing a class which is not inherited from QObject or any Qt
+class, you cannot use inherited tr() method. If you are using something like:</p>
+<pre> QObject::tr("text for translation")</pre>
+<p>replace it with:</p>
+ <pre>QObject::tr("text for translation", "describe what is it related")</pre>
+<p>An example from the scripter:</p>
+ <pre>QObject::tr("Item is not text frame", "scripter error")</pre>
+<p>It helps translators with context and it tells them what they are
+translating too, though in some cases strings are generic in nature.</p>
+
+
+<p>There's another issue related to translations, though it's more for
+encoding correctness etc: Please don't use:</p>
+
+<pre>tr( QString("blah %1").arg(something) )</pre>
+
+or otherwise use a QString inside a tr(...) . Doing so causes an
+implicit conversion to `const char*', in which the QString converts to a
+latin-1 byte string. If some characters cannot be represented in latin-1
+they're replaced with `?' . The correct usage is:
+
+<pre>tr("blah %1","context").arg("something")</pre>
+
+<p>... exploiting the fact that tr(...) returns a QString and that you can
+chain calls to QString::arg. That avoids any implicit conversions, and
+will avoid a whole class of weird encoding bugs.</p>
+
+<p>If you really have to translate text that can't be represented in
+latin-1, you need to use <strong>QObject::trUtf8(...).</strong> If you want to translate
+a string with "Δ" (uppercase delta) in it, for example, we could try:</p>
+
+ <p> tr("Δ is %1", "context")</p>
+
+<p>but that's wrong, not portable, may not compile, or worse might have
+different results on different systems. <strong>We must use escaped byte strings
+rather than including a unicode or extended latin-1 char directly in
+source. </strong>The UTF-8 byte sequence for that character is \xce\x94, so we
+could try:</p>
+
+ <pre>tr("\xce\x94 is %1", "context")</pre>
+
+<p>but that's also wrong, as that unicode byte sequence will be interpreted
+as latin-1 and you'll get a mangled result. You must instead use:</p>
+
+ <pre> trUtf8("\xce\x94 is %1", "context")</pre>
+
+<p>Similarly, if you wanted to include the &#169; (copyright) symbol, which
+exists in latin-1 as well, you could use either:</p>
+
+ <pre>tr("something \xa9 someone", "context")</pre>
+
+<p>or</p>
+
+ <pre>trUtf8("something \xc2\xa9 someone", "context")</pre>
+
+<h4>Portability</h4>
+
+<p>Don't cast a pointer to an int, it causes portability issues where sizeof(int) != sizeof(void*). You might want to find another way to do what you're trying to achieve.</p>
+
+<h4>Submitting of patches</h4>
+
+<p>Code patches should be sent to Franz, Craig Bradney, or Peter. Documentation patches should be sent to Peter and Craig Bradney. Scripting matters should be addressed to Petr and Craig Ringer.</p>
+<p>Patches should be in plain text. <code>diff -u old_file.cpp new_file.cpp &gt;difference.diff</code> is the best way of sending them. Please do not send patches to the main list. Remember to use <code>-u</code> (unified diff) as other types of diff are painful to use.</p>
+<p>Please ensure that when you have changed someth