Subversion Repositories Scribus

Compare Revisions

Ignore whitespace Rev 17465 → Rev 17471

/trunk/Scribus/doc/it/scripter1.html
0,0 → 1,28
<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>
 
<h3>Overview</h3>
<p>This is the description how to use the scripting plug-in for Scribus. The Scripter allows you to use the powerful Python programming language as a scripting language in Scribus. This can help you to automate otherwise repetitive tasks or add new features.</p>
 
<p>Note that additions to the Scripter are being made frequently, which means that the available documentation may be incomplete.</p>
 
 
<h3>Using the Plug-in</h3>
<p>Scribus is being shipped with some &ldquo;hard-wired&rdquo; scripts, which are available via <i>Scripter&nbsp;&gt; Scribus Scripts</i>:</p>
 
<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>There are some simple example scripts in the subdirectory &ldquo;samples.&rdquo; Its location depends on the operating system you use, e.g. <code>/usr/local/share/scribus</code> or <code>/usr/share/scribus</code> on Linux. If you have created a script which you think could be useful for others, please feel free to add it to the <a href="http://wiki.scribus.net/">Scribus Wiki</a> or paste it into an email and send it to the <a href="http://lists.scribus.info/mailman/listinfo/scribus/">Scribus mailing list</a>.</p>
 
<p>To execute an external Python script, you have to use <i>Script&nbsp;&gt; Execute Script</i>. Scribus will open a file dialog, which allows you to select a Python script (file extension: *.py). <i>Script&nbsp;&gt; Recent Scripts</i> shows a list of recently executed scripts.</p>
 
<p>You can use many Python modules with this plug-in, the only exception being scripts that expect parameters from the command Line. These won&rsquo;t work because the plug-in gives the Python interpreter an empty command line.</p>
 
<p>The menu entry <i>Script&nbsp;&gt; Show Console</i> will launch an interactive Python console, where you can execute commands directly. There is no need to use &ldquo;<code>from scribus import *</code>&rdquo;, as this has already been done. You can use all the commands listed in the following pages of the Scripter API documentation directly without any prefix.</p>
</body>
</html>
/trunk/Scribus/doc/it/print1.html
0,0 → 1,24
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Stampare con Scribus</title>
</head>
<body>
<h2>Stampare con Scribus</h2>
<p>Quando si utilizza un'applicazione avanzata per il desktop publishing come Scribus, pu&ograve; esserci qualche problema nella terminologia relativa alla stampa. La stampa potrebbe avvenire direttamente in casa o in ufficio, oppure presso un'azienda specializzata che svolge l'attivit&agrave; di stampa in modo professionale. Inoltre esiste una vasta gamma di macchine per la stampa, da piccoli apparecchi usati in casa o in ufficio, alle vere e proprie macchine tipografiche impiegate su scala industriale. Per evitare confusioni e fraintendimenti, chiameremo &ldquo;stampa locale&rdquo; la stampa per mezzo di un apparecchio da scrivania in casa o in ufficio, e &ldquo;stampa commerciale&rdquo; o &ldquo;stampa in tipografia&rdquo; quella eseguita presso un'azienda specializzata o per mezzo di una stampante di alto livello o una macchina tipografica.</p>
 
<h3>Stampa locale: alcune informazioni generali</h3>
 
<p>A prima vista pu&ograve; sembrare molto strano, ma il programma di DTP Scribus, il cui scopo principale &egrave; creare documenti destinati ad essere stampati, potrebbe non funzionare affatto con il rumoroso apparecchio che se ne sta sulla vostra scrivania, anche se il programma sembra rilevare benissimo la stampante locale attraverso le impostazioni di sistema. Questo &egrave; un problema noto. Gli sviluppatori ne sono a conoscenza, ma risolverlo &egrave; molto complicato, e, quel che &egrave; pi&ugrave; importante, vi sono facili soluzioni alternative.</p>
 
<p>Perch&eacute;, probabilmente chiederete, la stampa diretta dall'interno di Scribus &egrave; un tale problema? Le altre applicazioni stampano benissimo su tutte le piattaforme su cui Scribus &egrave; utilizzabile. La risposta breve &egrave; che i dati che Scribus genera e invia alla stampante sono pensati per una stampante PostScript di alto livello. Una macchina di questo tipo pu&ograve; essere (e probabilmente &egrave;) piuttosto costosa. La maggior parte delle stampanti per uso &ldquo;domestico&rdquo; (o i loro driver) non sono in grado di interpretare le istruzioni PostScript generate da Scribus.</p>
 
<p>Per gli utenti che hanno una formazione tecnica, e qualche conoscenza della pi&ugrave; recente storia dei computer, spieghiamo un'altra causa di potenziali problemi. Qualche decennio fa, quando i dispositivi per la stampa a prezzo contenuto erano poco pi&ugrave; che macchine per scrivere azionate dall'esterno, una nuova azienda chiamata Adobe, che in seguito sarebbe diventata uno dei giganti del settore del software, introdusse il linguaggio di descrizione pagina <a href="importhints1.html">PostScript</a>, che divenne parte integrante della &ldquo;rivoluzione del desktop publishing&rdquo;. Con il linguaggio PostScript e le stampanti compatibili con PostScript, divenne possibile stampare documenti con impaginazione elegante su macchine &ldquo;da scrivania&rdquo;, anche se le prime stampanti PostScript erano cos&igrave; costose che soltanto una piccola parte delle scrivanie ebbe mai l'onore di ospitare una macchina di questo tipo. Tra le cause che spingevano verso l'alto i costi delle stampanti PostScript vi erano i costi di licenza del linguaggio PostScript stesso e di un insieme di base di caratteri PostScript, poich&eacute; entrambi erano necessari per costruire una &ldquo;vera&rdquo; stampante PostScript. Un altro motivo era collegato all'hardware per la stampa. Questo &egrave; il punto in cui la Microsoft entr&ograve; in scena e fece ai fornitori di hardware un offerta che non potevano rifiutare. La Microsoft introdusse la cosiddetta Graphical Device Interface (GDI), che rese il PostScript largamente obsoleto (almeno per le stampanti da scrivania): essa forniva meno funzionalit&agrave; (ma nella maggior parte dei casi, sufficienti), e trasferiva una parte dell'elaborazione dei dati di stampa dalla stampante (hardware) al sistema operativo (software), che naturalmente era Windows. La possibilit&agrave; di risparmiare alcuni centesimi per macchina indusse i produttori a sviluppare stampanti da scrivania a basso costo che funzionavano solo con il sistema operativo Windows. Per gli sviluppatori di altri sistemi operativi ci vollero anni per creare un ponte tra le macchine &ldquo;GDI&rdquo; e i sistemi di stampa basati su PostScript (ad esempio in Mac&nbsp;OS&nbsp;X, Linux, *BSD, UNIX), ma non tutte le stampanti GDI sono pienamente utilizzabili con la stampa basata su PostScript (che significa, in sostanza, ogni sistema che non &egrave; Windows). Oggi molti produttori offrono driver per le loro stampanti anche per Mac&nbsp;OS&nbsp;X e Linux, oppure offrono agli sviluppatori abbastanza informazioni da permettere loro di scrivere driver funzionanti.</p>
<p>Questa digressione pu&ograve; aiutare a comprendere perch&eacute; la stampa diretta dall'interno di Scribus pu&ograve; non funzionare, ma non &egrave; una spiegazione sufficiente. Poich&eacute; l'output di Scribus &egrave; inteso per essere stampato su una &ldquo;vera&rdquo; (leggi: di alto livello) stampante PostScript, pu&ograve; non funzionare con molte altre macchine. I lettori che hanno qualche conoscenza dello standard di stampa UNIX (CUPS: Common UNIX Printing System, utilizzato da Mac&nbsp;OS&nbsp;X, Linux, *BSD, e altri), probabilmente chiederanno come ci&ograve; sia possibile, ma la risposta &egrave; che Scribus genera un output PostScript di alto livello, le cui istruzioni a volte non possono essere elaborate dai rispettivi interpreti o driver PostScript.</p>
 
<p>Tutto questo pu&ograve; suonare un po' inquietante, ma &egrave; abbastanza probabile che riuscirete a stampare direttamente sulla vostra stampante locale. Una stampante correttamente configurata in Windows probabilmente stamper&agrave; senza problemi. In Linux potrebbe funzionare bene, oppure potrebbe semplicemente richiedere un comando di stampa alternativo: vale la pena di fare qualche prova.</p>
 
<h4>Come stampare senza problemi sulla stampante locale</h4>
<p>Il modo pi&ugrave; sicuro di stampare un documento di Scribus sulla vostra stampante locale consiste nell'esportare il file di Scribus in PDF e poi stamparlo da <a href="toolbox1.html">Adobe Reader</a>. Anche se Adobe Reader ha ricevuto critiche ben meritate per quanto riguarda problemi di sicurezza, &egrave; ancora il visualizzatore PDF pi&ugrave; affidabile e funziona perfettamente con i sottosistemi di stampa di ogni moderno sistema operativo.</p>
</body>
</html>
/trunk/Scribus/doc/it/irc.html
0,0 → 1,42
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>IRC di Scribus</title>
</head>
<body>
<h2>IRC di Scribus</h2>
 
Per entrare nel canale IRC di Scribus (link cliccabile): <a href="irc://irc.freenode.net/#scribus">irc://irc.freenode.net/#scribus</a>
 
<h4>Alcuni consigli</h4>
<p>La comunit&agrave; di Scribus ha una presenza online in &ldquo;tempo reale&rdquo;: IRC o Internet Relay Chat. Per alcuni utenti questo potrebbe essere un mezzo poco familiare per ottenere assistenza, ma secondo noi funziona veramente bene. Di solito &egrave; presente almeno un membro del team di Scribus o un utente esperto. L'orario migliore per servirsi di IRC &egrave; l'ora dell'Europa centrale, e soprattutto la sera il canale di Scribus tende ad essere pi&ugrave; frequentato. IRC &egrave; a volte considerato un luogo di discussioni accese e persino di insulti e scortesie, ma #scribus (il simbolo &lsquo;#&rsquo; indica il nome del canale) ha un ambiente piacevole e amichevole. Scambi di insulti e provocazioni non sono tollerati in #scribus. Ecco una buona introduzione (in inglese) su come comportarsi: <a href="http://blog.fnmueller.de/2008/02/23/rules-of-engagement-the-ten-commandments-of-irc">Rules of Engagement - The ten commandments of IRC</a>; ed eccone una in italiano: <a href="http://www.irchelp.it/?modulo=policies&sez=netiquette">IRCHelp.it: Policies - Netiquette</a>.</p>
 
<h4>Non siate timidi, chiedete!</h4>
<p>Quando accedete per la prima volta, dite &lsquo;hi&rsquo; (&lsquo;ciao&rsquo;) e fate la vostra domanda: #scribus &egrave; un luogo amichevole. Una breve presentazione sar&agrave; ben accetta. Se non parlate inglese, non temete: dovreste prima tentare in inglese, ma in #scribus vi sono parecchie persone che parlano lingue diverse. Anche nel Team, sono almeno sette le lingue conosciute abbastanza bene per conversare in IRC. Altri frequentatori regolari probabilmente ne coprono un'altra mezza dozzina.</p>
 
<h4>Fornite dettagli</h4>
<p>&Egrave; utile dire di pi&ugrave; che &ldquo;Ho un problema con una certa cosa che non funziona.&rdquo;</p>
<ul>
<li>per cominciare, dovreste dire su quale piattaforma usate Scribus e con quale versione di Qt: questo &egrave; sempre utile. Certi problemi riguardano specifiche piattaforme o distribuzioni.</li>
<li>descrivete il vostro problema in modo che per gli altri sia facile rispondere.</li>
<li>siate pronti a rispondere a domande su quali versioni di determinate applicazioni sono installate sul vostro computer.</li></ul>
 
<h4>Siate pazienti</h4>
<p>Il pregio di IRC &egrave; la comunicazione diretta &ldquo;all'istante&rdquo;, ma a volte gli utenti sono impegnati in altre attivit&agrave;, come programmare Scribus :-). Su IRC, spesso gli utenti abituali e gli sviluppatori sono collegati 24 ore al giorno, ma potrebbero essere lontani dal computer. Ci&ograve; non significa che dovete aspettare giorni per avere una risposta. Inoltre, #scribus ha un amichevole bot il cui nome &egrave; mrscribe, che pu&ograve; facilmente ritrasmettere i messaggi: potete fare conoscenza con lui pi&ugrave; avanti in questa pagina.</p>
 
<h4>IRC non &egrave; una scusa per non leggere la documentazione</h4>
<p>Come minimo dovreste aver gi&agrave; letto le FAQ (domande frequenti) e le parti della documentazione attinenti al vostro problema. Se qualcuno (potrebbe essere mrscribe) vi d&agrave; una risposta o un link, significa che la vostra domanda &egrave; gi&agrave; stata fatta pi&ugrave; di una volta. E significa anche che le informazioni che cercate si possono trovare facilmente altrove. Molto tempo e fatica sono stati impiegati per scrivere la documentazione, per quanto imperfetta. Ma &egrave; stata scritta per aiutare <strong>voi</strong>.</p>
 
<h4>Vi presentiamo MrScribe</h4>
<p>MrScribe &egrave; il nostro amichevole &ldquo;bot&rdquo;. I bot sono molto utili su IRC, poich&eacute; aiutano ad automatizzare certe attivit&agrave; di manutenzione. MrScribe ha anche degli aspetti divertenti, che sono utili ad aiutare gli altri. Potete scoprire tutto su MrScribe qui: <a href="http://supybot.com/">http://supybot.com/</a>.</p>
 
<h4>Alcuni consigli su client IRC</h4>
<p>Visto che sui nostri pc abbiamo client IRC in funzione 7 giorni la settimana e 24 ore al giorno, ce ne sono un paio che possiamo consigliare:</p>
<ul>
<li><a href="http://www.xchat.org">X-Chat</a> - un client maturo, basato su GTK, che funziona su Linux e Windows. La versione Windows si trova anche su <a href="http://www.psyon.org/projects/xchat-win32/">http://www.psyon.org/projects/xchat-win32/</a>. Per MacOSX: <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> - un client IRC molto stabile e completo, e facile da usare per i principianti.</li>
</ul>
 
<h4>Soffermatevi in IRC</h4>
<p>Quando arriva la risposta che aspettavate, non siete obbligati a scomparire. #scribus non &egrave; solo per esperti e sviluppatori; i principianti sono altrettanto benvenuti. &Egrave; facile riconoscere gli sviluppatori, poich&eacute; di solito hanno lo status di &ldquo;operatore&rdquo;. IRC &egrave; il luogo dove gli sviluppatori vengono a sapere se gli utenti hanno difficolt&agrave; con qualche funzione di Scribus o se c'&egrave; qualcosa di poco chiaro nell'interfaccia del programma. Soffermarsi in IRC &egrave; un buon modo di venire a sapere particolari interessanti sulle caratteristiche pi&ugrave; recenti, e buoni trucchi e consigli per l'uso dai pi&ugrave; esperti. Cos&igrave;, quando ve la sentite, accomodatevi e godetevela.</p></body>
</html>
/trunk/Scribus/doc/it/translation_howto.html
0,0 → 1,86
<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 at least technically not a very difficult one. This page outlines the requirements and procedures for creating or updating such a translation.</p>
 
<p>Please note that 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&rsquo;t really have any &ldquo;official&rdquo; 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&nbsp;...</p>
<h3>Part One: Translating the TS files</h3>
 
<h4>Requirements</h4>
<ul>
<li>The Scribus source from SVN. Please see the <a href="install1.html">Installation</a> section for details on how to checkout SVN if you aren&rsquo;t up with that yet. Its not too hard so don&rsquo;t be dismayed. By working with the SVN 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><a href="http://i18n.kde.org/tools/">Lokalize</a> or Qt4 Linguist (do <b>not</b> use Qt3 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 will be the same. For those who are new to this kind of work, Qt4 Linguist may be the tool of choice, as it offers a very simple, yet efficient user interface. Moreover, it's availabe for all platforms that are supported by Scribus (Linux/UNIX, Mac OS&nbsp;X, Windows 2000+, OS/4 Warp4 and eComStation).</li>
<li>You will need to make sure you have the <code>lupdate</code> program installed, which is a part of Qt4, or perhaps a part of the Qt4 development package, depending on your distribution.</li>
</ul>
 
<h4>Procedure for creating or updating a translation file</h4>
<ol>
<li>Check out <a href="install1.html">SVN</a>.</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 += resources/translations/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 your translation program and load the <code>resources/translations/po/scribus.en_GB.ts</code> file.</li>
<li>Perform the translations.</li>
<li>Save the <code>.ts</code> file and copy it into the source directory that contains the translation files (e.g. <code>~/Scribus/resources/translations</code>).</li>
<li>If you want to test your translation before submitting it to the Scribus developers, delete the file CMakeCache.txt in your build directory (provided you have built Scribus from source before), rerun cmake as you did before, but now add the parameter <code>-DWANT_GUI_LANG="xx_XX</code>, where xx_XX is the language code for your translation, e.g. en_GB (British English) or pt_BR (Brazilian Portuguese).</li>
<li>If you only specified your translation as a parameter, this will the only UI language available. If you have built Scribus with more than one language, select your translation in <i>File &gt; Preferences</i>.</li>
</ol>
<h3>Part Two: Translating other parts of Scribus</h3>
<p>Unfortunately or fortunately, depending on your point of view, not all parts of the Scribus user interface can be translated via ts files. In two cases you need to edit XML files to translate Scribus, namely for Templates and the Render Frame editor.</p>
<h4>Translating Templates</h4>
<p>To translate Template categories, names and decriptions, you need the file <code>template.xml</code> from the directory <code> ~/Scribus/resources/templates</code>. Save this file under a name that helps Scribus identify the language you are translating to, e.g. <code>template.it.xml</code> for Italian.</p>
<p>The content of the XML file is (hopefully) self-explanatory. There is an entry for each template. A complete entry looks like this:
<pre>
&lt;template category=&quot;<span style="color: red;">Newsletters</span>&quot;&gt;
&lt;name&gt;<span style="color: red;">TextBased</span>&lt;/name&gt;
&lt;file&gt;textbased/textbased.sla.gz&lt;/file&gt;
&lt;tnail&gt;textbased/textbasedtn.png&lt;/tnail&gt;
&lt;img&gt;textbased/textbased.png&lt;/img&gt;
&lt;psize&gt;A4&lt;/psize&gt;
&lt;color&gt;<span style="color: red;">color</span>&lt;/color&gt;
&lt;descr&gt;<span style="color: red;">A decent newsletter/magazine originaly created for one non-profit organization. Unrealized unfortunately.</span>&lt;/descr&gt;
&lt;usage&gt;<span style="color: red;">Right click on text replace what's inside with your own. Or whatever you want to... ;)</span>&lt;/usage&gt;
&lt;scribus_version&gt;1.2RC1cvs&lt;/scribus_version&gt;
&lt;date&gt;2004-07-10&lt;/date&gt;
&lt;author&gt;Petr Van&amp;#283;k&lt;/author&gt;
&lt;email&gt;petr@yarpen.cz&lt;/email&gt;
&lt;/template&gt;
</pre>
Fortunately, you need not (actually <b>must</b> not) translate everything in here. What needs a translation is only the strings that are in red in the example above.</p>
<h4>Translating the Render Frame Editor</h4>
<p>As described in <a href="renderframes.html">Working with Render Frames</a>, this kind of frame is freely configurable. Not only can you add configuration files for new programs, but you can also add translations to existing ones. In contrast to Templates, you don&rsquo;t have to create new XML files for your translations. Instead, you need to edit the existing ones. The configuration files for Render Frames are located in <code>~Scribus/resources/editorconfig</code>. There is a file for each program, e.g. <code>100_latex.xml</code> for LaTeX, <code>300_lilypond.xml</code> for Lilypond etc.</p>
<p>To make life easier for translators, the developer of the Render Frame plugin has placed an indicator for translatable text strings in the files, namely <code>i18n</code>, which is an acronym for &ldquo;internationalization&rdquo;:</p>
<pre>
&lt;title&gt;&lt;i18n&gt;
&lt;en&gt;Ranges&lt;/en&gt;
&lt;cs&gt;Rozsahy&lt;/cs&gt;
&lt;de&gt;Bereiche&lt;/de&gt;
&lt;fr&gt;Rangées&lt;/fr&gt;
&lt;pl&gt;Zakresy&lt;/pl&gt;
&lt;ru&gt;&amp;#1044;&amp;#1080;&amp;#1072;&amp;#1087;&amp;#1072;&amp;#1079;&amp;#1086;&amp;#1085;&amp;#1099;&lt;/ru&gt;
&lt;hu&gt;Tartomány&lt;/hu&gt;
&lt;/i18n&gt;&lt;/title&gt;
</pre>
<p>If you want to add a, say, Dutch translation, simply add a string like this to the list above: <code>&lt;nl&gt;Bereik&lt;/nl&gt;</code>. Of course you should only submit a translated configuration file that&rsquo;s complete to the development team!</p>
 
<h3>Submitting your translation</h3>
<ul>
<li>Once you are happy with the result of your hard work, please open your web browser, head to the <a href="http://bugs.scribus.net">Scribus Bugtracker</a> and submit a new bug with the title of your translation update under the &ldquo;Translation&rdquo; category.</p>
<li><i><b>Please note that as of Scribus 1.3.9 it is no longer necessary to upload qm files, as these will be generated at build time. Also note that the translation of the Templates and Render Frame files is optional.</b></i></p></li>
<li>If you want to be credited (and we prefer to give credit where credit is due!), please add your name and your email address to the bug report.</li>
<li>That&rsquo;s it! When the next SVN release is made, your new translation will be added by the team. Usually, new translations are being added SVN within one or two days.</li>
</ul>
<h3>Translating the Online Help</h3>
<p>Before you start translating the Online Help, you should be aware of the fact that this a huge task, and this doesn&rsquo;t just refer to the skills or the time required to successfully complete the work. The documentation will be updated on a regular basis, which is why you should contact the team before you are wasting your time on translating files that are in the process of being rewritten or replaced. Also note that some basic HTML knowledge will help a lot, since all help files are written in HTML. Again, you are advised to contact the development team to learn about the rather strict HTML coding conventions for Scribus help files.</p>
</body>
</html>
/trunk/Scribus/doc/it/workspace1.html
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>
/trunk/Scribus/doc/it/scripterapi-extensions.html
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>
/trunk/Scribus/doc/it/cms.html
0,0 → 1,54
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Gestione del colore con Scribus</title>
</head>
<body>
<h2>Gestione del colore con Scribus</h2>
<h3>Panoramica</h3>
 
<p>L'obiettivo di un sistema di gestione del colore &egrave; di ridurre le differenze tra i colori visualizzati su schermo e quelli della stampa finale, e inoltre di individuare i colori &ldquo;fuori gamma,&rdquo; cio&egrave; non compresi nella gamma di colori (o &ldquo;gamut&rdquo;) della stampante che si intende usare. Per usare la gestione del colore sono necessari profili ragionevolmente accurati sia della stampante sia del monitor. Il concetto di gestione del colore, le opzioni e le descrizioni possono causare notevole confusione nell'utente inesperto. Se non si conosce la terminologia, &egrave; <strong>molto</strong> facile scegliere impostazioni errate, e di conseguenza spesso si peggiora l'aspetto delle immagini su video, su carta, o su entrambi. Allora il neofita dice &ldquo;ne ho abbastanza!&rdquo;, e disabilita la gestione del colore.</p>
 
<p>Ebbene: <strong>non fatelo</strong>. Vi baster&agrave; comprendere alcuni concetti di base e conoscere la destinazione finale di stampa, e sarete in grado di prevedere e controllare meglio l'aspetto che il documento avr&agrave; quando sar&agrave; stampato. Questo &egrave; utile specialmente quando dovete inviare dei file in tipografia per la stampa in quadricromia.</p>
 
<p>Questi sono i passi per fare in modo che la gestione del colore funzioni in modo affidabile (ci&ograve; che vedete a video &egrave; ci&ograve; che sar&agrave; stampato):</p>
 
<ol>
<li>Imparate un po' i concetti e la terminologia della gestione del colore. Esistono molti buoni libri e siti sull'argomento (ad esempio <a href="http://www.poynton.com">questo</a>, in inglese, e <a href="http://boscarol.com/">questo</a>, in italiano).</li>
<li>Procuratevi o create profili colore accurati. Il pi&ugrave; importante &egrave; un profilo preciso per il vostro monitor. <a href="toolbox14.html">Lprof</a> &egrave; un ottimo strumento per la creazione di profili per monitor. <i>Se non avete un profilo per il monitor correttamente creato, e attivate la gestione del colore, otterrete risultati di stampa insoddisfacenti e anteprime inaffidabili a video.</i> </li>
<li>Caricate i profili colore nelle applicazioni grafiche in modo corretto. Al giorno d'oggi la gestione del colore pu&ograve; essere utilizzata non solo nelle applicazioni grafiche proprietarie, ma anche nelle principali applicazioni open source come GIMP, Krita, digiKam, Inkscape, o sK1.</li>
</ol>
 
<p>Il sistema di gestione del colore di Scribus &egrave; pensato per permettere prove colore a monitor (&ldquo;soft proofs&rdquo;) con la gestione del colore attiva. Inoltre Scribus pu&ograve; avvisare della presenza di colori &ldquo;fuori gamma&rdquo;, che potrebbero essere riprodotti in modo non accurato da una stampante o da una macchina tipografica: questo pu&ograve; accadere perch&eacute; la maggior parte delle stampanti hanno una gamma meno ampia di colori stampabili (CMYK), rispetto alla maggior parte dei monitor (RGB). Scribus non incorpora profili nelle immagini, n&eacute; altera quelli incorporati in esse (alcuni formati immagine, come EPS, JPEG, PNG o TIFF, permettono di incorporare profili ICM o ICC.)</p>
 
<table width="100%"><tr><td align="center"><img src="images/rgb-cmyk.png"/></td></tr>
<tr><td><div align="center"><i>Il modello RGB (a sinistra) ha una gamma di colori molto pi&ugrave; ampia del modello CMYK (a destra).</td></tr></table>
 
<p><strong>Che cosa sono i profili di colore, e i profili di periferica?</strong></p>
 
<p>I profili <strong>ICC</strong> o <strong>ICM</strong> sono uno speciale tipo di file che descrive le caratteristiche di colore di una periferica come uno scanner, un monitor o una stampante. Possono esistere profili per qualunque apparecchio in grado di creare, visualizzare o manipolare immagini digitali, da cui il termine <b>profilo di periferica</b>.</p>
<p>Vi sono anche profili di colore detti <strong>indipendenti dalla periferica</strong> o di <strong>spazio di lavoro</strong>. Questi file speciali possono essere considerati &ldquo;traduttori&rdquo; che convertono i dati di colore da un tipo di profilo colore ad un altro.</p>
<p>Un file ICC o ICM &egrave; un insieme di tabelle che contengono i valori matematici per mezzo dei quali una periferica misura e descrive il colore. Fortunatamente, questi profili seguono uno <a href="http://www.color.org ">standard aperto internazionale</a> e funzionano allo stesso modo su Mac&nbsp;OS&nbsp;X, OS/2, eCS, Windows, Linux o UNIX.</p>
 
 
<h3>Attivare la gestione del colore</h3>
<p>Perch&eacute; la gestione del colore funzioni correttamente, i seguenti componenti devono essere installati, funzionanti e utilizzabili:</p>
<ul>
<li>La libreria littleCMS. &Egrave; compresa nelle versioni di Scribus per Mac&nbsp;OS&nbsp;X, OS/2, eComStation e Windows, ed &egrave; una dipendenza su Linux e UNIX.</li>
<li>Dovete avere almeno un profilo RGB e uno CMYK. Scribus fornisce due profili di base, in modo che la gestione del colore possa essere attivata subito dopo l'installazione. In pratica ne avrete bisogno di pi&ugrave;: un profilo sRGB per la maggior parte dei colori RGB e uno per ciascuna periferica a colori; uno per il monitor, che dovrebbe essere creato con uno strumento di profilazione; alcuni profili CMYK per la stampa commerciale. <br>Certi profili CMYK sono considerati &ldquo;standard,&rdquo; poich&eacute; rappresentano condizioni standardizzate per la stampa commerciale impiegate in Europa, Giappone e Nord America. Vi sono parecchi siti da cui &egrave; possibile scaricare profili ICC affidabili. Uno degli standard del settore &egrave; il pacchetto &ldquo;Adobe ICC Profiles&rdquo;, che sono quelli forniti con le applicazioni Adobe; si possono scaricare dal sito della Adobe: <a href="http://www.adobe.com/support/downloads/product.jsp?product=62&platform=windows">qui per Windows</a> e <a href="http://www.adobe.com/support/downloads/product.jsp?product=62&platform=Macintosh">qui per Mac OS</a>. Un insieme di profili che si &egrave; dimostrato di qualit&agrave; eccellente &egrave; quello fornito dalla <a href="http://www.basiccolor.de">basICColor GmbH</a>, un'azienda tedesca specializzata nella gestione del colore. I profili, coperti da una licenza CC, possono essere scaricati <a href="http://www.colormanagement.org">qui</a>.</li>
<li>Uno sviluppo pi&ugrave; recente sui desktop Linux &egrave; la possibilit&agrave; di utilizzare la gestione del colore quasi ovunque, almeno dove essa ha senso. Di conseguenza la gestione del colore ora &egrave; spesso usata non solo da programmi per l'editing di immagini bitmap o vettoriali o di desktop publishing, ma anche da browser web e semplici visualizzatori di immagini. Quindi molte distribuzioni Linux moderne mettono a disposizione molti insiemi di profili ICC di alta qualit&agrave;, sotto forma di pacchetti aggiuntivi facilmente installabili con il proprio gestore di pacchetti. Tra essi vi sono i profili Adobe ICC e basICColor sopra citati. A seconda dei criteri per la gestione delle licenze, potrebbe essere necessario aggiungere o attivare i repository &ldquo;non-free&rdquo; (comunque siano chiamati) della vostra distribuzione, per poter installare i pacchetti con licenze non (L)GPL/BSD.</li>
</ul>
 
<h3>Posizioni dei profili colore</h3>
<ul>
<li><b>Linux/UNIX:</b> <code>/usr/share/color/icc</code> (profili di sistema) e <code>/home/username/.color/icc</code> (profili utente).</li>
<li><b>Mac OS X:</b> <code>/Library/ColorSync/Profiles</code>.</li>
<li><b>Windows:</b>: <code>C:\WINNT\system32\spool\drivers\color</code> (Windows 2000) e <code>C:\Windows\system32\spool\drivers\color</code> (Windows XP, Vista, 7).<br>
<i>Si noti che sui sistemi Windows a 64 bit, alcuni programmi a 32 bit potrebbero non riuscire a trovare i profili nella directory <code>system32</code> perch&eacute; li cercano in <code>C:\Windows\SysWOW64</code>, che &egrave; una cartella contenente i file necessari per la compatibilit&agrave; dei programmi a 32 bit (questo non &egrave; un refuso: la cartella con un &ldquo;32&rdquo; nel nome &egrave; per i file a 64 bit, e quella con &ldquo;64&rdquo; nel nome &egrave; per file a 32 bit!). Se usate un programma a 32 bit su una versione di Windows a 64 bit, e i profili colore non sono disponibili, dovreste copiarli anche in <code>C:\Windows\SysWOW64\spool\drivers\color</code></i>.</li>
<li><b>OS/2 ed eComStation:</b> <code>X:\scribus-directory\lib\scribus\profiles</code>. <br>
<i>Su OS/2 ed eComStation non esiste una modalit&agrave; di gestione del colore a livello di sistema, quindi ciascun programma che usa la gestione del colore, come Scribus o GIMP, deve avere i profili nella propria directory. Tuttavia &egrave; possibile creare una singola directory che comprenda tutti i profili, e impostarla come fonte aggiuntiva per i profili; la directory potrebbe essere, ad esempio, </i> <code>X:\ICC</code>. <i>In Scribus potete aggiungere questo percorso nella scheda &ldquo;Generale&rdquo; delle <a href="settings1.html#1">preferenze</a>.</i></li>
</ul>
 
<br />
</body>
</html>
/trunk/Scribus/doc/it/readme-macosx.html
0,0 → 1,26
<html><head>
 
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Scribus su Mac OS X</title>
</head><body>
<h2>Scribus su Mac OS X</h2>
<h3>Hardware</h3>
<ul>
<li>Mac basato su Intel</li>
<li>512 MB RAM in aggiunta a quanto richiesto per la memoria di sistema; maggiore &egrave; la quantit&agrave; di RAM, meglio &egrave;. Per documenti grandi o complessi si consigliano almeno 1&ndash;2 GB.</li>
</ul>
<h3>Prima di installare Scribus</h3>
<ul>
<li>&egrave; consigliabile installare Ghostscript per Mac OS X, preferibilmente <a href="http://idisk.mac.com/yhonda-Public/ghostscript.dmg">Ghostscript 8.60+</a> o successivo. Questo &egrave; importante per l'importazione e la stampa di EPS, PS e PDF. Potete anche installarlo per mezzo di <a href="http://www.macports.org/">MacPorts</a> o <a href="http://www.finkproject.org/">Fink</a>: il risultato sar&agrave; lo stesso.</li>
</ul>
<h3>Installazione</h3>
<ul>
<li>per installare Scribus basta <a href="http://sourceforge.net/project/showfiles.php?group_id=125235&amp;package_id=201484">prelevare</a> il pacchetto DMG o *.pkg per Mac OS&nbsp;X da Sourceforge, aprirlo e trascinare l'icona di Scribus nella posizione che preferite. La finestra di DMG Finder propone la directory predefinita di sistema Applicazioni. Da essa potete fare clic sull'icona e lanciare Scribus.</li>
<li>il primo avvio di Scribus, o quando un nuovo utente lancia Scribus, pu&ograve; richiedere molto pi&ugrave; tempo del normale. Questo accade perch&eacute; Scribus crea un file di cache dei caratteri presenti sul vostro sistema. I lanci successivi sono molto pi&ugrave; rapidi.</li>
</ul>
<h3>Software aggiuntivo</h3>
<ul>
<li>Scribus 1.4 contiene un nuovo tipo di cornice, la <a href="WwRenderframes.html">cornice rendering</a>. Permette di utilizzare altri programmi e di visualizzare il loro output all'interno di un documento di Scribus. Per poterla utilizzare, &egrave; necessario installare questi programmi. Per impostazione predefinita, Scribus &egrave; preconfigurato per usare <a href="http://www.tug.org/mactex/">LaTeX</a>, <a href="http://lilypond.org/web/install/">Lilypond</a>, <a href="http://www.povray.org/ftp/pub/povray/Official/Macintosh/povpmac.sit">POV-Ray</a>, <a href="http://www.pixelglow.com/graphviz/">Graphviz</a>, e <a href="http://lee-phillips.org/info/Macintosh/gnuplot.html">Gnuplot</a>.
</li>
</ul>
</body></html>
/trunk/Scribus/doc/it/scripter-extensions.html
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>
/trunk/Scribus/doc/it/WwLines.html
57,11 → 57,11
</tr>
</table>
<h3>Punto base</h3>
Abbiamo lasciato quest'impostazione per ultima perch&eacute; &egrave; un po' complicata. Per ogni tipo di linea o figura, le impostazioni iniziali nella scheda X,Y,Z del pannello Propriet&agrave; mostrano la <b>Pos X</b> e la <b>Pos Y</b> del punto base, che all'inizio &egrave; l'angolo superiore sinistro della cornice o della bounding box. Nel caso di una linea retta, <b>Pos X</b> e <b>Pos Y</b> indicano il punto iniziale da cui la linea &egrave; stata tracciata. Le altre caselle di controllo nella scheda X,Y,Z mostrano la <b>Larghezza</b> e l'<b>Altezza</b> della bounding box, tranne che per una linea retta, che &egrave; definita soltanto da <b>Larghezza</b> (cio&egrave; lunghezza), direzione (<b>Rotazione</b>) e spessore della linea.
Abbiamo lasciato quest'impostazione per ultima perch&eacute; &egrave; un po' complicata. Per ogni tipo di linea o figura, le impostazioni iniziali nella scheda X,Y,Z del pannello Propriet&agrave; mostrano la <b>Pos X</b> e la <b>Pos Y</b> del punto base, che all'inizio &egrave; l'angolo superiore sinistro della cornice o del riquadro di delimitazione. Nel caso di una linea retta, <b>Pos X</b> e <b>Pos Y</b> indicano il punto iniziale da cui la linea &egrave; stata tracciata. Le altre caselle di controllo nella scheda X,Y,Z mostrano la <b>Larghezza</b> e l'<b>Altezza</b> del riquadro di delimitazione, tranne che per una linea retta, che &egrave; definita soltanto da <b>Larghezza</b> (cio&egrave; lunghezza), direzione (<b>Rotazione</b>) e spessore della linea.
<p>Questo &egrave; valido se il <b>Punto base</b> nella scheda Linea &egrave; impostato a <b>Punto sinistro</b>. Se impostate il punto base a <b>Estremit&agrave;</b> la scheda X,Y,Z mostra caselle di controllo per <b>X1</b>, <b>Y1</b>, e <b>X2</b>, <b>Y2</b>.
<p>Per una linea retta <b>X1</b> e <b>Y1</b> indicano il <i>punto iniziale della linea</i>, cio&egrave; il punto a partire dal quale essa &egrave; stata disegnata; <b>X2</b> e <b>Y2</b> indicano le coordinate dell'altro estremo della linea.
<p>L'esempio mostrato sotto riguarda una linea retta, e potete vedere che <b>X-Pos</b> = <b>X1</b> e <b>Y-Pos</b> = <b>Y1</b>.
<p>Per un oggetto pi&ugrave; complesso di una linea retta, i valori sono riferiti alla bounding box, e in questo caso <b>X1</b> e <b>Y1</b> indicano il punto base impostato nella scheda X,Y,Z,; i valori <b>X2</b> e <b>Y2</b> indicano la larghezza e l'altezza della bounding box, che quindi saranno sempre numeri positivi.
<p>Per un oggetto pi&ugrave; complesso di una linea retta, i valori sono riferiti al riquadro di delimitazione, e in questo caso <b>X1</b> e <b>Y1</b> indicano il punto base impostato nella scheda X,Y,Z; i valori <b>X2</b> e <b>Y2</b> indicano la larghezza e l'altezza del riquadro di delimitazione, che quindi saranno sempre numeri positivi.
<table cellpadding="15">
<tr><td>Punto base: <b>punto sinistro</b>
<p><img src="images/geometry.png"></td>
/trunk/Scribus/doc/it/install3.html
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>
/trunk/Scribus/doc/it/toolbox14.html
0,0 → 1,13
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>LProf</title>
</head>
<body>
<h2>LProf</h2>
<p><a href="http://lprof.sourceforge.net/">LProf</a> &egrave; uno strumento molto utile per far s&igrave; che la gestione dei colori funzioni in modo affidabile in Scribus, specialmente per chi usa Linux o UNIX (ma ne esistono versioni anche per Windows e Mac&nbsp;OS&nbsp;X).</p>
<p>In generale, LProf &egrave; uno strumento facile da usare per creare un <a href="cms.html">profilo ICC</a> di periferiche grafiche, tra cui il monitor, e questo aiuta a rendere pi&ugrave; accurate le anteprime con la gestione del colore attiva.</p>
<p>LProf pu&ograve; funzionare con molti, ma non con tutti, i dispositivi di calibrazione. Controllate il <a href="http://lprof.sourceforge.net/">sito di LProf</a> per avere un elenco dei dispositivi con cui funziona, e anche per avere una documentazione pi&ugrave; dettagliata.</p>
<table width="100%"><tr><td align="center"><img src="images/lprof.png" alt="Creazione di un profilo con LProf." /></td></tr></table>
</body>
</html>
/trunk/Scribus/doc/it/importhints4.html
29,22 → 29,22
&#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;h1&#062;Intestazione di primo livello (H1)&#060;/h1&#062;
&#060;h2&#062;Intestazione di secondo livello (H2)&#060;/h2&#062;
&#060;h3&#062;Intestazione di terzo livello (H3)&#060;/h3&#062;
&#060;h4&#062;Intestazione di quarto livello (H4)&#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;li&#062;Lista ordinata 1 &#060;/li&#062;
&#060;li&#062;Lista ordinata 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;li&#062;Lista non ordinata 1 &#060;/li&#062;
&#060;li&#062;Lista non ordinata 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;code&#062;frammento di codice&#060;/code&#062;
&#060;p&#062;&#060;b&#062;Paragrafo con testo in grassetto&#060;/b&#062;&#060;/p&#062;
&#060;p&#062;&#060;i&#062;Paragrafo con testo in corsivo&#060;/i&#062;&#060;/p&#062;
&#060;p align="center"&#062;Testo centrato&#060;/p&#062;
&#060;/body&#062;
&#060;/html&#062;</pre>
<p>Ecco gli stili generati con l'importazione del file:</p>
/trunk/Scribus/doc/it/toolbox7.html
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>
/trunk/Scribus/doc/it/faq1.html
0,0 → 1,166
<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, find interactive help or hire an experienced Scribus trainer?</a></li>
<li><a href="#2">How do I get formatted tables in Scribus?</a></li>
<li><a href="#3">Help! My palettes have disappeared!</a></li>
<li><a href="#4">Why do Scribus DMGs from SourceForge not work on Mac OS X 10.4.x?</a></li>
<li><a href="#5">What is the difference between PDF 1.3, PDF 1.4 and PDF 1.5?</a></li>
<li><a href="#6">How do you change paper size once the document has been created?</a></li>
<li><a href="#7">How do you get your printer to print on a non-standard size sheet?</a></li>
<li><a href="#8">The CUPS options do not show up in print options dialog, what is wrong?</a></li>
<li><a href="#9">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="#10">Scribus seems to hang in an infinite loop when importing EPS or PS files. Why?</a></li>
<li><a href="#11">How do I get Arabic text to display correctly with proper glyph shaping and RTL text direction?</a></li>
<li><a href="#12">There are many Scribus versions. Which one should I use?</a></li>
<li><a href="#13">Why is Scribus built with Qt and not some other toolkit?</a></li>
<li><a href="#14">Where does the name &ldquo;Scribus&rdquo; derive from?</a></li>
<li><a href="#15">Why are there no import filters for XPress, InDesign or other commercial DTP applications?</a></li>
<li><a href="#16">Is there or will there be a Microsoft Publisher importer?</a></li>
<li><a href="#17">So, how can I work with those who use other page layout applications?</a></li>
</ul>
 
<h3>Answers</h3>
 
<ul>
<li><a name="1"></a>
<p class="faqquestion">How do I contact the Scribus Team, find interactive help or hire an experienced Scribus trainer?</p>
<p>1. There is an active and friendly <a href="mailing_lists.html">mailing list</a>. </p>
<p>2. Find the developers on <a href="irc.html">IRC</a> in the #scribus channel.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="2"></a>
<p class="faqquestion">How do I get formatted tables in Scribus?</p>
<p>Scribus added basic table support in 1.1.6, but unfortunately, tables are nothing more than combined text frames, and it is a bit hard to work with them. If you need to have more complex tables, here is a reliable workaround:</p>
<ol>
<li> Create your table in either OpenOffice.org Writer or Calc.</li>
<li> Copy the table cells you need in Scribus (i.e: not the whole spreadheet in Calc) to the clipboard, create a new OpenOffice.org Draw document, and use <i>Edit &gt; Paste Special &gt; GDI Metafile</i> to insert the table as a vector file into Draw.</li>
<li> Use <i>File &gt; Export</i> to export the graphic as an EPS file. Make sure that <i>Selection</i> is checked in the export dialog, because otherwise the whole page will be exported.</li>
<li> Now import the EPS file as a vector drawing in Scribus via <i>File &gt; Import &gt; Import Vector File</i></li>
</ol>
 
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="3"></a>
<p class="faqquestion">Help! My palettes have disappeared!</p>
<p>Close Scribus. Then open <code>~/.scribus/scribus.rc</code>, 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. <code>ex: MEASUREMENTS YPOS=&quot;-264&quot; XPOS=&quot;-692&quot; VISIBLE=&quot;1&quot;</code>.</p>
<p>Notice the negative numbers in front of the <code>YPOS</code> and <code>XPOS</code> statements. Remove the minus, set the visible setting to 0 and save. You might find the coordinates too large: (<code>YPOS=&quot;3046&quot; XPOS=&quot;7690&quot;</code>). Either way, these coordinates are screen positions in pixels. They should be within 1024x768 or whatever screen resolution you are running. Restart Scribus, go to the <i>Windows</i> menu and select show for the missing palette. It will reappear like normal.</p>
<p><i>This has been corrected in the most recent versions of Scribus and should not be a problem in the future.</i></p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="4"></a>
<p class="faqquestion">Why do Scribus DMGs from SourceForge not work on Mac OS X 10.4.x?</p>
<p>To run Scribus under OS X 10.4.x, you need to install <a href="http://www.finkproject.org/">Fink</a>, an Open Source packaging system for OS X, and <a href="http://finkcommander.sourceforge.net/">FinkCommader</a>, Fink's graphical user interface. In FinkCommnader, go to <i>Preferences > Fink</i> and check <i>Use Unstable Packages</i>.</p>
<p>You can also <a href="install5.html">build Scribus from source.</a></p>
<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 installed and slow launch times are a problem, reduce the number of fonts or font paths. </p>
<p>The other reason is that your Scrapbook might be filled with complex or large objects. Deleting unneeded 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="5"></a>
<p class="faqquestion">What is the difference between PDF 1.3, PDF 1.4 and PDF 1.5?</p>
<p>PDF 1.2 = Acrobat 3.0 &ndash; Relatively obsolete now.</p>
<p>PDF 1.3 = Acrobat 4.0 &ndash; The first version of PDF which truly had all the needed features to support &ldquo;press-ready&rdquo; 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 &ndash; actually introduced with Illustrator 9, The main difference to concern Scribus users is that 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 either the latest commerical RIPs or a Level 3 PostScript printer to use these features properly. The latest versions of Ghostscript support the advanced PDF 1.4 features Scribus can create when exporting PDF.</p>
<p>PDF 1.5 = Acrobat 6.0 &ndash; Among the most interesting for Scribus users: Many improvements for &ldquo;press-ready&rdquo; PDF, the capability to have true layering within the PDF, PDF-X &ldquo;pre-flight&rdquo; capability, more security and interactive features, like the ability to add comments which are separate from the original document.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="6"></a>
<p class="faqquestion">How do you change paper size once a document 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 <i>Page</i> menu, under <i>Manage Page Properties</i>.</p>
<p>You can change this for the whole document under <i>File > Document Setup</i>.</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="7"></a>
<p class="faqquestion">How do you get your printer to print on a non-standard size sheet?</p>
<p>It depends:</p>
<ol>
<li>If you are printing to a local printer which is <b>not</b> 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 &ldquo;real&rdquo; PostScript printer, Scribus &ndash; with CUPS support &ndash; will support any arbitrary page size, as long as the printer supports it.</li>
</ol>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="8"></a>
<p class="faqquestion">The CUPS options do not show up in print options dialog, What is wrong?</p>
<p>See <a href="http://bugs.scribus.net/bug_view_advanced_page.php?bug_id=0000271">this bug</a> for an explanation of how CUPS can be misconfigured.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="9"></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 distro's source RPMs or source packages.</p>
<ol>
<li>Recent versions of freetype have an autohinter, which works very well.</li>
<li><b>Many</b> packages are compiled against freetype2 (Xfree86, Qt, Gtk+ etc..), thus, upgrading freetype2 will require recompiling <b>all</b> of these packages or system instability might be the result.</li>
</ol>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="10"></a>
<p class="faqquestion">Scribus seems to hang in an infinite loop when importing EPS or PS files. Why?</p>
<p>Three possible solutions:</p>
<ol>
<li>Upgrade to the latest Ghostscript. There are <a href="toolbox7.html">notes</a> in the &ldquo;Toolbox&rdquo; section on parallel installs of GS.</li>
<li>Reduce the complexity of your EPS/PS file.</li>
<li>You do not have enough memory/swap space when importing complex EPS files.</li>
</ol>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="11"></a>
<p class="faqquestion">How do i get Arabic or Hebrew text to display correctly with proper glyph shaping and RTL text direction?</p>
<p>The glyph shaping is a very difficult thing to achieve. We plan to add this in one of the 1.5.x development versions.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="12"></a>
<p class="faqquestion">There are many Scribus versions. Which one should I use?</p>
<p>There are currently three branches of Scribus available:
<ol>
<li>The officially stable branch is 1.3.3.x, and installers for Windows and OS/2 are available from <a href="http://sourceforge.net/projects/scribus/files/scribus/">Sourceforge</a>. This branch is unlikely to see any updates or bugfixes.</li>
<li>The next version of Scribus is being developed in the branch called &ldquo;Next Generation&rdquo; (NG), and it will result in Scribus 1.4. This branch is already quite stable and useable. Installers for this branch are regularly updated and <a href="http://sourceforge.net/projects/scribus/files/scribus-svn/">available</a> for Mac OS X 10.5+, OS/2 and Windows. Users of Linux/UNIX can use their distribution&rsquo;s package management or check out <a href="install1.html">svn</a> and <a href="install4.html">build from source</a>.</li>
<li>1.5.x is an experimental branch, in which new features are implemented and tested. If possible, those new features will be backported to the 1.3.x/1.4 branch. There are no installers or packages available, as it's only recommended for users who want to test the latest features. <b>Do not use 1.5+ for serious work, because we cannot even guarantee that the file format won&rsquo;t change!</b> 1.5+ must be compiled from source.</li>
</ol>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="13"></a>
<p class="faqquestion">Why is Scribus built with Qt and not some other toolkit?</p>
<p>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 the release of version 0.6. Currently, Scribus uses Qt 4.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="14"></a>
<p class="faqquestion">Where does the name &ldquo;Scribus&rdquo; derive from?</p>
<p>When Franz Schmid launched the project, the first working name was &ldquo;Open Page&rdquo;, but he thought it would be too generic. &ldquo;Scribus&rdquo; is derived from the Latin name of the official writers in Ancient Rome, &ldquo;scriba&rdquo;, from which we get &ldquo;scribe&rdquo; or writer. This translates well in to many languages besides English. The German word is &ldquo;Schreiber&rdquo;, for example.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="15"></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 &ndash; they are probably the most complex file formats. Creating import/export filters is a task far more difficult than importing a spreadsheet or simpler word processing document. An engineer familiar with the internal file format of PageMaker compared it to a 2m&nbsp;x&nbsp;3&nbsp;m flow chart diagram in 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.</li>
<li>The file formats are not documented publically.</li>
<li>So, is it unethical/illegal to apply hexedit to an InDesign or XPress file to reverse engineer the file format with hexedit or others for the purpose of creating the export/import plugins for Scribus?<br/>Probably not, but given their closed nature, we cannot rule out the possibility of legal bullying by a commercial vendor, 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. A German vendor of DTP software successfully reverse-engineered Quark&rsquo;s file format and created an import filter. It took a long legal battle for them 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>
<li>As an exception to the rule, we are open to implement publically available format specifications. For example, the XML version of InDesign's file format (IDML) is very well documented, and the spec is freely (i.e. without any legal restrictions that prevent the implementation of an import filter) available. Thus, a team member took the time and wrote an import filter, which is currently being tested. The same goes for formatted text snippets from QuarkXPress, called XPress Tags.</li>
</ol>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="16"></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 QuarkXpress, the file format is undocumented. PUB files are difficult and sometimes impossible to reverse engineer.</p>
<p>As with InDesign or XPress, we are considering to implement a workaround: Newer versions of Publisher are capable of exporting to Microsoft's XML Paper Specification (XPS), which is freely available and can be implemented without any legal encumbrances. Thus, if time constraints permit, we may create XPS import/export filters. If you urgently need to exchange files with users of Publisher, you should consider to either get your hands dirty by writing the filters yourself or by paying someone to do so for you.</p>
<a href="#top">Back to top</a><hr/>
</li>
<li><a name="17"></a>
<p class="faqquestion">So, how can I work with those who use other page layout applications?</p>
<p>Use EPS, PS, 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 &ndash; 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>
</ul>
<p>The <a href="http://wiki.scribus.net/index.php/Category:FAQ">Scribus Wiki</a> has an additional FAQ.</p>
</body>
</html>
/trunk/Scribus/doc/it/WwRenderframes.html
14,12 → 14,12
<p>Il passo successivo consiste nel fare clic e trascinare il mouse per tracciare la cornice, proprio come per una cornice di testo. Per impostazione predefinita, Scribus mostra un messaggio di benvenuto, indicante almeno che la configurazione per LaTeX &egrave; corretta. Qui sotto &egrave; mostrato l'output fornito da LaTeX, rappresentato in Scribus. Il messaggio di benvenuto appare nella lingua dell'interfaccia utente selezionata in <i>File &gt; Preferenze</i>; se non esiste una traduzione, sar&agrave; mostrata la versione inglese:</p>
<table width="100%"><tr><td align="center"><img src="images/rf3.png"/></td></tr></table>
<p>La schermata qui sopra ha la risoluzione predefinita di 72 DPI, che ovviamente &egrave; troppo bassa per la stampa. La risoluzione pu&ograve; essere modificata facilmente, come spiegheremo pi&ugrave; avanti.</p>
<h1>Modificare le cornici rendering</h1>
<h1>L'editor della cornice rendering</h1>
<p>Se fate clic col tasto destro su una cornice rendering, il men&ugrave; contestuale comprende una voce &ldquo;Modifica origine:&rdquo;</p>
<table width="100%"><tr><td align="center"><img src="images/rf4.png"/></td></tr></table>
<p>quando la selezionate, si apre il &ldquo;cuore&rdquo; della cornice rendering, l'editor:</p>
<table width="100%"><tr><td align="center"><img src="images/rf5.png"/></td></tr></table>
<p>In Scribus 1.3.5, l'editor &egrave; preconfigurato per utilizzare LaTeX, Lilypond, gnuplot, dot/GraphViz e POV-Ray.</p>
<p>In Scribus 1.3.5 e successivi, l'editor &egrave; preconfigurato per utilizzare LaTeX, Lilypond, gnuplot, dot/GraphViz e POV-Ray.</p>
<p>A sinistra vi &egrave; un campo denominato &ldquo;Inserisci codice&rdquo;: qui potete inserire il codice per l'output che volete ottenere dal programma esterno. Per i programmi preconfigurati Scribus comprende dei frammenti di codice che vi permetteranno di verificare se essi sono installati e configurati correttamente. Come potete vedere, l'editor esegue anche l'evidenziazione della sintassi.</p>
<p>Il pulsante &ldquo;Aggiorna&rdquo; sotto il campo di testo aggiorna il contenuto della cornice rendering, e vi permette di controllare il risultato dei cambiamenti fatti al codice sorgente senza chiudere l'editor. &ldquo;Annulla&rdquo; annulla gli eventuali cambiamenti fatti. Tenete presente che, una volta iniziato a creare e modificare il testo, non &egrave; possibile cambiare il programma esterno usato per interpretarlo; quindi, ad esempio, se avete iniziato a lavorare su del codice sorgente LaTeX, non potete passare a Lilypond.</p>
<p>La parte destra della finestra contiene una serie di schede. Non tutte sono presenti per ciascuno dei programmi preconfigurati, e per alcuni di essi l'editor mostra soltanto la scheda &ldquo;Opzioni&rdquo;.</p>
127,6 → 127,6
<br></br>
<table width="100%"><tr><td align="center"><img src="images/rf-error3.png"/></td></tr></table>
<br></br>
<p>Inoltre, avete la possibilit&agrave; di iniziare con una cornice vuota. Contrassegnando l'opzione &ldquo;Forza DPI&rdquo;, Scribus visualizzer&agrave; l'output di tutte le cornici rendering con la risoluzione impostata nella casella di controllo a destra. La risoluzione predefinita &egrave; impostata a 72 DPI per motivi di efficienza, ma se intendete creare un documento destinato alla stampa professionale, vi servir&agrave; una risoluzione maggiore.</p>
<p>Inoltre, avete la possibilit&agrave; di iniziare con una cornice vuota. Contrassegnando l'opzione &ldquo;Forza DPI&rdquo;, Scribus visualizza l'output di tutte le cornici rendering con la risoluzione impostata nella casella di controllo a destra. La risoluzione predefinita &egrave; impostata a 72 DPI per motivi di efficienza, ma se intendete creare un documento destinato alla stampa professionale, vi servir&agrave; una risoluzione maggiore.</p>
</body>
</html>
/trunk/Scribus/doc/it/scripterapi-constants.html
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>
/trunk/Scribus/doc/it/toolbox19.html
0,0 → 1,98
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Strumenti da riga di comando</title>
</head>
<body>
 
<h2>Strumenti da riga di comando</h2>
<p>Ecco un elenco di utili strumenti da riga di comando che possono essere usati insieme a Scribus. Non tutti questi programmi sono disponibili per ogni piattaforma su cui Scribus &egrave; utilizzabile, ma certamente sono tutti disponibili su Linux e UNIX (compreso Mac&nbsp;OS&nbsp;X). Per scoprire cosa questi strumenti possono fare e come servirvene, potete usare i consueti comandi della shell, come <code>man program</code>, <code>program --help</code>, o <code>program -h</code> (dove <code>program</code> &egrave; il nome dello strumento).</p>
<h3>PDF/PostScript</h3>
 
<h4>Strumenti Ghostscript</h4>
<ul>
<li><b><code>epswrite</code></b></li>
<li><b><code>pstoedit</code></b></li>
<li><b><code>ps2pdf</code></b></li>
<li><b><code>ps2pdf13</code></b></li>
<li><b><code>ps2pdf14</code></b></li>
<li><b><code>pdfopt</code></b></li>
</ul>
 
<h4>Strumenti PoDoFo</h4>
<ul>
<li><b><code>podofocolor</code></b></li>
<li><b><code>podofocountpages</code></b></li>
<li><b><code>podofocrop</code></b></li>
<li><b><code>podofoencrypt</code></b></li>
<li><b><code>podofoimg2pdf</code></b></li>
<li><b><code>podofoimgextract</code></b></li>
<li><b><code>podofoimpose</code></b></li>
<li><b><code>podofoincrementalupdates</code></b></li>
<li><b><code>podofomerge</code></b></li>
<li><b><code>podofopages</code></b></li>
<li><b><code>podofopdfinfo</code></b></li>
<li><b><code>podofotxt2pdf</code></b></li>
<li><b><code>podofotxtextract</code></b></li>
<li><b><code>podofouncompress</code></b></li>
<li><b><code>podofoxmp</code></b></li>
</ul>
<h4>PDF Toolkit</h4>
<ul><li><b><code>pdftk</code></b></li></ul>
 
<h4>PDF Jam</h4>
<ul>
<li><b><code>pdfjam</code></b></li>
<li><b><code>pdfbook</code></b></li>
</ul>
<h3>Strumenti per bitmap</h3>
<h4>ImageMagick/GraphicsMagick</h4>
<ul>
<li><b><code>convert</code></b></li>
<li><b><code>identify</code></b></li>
<li><b><code>mogrify</code></b></li>
<li><b><code>composite</code></b></li>
<li><b><code>montage</code></b></li>
<li><b><code>compare</code></b></li>
</ul>
<h4>Strumenti di LittleCMS</h4>
<ul>
<li><b><code>icc2ps</code></b></li>
<li><b><code>icclink</code></b></li>
<li><b><code>icclink</code></b></li>
<li><b><code>jpegicc</code></b></li>
<li><b><code>tifficc</code></b></li>
<li><b><code>tiffdiff</code></b></li>
<li><b><code>wtpt</code></b></li>
</ul>
 
<h3>Altri strumenti per bitmap</h3>
<ul>
<li><b><code>pngcrush</code></b></li>
<li><b><code>optipng</code></b></li>
</ul>
 
<h3>Caratteri</h3>
<h4>Strumenti per i caratteri lcdf</h4>
<ul>
<li><b><code>cfftot1</code></b></li>
<li><b><code>mmafm</code></b></li>
<li><b><code>mmpfb</code></b></li>
<li><b><code>otfinfo</code></b></li>
<li><b><code>otftotfm</code></b></li>
<li><b><code>t1dotlessj</code></b></li>
<li><b><code>t1lint</code></b></li>
<li><b><code>t1reencode</code></b></li>
<li><b><code>ttftotype42</code></b></li>
</ul>
 
<h4>Altri strumenti per i caratteri</h4>
<ul>
<li><b><code>afm2afm</code></b></li>
<li><b><code>pf2afm</code></b></li>
<li><b><code>pfb2pfa</code></b></li>
<li><b><code>fondu</code></b></li>
</ul>
 
</body>
</html>
/trunk/Scribus/doc/it/WwShapes.html
12,7 → 12,7
<h3>Forme</h3>
<table cellpadding=5><tr>
<td>Lo strumento &ldquo;Forme&rdquo; comprende un insieme di forme predefinite, che nella versione 1.4.x sono molto pi&ugrave; numerose che nelle precedenti. All'avvio di Scribus la forma predefinita &egrave; il rettangolo mostrato nell'icona. Immediatamente alla sua destra c'&egrave; una freccia che apre un men&ugrave; con alcuni sottomen&ugrave;; se selezionate uno dei sottomen&ugrave; e poi una particolare forma (facendo clic con il mouse) l'icona sulla barra degli strumenti assume la forma che avete selezionato. <i>Nota: l'aspetto delle icone delle forme &egrave; stato reso pi&ugrave; nitido nell'immagine qui a destra; in Scribus non hanno un aspetto cos&igrave; distinto.</i>
<p>Come spiegato in Lavorare con le cornici, nelle forme e nei poligoni i colori predefiniti per la linea e il riempimento sono rispettivamente <i>nero</i> e <i>nessuno</i>. Potete cambiare queste impostazioni per il documento corrente in <i>File &gt; Impostazioni documento &gt; Strumenti &gt; Propriet&agrave; disegno forme (icona)</i>, e per i documenti futuri in <i>File &gt; Preferenze &gt; Strumenti &gt; Propriet&agrave; disegno forme (icona)</i>.
<p>Come spiegato in &ldquo;Lavorare con le cornici&rdquo;, nelle forme e nei poligoni i colori predefiniti per la linea e il riempimento sono rispettivamente <i>nero</i> e <i>nessuno</i>. Potete cambiare queste impostazioni per il documento corrente in <i>File &gt; Impostazioni documento &gt; Strumenti &gt; Propriet&agrave; disegno forme (icona)</i>, e per i documenti futuri in <i>File &gt; Preferenze &gt; Strumenti &gt; Propriet&agrave; disegno forme (icona)</i>.
<p>Come per le altre cornici, potete disegnare una forma facendo clic e trascinando il mouse da un angolo a quello opposto. Se tenete premuto il tasto Maiusc mentre trascinate, quando lasciate andare il mouse la forma riempir&agrave; l'intero spazio fino ai margini della pagina.</td><td>
<img src="images/shapes8.png" ALT="Menù per la scelta della forma" ALIGN=right></td>
</tr>
20,7 → 20,7
 
<table cellpadding=5 width="80%"><tr><td><img src="images/shapes7.png" ALT="Inserisci dimensioni oggetto"></td>
<td>Un'altra possibilit&agrave; consiste nel selezionare una forma nel men&ugrave;, e poi fare clic sulla pagina (senza trascinare il mouse): si apre allora una finestra di dialogo, <b>Inserire dimensione oggetto</b>, in cui potete inserire le dimensioni della forma che volete creare.
<p>Questo potrebbe essere utile, ad esempio, per disegnare esattamente un quadrato o un cerchio. L'<b>Origine</b> si riferisce al punto sulla pagina in cui avete fatto clic per aprire questa finestra.
<p>Questo potrebbe essere utile, ad esempio, per disegnare esattamente un quadrato o un cerchio. L'<b>origine</b> si riferisce al punto sulla pagina in cui avete fatto clic per aprire questa finestra.
</td></tr>
</table>
<br clear=all>
/trunk/Scribus/doc/it/scripterapi-select.html
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>
/trunk/Scribus/doc/it/gsview.html
0,0 → 1,95
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GSview and Scribus</title>
 
</head><body>
<h2>GSview*</h2>
 
<p>One important thing to note is that <a href="http://pages.cs.wisc.edu/%7Eghost/gsview/index.htm">GSview</a> <span style="font-style: italic;">must not be confused</span> with <strong style="font-weight: normal;">ghostview, gv and their derivatives!</strong>
Although Adobe Reader® is often a better pure viewer for PDFs, GSview
should be regarded as one of the most essential tools to have when
using
Scribus. GSview has some extremely useful functions. For those
unfamiliar with the program, it provides an easy to use “front end” to
Ghostscript, as well as <code>pstoedit</code> for converting bitmaps
into vector files or vice versa. For those coming from a traditional
DTP background in the Mac/Windows world, it also
provides some of the functionality of Acrobat Distiller.<br>
</p>
 
<p>You should always use the latest version, at least 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.</li>
<li>An easy-to-use front end to Ghostscript’s less well known
features such as image conversion and re-sampling. There are other
features in
Ghostscript, including: converting between TIFF formats, changing the
color depth of a TIFF, JPEG or the color space of an image.</li>
</ul>
 
<p>One example where GSview is extremely useful with Scribus is
troubleshooting or fixing EPS files that 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 programs (like Scribus).</p>
 
<p>So, if you find difficulty with an EPS 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>
“device” 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, by converting it to
PNG
or TIFF and then resize, adjust colors etc with an image program like
GIMP or Krita.<br>
</p>
 
<p> Note that 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>GSview is available for most Linux distributions, at least the major
ones. Otherwise you can build GSview by following
the instructions provided in the <a href="http://pages.cs.wisc.edu/%7Eghost/">source package</a>. For
Windows and OS/2 and eComStation you can download&nbsp;<a href="http://pages.cs.wisc.edu/%7Eghost/gsview/get49.htm">conventional
installers</a> .
Unfortunately, there is no current version for Mac OS X available. </p>
 
<p>A special note to users of OpenSUSE 11.3: The required GTK&nbsp;1
libraries are no longer available for this Linux distribution, but you
can use the <a href="http://download.opensuse.org/repositories/GNOME:/GNOME1/openSUSE_11.2/i586/">versions
compiled for 11.2</a>. You need to install the gtk-1.20 and glib
packages (if you want to build GSview yourself, you also need the
respective devel RPMs), as well as the <a href="http://download.opensuse.org/repositories/GNOME:/GNOME1/openSUSE_11.2/noarch/gtk-lang-1.2.10-1093.1.noarch.rpm">lang
package</a>.<br>
</p>
 
<p>Now, for advanced hints with GSview and Ghostscript, see: <a href="toolbox7.html">Advanced Ghostscript and GSview Hints</a></p>
 
<p>*) <span style="font-style: italic;">Parts of this section are
thanks to Russell Lang, author and maintainer of GSview, epstool and
Ghostscript for his hints and patiently answering questions about
GSview and Ghostscript.</span></p>
 
</body></html>
/trunk/Scribus/doc/it/toolbox4.html
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>Non c'&egrave; molto da dire sulla migliore applicazione per il trattamento di immagini in Linux. I miglioramenti in GIMP 2.x sono troppi per elencarli. </p>
 
<p>Tuttavia, impostare GIMP per l'utilizzo con Scribus (il cui prodotto finale &egrave; destinato alla stampa) richiede alcuni aggiustamenti alle impostazioni predefinite, come mostrato sotto: </p>
 
<ul>
<li>Accertatevi di avere la pi&ugrave; recente versione stabile 2.6.x. </li>
<li>GIMP ora &egrave; in grado di lavorare con i colori CMYK. Anche se il modello di colore internamente &egrave; ancora RGB pi&ugrave; canali alfa, potete usare i valori CMYK e le definizioni di colore CMYK. Per completare queste funzionalit&agrave;, esiste un plugin (prodotto da terzi) chiamato <a href="http://cue.yellowmagic.info/softwares/separate.html">separate+</a>, che pu&ograve; esportare in formato TIFF CMYK utilizzando un abile espediente con i livelli alfa. Il plugin separate+ pu&ograve; inoltre incorporare i profili ICC nei file TIFF esportati e creare TIFF in bicromia.</li>
<li>Uno dei miglioramenti pi&ugrave; apprezzati riguarda la gestione del testo. GIMP 2.x utilizza <code>fontconfig</code>, quindi il rilevamento dei caratteri presenti sul sistema &egrave; molto meno problematico. Il testo pu&ograve; essere mantenuto in un livello a s&eacute; per facilitarne la modifica e la correzione. Nelle versioni 1.2.x certe operazioni sul testo erano difficili, ma ora vi sono ben pochi motivi per lamentarsi; &egrave; un piacere usare i nuovi controlli per il testo. Inoltre esiste anche un apposito plugin freetype per GIMP, che permette di manipolare i caratteri come in Scribus e Inkscape. Lo consigliamo, e lo potete trovare su ftp.gimp.org.</li>
<li>Le versioni pi&ugrave; recenti di GIMP possono esportare tutti i tracciati come maschere di ritaglio nei file TIFF, e sono anche in grado di eseguirne meglio l'importazione da file TIFF. </li>
<li>Nei filtri e negli effetti, per impostazione predefinita i pixel sono adattati (interpolati) con il metodo lineare: questo &egrave; un buon compromesso tra velocit&agrave; e accuratezza. <b>Per materiale destinato alla stampa, si dovrebbe quasi sempre utilizzare il filtro di Lanczos</b>, ma dovete aspettarvi che molte operazioni, (come riscalatura e applicazione di filtri) siano pi&ugrave; lente. L'utilizzo del filtro di Lanczos a volte pu&ograve; produrre una differenza eccezionale nella qualit&agrave; percepita di stampa di un'immagine, quindi dovreste fare in modo che GIMP lo usi per impostazione predefinita.</li>
</ul>
 
<table width="100%"><tr><td align="center"><img src="images/gimpoptions1.png" alt="Interpolazione Lanczos" /></td></tr></table>
 
<p>Come accade per la maggior parte dei programmi per la creazione e la modifica di immagini, le impostazioni predefinite di GIMP sono pensate primariamente per immagini destinate a siti web, il che significa che la risoluzione &egrave; di gran lunga troppo bassa per la stampa. Quindi, per prima cosa, impostate la risoluzione predefinita a un <strong>minimo</strong> di 144 DPI. Ricordate che l'uso di queste risoluzioni pi&ugrave; alte provocher&agrave; la creazione di file di dimensioni molto maggiori, quindi potreste dover regolare anche le impostazioni di massimo utilizzo della memoria nelle preferenze di GIMP. </p>
 
<table width="100%"><tr><td align="center"><img src="images/gimpoptions3.png" alt="Impostazioni DPI predefinite" /></td></tr></table>
 
<p>L'altra aggiunta notevole &egrave; la capacit&agrave; (per ora a un livello molto semplice) di creare una prova colore a video (&ldquo;soft proof&rdquo;) con l'utilizzo della gestione del colore. Questa viene eseguita con LittleCMS (che &egrave; utilizzato anche da Scribus), e potete impostarla nelle preferenze. Ci&ograve; &egrave; utile se desiderate vedere l'aspetto dell'immagine in uno spazio colore CMYK quando sar&agrave; stampata o esportata in PDF. </p>
 
<table width="100%"><tr><td align="center"><img src="images/gimpoptions2.png" alt="Impostazioni per la gestione del colore" /></td></tr></table>
</body>
</html>
/trunk/Scribus/doc/it/plugin_howto.html
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>
/trunk/Scribus/doc/it/print3.html
0,0 → 1,21
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Strumenti per la stampa (2): la finestra di dialogo Stampa</title>
</head>
<h2>Strumenti per la stampa (2): la finestra di dialogo Stampa</h2>
<p>Se la vostra stampante e il sottosistema di stampa del vostro sistema operativo permettono la stampa diretta dall'interno di Scribus, specialmente se vi servite di una stampante PostScript, Scribus offre alcune funzioni per la stampa che non si trovano nella maggior parte degli altri programmi. &Egrave; importante osservare nuovamente che la disponibilit&agrave; di queste funzioni dipende dalla qualit&agrave; del driver della stampante. Inoltre, almeno su Windows, dove Scribus utilizza la &ldquo;Graphical Device Interface&rdquo;, dipende anche dalle funzioni che il produttore ha reso <i>accessibili</i> attraverso il driver. Per ragioni di usabilit&agrave;, il numero di opzioni potrebbe essere stato intenzionalmente limitato su questo sistema operativo. Di seguito descriveremo la finestra di dialogo Stampa per i sistemi operativi che utilizzano il sistema di stampa CUPS (Linux, *BSD, UNIX, Mac&nbsp;OS&nbsp;X).</p><br>
<table width="100%"><tr><td align="center"><img src="images/print-dialog1.png" alt="La finestra di dialogo Stampa" title="La finestra di dialogo Stampa"/></td></tr></table>
<h3>Destinazione della stampa</h3>
<p>La prima cosa che dovete decidere qui &egrave; se volete effettivamente stampare su carta (o su un supporto fisico simile) oppure &ldquo;stampare&rdquo; su un file, cio&egrave; creare un file PostScript, che in seguito pu&ograve; essere inviato a una tipografia in grado di utilizzare il PDF. Se non &egrave; installato alcun driver per la stampa, creare un file PostScript sar&agrave; la sola opzione disponibile.</p>
<h4>Opzioni della stampante</h4>
<p>La casella &ldquo;Comando alternativo per la stampa&rdquo; &egrave; importante solo su sistemi Linux e UNIX. Un esempio del suo utilizzo &egrave; l'uso di una specifica finestra di dialogo per la stampa in un particolare ambiente desktop, poich&eacute; tale finestra di dialogo potrebbe offrire funzioni aggiuntive (come esportazione PDF basata su Ghostscript), oppure un insieme ridotto di funzioni, che pu&ograve; facilitare la stampa diretta da Scribus per l'utente medio.</p>
<p>Come accennato prima, i sistemi operativi che usano CUPS (Common UNIX Printing System) per la stampa, di solito offrono la possibilit&agrave; di utilizzare un gran numero di funzioni per una data stampante, molte delle quali sono importanti solo per gli utenti esperti. Come si vede nella schermata sotto, tra questi vi sono il bilanciamento dei colori dell'inchiostro o le dimensioni delle goccioline di inchiostro. Se avete bisogno di un elevato livello di controllo sulla stampante locale, &egrave; consigliabile che vi serviate di un driver <a href="http://gutenprint.sourceforge.net/index.php">Gutenprint</a>, purch&eacute; ne esista uno per la vostra stampante. Scribus permette di utilizzare direttamente le funzioni dei driver Gutenprint via CUPS.</p><br>
<table width="100%"><tr><td align="center"><img src="images/print-dialog2.png" alt="Opzioni stampante fornite da CUPS" title="Opzioni stampante fornite da CUPS"/></td></tr></table>
 
<h3>Intervallo</h3>
<p>Le opzioni di questa parte della finestra di dialogo dovrebbero esservi familiari, almeno se avete mai stampato da un elaboratore di testi.</p>
<h3>Altre opzioni per la stampa</h3>
<p>Probabilmente non si sbaglia dicendo che la maggior parte delle funzioni nella parte inferiore della finestra di dialogo sono importanti solo per utenti professionali, il che significa che l'utente &ldquo;medio&rdquo; pu&ograve; ignorarle. Ci&ograve; significa anche che non &egrave; necessario che le spieghiamo in dettaglio qui, poich&eacute; esse sono (o dovrebbero essere) ovvie per gli utenti professionali.</p>
</body>
</html>
/trunk/Scribus/doc/it/fileproblems.html
0,0 → 1,80
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Problems with Opening Scribus Files</title>
</head>
<body>
<h2>Problems with Opening Scribus Files</h2>
 
<h3>Damaged Files</h3>
 
<h4>Parsing Errors</h4>
<p>One of the major reasons for a damaged file (any file, not just Scribus files) is an interrupted saving procedure, e.g. a power failure or a system crash while the program was writing the data to the storage medium (like a hard drive or a USB stick). Other reasons can be file system errors or a damaged storage medium. Since Scribus SLA (and the older SCD) files are Plain Text XML-based files, these files can also be damaged by users themselves if they open and edit the files in a text editor. </p>
<p>No matter what the reason for a damage to a particular file may be, the result will be that Scribus can&rsquo;t &ldquo;parse&rdquo; (i.e., in very general terms, read and interpret) the file&rsquo;s content, e.g. due to missing XML tags or invalid data. In such a case, Scribus will display a warning that indicates the line number of the file in which it stumbled across the error:</p>
 
<table width="100%"><tr><td align="center"><img src="images/file-error3.png" title="Indicator for a parsing error" alt="Indicator for a parsing error"/></td></tr></table>
 
<p>To fix damaged SLA and SCD files, a simple text editor is sufficient. For practical reasons, however, it&rsquo;s recommended that the text editor provide a little more features than, for instance, Notepad on Windows. At the very least, the text editor should be able to show line numbers and support XML syntax highlighting. In case you are unfamiliar with XML concepts like tags etc., you can file a <a href="bugreport.html">bug report</a> and upload the damaged file to the bugtracker. In general, you can expect the file to be fixed by the developers within 48 hours. Be aware, though, that fixing a file by the developers need not mean that all content can be restored, as not all of it may have been written to the storage medium before the error occured. Thus, repairing a file may only result in a file that can be opened by Scribus again.</p>
 
<h4>Other File Errors</h4>
<p>While it&rsquo;s relatively easy to repair SLA and SCD files, things are more complicated if you&rsquo;ve been saving a compressed version (SLA.GZ or SCD.GZ). In such a case you will have to use a tool that can either repair a damaged gzip archive or, if the latter is impossible, retrieve as much of the archive&rsquo;s content as possible.</p>
 
<h3>Documents Created with Another Version of Scribus</h3>
 
<h4>Files Created with an Earlier Version of Scribus</h4>
<p>When you open a file created with an earlier version of Scribus, you will see a warning that you may or may not want to ignore. You can ignore it if you are sure that the file won&rsquo;t have to be opened in an earlier version again, e.g. if you created the file yourself and simply upgraded to a newer Scribus version. If you&rsquo;re working in a team, you should <b>always</b> make sure that all team members use the same version of Scribus.</p>
 
<table width="100%"><tr><td align="center"><img src="images/file-error2.png" title="Warning about file format backward incompatibilty" alt="Warning about file format backward incompatibilty"/></td></tr></table>
 
<p>But what if you ignored the warning or saved the file inadvertently, knowing that your partner has to or wants to use an earlier version? Saving back to an older file format version isn&rsquo;t possible. What you can do in such a case is to <i>group</i> all items on every page and then copy each group to the Scrapbook, page by page. You can then send your Scrapbook to the person that uses the older version, because the Scrapbook format didn&rsquo;t change between versions. Be aware, though, that <i>linked text frames</i> on different pages cannot be re-created this way: You&rsquo;ll have to re-link them in the earlier version.</p>
<p>While every newer version of Scribus can open files created in older versions, including SCD and SCD.GZ files saved by early 0.x versions from more than a decade ago, you should <b>always</b> check the text layout, because the Scribus text layout algorithms have changed significantly over time. This measure of caution is especially important with older file versions, but it is recommended to always check the text layout if you open the file on another computer or after a font upgrade. While Scribus always does a <a href="fonts2.html">font check</a> during startup, it does not check for different font versions when it opens a file. Thus, different font versions or fonts with the same PostScript font name, but from different vendors/sources may result in broken text layout, e.g. unintended text overflow.</p>
<table border="1" align="center">
<tbody>
<tr>
<td><span style="color: red;"><i><b>A special note about files created with Scribus versions 1.3.5 to 1.4 Release Candidate 5:</b> An important fix to the text layout engine in Scribus 1.4 Release Candidate 6 may cause significant text layout changes in text frames with certain text layout features (e.g. First Line Offset) applied, so re-formatting of text may be necessary in files created in versions prior to 1.4RC6.</i></span></td>
</tr>
</tbody>
</table>
 
 
<h4>Files Created with a Later Version of Scribus or Non-Scribus Files</h4>
<p>Files created in later versions of Scribus cannot be opened by earlier ones. This is even true when both versions use the same file format, e.g. 1.3.9 and 1.4.0. Trying to open a file created in a later version with an earlier one will result in the following warning. This warning will also be displayed if you open a SLA, SLA.GZ, SCD or SCD.GZ file that is no Scribus file at all (there may be other programs that use these file extensions). The same goes, of course, for other file formats that can be opened by Scribus directly.</p>
 
<table width="100%"><tr><td align="center"><img src="images/file-error1.png" title="Indicator for a file that has been created with a later version or that isn&rsquo;t a Scribus file at all" alt="Indicator for a file that has been created with a later version or that isn&rsquo;t a Scribus file at all"/></td></tr></table>
<p>If you, for one reason or the other, can&rsquo;t use the latest stable release of Scribus, and your version supports the same file format, you can open the SLA file in a text editor and replace the Scribus version in the file header:</p>
<p>Example:</p>
<p><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;<br>
&lt;SCRIBUSUTF8NEW Version="1.4.0"&gt;</code></p>
<p>can be changed to:</p>
<p><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;<br>
&lt;SCRIBUSUTF8NEW Version="1.3.9"&gt;</code></p>
<p>Be aware, though, that you do so at your own risk, especially if you consider the changes made to the text layout engine since 1.4RC6.</p>
<h3>Safety Measures</h3>
<p>It may sound like a platitude, but every program and every operating system can crash, which means you may lose some or all of your work. Likewise, no computer is expected to run flawlessly forever and, like all material things, will cease working one day. Thus, the timeless hint &ldquo;save your file regularly&rdquo; also applies to Scribus. Fortunately, Scribus allows for automating the saving procedure to let you concentrate on your layout.</p>
<h4>Autosave</h4>
<p>To let Scribus save your results in regular intervals, you can activate &ldquo;Autosave&rdquo; and set the interval in the <a href="settings1.html#2">Document section</a> of the Document Setup/Preferences. In addition to automatically saving your Scribus document, Scribus also creates a copy of the document. The copy&rsquo;s file name consists of the original file name extended by the extension &ldquo;.autosave&rdquo;. Thus, the &ldquo;autosave&rdquo; copy of <code>myfile.sla</code> will be stored as <code>myfile.sla.autosave</code>. Should a SLA file have been damaged, you can always remove the &ldquo;.autosave&rdquo; extension and then open the &ldquo;autosaved&rdquo; version in Scribus. This procedure will give you the latest automatically saved version of your Scribus document.</p>
<h4>Emergency Backup Files</h4>
 
<h3>Other Potential Sources for Errors</h3>
 
<h4>Missing Images</h4>
<p>Images you have loaded into an <a href="WwImages.html">image frame</a> will not be stored in your Scribus file. Instead, Scribus will save the path to the image relative the Scribus file. When you open the Scribus file, Scribus will search for the image(s) used in the document in the paths stored in the file and the directory where the Scribus file itself is located. If you have moved either the Scribus file or the image(s) to another directory, Scribus probably won&rsquo;t find the image(s) and display empty image frames. You can then use <i>Extras&nbsp;&gt; Manage Images</i> to let scribus search for the new location of the image(s).</p>
<p>If you plan to exchange Scribus files with images between computers, you should always use <i>File&nbsp;&gt; Collect for Output</i> to make sure all images are included.</p>
<p>Note that bitmap <a href="WwFill.html">patterns</a> will also have to be treated like regular images.</p>
 
<h4>File Substitutions</h4>
<p>Scribus not only saves the paths to images but also paths to other file types used in connection with your documents. These are fonts and color profiles. Upon opening a file, you will be asked to substitute both file types. See the <a href="fonts1.html">font</a> and <a href="cms.html">color management</a> chapters for more information. Note that substituting fonts and/or color profiles may have consequences for your layout or color correctness. To avoid potential errors, you are advised to export these resources with your Scribus document by using <i>File&nbsp;&gt; Collect for Output</i>.</p>
 
<h4>Render Frames</h4>
<p>Since the content of <a href="WwRenderframes.html">Render Frames</a> will be rendered anew each time you open a file, you have to make sure that third party applications used for rendering content are installed and configured correctly if you are exchanging files between computers and/or platforms. Otherwise, the frames will remain empty.</p>
 
<h4>Settings/Preferences</h4>
<p>If, for no obvious reasons, a Scribus installation that used to work without any issues suddenly starts to behave strangely or doesn&rsquo;t work at all, the reason may be damaged <a href="settings1.html#20">Preferences</a> files. In case you are encountering any strange behavior of Scribus you can try to <b>rename</b> the hidden <code>.scribus</code> directory that contains these files and start Scribus anew. The program will then create new configuration files from scratch. This may or may not solve the issue. If it doesn&rsquo;t, the reason for your problem is probably unrelated to Scribus, e.g. a hardware issue or compatibility issues after an update of other components of your system, like a Windows update or a Qt4 update under Linux/UNIX. In such a case you can delete the newly created <code>./scribus</code> directory and restore the previously renamed folder. Of course this won&rsquo;t solve your problem, but at least you don&rsquo;t lose your previous default settings that way.</p>
<!--<hr>
See also:
<ul>
<li><a href="scribus-files.html">Scribus Files and File Formats</a></li>
</ul>-->
<br>
</body>
</html>
/trunk/Scribus/doc/it/scripterapi-font.html
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>
/trunk/Scribus/doc/it/short-words.html
21,7 → 21,7
<li><strong>tutti gli elementi</strong> - applica gli spazi protetti all'intero documento.</li>
</ul>
 
<p>La parte inferiore (&ldquo;Impostazioni lingua&rdquo;) sembra pi&ugrave;, ma concettualmente &egrave; un po' pi&ugrave; complicata. L'impostazione predefinita (&rdquo;Usa la stessa lingua dello stile&rdquo;) significa che Scribus user&agrave; <b>o</b> le impostazioni della lingua di sistema, <b>o</b> le <a href="settings1.html#1">impostazioni della lingua di Scribus</a>, <b>o</b> le impostazioni della lingua di un certo <a href="WwStyles.html">stile</a>, e il successivo prevale sempre sul precedente. Se disabilitate l'impostazione predefinita, potete far s&igrave; che Scribus appliche le mregole di una lingua diversa, ma (cos&igrave; come per le impostazioni di sistema, di Scribus e di stile) Scribus deve avere a disposizione le informazioni corrette sulla lingua che volete utilizzare. Se per una certa lingua non esiste una configurazione, dovrete crearla.</p>
<p>La parte inferiore (&ldquo;Impostazioni lingua&rdquo;) sembra pi&ugrave; semplice, ma concettualmente &egrave; un po' pi&ugrave; complicata. L'impostazione predefinita (&rdquo;Usa la stessa lingua dello stile&rdquo;) significa che Scribus user&agrave; <b>o</b> le impostazioni della lingua di sistema, <b>o</b> le <a href="settings1.html#1">impostazioni della lingua di Scribus</a>, <b>o</b> le impostazioni della lingua di un certo <a href="WwStyles.html">stile</a>, e il successivo prevale sempre sul precedente. Se disabilitate l'impostazione predefinita, potete far s&igrave; che Scribus appliche le mregole di una lingua diversa, ma (cos&igrave; come per le impostazioni di sistema, di Scribus e di stile) Scribus deve avere a disposizione le informazioni corrette sulla lingua che volete utilizzare. Se per una certa lingua non esiste una configurazione, dovrete crearla.</p>
 
<h4>Configurare il plugin Parole Brevi</h4>
<p>il plugin Parole Brevi utilizza un file di configurazione globale chiamato <code>scribus-short-words.rc</code>, che di solito si trova nella directory <code>$prefix/lib/scribus/plugins</code> (la directory effettiva pu&ograve; essere diversa, a seconda del sistema operativo e/o della posizione in cui Scribus &egrave; stato installato dalla vostra distribuzione o da voi). La struttura del file di configurazione &egrave; piuttosto semplice e non ha bisogno di molte spiegazioni: contiene un elenco di abbreviazioni per una data lingua, precedute o seguite da uno spazio e separate da virgole. La posizione dello spazio, prima o dopo un'abbreviazione, indica al plugin dove lo spazio protetto deve essere inserito. Ciascuna riga contenente le impostazioni deve iniziare con l'indicazione della lingua a cui si riferisce, quindi ad esempio <code>en</code> per l'inglese o <code>cs</code> per il ceco:</p>
/trunk/Scribus/doc/it/about1.html
0,0 → 1,105
<html><head>
 
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Il team di Scribus</title>
</head><body>
<h2>Il team di Scribus: i protagonisti (in ordine di apparizione)</h2>
 
<p><b>Franz Schmid (fschmid):</b> &ldquo;il nostro Linus&nbsp;&hellip;&rdquo;. L'autore originale e principale sviluppatore; programmatore per un'azienda industriale.</p>
 
<p><b>Peter Linnell (mrdocs):</b> cominci&ograve; con i test sulla versione 0.3.6, si incaric&ograve; di scrivere la documentazione per la 0.5.0; collaudatore, creatore dei pacchetti RPM, primo webmaster del sito di Scribus; consulente per la prestampa e l'informatica per aziende editoriali e di e-commerce.</p>
 
<p><b>Craig Bradney (MrB):</b> cominci&ograve; con la versione 1.1.1; si occupa di programmazione e test, ha creato i siti docs.scribus.net e bugs.scribus.net, gestisce i canali IRC su freenode.net; responsabile informatico di una grande azienda del settore e-commerce.</p>
 
<p><b>Petr Van&#283;k:</b> cominci&ograve; con la versione 1.1.4; specialista di plugin, ha creato parecchi plugin e lo &ldquo;how-to&rdquo; per la scrittura di plugin per Scribus; tecnico informatico.</p>
 
<p><b>Riku Leino (Tsoots):</b> cominci&ograve; con la versione 1.1.5; ha scritto il plugin per i modelli di documento e gli importatori OpenOffice.org/HTML per la 1.2.2; responsabile informatico di una grande organizzazione non-profit finlandese.</p>
 
<p><b>Andreas Vox (pronuncia: [fox]) (avox):</b> cominci&ograve; con la 1.3.0; autore della prima versione nativa per Mac&nbsp;OS&nbsp;X, specialista su caratteri e PostScript, detesta il C++ e apprezza la buona impaginazione; programmatore.</p>
 
<p><b>Jean Ghali (jghali):</b> si occupa della versione nativa per Windows e della maggior parte del codice per la gestione del colore, cacciatore di bug di gran talento; tecnico informatico e di prestampa.</p>
 
<p><b>Oleksandr Moskalenko (malex):</b> prepara i pacchetti di Scribus per Debian, contribuisce all'internazionalizzazione e alla traduzione, gestisce il sito di Scribus, rappresenta il progetto alla GSoC; biologo molecolare.</p>
 
<p><b>Pierre Marchand (pierremarc);</b> si occupa di caratteri, spazio di lavoro, composizione e impaginazione del testo. Autore di FontMatrix, programmatore per un'azienda editoriale.</p>
 
<p><b>Christoph Sch&auml;fer (christoph_s):</b> collaudatore e cacciatore di bug per la versione di sviluppo, redattore del wiki, traduttore e revisore della documentazione, uno dei principali autori del manuale ufficiale e della guida in linea di Scribus.</p>
 
<p><b>Hermann Kraus (Herm):</b> autore del plugin &ldquo;Cornice Rendering&rdquo; per la versione 1.4, integrazione di GraphicsMagick e UniConvertor nella 1.5.</p>
 
<p><b>Jain Basil Aliyas (jainbasil)</b>: autore dei filtri d'importazione XTG e IDML, lavora sullo scripter Scribus di nuova generazione.</p>
 
<p><b>Paul Smedley (smedles):</b> autore e manutentore della versione per OS/2.</p>
 
 
<h2>Il resto del cast e gli ex sviluppatori (in nessun particolare ordine):</h2>
 
<p><b>Paul F. Johnson (Nodoid):</b> cominci&ograve; a contribuire patch per la 0.8, si &egrave; occupato di revisione e ottimizzazione del codice, ha scritto il documento &ldquo;Coding Standards&rdquo;. </p>
 
<p><b>Steve Callcott (sjc):</b> autore del plugin in Python &ldquo;Anteprima caratteri&rdquo;, che dimostr&ograve; il vero potere dello scripter Python di Scribus; si occupa di controllo di sistemi, elettronica di consumo, sviluppo e assistenza software su misura.</p>
 
<p><b>Alessandro Rimoldi:</b> ha contribuito alla correzione di errori nello Scripter e alla messa a punto del codice, mentor per la GSoC.</p>
 
<p><b>Jean-Jacques Sarton:</b> ha fornito alcune importanti patch per il miglioramento della gestione delle immagini e di altre funzioni. Ha aggiunto a Scribus la possibilit&agrave; di lanciare applicazioni di grafica esterne.</p>
 
<p><b>Alistair Robinson:</b> ha contribuito alcuni importanti aggiustamenti per la gestione dei caratteri nelle prime versioni di Scribus, e ha scritto un intelligente hack di GIMP per la creazione di immagini TIFF CMYK.</p>
 
<p><b>Maciej Hanski:</b> traduttore in polacco e uno dei principali collaboratori al wiki di Scribus.</p>
 
<p><b>Yves Ceccone:</b> il primo traduttore in francese, autore di molti degli script Python di esempio forniti con Scribus, si &egrave; occupato di gran parte della documentazione di Scribus in francese.</p>
 
<p><b>Craig Ringer:</b> ha lavorato allo scripter, al sistema per la gestione del codice e la generazione del programma, e al test delle prime versioni per Windows e Mac&nbsp;OS&nbsp;X. Ha contribuito aggiustamenti per Python e altri miglioramenti; responsabile IT/DTP per un quotidiano. </p>
 
<p><b>Martin Costabel:</b> mantiene la versione di Scribus e le librerie di supporto per Fink, rendendo possibile l'uso di Scribus in ambiente X11 su Mac&nbsp;OS&nbsp;X.</p>
 
<p><b>Niyam Bhushan:</b> autore di un eccezionale corso pratico per Scribus.</p>
 
<p><b>Marti Maria:</b> ha risposto a una montagna di domande sulla gestione del colore, e ha dato littleCMS al mondo open source.</p>
 
<p><b>Johannes R&uuml;schel:</b> ottimo cacciatore di bug, gi&agrave; traduttore in tedesco.</p>
 
<p><b>Alexandre Prokoudine:</b> traduttore in russo, ha aiutato molto a risolvere problemi di internazionalizzazione e a migliorare l'interfaccia utente; autore professionale di documentazione tecnica.</p>
 
<p><b>Lukasz Jernas (DeeJay1):</b> manutentore del pacchetto per PLD Linux.</p>
 
<p><b>Howard White:</b> collaudo, collaudo e ancora collaudo; tecnico di prestampa in pensione.</p>
 
<p><b>Cedric G&eacute;my:</b> collaudo e contributi per l'interfaccia utente, mentor GSoC; professore di grafica e autore di libri su programmi di grafica open source.</p>
 
<p><b>Gregory Pittman:</b> uno dei principali contributori al wiki e alla documentazione di Scribus, uno dei principali autori del manuale ufficiale e della guida in linea; autore di molti utili script per Scribus; neurologo.</p>
 
<p><b>Volker Ribbert:</b> cominci&ograve; con la traduzione tedesca della documentazione.</p>
 
<p><b>Louis Desjardins:</b> organizzatore del Libre Graphics Meeting, si &egrave; occupato di test e ha suggerito molti miglioramenti. Traduttore della documentazione originale in francese.</p>
 
<p><b>Frederic Dubuy:</b> traduttore della documentazione originale in francese.</p>
 
<p><b>François Lanct&ocirc;t:</b> traduttore della documentazione originale in francese.</p>
 
<p><b>Eirik &Oslash;verby:</b> si occupa con perseveranza della manutenzione dei nostri server.</p>
 
<p><b>Gora Mohanty:</b> autore del plugin per il controllo ortografico.</p>
 
<p><b>Elvis Stansvik:</b> autore della funzione di ricerca per lo &ldquo;Schema documento&rdquo; e creatore della gestione delle tabelle nella versione 1.5svn.</p>
 
<p><b>Tomas Mecir:</b> creazione del controllo su orfani e vedove e altri miglioramenti nella versione 1.5svn.</p>
 
<p><b>Michael Doubez</b></p>
 
<p><b>Cezary Grabski:</b> ha fornito un gran numero di correzioni e miglioramenti al sistema di gestione del testo e ad altre parti del programma.</p>
 
<p><b>Marcus Holland-Moritz:</b> miglioramenti delle prestazioni per documenti con immagini grandi.</p>
 
<p><b>Christian T&ouml;pp</b></p>
 
<p><b>Andy Fitzsimmon:</b> creatore della schermata iniziale di Scribus.</p>
 
<p><b>Andreas Nilsson:</b> icone dal Progetto Tango.</p>
 
<p><b>Jakub Steiner:</b> icone dal Progetto Tango.</p>
 
<p><b>Antoine Cailliau:</b> icone dal Progetto Tango.</p>
 
<p><b>Alessandro Levati:</b> traduttore della guida in linea in italiano.</p>
</body></html>
 
/trunk/Scribus/doc/it/install5.html
0,0 → 1,79
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 
<title>Compilare e installare Scribus 1.4+ su Mac&nbsp;OS&nbsp;X</title>
</head>
 
<body>
<h2>Compilare e installare Scribus 1.4+ su Mac&nbsp;OS&nbsp;X</h2>
 
<p>Questo documento descrive sommariamente la procedura per generare Scribus 1.4 o superiore dal codice sorgente SVN su Mac&nbsp;OS&nbsp;X. Non &egrave; descritta (per ora) la procedura per creare un vero e proprio pacchetto di installazione.</p>
 
<h3>Ci&ograve; che vi serve:</h3>
 
<ul>
<li>il programma di installazione di MacPorts (gi&agrave; noto come DarwinPorts nelle versioni precedenti la 1.5)</li>
 
<li>Qt 4.4.x, della Trolltech</li>
 
<li>XCode, della Apple, che trovate nel DVD di installazione di OS X, o che potete prelevare da http://www.apple.com</li>
 
<li>il codice sorgente di Scribus, che potete prelevare da SVN</li>
</ul>
 
<h3>Compilazione e installazione</h3>
 
<p>Questi sono i passaggi per compilare e installare Scribus 1.4 su OS X/Aqua:</p>
 
<ul>
<li>installate X11 (lo trovate sui CD di OS X oppure sul sito della Apple)</li>
 
<li>installate <a href="http://developer.apple.com/tools/xcode/">XCode</a> (lo trovate sui CD di OS X oppure nella sezione per gli sviluppatori sul sito della Apple)</li>
 
<li>installate MacPorts (potete prelevarlo da <a href="http://www.macports.org">www.macports.org</a>)</li>
 
<li>installate Qt 4.4.0+ per OS X (potete prelevarlo da <a href="http://www.trolltech.com">www.trolltech.com</a>)</li>
</ul>
 
<p>Poi dovete installare alcuni pacchetti da MacPorts. Eventuali dipendenze necessarie saranno installate automaticamente, se non sono gi&agrave; presenti sul vostro sistema. Se avete gi&agrave; installato MacPorts per altro software, dovreste eseguire i comandi <code>sudo port selfupdate</code> e <code>sudo port upgrade installed</code> per far s&igrave; che vengano installate le versioni pi&ugrave; recenti delle applicazioni e librerie gi&agrave; presenti sul sistema.</p>
 
<ul>
<li>installate CMake (<code>sudo port install cmake</code> ) </li>
 
<li>installate freetype2 (<code>sudo port install freetype</code>). La versione disponibile su MacPorts &egrave; migliore di quella fornita con OS X.</li>
 
<li>installate lcms (<code>sudo port install lcms</code>). Questo installa anche libjpeg, zlib e libtiff.</li>
 
<li>installate Cairo (<code>sudo port install cairo</code>). Questo installa anche fontconfig.</li>
 
<li>installate libxml2 (<code>sudo port install libxml2</code>).</li>
 
<li>installate Subversion (<code>sudo port install subversion</code>) OPPURE installate subversion da un'altra fonte.</li>
 
<li>opzionale, ma consigliato: installate Ghostscript: <code>sudo port install ghostscript</code></li>
 
<li>create una directory in cui scaricare il codice sorgente di Scribus (ad esempio, nel Terminale, <code>mkdir -p ~/scribus/14</code>)</li>
 
<li>spostatevi in questa directory (<code>cd ~/scribus/14</code>)</li>
</ul>
 
<p>Prelevate il codice sorgente di Scribus da SVN:</p>
 
<ul>
<li><code>svn co svn://scribus.info/Scribus/branches/Version140</code></li>
 
<li>create una directory per la compilazione (<code>mkdir builddir</code>)</li>
 
<li>spostatevi nella directory per la compilazione (<code>cd builddir</code>)</li>
 
<li>Lanciate il comando cmake: <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>Ed ora, se tutto &egrave; andato bene, Scribus 1.4 &egrave; pronto per l'uso sul vostro OS X.</p>
</body>
</html>
/trunk/Scribus/doc/it/toolbox16.html
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>Coloro che provengono da MacOSX o anche da una versione pi&ugrave; vecchia di MacOS, possono sentire la mancanza di un buon strumento grafico per la gestione dei caratteri. Ecco dunque <a href="http://fontmatrix.net">Fontmatrix</a>. &Egrave; un programma giovane, ma ha tutti gli strumenti essenziali per gestire i tipi di carattere, sia singolarmente, sia in gruppi per mezzo di &ldquo;etichette&rdquo;. Fontmatrix &egrave; anche in grado di visualizzare i tipi di carattere in un testo di esempio, e di farlo in dimensioni variabili; e pu&ograve; visualizzare anche singoli glifi. Ancora meglio, Fontmatrix ha un ottime capacit&agrave; di gestire i caratteri OpenType, e in futuro saranno ulteriormente migliorate.</p>
 
<p>Fontmatrix non attiva i caratteri &ldquo;al volo&rdquo; per le applicazioni gi&agrave; aperte, ma pu&ograve; attivare e disattivare caratteri velocemente senza interferire con i caratteri di sistema, che devono essere sempre utilizzabili da tutte le applicazioni. Quindi, per lavorare con Scribus o altre applicazioni di grafica, basta visualizzare e attivare i tipi di carattere che vi servono, e riavviare l'applicazione interessata. Infine, Fontmatrix pu&ograve; creare dei campionari di caratteri, che sono documenti PDF che mostrano ciascun tipo di carattere. </p>
 
<br /><br />
<table width="100%"><tr><td align="center"><img src="images/fontmatrix.png" alt="Fontmatrix con la visualizzazione dell'elegante carattere Gentium." /></td></tr></table>
</body>
</html>
/trunk/Scribus/doc/it/readme-os2.html
0,0 → 1,48
<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 Warp4&#0174; and eComStation&#0153;</h2>
 
<p>The Scribus Team is much obliged to Paul Smedley for taking pains over porting Scribus to the OS/2 and eComStation platforms.</p>
 
<p>The Scribus Team also wants to thank <a href="http://www.serenity-systems.com/">Serenity Systems</a> for supporting development and testing of the OS/2 and eComStation port.</p>
 
<table width="100%"><tr><td align="center"><img src="images/scribus-os2.png" alt="Scribus on eComStation" title="Scribus on eComStation" /></td></tr></table>
 
<h4>Requirements</h4>
<p>To use Scribus on OS/2 and eCS, the following requirements have to be met:
<ul>
<li>A copy of libc063.dll and gcc445.dll. Both files need to copied to <code>C:\OS2\DLL</code> (OS/2) or <code>C:\ECS\DLL</code> (eComStation).</li>
<li>It also requires the Qt4 GA dll&rsquo;s, which can be downloaded from http://svn.netlabs.org/qt4</li>
<li>Note that some of the abovementioned libraries are available as WarpIn packages from http://www.netlabs.org. To successfully install all *.wpi files, you need to have at least WarpIn 1.0.15 installed.</li>
<li>Ghostscript and Python 2.6 (both available from http://os2ports.smedley.info) are required to support some functionality. For instance, Python scripts won&rsquo;t work if Python is missing. The print preview and EPS import will not work if Ghostscript isn&rsquo;t available.</li>
<li>As of eComStation 2.0, Scribus 1.3.8 is being shipped with the installation CDs, so by installing this older version from the Add-on CD, all required components are already available and properly installed on your system. Thus, you can easily download the latest Scribus version and use it as described below.</li>
</ul>
</p>
 
<h4>Installation</h4>
<p>The Scribus version for OS/2 and eCS is not being shipped with an installer. All you need to do is download the ZIP file from <a href="http://sourceforge.net/projects/scribus/files/">Sourceforge</a> (the OS/2 and eCS version is the ZIP file with &ldquo;OS2&rdquo; in the file name) and unzip the archive to wherever you want. Then enter the extracted <code>SCRIBUS-1.4.x-OS2-date\scribus</code> directory, where &ldquo;x&rdquo; is a placeholder for the respective Scribus version number, and &ldquo;date&rdquo; stands for the creation date of your Scribus version, e.g. <code>20110128</code> (=28 January 2011) and double-click the <code>scribus.exe</code> file. You can also start Scribus from the command prompt.</p>
<p><i>Note that you have to extract the content of the ZIP file to a partition that uses a file system which supports long file names. FAT16 does <b>not</b> support long file names, while the existing FAT32 or even NTFS file system drivers for OS/2 and eCS are experimental at best, so the safest bet is to use a native IBM file system like HPFS (the OS/2 and eCS default FS) or JFS.</i></p>
 
<h4>Installing and Configuring Ghostscript</h4>
<p>Like Scribus, Ghostscript doesn&rsquo;t come with an installer. Simply download and extract the ZIP file from the link mentioned above. To configure Scribus for the use of Ghostscript, open the <i>File > Preferences</i> dialog in Scribus, then go to the &ldquo;External Tools&rdquo; tab. Under &ldquo;PostScript Interpreter&rdquo; you can either enter the path to the Ghostscript executable file manually or use the file dialog by clicking on &ldquo;Change&nbsp;...&rdquo;. The name of the executable is <code>gsos2.exe</code>, and it&rsquo;s located in the subdirectory <code>\bin</code>, so the path to the file may look like this: <code>X:\GHOSTSCRIPT-900-OS2-date\GS900OS2\bin\gsos2.exe</code>.</p>
 
<h4>Known issues</h4>
<p>
<ul>
<li>Printing support is not complete, but PDF export is. You can easily print via Adobe Reader or another PDF viewer as a temporary workaround.</li>
<li>As for Adobe Reader on OS/2, please read the detailed hints in the <a href="toolbox1.html">toolbox section</a>.</li>
</ul>
</p>
 
<h4>A Special Note to OS/2 and eComStation Users</h4>
 
<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>If you like this software and want to support continued OS/2 and eCS 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>You can also sponsor/support the <a href="http://www.mensys.com/NetlabsQT4">Qt4 for OS/2 project</a> &ndash; without the Netlabs Qt4 project, this port could not exist!</p>
 
</body>
</html>
/trunk/Scribus/doc/it/scripterapi-page.html
0,0 → 1,118
<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 document page margins as a (top, left, right, bottom) tuple in the document's current units. See UNIT_&lt;type&gt; constants and <a href="#-getPageSize">getPageSize</a>().</p></dd>
 
<dt><a name="-getPageNMargins"><strong>getPageNMargins</strong></a>(...)</dt>
<dd><code>getPageNMargins(nr)</code>
<p>Returns a tuple with a particular page's margins measured in the document's 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 document 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="-getPageNSize"><strong>getPageNSize</strong></a>(...)</dt>
<dd><code>getPageNSize(nr) -&gt; tuple</code>
<p>Returns a tuple with a particular page's size 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>
/trunk/Scribus/doc/it/scripterapi-layer.html
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>
/trunk/Scribus/doc/it/color2.html
21,7 → 21,7
 
<h4>Linux/UNIX:</h4>
<p>Se avete installato Scribus per mezzo di un sistema di gestione dei pacchetti come RPM, DEB o BSD Ports, i file delle raccolte devono essere copiati in <code>/usr/lib/scribus/swatches</code> o <code>/usr/local/lib/scribus/swatches</code>. L'esatta posizione dipende dalla configurazione del gestore di pacchetti di ciascuna distribuzione.</p>
<p>Se avete compilato Scribus personalmente dovete copiare i file delle raccolte in <code>installation_directory/share/scribus/swatches</code>.</p>
<p>Se avete compilato Scribus personalmente dovete copiare i file delle raccolte in <code>installation_directory/lib/scribus/swatches</code>.</p>
<p>Se non avete permessi di root, potete anche copiare i file in <code>/home/user_name/.scribus/swatches/locked</code>.</p>
<p>Se la cartella <code>locked</code> non esiste, dovrete crearla.</p>
<h4>Mac OS X</h4>
/trunk/Scribus/doc/it/scripterapi-color.html
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>
/trunk/Scribus/doc/it/images/table-import-2.png
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_guides1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_guides1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/mpage3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/mpage3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Cover_en1-page1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Cover_en1-page1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_gutenberg.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_gutenberg.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt12.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt12.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt16.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt16.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/editcols1a.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/editcols1a.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vectimp2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vectimp2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons5.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/colormanager2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/colormanager2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/printpreview.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/printpreview.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-tetradic.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-tetradic.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht6.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/result.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/result.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_searching.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_searching.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt21.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt21.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/spot.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/spot.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/editcols1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/editcols1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/file-error3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/file-error3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/fonts.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/fonts.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_translatescaling.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_translatescaling.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/rf3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_magazine.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_magazine.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/resene-pal.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/resene-pal.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf7.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Index: Scribus/doc/it/images/eps-imp4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/eps-imp4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-pdf-imp.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-pdf-imp.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/htmlimport.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/htmlimport.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/print-dialog1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/print-dialog1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/fileimport.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/fileimport.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gradient_adjuster1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gradient_adjuster1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gradient_adjuster_vector.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gradient_adjuster_vector.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_new_report3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_new_report3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt17a.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt17a.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdfx1a-lo.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdfx1a-lo.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_dialogb.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_dialogb.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/boundingbox1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/boundingbox1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab5.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prop_shape.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prop_shape.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt4.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab5.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/colorwheel.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/colorwheel.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab9.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab9.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/shape_edit.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/shape_edit.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt8.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt8.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs-mac-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs-mac-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/multipledup_rows.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/multipledup_rows.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cms-gamut2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cms-gamut2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/lprof.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/lprof.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gimpoptions3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gimpoptions3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_document1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_document1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/table-import-3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/table-import-3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab7a.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab7a.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-gsview.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-gsview.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rgb.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/rgb.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/shapes8.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/shapes8.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cmsmodify1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cmsmodify1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab11.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab11.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/mpage4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/mpage4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/RYB_color_wheel.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/RYB_color_wheel.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/layers1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/layers1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/patterns1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/patterns1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt13.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt13.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt17.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt17.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/colrs-mgt1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/colrs-mgt1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vectimp3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vectimp3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-splitcompl.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-splitcompl.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/context_shape.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/context_shape.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text-frame-link.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text-frame-link.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/fonts2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/fonts2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/xnview.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/xnview.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/editcols2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/editcols2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/insert-frame-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/insert-frame-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/eps-imp1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/eps-imp1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/geometry.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/geometry.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-analogous.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-analogous.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/eps-imp5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/eps-imp5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vector-advanced.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vector-advanced.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/polygons.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/polygons.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/scribus-os2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/scribus-os2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/print-dialog2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/print-dialog2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-warning.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-warning.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/missing-gs.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/missing-gs.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-bookbinder.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-bookbinder.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/multipledup_rotation.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/multipledup_rotation.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/htmlstyle.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/htmlstyle.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-triadic.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-triadic.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt17b.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt17b.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/edit_shapes.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/edit_shapes.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_my_view.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_my_view.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/polygons1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/polygons1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/squat_tux.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/squat_tux.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab6.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt5.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab6.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt9.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt9.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/swdialog.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/swdialog.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/geometry1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/geometry1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/nodes_edit.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/nodes_edit.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_translateskewing.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_translateskewing.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cw-compl.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cw-compl.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vector-clipart.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vector-clipart.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/docheader1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/docheader1.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab7b.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab7b.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/multipledup_copies.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/multipledup_copies.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/alert.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/alert.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/mpage1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/mpage1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab12.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab12.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/mpage5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/mpage5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/node_edit_close.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/node_edit_close.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt10.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt10.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/layers2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/layers2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdfx3-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdfx3-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/patterns2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/patterns2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/duotone-imp2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/duotone-imp2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdfxintent.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdfxintent.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt14.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt14.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/preflight-v.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/preflight-v.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt18.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt18.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons3.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/colrs-mgt2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/colrs-mgt2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/lilyp.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/lilyp.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/SwB.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/SwB.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vectimp4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vectimp4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/dtp-studio.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/dtp-studio.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/plot1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Index: Scribus/doc/it/images/oogettext1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/oogettext1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/ink-cov.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/ink-cov.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht4.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_signup.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_signup.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/qsg-col1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/qsg-col1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/file-error1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/file-error1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/editcols3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/editcols3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/insert-frame-2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/insert-frame-2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Index: Scribus/doc/it/images/eps-imp2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/eps-imp2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/round_rectangle.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/round_rectangle.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new6.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_new_report1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_new_report1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_9parts.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_9parts.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab7.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab7.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/scribus-pres1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/scribus-pres1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/colrs-caricature.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/colrs-caricature.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt6.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab7.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab7.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/DrawLatexFrame.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/DrawLatexFrame.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/style_manager7.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/style_manager7.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/register.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/register.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt18b.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt18b.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gimpoptions1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gimpoptions1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/fontmatrix.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/fontmatrix.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/table-import-1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/table-import-1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/docheader2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/docheader2.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/frame_shape_flow.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/frame_shape_flow.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/mpage2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/mpage2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/batik1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/batik1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab11b.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab11b.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt11.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt11.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt15.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt15.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-jpdf.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-jpdf.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/sadie4by2b.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/sadie4by2b.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/contourline_flow.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/contourline_flow.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt19.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt19.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vectimp1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vectimp1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/combine_polygons4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/combine_polygons4.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/vectimp5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/vectimp5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-inkscape.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-inkscape.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/plot2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Index: Scribus/doc/it/images/cmyk.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cmyk.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/skewing.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/skewing.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdf-form-ht5.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdf-form-ht5.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text-frame-unlink.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text-frame-unlink.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/tb-libreoffice.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/tb-libreoffice.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf-error1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/rf-error1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt20.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt20.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/import-pdfimage.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/import-pdfimage.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/numb-sections.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/numb-sections.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/qsg-col2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/qsg-col2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/file-error2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/file-error2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/rf2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_translaterotation1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_translaterotation1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rf6.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Index: Scribus/doc/it/images/eps-imp3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/eps-imp3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gradient_adjuster.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gradient_adjuster.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/pdfxcolor.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/pdfxcolor.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/duotone-imp.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/duotone-imp.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_translateskewing1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_translateskewing1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/printer2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/printer2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_goldenmean.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_goldenmean.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_flow.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_flow.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/rgb-cmyk.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/rgb-cmyk.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/new3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/new3.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/boundingbox.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/boundingbox.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Mantis_new_report2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Mantis_new_report2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/krita1.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/jpeg
/Scribus/doc/it/images/krita1.jpg
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/jpeg
\ No newline at end of property
Index: Scribus/doc/it/images/CMakeLists.txt
===================================================================
--- Scribus/doc/it/images/CMakeLists.txt (revision 17465)
+++ Scribus/doc/it/images/CMakeLists.txt (revision 17471)
@@ -3,7 +3,7 @@
)
#Install our image files
-FILE( GLOB SCRIBUS_DOC_IT_IMAGES_FILES *.jpg *.png )
+FILE( GLOB SCRIBUS_DOC_EN_IMAGES_FILES *.jpg *.png )
-INSTALL(FILES ${SCRIBUS_DOC_IT_IMAGES_FILES} DESTINATION ${DOCDIR}it/images)
+INSTALL(FILES ${SCRIBUS_DOC_EN_IMAGES_FILES} DESTINATION ${DOCDIR}en/images)
/trunk/Scribus/doc/it/images/text_tab4.png
Cannot display: file marked as a binary type.
svn:mime-type = image/png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt3.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt3.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab4.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab4.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/text_tab8.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/text_tab8.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/scribus-pres2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/scribus-pres2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Rembrandt7.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Rembrandt7.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/transform_translaterotation.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/transform_translaterotation.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/givelife1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/givelife1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/prefs_fibonacci.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/prefs_fibonacci.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/line_tab.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/line_tab.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/cms-gamut1.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/cms-gamut1.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/povray.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/povray.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/style_manager8.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/style_manager8.png
Property changes:
Added: svn:executable
## -0,0 +1 ##
+*
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/gimpoptions2.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/gimpoptions2.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/images/Scripter.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = image/png
/Scribus/doc/it/images/Scripter.png
Property changes:
Added: svn:mime-type
## -0,0 +1 ##
+image/png
\ No newline at end of property
Index: Scribus/doc/it/scripterapi-textframes.html
===================================================================
--- Scribus/doc/it/scripterapi-textframes.html (nonexistent)
+++ Scribus/doc/it/scripterapi-textframes.html (revision 17471)
@@ -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 1 if there are overflowing characters in text frame "name", 0 if not. 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>
Index: Scribus/doc/it/toolbox1.html
===================================================================
--- Scribus/doc/it/toolbox1.html (nonexistent)
+++ Scribus/doc/it/toolbox1.html (revision 17471)
@@ -0,0 +1,23 @@
+<html>
+<head>
+        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+        <title>Adobe Reader </title>
+</head>
+<A>
+<h2>Adobe Reader</h2>
+
+<p>Adobe Reader &egrave; uno degli strumenti essenziali da usare con Scribus. Serve principalmente per visualizzare documenti, ma ha alcune funzioni avanzate che non sono presenti in alcun altro visualizzatore PDF, come la piena capacit&agrave; di eseguire JavaScript con documenti PDF e quella di fornire informazioni dettagliate incluse nel PDF e visualizzabili soltanto in Adobe Reader.</p>
+
+<p>In generale, non consigliamo di valutare la correttezza del colore nell'applicazione Anteprima di Mac o nei visualizzatori PDF open source.</p>
+
+<p>Inoltre, anche se il PDF &egrave; divenuto uno standard ISO, la Adobe ha inventato il PostScript e il PDF, che &egrave; basato sul PostScript, e ha un incentivo commerciale a promuovere il PDF e il rispetto degli standard su tutte le piattaforme.</p>
+<h3>Suggerimenti per gli utenti di Scribus:</h3>
+<p><strong>Consigliamo fortemente di aggiornarvi alla pi&ugrave; recente versione di Adobe Reader</strong>. In poche parole, non esiste nient'altro con migliori capacit&agrave; di visualizzare correttamente i documenti PDF. Per quante obiezioni possiate avere nei confronti delle versioni pi&ugrave; vecchie (e ve n'erano di sostanziali, soprattutto su Linux), nelle versioni successive, specialmente dopo la 7.0.9, la grande maggioranza dei problemi &egrave; risolta. E anche se spesso &egrave; liquidato come &ldquo;divora-risorse&rdquo;, &egrave; molto pi&ugrave; stabile, contiene meno errori e viene caricato pi&ugrave; velocemente rispetto alle versioni pi&ugrave; vecchie. Su Linux ora ha un aspetto moderno. Le versioni dopo la 7.0.9 sono in grado di stampare direttamente tramite CUPS e offrono molte opzioni aggiuntive per la stampa. <strong>Se riscontrate problemi con documenti PDF generati da Scribus quando vengono aperti in altri visualizzatori, dovreste controllare se sono presenti anche su Reader 7 o successivo, prima di considerarli errori e segnalarli al team di Scribus.</strong></p>
+<p>Uno dei principali vantaggi delle pi&ugrave; recenti versioni di Adobe Reader &egrave; la capacit&agrave; di &ldquo;appiattire&rdquo; le trasparenze nei file PDF 1.4+. Questa caratteristica &egrave; importante, perch&eacute; vi sono tipografie non in grado di stampare PDF con trasparenze; inoltre lo standard PDF/X-3, che oggi &egrave; richiesto da molte tipografie, non consente l'uso di trasparenze. Anche se l'appiattimento da PDF a PDF &egrave; presente solo in Adobe Acrobat, Adobe Reader permette di creare un file PostScript &ldquo;appiattito&rdquo; tramite la finestra di dialogo di stampa. Il file PostScript cos&igrave; ottenuto pu&ograve; essere riconvertito in PDF con GSview o con uno strumento da riga di comando.</p>
+<h4>Problemi noti</h4>
+<p>Siamo informati che possono verificarsi errate corrispondenze di colore quando si visualizzano PDF con qualche tipo di trasparenza in file PDF 1.4+. La Adobe &egrave; stata informata di questo problema.</p>
+<p>Dovreste sempre fare in modo che le vostre applicazioni siano aggiornate alla versione pi&ugrave; recente, per far s&igrave; che il vostro sistema sia sicuro. Il formato PDF offre grandi vantaggi, ma &egrave; divenuto obiettivo di creatori di software maligno e attacchi via JavaScript. In base alla vostra situazione, potrebbe essere consigliabile disabilitare l'esecuzione di JavaScript nei vostri visualizzatori PDF quando questa funzione non vi serve.</p>
+<h3>Nota per gli utenti di OS/2 ed eComStation</h3>
+<p>Purtroppo la Adobe non fornisce pi&ugrave; nuove versioni di Adobe Reader per OS/2. L'ultima versione che, a quanto risulta, funziona su queste piattaforme &egrave; la 5.1, e richiede un ambiente di runtime aggiuntivo. L'ambiente di runtime pu&ograve; essere prelevato <a href="http://www.os2site.com/sw/dev/InnoTek/innotekruntime_112b20.exe">qui</a>. Il programma di installazione di AR si trova <a href="http://www.os2site.com/sw/util/pdf/os2kitacrobatreader51preview1.exe">qui</a>.</p>
+</body>
+</html>
Index: Scribus/doc/it/download.html
===================================================================
--- Scribus/doc/it/download.html (nonexistent)
+++ Scribus/doc/it/download.html (revision 17471)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Download</title>
+</head>
+<body>
+
+<h2>Scribus Download</h2>
+<p>Scribus is being updated on a regular basis. If you always want to use the latest and greatest stable Scribus version, here are the download resources:</p>
+<h3>Pre-compiled Binaries</h3>
+<p>Pre-compiled binaries for Mac OS X, OS/2 Warp4/eComStation and Windows are available from our <a href="http://sourceforge.net/projects/scribus/files/">Sourceforge repository</a>.</p>
+<p>RPM packages for most RPM-based Linux distributions are available mrdocs' <a href="http://download.opensuse.org/repositories/home:/mrdocs">RPM repository</a>. Simply add the repository for your distribution to your package manager (YaST, yum etc.) to update Scribus automatically.</p>
+<p>For DEB-based distributions (Debian, *buntu), please read the <a href="install-dpkg.html">installation instructions</a>.</p>
+<h3>Source Code</h3>
+<p>Along with the binaries for Mac OS X, OS/2 Warp4/eComStation and Windows, the Scribus Team also makes the Scribus source code of every release available via <a href="http://sourceforge.net/projects/scribus/files/">Sourceforge</a>.</p>
+<p>If you want to enjoy the latest bugfixes and feature enhancements that have been added to the source code, but haven't been released yet, you need to check out <a href="install1.html">SVN</a>.
+
+<br>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/developers.html
===================================================================
--- Scribus/doc/it/developers.html (nonexistent)
+++ Scribus/doc/it/developers.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/toolbox9.html
===================================================================
--- Scribus/doc/it/toolbox9.html (nonexistent)
+++ Scribus/doc/it/toolbox9.html (revision 17471)
@@ -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>Inkscape &egrave; rapidamente divenuto uno dei pi&ugrave; importanti strumenti open source per la grafica vettoriale o l'&ldquo;illustrazione&rdquo;. Gli sviluppatori di Inkscape hanno compiuto grandi sforzi per aderire fedelmente alle specifiche tecniche del formato SVG elaborate dal W3C. Le versioni pi&ugrave; recenti hanno fatto molti progressi e contengono un'ampia gamma di miglioramenti, tra cui la gestione del colore, uno dei migliori strumenti di tracciamento e molte funzionalit&agrave; che rendono pi&ugrave; facile la vita ai grafici. Come per Scribus, le capacit&agrave; di Inkscape possono facilmente essere estese tramite script in Python.</p>
+
+<table width="90%"><tr><td align="center"><img src="images/tb-inkscape.png"></td></tr></table>
+
+<p>Inkscape ha un'interfaccia utente facile da usare, con ampi suggerimenti e un paio di corsi pratici sul disegno vettoriale veramente ben fatti. Quasi ogni funzione pu&ograve; essere attivata con tasti di scelta rapida (l'elenco &egrave; lungo quasi dieci pagine!). Come per Scribus, gli sviluppatori di Inkscape correggono gli errori rapidamente, e sono molto aperti a suggerimenti per nuove funzioni e miglioramenti.</p>
+
+<p>Ma il meglio di Inkscape &egrave; la sua fedelt&agrave; alle specifiche tecniche SVG. Non &egrave; perfetto; nessuna applicazione lo &egrave;; ma le immagini SVG create con Inkscape sembrano funzionare meglio della media con altre applicazioni SVG, anche rispetto a quelle create con applicazioni commerciali costose.</p>
+
+<p>Nella maggior parte dei casi, le immagini SVG create con Inkscape vengono importate facilmente in Scribus. Vi sono alcune caratteristiche del formato SVG che Scribus non &egrave; ancora in grado di gestire (come i motivi o le ombreggiature), ma nel 99% dei casi &ldquo;It Just Works&trade;&rdquo;. Se un file non sembra essere importato correttamente in Scribus, provate a salvarlo in &ldquo;Plain SVG&rdquo; in Inkscape.</p>
+<p>Per altre informazioni leggete la pagina sull'<a href="scribus-svg.html">importazione di SVG</a>.</p>
+</body>
+</html>
Index: Scribus/doc/it/WwImages.html
===================================================================
--- Scribus/doc/it/WwImages.html (revision 17465)
+++ Scribus/doc/it/WwImages.html (revision 17471)
@@ -64,9 +64,9 @@
<p>Vedi anche:
<ul>
<li><a href="WwFrames.html">Lavorare con le cornici</a></li>
-<li><a href="importhints.html">Importing</a></li>
-<li><a href="importhints1.html">Importing EPS</a></li>
-<li><a href="psd.html">Importing PSD</a></li>
+<li><a href="importhints.html">Importare contenuto in Scribus</a></li>
+<li><a href="importhints1.html">Importare file EPS</a></li>
+<li><a href="psd.html">Importare file PSD</a></li>
</ul>
</p>
</body>
Index: Scribus/doc/it/install2.html
===================================================================
--- Scribus/doc/it/install2.html (nonexistent)
+++ Scribus/doc/it/install2.html (revision 17471)
@@ -0,0 +1,49 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Requisiti per la compilazione</title>
+</head>
+<body>
+<h2>Requisiti per la compilazione</h2>
+<p>I programmi che dovete avere per poter compilare Scribus 1.4 sono:</p>
+<ol>
+ <li><strong>Per Scribus 1.4.x &egrave; necessario GCC 3.x+, si consiglia fortemente GCC 3.3+</strong>. Il team di Scribus ha verificato la compilazione con GCC 4.1+. Si consiglia di utilizzare la pi&ugrave; recente versione stabile di GCC 4.x per i benefici di prestazioni che offre.</li>
+ <li>CMake</li>
+ <li>GNU make</li>
+</ol>
+Le dipendenze per la compilazione, e anche per l'esecuzione di Scribus, sono:
+<ol>
+<li>Qt 4.6.0+: sia le librerie di esecuzione sia quelle di sviluppo.</li>
+<li>Python e Python-devel: librerie 2.3+. Python 2.2 non funziona.</li>
+<li>Freetype2 2.1.7+. A causa di vari difetti presenti in freetype2, consigliamo, se la vostra distribuzione/sistema operativo lo permette, di usare la versione 2.3.x.</li>
+<li>Cairo 1.4.x. Consigliamo la versione 1.4.10 o successiva per ragioni di prestazioni.</li>
+<li>libxml2 2.6+.</li>
+<li>Ghostscript 8.60+ &egrave; altamente consigliato.</li>
+<li>littleCMS (noto anche come lcms in alcune distribuzioni). La versione minima &egrave; la 1.12, ma si consiglia la 1.17 o successiva. lcms 1.12+ &egrave; in grado di eseguire la compensazione del punto nero.</li>
+<li>libtiff 3.6.0+.</li>
+<li>libjpeg.</li>
+<li>librerie di sviluppo di CUPS; Scribus &egrave; in grado di stampare direttamente con CUPS (solo Linux/UNIX/Mac&nbsp;OS&nbsp;X).</li>
+<li>tkinter (per gli script Font Sampler e Calendar Wizard).</li>
+<li>le librerie Python-imaging sono utilizzate da certe funzioni di scripting.</li>
+<li>openssl-devel; alcune distribuzioni di Linux, tra cui OpenSUSE, permettono di utilizzare il protocollo ssl con CUPS.</li>
+<li>fontconfig-devel: per il rilevamento automatico dei caratteri su Linux, Mac&nbsp;OS&nbsp;X e UNIX. Non richiesto su Windows, OS/2 ed eComStation.</li>
+<li>Podofo 0.6 o successivo: utilizzato per aumentare le capacit&agrave; dell'importatore Adobe Illustrator.</li>
+</ol>
+<h3>Requisiti opzionali:</h3>
+<ul>
+<li>antiword: serve per l'importazione da MS Word. Non &egrave; necessario per la compilazione, ma Scribus lo rileva quando viene eseguito.</li>
+<li>per utilizzare le <a href="WwRenderframes.html">cornici rendering</a> sono necessari programmi aggiuntivi, come LaTeX o Lilypond.</li>
+</ul>
+<p>Scribus funziona con quasi ogni window manager e non richiede KDE. Tuttavia le funzionalit&agrave; di trascinamento e rilascio sono assenti senza KDE.</p>
+<p>Se la gestione del colore non funziona, dovete avere installati almeno un profilo RGB e uno CMYK, altrimenti le preferenze e opzioni per il colore non saranno presenti nei men&ugrave;. Scribus installa un profilo RGB e uno CMYK in modo che la gestione del colore sia attiva, ma alcune distribuzioni, tra cui Debian, forniscono dei profili ICC in pacchetti separati, a causa dei loro criteri di gestione delle licenze. </p>
+<p>In base alle prove eseguite, si è constatato che l'impostazione corretta del parametro CXXFLAGS al valore &#034;-march=&#034; ha un effetto assai benefico sulle prestazioni di Scribus. Ad esempio, se avete un processore Duron o Athlon, l'utilizzo di <code>export CXXFLAGS=&#034;-march=athlon&#034;</code> apporta notevoli benefici. Verificate se la vostra distribuzione imposta questo parametro e come, e per altre informazioni consultate:
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>man gcc</pre>
+</td></tr></table></blockquote></p>
+<p>Vi sono istruzioni dettagliate nel file BUILDING, e per la creazione dei pacchetti si dovrebbe consultare il file PACKAGING nel codice sorgente per ulteriori istruzioni.</p>
+<h4>Uso di CMake</h4>
+<p>Nella versione 1.3.3.6+ fu aggiunta la possibilit&agrave; di utilizzare CMake in alternativa ai tradizionali autotools. A partire dalla versione 1.3.5 CMake &egrave; obbligatorio, e non &egrave; pi&ugrave; possibile servirsi di autotools. Attualmente la compilazione su Linux, UNIX e Mac&nbsp;OS&nbsp;X funziona in modo soddisfacente. Per ulteriori informazioni leggete la pagina con le <a href="install4.html">istruzioni per CMake</a>.</p>
+<p>La posizione predefinita per l'eseguibile di Scribus &egrave; <code>/usr/local/bin</code>. La documentazione si trova in <code>/usr/local/lib/scribus/doc</code>.</p>
+<p>Inoltre, per i desktop Linux/UNIX, esiste un file <code>desktop.config</code> il cui nome &egrave; <code>scribus.desktop</code>, che pu&ograve; essere utilizzato per creare un collegamento nel men&ugrave; o sul desktop. Basta copiarlo dalla directory base del codice di installazione al desktop, e tramite esso potrete lanciare Scribus. Dopo aver spostato il file sul desktop, fate clic col tasto destro e controllate che la casella &ldquo;esecuzione&rdquo; sia contrassegnata. Questo file &egrave; conforme alle pi&ugrave; recenti specifiche <a href="http://www.freedesktop.org">www.freedesktop.org</a>.</p>
+</body>
+</html>
Index: Scribus/doc/it/toolbox13.html
===================================================================
--- Scribus/doc/it/toolbox13.html (nonexistent)
+++ Scribus/doc/it/toolbox13.html (revision 17471)
@@ -0,0 +1,16 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>XnView</title>
+</head>
+<body>
+<h2>XnView</h2>
+<p>Di applicazioni per visualizzare immagini e miniature ne esistono a bizzeffe; anche Konqueror e Nautilus lo fanno, quindi perch&eacute; mai si dovrebbe usare XnView?</p>
+
+<p>&Egrave; brutto. Usa vecchie librerie in stile Motif, ma due qualit&agrave; lo riscattano ampiamente: </p>
+<ol><li>&egrave; molto veloce, più veloce di quasi tutti gli altri programmi simili;</li>
+<li>&egrave; in grado di visualizzare una vasta gamma di formati immagine, con ottime capacit&agrave; di conversione. Vi sono alcuni formati di file veramente poco noti che XnView pu&ograve; aprire e convertire. Probabilmente soltanto ImageMagick ne pu&ograve; aprire di pi&ugrave;. &Egrave; molto stabile, ed &egrave; uno strumento che dovreste almeno prendere in considerazione.</li></ol>
+
+<table width="100%"><tr><td align="center"><img src="images/xnview.png" alt="Xnview" /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/it/faq3.html
===================================================================
--- Scribus/doc/it/faq3.html (nonexistent)
+++ Scribus/doc/it/faq3.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/readme.html
===================================================================
--- Scribus/doc/it/readme.html (nonexistent)
+++ Scribus/doc/it/readme.html (revision 17471)
@@ -0,0 +1,216 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>What&rsquo;s New in Scribus 1.4?</title>
+</head>
+<body>
+<h2>What&rsquo;s New in Scribus 1.4?</h2>
+<p>This is a cursory overview over the changes in Scribus compared to to the latest stable version 1.3.3.14.</p>
+
+<p><b><i>Note that the file format has changed and is not backwardly compatible with any prior stable version (1.3.3.14 or earlier). To be precise, you will not be able to open 1.4.0 files with version 1.3.3.14 or any earlier version.</i></b></p>
+<h3>General</h3>
+<ol>
+<li>On initial launch, 1.4 will offer to inherit the configuration data from any existing prior version, but it will store them separately, so you can run 1.3.3.x in parallel with 1.4 </li>
+<li>You <b>can</b> install both versions in parallel and run them at the same time. The only caveat is to install them using different installation directories, e.g 1.3.3.x in /usr/local and 1.4 in /opt or $home/bin on Linux/UNIX. If you&rsquo;re building Scribus from source, you can use the <code>-DCMAKE_INSTALL_PREFIX:PATH=</code> argument to configure where Scribus should be installed. On other platforms you can determine the location during the installation process.</li>
+</ol>
+<h3>New in Scribus 1.4</h3>
+
+<h4>Qt4 Port</h4>
+<p>One of the major endeavours on the way from 1.3.3.x to 1.4 was the porting to the Qt4 toolkit. Among others, it enabled a vastly better performance under Mac OS&nbsp;X, as well as the creation of native DMGs for OS&nbsp;X. Scribus 1.4 DMGs will run on OS&nbsp;X 10.5 or later.</p>
+
+<h4>Object Handling</h4>
+<ul>
+<li>Significant enhancements to Multiple Duplicate.</li>
+<li>Transform tools as known from Illustrator.</li>
+<li>New options to align and distribute objects.</li>
+<li>Advanced multiple object selection.</li>
+</ul>
+
+<h4>Text and Typography</h4>
+<h5><b>Typography:</b></h5>
+<ul>
+<li>Glyph Extension</li>
+<li>Variable First Line Offset for text frames.</li>
+<li>Character Styles.</li>
+<li>New Style Manager that allows for style hierarchies, cloned styles and style inheritance.</li>
+<li>A new glyph selector which allows for the creation of glyph sets that can be shared between users.</li>
+<li>Major improvements to the hyphenator.</li>
+<li>Optical margins to give the impression of a straighter edge with justified text by moving hyphens, commas and parts of certain glyphs slightly into the margin:</li>
+</ul>
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new1.png" title="Optical Margins" alt="Optical Margins" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>Optical Margins</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+<h5><b>Text</b></h5>
+<ul>
+<li>Basic spellchecking via aspell (not available for Windows, OS/2 and eComStation).</li>
+<li>New text variable: Number of pages.</li>
+<li>Undo/Redo is finally available for text-related actions.</li>
+</ul>
+
+<h4>Vector Tools</h4>
+
+<ul>
+<li>New default shapes.</li>
+<li>New Path Tools, like Boolean path operations, lens effects or mesh distortion.</li>
+<li>More options for text on path.</li>
+</ul>
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new2.png" title="Boolean path operations" alt="Boolean path operations" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>Boolean path operations</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+
+<h4>Lines</h4>
+<ul>
+<li>New line styles.</li>
+<li>Line style editor.</li>
+</ul>
+
+
+<h4>Solid Colors, Gradients and Patterns</h4>
+<ul>
+<li>Major improvements to the Color Wheel (support for multiple color models).</li>
+<li>An option to replace solid colors throughout the whole document.</li>
+<li>Support for external color palette formats (EPS, AI, PS, SOC, GPL).</li>
+<li>Locking of standardized color palettes.</li>
+<li>Many new color palettes, among them the national standard color sets of Australia, France, Japan, the United Kingdom and the United States, as well as Resene&#0174; color and dtp studio collections.</li>
+<li>New gradient types.</li>
+<li>Support for pattern fills: All graphics formats supported by Scribus can be used as patterns.</li>
+<li>Emulation of color blindness for all colors in a document.</li>
+</ul>
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new5.png" title="Replacing solid colors" alt="Replacing solid colors" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>Replacing solid colors</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+
+<h4>Transparency</h4>
+<ul>
+<li>Blending modes as known from Photoshop or GIMP are now available for all objects in a Scribus document and can also be applied to layers.</li>
+</ul>
+
+<h4>Render Frames</h4>
+<ul>
+<li>One of the major new features is the introduction of Render Frames, a special frame type that allows for rendering the output of programs like LaTeX, Lilypond or POV-Ray inside Scribus.</li></ul>
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new3.png" title="Render Frame Editor" alt="Render Frame Editor" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>Render Frame Editor</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+
+<h4>Import Filters</h4>
+<ul>
+<li>A considerable amount of work has been spent on new import filters for vector formats, most notably Adobe Illustrator (AI). Scribus can now import both EPS and PDF based AI files. Other filters are: Windows Metafile (WMF), Xfig (FIG), Calamus Vector Graphics (CVG), Macintosh PICT (PICT), Kivio Stencils (SML) and Dia Shapes (SHAPE).</li></ul>
+
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new4.png" title="Adobe Illustrator import" alt="Adobe Illustrator import" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>Adobe Illustrator import</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+
+<h4>Image Handling</h4>
+<ul>
+<li>New non-destructive image effects.</li>
+<li>Better handling of PSD-specific features, like clipping paths and layers.</li>
+<li>Major improvements to the image manager.</li>
+</ul>
+<br>
+<table width="100%">
+ <tbody>
+ <tr>
+ <td align="center"><img src="images/new6.png" title="The new image manager" alt="The new image manager" /></td>
+ </tr>
+ <tr>
+ <td><div align="center"><i>The new image manager</i></div></td>
+ </tr>
+ </tbody>
+</table>
+<br>
+
+<h4>Layers</h4>
+<ul>
+<li>Scribus layers can now be exported as PDF layers (PDF 1.5 only).</li>
+<li>Duplicate Layers feature.</li>
+<li>Wireframe mode for layers to speed up performance.</li>
+<li>Enforceable text flow around objects on a lower layer.</li>
+</ul>
+
+<h4>Pre-press</h4>
+<ul>
+<li>Enhancements to the Print Preview, like indication of ink coverage.</li>
+<li>Improvements to the Preflight Verifier.</li>
+<li>New pre-press features, like bleed and printing marks.</li>
+<li>Optional conversion of spot colors to process colors.</li>
+</ul>
+
+<h4>PDF Export</h4>
+<ul>
+<li>Support for PDF 1.5 features, e.g. slide effects for PDF presentations or PDF layers.</li>
+<li>Optional embedding of EPS and PDF files in PDF documents.</li>
+<li>Better font subsetting.</li>
+</ul>
+
+<h4>Usability</h4>
+<p>Much work has been spent on major and minor usability improvements throughout the whole program, e.g.:</p>
+<ul>
+<li>A search feature for the Document Outline.</li>
+<li>Many more viewing options, including a document preview without guides and frame borders.</li>
+<li>One-click activation of color management.</li>
+<li>Context menu for the document canvas with options to insert vector graphics directly or to activate viewing options</li>
+<li>Many more options to automate and speed up the insertion of frames (e.g. Insert Frame dialog, &ldquo;Sticky Tools&rdquo; option).</li>
+<li>Enhancements to the Scrapbook.</li>
+</ul>
+
+<h4>Templates</h4>
+<ul>
+<li>Many templates, donated by artists, have been added.</li>
+<li>We have finally begun to translate the template categories and template descriptions into other languages.</li>
+</ul>
+
+<h4>Help System</h4>
+<ul>
+<li>The content of the Online Help system has almost doubled since the relase of the latest stable version 1.3.3.14. Moreover, major parts of the existing documentation have been updated or completely rewritten to reflect the feature set of Scribus 1.4+.</li>
+<li>Many new tooltips have been added, and existing ones have been expanded.</li>
+<li>Online help resources are now accessible from the <i>Help</i> menu.</li>
+</ul>
+<br>
+<br>
+</body>
+</html>
Index: Scribus/doc/it/doccopyright.html
===================================================================
--- Scribus/doc/it/doccopyright.html (nonexistent)
+++ Scribus/doc/it/doccopyright.html (revision 17471)
@@ -0,0 +1,84 @@
+<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 the Scribus Online Help, written by the Scribus team composed of Franz Schmid, Peter Linnell, Craig Bradney, Jean Ghali, Hermann Kraus, Riku Leino, Oleksandr Moskalenko, Craig Ringer, Christoph Sch&auml;fer, Petr Van&#283;k, Andreas Vox and Jain Basil with major contributions from Gregory Pittman and addtional documentation by Maciej Hanski.
+
+<p>The &ldquo;PDF Forms&rdquo; section is licensed under the Free Documentation License. The FDL applies ONLY to this section of the documentation.</p>
+
+<p>The Scribus Online Help (excluding the aforementioned &ldquo;PDF Form&rdquo; 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 online help manual &ldquo;Scribus Online Help&rdquo; 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 &copy; 2003&ndash;2011 the Scribus team composed of Franz Schmid, Peter Linnell, Craig Bradney, Jean Ghali, Hermann Kraus, Riku Leino, Oleksandr Moskalenko, Craig Ringer, Christoph Sch&auml;fer, Petr Van&#283;k, Andreas Vox and Jain Basil, as well as Gregory Pittman. The 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 Franz Schmid, Peter Linnell, Craig Bradney, Jean Ghali, Hermann Kraus, Riku Leino, Oleksandr Moskalenko, Craig Ringer, Christoph Sch&auml;fer, Petr Van&#283;k, Andreas Vox and Jain Basil, as well as Gregory Pittman.</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 &ldquo;as is&rdquo; 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&rsquo;s name may not be used to assert or imply endorsement of the resulting document without the original author&rsquo;s (or authors&rsquo;) 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>
+<h3>===================</h3>
+<ul>
+<li>Adobe, Adobe Reader, Adobe Acrobat, Adobe Illustrator, Adobe InDesign, Adobe PageMaker, Adobe Photoshop, and PostScript are trademarks of Adobe corporation in the United States, other countries, or both.</li>
+<li>Apple, Mac, Mac OS, Mac&nbsp;OS&nbsp;X, Macintosh, and TrueType are trademarks of Apple corporation in the United States, other countries, or both.</li>
+<li>CorelDraw is a registered trademark of Corel corporation in the United States, other countries, or both.</li>
+<li>Ghostscript is a registered trademark of Artifex, Inc. in the United States, other countries, or both.</li>
+<li>Java, StarOffice, and OpenOffice.org are registered trademarks of Oracle America in the United States, other countries, or both.</li>
+<li>Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.</li>
+<li>Microsoft, Windows, Windows NT, Windows 2000, Windows XP, Windows Vista, Windows 7, Visual Studio, Microsoft Word, Microsoft PowerPoint, and OpenType are trademarks of Microsoft corporation in the United States, other countries, or both.</li>
+<li>Novell and OpenSUSE are trademarks of Novell in the United States, other countries, or both.</li>
+<li>OS/2 is a registered trademark of International Business Machines corporation in the United States, other countries, or both.</li>
+<li>QuarkXPress is a registered trademark of Quark, Inc. in the United States, other countries, or both.</li>
+<li>Red Hat and Fedora are trademarks of Red Hat corporation in the United States, other countries, or both.</li>
+<li>UNIX and Motif are registered trademarks of The Open Group in the United States, other countries, or both.</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
Index: Scribus/doc/it/mailing_lists.html
===================================================================
--- Scribus/doc/it/mailing_lists.html (nonexistent)
+++ Scribus/doc/it/mailing_lists.html (revision 17471)
@@ -0,0 +1,195 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Mailing List</title>
+</head>
+<body>
+<h3>Regole di utilizzo delle mailing list e dichiarazioni di non responsabilit&agrave;</h3>
+<h3>Introduzione</h3>
+<p>
+Gli sviluppatori e i collaboratori di Scribus vivono in localit&agrave; distribuite su ogni continente, e spesso sono geograficamente molto lontani tra loro. La comunit&agrave; degli utenti &egrave; ancora pi&ugrave; varia e sparpagliata nel mondo. Quindi IRC e la posta elettronica sono i mezzi preferiti per parlare dell'utilizzo e dello sviluppo di Scribus. La comunicazione via posta elettronica per gli sviluppatori e la comunit&agrave; di Scribus avviene attraverso le mailing list di Scribus.
+</p>
+<p>
+Le nostre liste sono pubbliche, il che significa che chiunque pu&ograve; leggere tutto ci&ograve; che vi viene scritto e partecipare alla discussione. Incoraggiamo tutti a contribuire allo sviluppo di Scribus e a far conoscere il software libero. La lista &ldquo;scribus&rdquo; &egrave; dedicata a discussioni sull'uso di Scribus e pi&ugrave; in generale sul desktop publishing, a richieste di aiuto e annunci. La lista &ldquo;scribus-dev&rdquo; &egrave; dedicata a discussioni sullo sviluppo di Scribus tra gli sviluppatori e gli utenti interessati a questo tema.</p>
+
+<h3>Istruzioni fondamentali per l'uso</h3>
+
+<p>
+Ciascuna delle mailing list di Scribus (che da qui in poi indicheremo con &ldquo;listname&rdquo;) ha un indirizzo per l'invio avente la forma <code>listname@lists.scribus.net</code>, un indirizzo per le richieste avente la forma <code>listname-request@lists.scribus.net</code>, e una pagina web all'indirizzo
+<a href="http://lists.scribus.net/mailman/listinfo/">http://lists.scribus.net/mailman/listinfo/</a>.
+</p>
+<p>
+Per mandare un'email a una lista, basta mandarla all'indirizzo per l'invio: <code>listname@lists.scribus.net</code>. Per iscrivervi a una lista e poter leggere le mail via via che arrivano, o per cancellare l'iscrizione, usate l'indirizzo per le richieste (vedi sotto).
+</p>
+<p>
+Le mailing list attualmente attive sono elencate in ordine alfabetico nella pagina <a href="http://lists.scribus.net">http://lists.scribus.net</a>.
+</p>
+
+<h3>Iscrizione / cancellazione</h3>
+
+<p>
+Chiunque pu&ograve; direttamente iscriversi o cancellarsi da qualunque mailing list, purch&eacute; la lista stessa consenta l'iscrizione libera.
+</p>
+<p>
+Potete iscrivervi o cancellarvi da ciascuna mailing list direttamente dalla rispettiva pagina web all'indirizzo
+<a href="http://lists.scribus.net/">http://lists.scribus.net/</a>.
+</p>
+<p>
+Le richieste di iscrizione o cancellazione possono anche essere inviate via email, a un apposito indirizzo per le richieste che &egrave; un po' diverso da quello della lista. I messaggi di iscrizione o cancellazione NON devono essere mandati all'indirizzo vero e proprio della lista.
+</p>
+<p>
+Per iscrivervi o cancellarvi da una lista, mandate un'email a:
+</p>
+<p>
+<code>listname-REQUEST@lists.scribus.net</code>
+</p>
+<p>
+con la parola <code>subscribe</code> (per l'iscrizione) oppure <code>unsubscribe</code> (per la cancellazione) come oggetto.
+</p>
+<p>
+Fate attenzione a non omettere la parte -REQUEST dall'indirizzo.
+</p>
+<p>
+Come parte della procedura di iscrizione, il software che gestisce la lista invia automaticamente una mail a cui dovrete rispondere per confermare l'iscrizione. Questa &egrave; una misura di sicurezza per impedire che qualcuno iscriva alla lista un'altra persona senza il suo consenso.
+</p>
+<p>
+Ricordate che una richiesta di cancellazione deve essere mandata dallo stesso indirizzo iscritto alla lista. Se ci&ograve; non &egrave; possibile, l'oggetto della richiesta deve avere la forma: <code>unsubscribe&nbsp;indirizzoiscritto@dominio.iscritto</code>.
+</p>
+<p>
+Se ricevete messaggi da una mailing list, ma non riuscite a individuare l'indirizzo con cui vi siete iscritti, potete controllare le intestazioni complete dei messaggi ricevuti, in cui troverete alcune righe simili alle seguenti:
+</p>
+<pre>
+ To: quux@example.com
+ List-Id: &lt;scribus.lists.scribus.net&gt;
+ Sender: scribus-bounces@lists.scribus.net
+</pre>
+<p>
+Questo vi dice con certezza che la lista in questione si chiama <code>scribus</code> e che l'indirizzo iscritto &egrave; <code>quux@example.com</code>. In questo caso (immaginario), per cancellarvi dalla lista dovreste mandare un'email a <code>scribus-request@lists.scribus.net</code> con oggetto <code>unsubscribe&nbsp;quux@example.com</code>.
+</p>
+
+<h3>Pagina delle opzioni</h3>
+
+<ul>
+<li>
+Questa pagina si trova all'indirizzo http://lists.scribus.net/mailman/options/listname/email (ad esempio, http://lists.scribus.net/mailman/options/scribus/john.doe@example.com)
+</li>
+<li>
+La pagina pu&ograve; essere raggiunta anche da quella delle informazioni sulla lista (ad esempio <a href="http://lists.scribus.net/mailman/listinfo/scribus">http://lists.scribus.net/mailman/listinfo/scribus</a>) inserendo il vostro indirizzo di posta nella casella accanto al pulsante &ldquo;Unsubscribe or Edit Options&rdquo;" in fondo alla pagina.
+</li>
+<li>
+Per accedere alla pagina delle opzioni: se non avete gi&agrave; eseguito l'accesso, vi sar&agrave; in alto una casella per l'inserimento della password. Inserite la vostra password e premete il pulsante. Se non sapete la password, premete il pulsante &ldquo;Email My Password To Me&rdquo; in basso a sinistra: il software che gestisce la lista vi mander&agrave; un messaggio automatico con la password.
+</li>
+<li>
+Nella pagina delle opzioni potete accedere o uscire, modificare le impostazioni di iscrizione, cancellarvi dalla lista o farvi mandare una copia della password.
+</li>
+</ul>
+
+<h3>Regole di comportamento</h3>
+
+<p>
+Quando usate le mailing list di Scribus dovreste seguire queste regole:
+</p>
+
+<ul>
+<li>
+Non mandate spam. Vedete sotto le informazioni sul trattamento della pubblicità.
+</li>
+<li>
+Se potete, scrivete sempre in inglese. Potete provare a usare altre lingue; nella comunit&agrave; di Scribus vi sono persone che parlano molte lingue, ma non &egrave; garantito che riceviate una risposta nella vostra lingua. Tra gli sviluppatori di Scribus vi sono persone che parlano inglese, tedesco, francese, olandese, russo, ucraino, finlandese, ceco, svedese e lussemburghese.
+</li>
+<li>
+Fate attenzione a usare la lista adatta. In particolare non mandate richieste sull'uso del programma alla lista scribus-dev, che &egrave; dedicata a questioni relative allo sviluppo.
+</li>
+<li>
+Normalmente dovreste fare in modo che le righe vadano a capo dopo 80 caratteri. Righe pi&ugrave; lunghe sono accettabili per output generato da computer (ad esempio da <code>ls -l</code>).
+</li>
+<li>Se rispondete a un messaggio, inserite la vostra risposta in fondo; <a href="http://www.blakjak.demon.co.uk/gey_stv0.htm">qui &egrave; spiegato il perch&eacute;.</a> Molti iscritti ricevono i messaggi in forma raggruppata (<i>digest</i>), e se le risposte sono inserite all'inizio il gruppo di messaggi pu&ograve; diventare difficilmente comprensibile. </li>
+<li>
+Non mandate messaggi automatici che avvisano delle vostre assenze o vacanze.
+</li>
+<li>
+Non mandate richieste di iscrizione o cancellazione alla lista stessa; usate invece il rispettivo indirizzo -request.
+</li>
+<li>
+<b>Non mandate mai</b> messaggi in HTML; usate il testo semplice.
+</li>
+<li>
+Non mandate allegati di grandi dimensioni. Le liste di Scribus hanno un limite per le dimensioni dei messaggi; gli allegati vengono automaticamente rimossi e sono accessibili solo attraverso l'interfaccia web delle liste.
+</li>
+<li>
+Per comunicare con la lista usate l'indirizzo con cui vi siete iscritti. Se usate un indirizzo diverso, i messaggi che mandate dovranno essere approvati dai moderatori prima che siano pubblicati.
+</li>
+<li>
+Non inserite messaggi o parti di messaggio che avete ricevuto privatamente, a meno che non abbiate il consenso del mittente.
+</li>
+<li>
+Quando rispondete a messaggi inviati alla lista, non mandatene una copia (CC) al mittente originale, a meno che non sia stata richiesta esplicitamente.
+</li>
+<li>
+Se inviate un messaggio a una lista a cui non siete iscritti, citate sempre questo fatto nel testo del messaggio.
+</li>
+<li>
+Non usate linguaggio volgare o indecente; anche perch&eacute; alcuni utenti potrebbero ricevere i messaggi tramite mezzi come la radio a pacchetti, su cui tale linguaggio &egrave; illegale.
+</li>
+<li>
+Non insultate gli altri utenti; siate educati.
+</li>
+<li>
+Usate sempre il buon senso.
+</li>
+</ul>
+
+<h3>Manutenzione e amministrazione delle liste</h3>
+
+<p>
+A volte il server delle mailing list pu&ograve; essere spento per manutenzione o aggiornamento del software. Non allarmatevi: in questi casi facciamo tutto il possibile per riattivare le liste nel pi&ugrave; breve tempo possibile.
+</p>
+<p>
+Se avete problemi con l'iscrizione o la cancellazione, controllate di aver seguito le procedure corrette prima di contattarci. Assicuratevi di aver letto le avvertenze su iscrizione e cancellazione.
+</p>
+<p>
+Per contattare la persona che si occupa del funzionamento delle liste, mandate una mail in inglese a <code>mailman@lists.scribus.net</code>. Oppure potete inserire una segnalazione nel nostro sistema per la gestione degli errori alla pagina <a href="http://bugs.scribus.net">http://bugs.scribus.net</a>.
+</p>
+<p>
+Se non siete riusciti a cancellarvi da una lista, dovreste includere nella vostra segnalazione una copia di tutte le intestazioni di un messaggio che avete ricevuto da quella lista.
+</p>
+
+<h3>Dichiarazione di non responsabilit&agrave;/informazioni sulla privacy</h3>
+
+<p>
+Le mailing list sono luoghi di discussione pubblica.
+</p>
+<p>
+Tutti i messaggi inviati a una lista sono distribuiti agli iscritti alla lista e copiati nell'archivio pubblico, dove possono essere letti e cercati da chiunque senza bisogno di essere iscritti.
+</p>
+<p>
+Inoltre le nostre mailing list possono essere lette sotto forma di gruppi di discussione (Usenet). &Egrave; possibile farlo anche tramite un'interfaccia web come Google o Gmane.
+</p>
+<p>
+Le liste potrebbero essere distribuite anche in altri luoghi; accertatevi di non mandare alle liste alcun materiale confidenziale o non autorizzato, comprese informazioni come indirizzi di posta elettronica. Da notare in particolare &egrave; il fatto che spammer, virus, e altri software malevoli a volte raccolgono indirizzi da mailing list pubbliche per scopi abusivi.
+</p>
+<p>
+Il team di Scribus gestisce le liste in buona fede, e agir&agrave; per contenere qualunque abuso di cui venga a conoscenza e mantenere il normale e continuo funzionamento delle liste. Allo stesso tempo, il team di Scribus non &egrave; responsabile per del contenuto dei messaggi inviati alle liste o di qualunque cosa possa accadere in relazione a essi.
+</p>
+
+<h3>Trattamento della pubblicit&agrave; sulle mailing list di Scribus</h3>
+
+<p>
+L'invio di qualunque tipo di posta non richiesta in grandi quantit&agrave; (nota anche come spam) alle liste di Scribus &egrave; vietato. Ai mittenti di tali messaggi pu&ograve; essere impedito di scrivere alle liste e/o possono essere segnalati alle autorit&agrave; competenti.
+</p>
+<p>
+I gestori delle liste di Scribus fanno tutto ci&ograve; che &egrave; loro possibile per impedire la pubblicazione in lista di messaggi di questo tipo.
+</p>
+<p>
+Molte delle regole che usiamo per bloccare gli spammer e i loro messaggi ci sono state segnalate dagli iscritti. Se desiderate aiutarci a ridurre ulteriormente la quantit&agrave; di spam, il vostro aiuto sar&agrave; apprezzato. Per segnalare spam potete scrivere a <code>mailman@lists.scribus.net</code> indicando la URL del messaggio presa dall'archivio della mailing list. Quando esamineremo la vostra richiesta riceverete una risposta. Tenete presente che prenderemo provvedimenti solo sui messaggi segnalati come spam nelle ultime ore, poich&eacute; &egrave; inutile avere regole di filtraggio non aggiornate.
+</p>
+<p>
+Fate in modo che i messaggi che ricevete dalle mailing list di Scribus non vengano mai mandati a sistemi automatici per la segnalazione di spam. Questo comportamento &egrave; spesso dannoso per tutti gli utenti e ci costringer&agrave; a bloccare qualunque traffico dalle mailing list verso di voi, finch&eacute; dimostrerete che non lo farete di nuovo.
+</p>
+
+<h3>Licenza</h3>
+<p>
+<i>Questo documento &egrave; stato adattato dalla descrizione delle mailing list del Progetto Debian. Questo materiale pu&ograve; essere distribuito soltanto alle condizioni esposte nella Open Publication License, Draft v1.0 o successiva. La versione pi&ugrave; recente di solito &egrave; disponibile all'indirizzo <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).</i>
+</p>
+</body>
+</html>
Index: Scribus/doc/it/menu.xml
===================================================================
--- Scribus/doc/it/menu.xml (revision 17465)
+++ Scribus/doc/it/menu.xml (revision 17471)
@@ -7,16 +7,16 @@
<area text="Documentazione" file="intro.html">
<submenuitem text="Introduzione" file="documentation.html">
<submenuitem text="Editorial Notes" file="editorial.html"/>
- <submenuitem text="About the team" file="about1.html"/>
+ <submenuitem text="Il team di Scribus" file="about1.html"/>
</submenuitem>
<submenuitem text="Installazione" file="install.html">
<submenuitem text="Mac OS X" file="readme-macosx.html"/>
<submenuitem text="OS/2 and eComStation" file="readme-os2.html"/>
<submenuitem text="Windows" file="readme-win32.html"/>
- <submenuitem text="Scribus Source and SVN" file="install1.html"/>
- <submenuitem text="Requirements" file="install2.html"/>
- <submenuitem text="Compiling using CMake" file="install4.html"/>
- <submenuitem text="Compiling using CMake on OS X" file="install5.html"/>
+ <submenuitem text="Sorgenti di Scribus e SVN" file="install1.html"/>
+ <submenuitem text="Requisiti per la compilazione" file="install2.html"/>
+ <submenuitem text="Compilazione con CMake" file="install4.html"/>
+ <submenuitem text="Compilazione con CMake su OS X" file="install5.html"/>
</submenuitem>
<submenuitem text="Configurazione" file="config.html">
<submenuitem text="Configurazione di Scribus" file="settings1.html"/>
@@ -52,7 +52,7 @@
<submenuitem text="Raccolte colori Resene" file="color5.html" />
<submenuitem text="Raccolte colori dtp studio" file="color6.html" />
<submenuitem text="Colori per scopi speciali" file="color8.html" />
- <submenuitem text="The Color Wheel" file="colorwheel.html" />
+ <submenuitem text="La mappa cromatica" file="colorwheel.html" />
</submenuitem>
<submenuitem text="Importare contenuti" file="importhints.html">
<submenuitem text="Importare file bitmap" file="importbitmap1.html" />
@@ -71,18 +71,18 @@
<submenuitem text="Formulari PDF" file="pdf_form.html"/>
<submenuitem text="PDF/X-3" file="pdfx3.html"/>
</submenuitem>
- <submenuitem text="Printing with Scribus" file="print1.html">
- <submenuitem text="Printing Tools (1)" file="print2.html"/>
- <submenuitem text="Printing Tools (2)" file="print3.html"/>
- <submenuitem text="Commercial Printing" file="print4.html"/>
+ <submenuitem text="Stampare con Scribus" file="print1.html">
+ <submenuitem text="Strumenti per la stampa (1)" file="print2.html"/>
+ <submenuitem text="Strumenti per la stampa (2)" file="print3.html"/>
+ <submenuitem text="Stampa commerciale" file="print4.html"/>
</submenuitem>
- <submenuitem text="Color Management" file="cms.html">
- <submenuitem text="Color Management Setup" file="cms2.html"/>
- <submenuitem text="Rendering Intents" file="cms3.html"/>
+ <submenuitem text="Gestione del colore" file="cms.html">
+ <submenuitem text="Impostazioni per la gestione del colore" file="cms2.html"/>
+ <submenuitem text="Intenti rendering" file="cms3.html"/>
</submenuitem>
- <submenuitem text="DTP ToolBox" file="toolbox.html">
+ <submenuitem text="La cassetta degli attrezzi del DTP" file="toolbox.html">
<submenuitem text="Adobe Reader" file="toolbox1.html"/>
- <submenuitem text="PDF/PostScript Tools" file="toolbox2.html"/>
+ <submenuitem text="Strumenti per PDF e PostScript" file="toolbox2.html"/>
<submenuitem text="Ghostscript" file="toolbox5.html"/>
<submenuitem text="GSview" file="toolbox6.html"/>
<submenuitem text="Advanced Ghostscript &amp; GSView" file="toolbox7.html"/>
@@ -96,7 +96,7 @@
<submenuitem text="Fontmatrix" file="toolbox16.html"/>
<submenuitem text="SwatchBooker" file="toolbox17.html"/>
<submenuitem text="LibreOffice/OpenOffice.org" file="toolbox18.html"/>
- <submenuitem text="Commandline Tools" file="toolbox19.html"/>
+ <submenuitem text="Strumenti da riga di comando" file="toolbox19.html"/>
</submenuitem>
</area>
<area text="Troubleshooting" file="fileproblems.html" >
@@ -135,10 +135,9 @@
</area>
<area text="Altre informazioni" file="otherinfo.html">
<submenuitem text="Comunità e risorse per gli utenti" file="resources.html"/>
- <submenuitem text="Bug Reports" file="bugreport.html"/>
- <submenuitem text="Mailing Lists" file="mailing_lists.html"/>
+ <submenuitem text="Segnalare un bug" file="bugreport.html"/>
+ <submenuitem text="Mailing List" file="mailing_lists.html"/>
<submenuitem text="IRC" file="irc.html"/>
- <submenuitem text="Printers" file="scprinters.html"/>
<submenuitem text="Download" file="download.html"/>
<submenuitem text="Release History" file="releases.html"/>
<submenuitem text="Scribus Copyright" file="scribuscopyright.html"/>
Index: Scribus/doc/it/contributions.html
===================================================================
--- Scribus/doc/it/contributions.html (nonexistent)
+++ Scribus/doc/it/contributions.html (revision 17471)
@@ -0,0 +1,46 @@
+<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 Online Help is the latest generation of the Scribus online documentation. The initial documents were written by Peter Linnell with help from Franz Schmid. Since then, the Scribus Team has grown, as did the number of contributions from other people, and we have seen an increasing number of additions and updates. The following table attempts to list the contributors to the documentations. Hopefully we didn&rsquo;t miss anyone out (if so, please contact us and we will add you in):
+</p>
+
+<h3>Online Help</h3>
+
+<table border="1">
+ <tr><td><b>Name</b></td><td><b>Contribution(s)</b></td></tr>
+ <tr><td>Craig Bradney</td><td>Site implementation, management and documentation verification</td></tr>
+ <tr><td>Maciej Ha&#324;ski</td><td>PHP form document</td></tr>
+ <tr><td>V&#225;clav Hlobil</td><td>Title graphics</td></tr>
+ <tr><td>Paul Johnson</td><td>Coding Standards document</td></tr>
+ <tr><td>Riku Leino</td><td>Get Text plug-in Howto</td></tr>
+ <tr><td>Peter Linnell</td><td>Original documentation</td></tr>
+ <tr><td>Gregory Pittman</td><td>Main author of the <a href="http://wiki.scribus.net/index.php/Get_Started_with_Scribus">next generation</a> of the &ldquo;Get Started with Scribus&rdquo; tutorial, one of the main authors of the latest updates to this Online Help, proofeader</td></tr>
+ <tr><td>Franz Schmid</td><td>Scribus :) and documentation verification</td></tr>
+ <tr><td>Petr Van&#283;k</td><td>Scripter and plug-in documentation</td></tr>
+ <tr><td>Craig Ringer</td><td>Scripter documentation</td></tr>
+ <tr><td>Christoph Sch&auml;fer</td><td>One of the main authors of the latest updates to this Online Help, proofeader, German translation of this Online Help and the Scribus Wiki.</td></tr>
+</table>
+
+<h4>Translators of the Online Help</h4>
+<table border="1">
+ <tr><td><b>Name</b></td><td><b>Language(s)</b></td></tr>
+ <tr><td>Louis Desjardins</td><td>French</td></tr>
+ <tr><td>Frederic Dubuy</td><td>French</td></tr>
+ <tr><td>François Lanctôt, thanks to <A href="http://grics.qc.ca">GRICS</A></td><td>French</td></tr>
+ <tr><td>Volker Ribbert</td><td>German</td></tr>
+ <tr><td>Johannes R&#252;schel</td><td>German</td></tr>
+</table>
+
+<h4>Additional Documentation</h4>
+<table border="1">
+<tr><td><b>Name</b></td><td><b>Contribution(s)</b></td></tr>
+<tr><td>Niyam Bhushan</td><td>Initial version of the &ldquo;Get Started with Scribus&rdquo; tutorial</td></tr>
+</table>
+<br>
+</body>
+</html>
Index: Scribus/doc/it/color7.html
===================================================================
--- Scribus/doc/it/color7.html (nonexistent)
+++ Scribus/doc/it/color7.html (revision 17471)
@@ -0,0 +1,26 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Color Palettes in Scribus (5): GiveLife Color System&reg;</title>
+</head>
+<body>
+<h2>Color Palettes in Scribus (5): GiveLife Color System&reg;</h2>
+
+<p><a href="http://www.givelifecolorsystem.com">GiveLife Color System&reg;</a> is a Spanish company founded by designers and engineers to create new color systems for graphics and design professionals, especially in the Hispanic world.</p>
+
+<p>Until now, GiveLife Color System&reg; has developed two numerical color systems, one in RGB and one in CMYK. Scribus is the first graphics program which is being shipped by default with the GiveLife Color System&reg; color palettes.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/givelife1.png" title="The GiveLife Color&reg; System CMYK palette in the Scribus Color Manager" alt="The GiveLife Color&reg; System CMYK palette in the Scribus Color Manager"/></td></tr></table><br>
+
+<h3>The palette &ldquo;GiveLife Color System CMYK&rdquo;</h3>
+<p>This palette consists of 2265 CMYK colors, each of which has a five-digit numerical code. The system has been developed for use in print-related projects. The company offers a printed color reference for this palette on its <a href="http://www.givelifecolorsystem.com">website</a>. This <a href="http://www.flickr.com/photos/givelifecolorsystem/">&ldquo;Color Guide Book&rdquo;</a> has been created using the ICC profile FOGRA 39 (ISO 12647-2:2004).</p>
+
+<h3>The palette &ldquo;GiveLife Color System RGB&rdquo;</h3>
+<p>The second palette comprises 5101 RGB colors, each of which has a four-digit numerical code. The correct ICC profile for use with this palette is sRGB.</p>
+
+<p>Note that you need to <a href="cms.html">install</a> the profiles listed above to use the colors reliably.</p>
+
+<p>The Scribus Team will cooperate with GiveLife Color System&reg; to ensure that updates to the existing palettes, as well as new color systems will be made available to our users in the future.</p>
+<br>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/cms3.html
===================================================================
--- Scribus/doc/it/cms3.html (nonexistent)
+++ Scribus/doc/it/cms3.html (revision 17471)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Intenti rendering</title>
+</head>
+<body>
+<h2>Intenti rendering</h2>
+
+<p>Il concetto di <i>intento rendering</i> pu&ograve; essere un po' difficile da capire per chi non &egrave; esperto nella gestione del colore. In sostanza, scegliere un certo intento rendering significa indicare a littleCMS in che modo i colori di un certo spazio colore devono essere fatti corrispondere a quelli di un altro spazio colore. Esistono quattro intenti rendering:</p>
+<ul>
+<li><b>Percettivo:</b> questo intento rendering fa corrispondere i colori in modo &ldquo;continuo&rdquo; e senza &ldquo;sbalzi&rdquo;, conservando i rapporti tra colori simili. Previene il &ldquo;clipping del gamut&rdquo; con la sua potenziale perdita di dettagli, e i problemi di &ldquo;bandeggio tonale&rdquo;. Il &ldquo;clipping del gamut&rdquo; si verifica quando due o pi&ugrave; colori, diversi nell'immagine iniziale, appaiono uguali nell'immagine stampata. L'intento rendering percettivo effettua piccoli aggiustamenti in tutta l'immagine per mantenere i rapporti tra i colori; sacrifica una parte della precisione dei colori per assicurare risultati piacevoli. Per immagini e scansioni fotografiche &egrave; di solito la scelta migliore come impostazione predefinita. <br>L'intento percettivo produce i risultati pi&ugrave; prevedibili quando si stampa da una vasta gamma di immagini sorgente, ad esempio quando si stampano immagini RGB su stampanti CMYK, o quando si tenta di utilizzare insieme dispositivi CMYK radicalmente diversi tra loro. Potete considerarla un'impostazione di uso semplice e sicuro, la migliore per gli utenti che devono gestire l'ampia variet&agrave; di immagini comunemente fornite a tipografie per grandi formati.</li>
+
+<li><b>Saturazione:</b> dovrebbe essere usato per loghi, <a href="color1.html">colori spot</a>, ecc. Tende a conservare la quantit&agrave; o la vivacit&agrave; dei colori, ma pu&ograve; dare alle fotografie un aspetto sgradevole. Se lavorate con loghi che hanno una specifica sfumatura, la saturazione fornisce una migliore corrispondenza dei colori, se per voi &egrave; pi&ugrave; importante il colore a tinta unita rispetto ai colori dell'immagine.</li>
+
+<li><b>Colorimetrico assoluto:</b> quando un colore non &egrave; stampabile (cio&egrave; non &egrave; compreso) nel gamut della periferica di output, questo intento rendering stampa al suo posto il colore pi&ugrave; simile. Riproduce i colori compresi nel gamut senza compormessi nel modo pi&ugrave; fedele possibile. Ci&ograve; produce la corrispondenza pi&ugrave; precisa dei colori spot; purtroppo pu&ograve; anche causare il &ldquo;clipping del gamut&rdquo;, in cui due colori diversi nell'originale sono identici nella stampa. Anche i punti bianchi sono soggetti a clipping, causando problemi nei rapporti tra colori nelle aree pi&ugrave; luminose delle immagini. Questo tipo di clipping, con i problemi che causa, di solito rende questo intento difficile da usare, tranne che con i colori spot. Alcuni utenti saranno sconcertati dalla sfumatura giallastra che pu&ograve; dare alle immagini, ma quest'intento &egrave; misurato in condizioni di illuminazione strettamente controllate con un illuminante standard D50; spesso ha una temperatura &ldquo;pi&ugrave; calda&rdquo; rispetto a condizioni di osservazione pi&ugrave; tipiche. Questo intento rendering &egrave; usato quasi esclusivamente quando &egrave; necessario riprodurre esattamente un logo o un colore aziendale, indipendentemente dal supporto. Il giallo Kodak pu&ograve; essere un buon esempio.</li>
+
+<li><b>Colorimetrico relativo:</b> quando un colore non &egrave; stampabile all'interno del gamut della periferica di output, questo intento rendering stampa il colore pi&ugrave; simile, con un aggiustamento che fa corrispondere il bianco alla carta usata per la stampa. Questa corrispondenza del &ldquo;punto bianco&rdquo; evita i problemi del colorimetrico assoluto con immagini che non saranno stampate con colori spot.</li>
+</ul>
+</body>
+</html>
Index: Scribus/doc/it/scripterapi-ImageExport.html
===================================================================
--- Scribus/doc/it/scripterapi-ImageExport.html (nonexistent)
+++ Scribus/doc/it/scripterapi-ImageExport.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/codingstandards.html
===================================================================
--- Scribus/doc/it/codingstandards.html (nonexistent)
+++ Scribus/doc/it/codingstandards.html (revision 17471)
@@ -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 something you put a comment immediately before the change. Ensure you put a date and who made the change and what the change is for. Make sure that the comments include the original line of code. Over time, these will be weeded out, but it useful to see what has been altered.</p>
+<p>Send a single diff for each file altered. It makes committing the changes far more simple for us!</p>
+
+<h4>Writing plugins</h4>
+
+<p>Please use the current functions and refer to the <a href="plugin_howto.html">Plugin howto</a> for further information.</p>
+<p>All code called from the main Scribus application has to be encompassed within an <code>extern "C" { ... };</code> to enable the plugin to work.
+Ensure that all the code is documented and follows the coding guidelines set out above.</p>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/toolbox6.html
===================================================================
--- Scribus/doc/it/toolbox6.html (nonexistent)
+++ Scribus/doc/it/toolbox6.html (revision 17471)
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <title>GSview</title>
+
+
+</head><body>
+<h2>GSview*</h2>
+
+<p>&Egrave; importante notare che <a href="http://pages.cs.wisc.edu/%7Eghost/gsview/index.htm">GSview</a> <b>non deve essere confuso</b> con <strong style="font-weight: normal;">ghostview, gv e i loro derivati!</strong> Anche se Adobe Reader spesso &egrave; migliore come visualizzatore puro per documenti PDF, GSview dovrebbe essere considerato uno degli strumenti essenziali per l'uso con Scribus. GSview comprende alcune funzioni estremamente utili. Per coloro che non conoscono il programma, diciamo che fornisce un'interfaccia di facile uso per <a href="toolbox5.html">Ghostscript</a> e per <code>pstoedit</code>, per la conversione di file bitmap in file vettoriali e viceversa. Per coloro che hanno un'esperienza di DTP tradizionale in ambiente Mac/Windows, fornisce anche alcune delle funzionalit&agrave; di Adobe Acrobat.<br>
+</p>
+
+<p>Dovreste sempre usare la versione pi&ugrave; recente, almeno la 4.7. (GSview fu originariamente sviluppato in ambiente Windows, e ha raggiunto una qualit&agrave; eccellente fin dalle versioni 4.x.)</p>
+
+<p>Per l'uso con Scribus, GSview offre le seguenti funzionalit&agrave;:</p>
+
+<ul>
+
+ <li>con l'aiuto di <a href="http://pstoedit.net">pstoedit</a>, potete convertire immagini bitmap o documenti PDF in file SVG e altri <a href="importhints.html">formati vettoriali</a>;</li>
+ <li>la capacit&agrave; di visualizzare in anteprima, convertire e aggiungere anteprime (consigliato per il TIFF) a file PostScript ed <a href="importhints1.html">EPS (Encapsulated PostScript)</a>;</li>
+ <li>la capacit&agrave; di estrarre testo da file PDF, EPS e PostScript;</li>
+ <li>una facile interfaccia per le caratteristiche meno note di Ghostscript come la conversione e il ricampionamento di immagini;</li>
+<li>altre caratteristiche sono: la conversione tra formati TIFF, la modifica della profondit&agrave; di colore di un file TIFF o JPEG o dello spazio colore di un'immagine.</li>
+</ul>
+
+<table width="90%"><tr><td align="center"><img src="images/tb-gsview.png"></td></tr></table>
+
+<p>Un esempio di una situazione in cui GSview &egrave; molto utile con Scribus &egrave; l'individuazione e la correzione di errori presenti in file EPS che non vengono visualizzati correttamente in Scribus. Molte applicazioni sono in grado di generare file EPS, ma alcune vi aggiungono delle caratteristiche insolite che possono causare problemi quando questi file sono utilizzati in altri programmi (come Scribus).</p>
+
+<p>Quindi, se incontrate difficolt&agrave; con un file EPS che desiderate utilizzare in Scribus, apritelo in GSview. Poi usate il comando da tastiera <strong>M</strong> per visualizzare i messaggi emessi da Ghostscript: questi messaggi possono indicare i problemi che causano errori di visualizzazione o stampa. Potete inoltre usare la &lsquo;periferica&rsquo; <strong>epswrite</strong> da GSview per salvare nuovamente l'EPS, operazione che pu&ograve; aiutare a eliminare o correggere errori in un file EPS.</p>
+
+<p>Potete anche <em>rasterizzare</em> un'immagine EPS, convertendola in PNG o TIFF e poi ridimensionarla, correggere i colori, e cos&igrave; via, con programmi di grafica come <a href="toolbox4.html">GIMP</a> o <a href="toolbox15.html">Krita</a>.<br>
+</p>
+
+<p>GSview utilizza la libreria condivisa <code>libgs.so</code> per accedere a Ghostscript. Non tutte le distribuzioni Linux la comprendono; in queste situazioni dovreste seguire i consigli per compilare Ghostscript con un'installazione parallela.</p>
+
+<h4>Procurarsi GSview:</h4>
+
+<p>GSview &egrave; disponibile per la maggior parte delle distribuzioni Linux, almeno per le maggiori. Altrimenti potete compilarlo seguendo le istruzioni contenute nel <a href="http://pages.cs.wisc.edu/%7Eghost/">pacchetto del codice sorgente</a>. Per Windows, OS/2 ed eComStation potete scaricare <a href="http://pages.cs.wisc.edu/%7Eghost/gsview/index.htm">i normali programmi di installazione</a>. Purtroppo non &egrave; disponibile alcuna versione attuale per Mac OS X.</p>
+
+<p><i>Una nota speciale per gli utenti di OpenSUSE</i>: a partire dalla versione 11.3, le librerie GTK&nbsp;1, che sono necessarie, non sono pi&ugrave; disponibili per questa distribuzione, ma potete servirvi delle <a href="http://download.opensuse.org/repositories/GNOME:/GNOME1/openSUSE_Factory">versioni che si trovano nel repository OpenSUSE Factory</a>. Dovete installare i pacchetti gtk-1.20 e glib (e se volete compilare direttamente GSview, anche i rispettivi pacchetti RPM devel), e inoltre il pacchetto linguistico che si trova nella directory &ldquo;noarch&rdquo;.<br>
+</p>
+
+<p>Per suggerimenti avanzati su GSview e Ghostscript, vedere <a href="toolbox7.html">Ghostscript avanzato &amp; GSView</a>.</p>
+
+<p>*) <span style="font-style: italic;">Per il contenuto di questa pagina ringraziamo Russell Lang, autore e sviluppatore di GSview, epstool e Ghostscript, per i suggerimenti e le pazienti risposte ai quesiti su GSview e Ghostscript.</span></p>
+
+</body></html>
Index: Scribus/doc/it/specs.html
===================================================================
--- Scribus/doc/it/specs.html (nonexistent)
+++ Scribus/doc/it/specs.html (revision 17471)
@@ -0,0 +1,540 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus 1.4 Data Sheet</title>
+</head>
+<body>
+<h2>Scribus 1.4 Data Sheet</h2><br>
+
+<body text="#000000">
+<table frame=VOID cellspacing=0 cols=2 rules=NONE border=0>
+
+ <tbody>
+ <tr>
+ <td height=42 align=LEFT bgcolor="#CCCCCC"><b>Supported Operating Systems</b></td>
+ <td align=LEFT bgcolor="#CCCCCC">Linux, FreeBSD, NetBSD, OpenBSD, Solaris, OpenSolaris, Nexenta, Mac&nbsp;OS&nbsp;X 10.5 or later, OS/2 Warp 4, eComStation 1 or later, Windows 2000 or later</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>UI Languages</b></td>
+ <td align=LEFT sdval="25" sdnum="1031;">25</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Import Filters</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Text</td>
+ <td align=LEFT>Open Document Text (ODT), OpenOffice.org Writer 1 (SXW), HTML, MS Word (DOC), Comma Separated Values (CSV), Plain Text in various encodings. </td>
+ </tr>
+ <tr>
+ <td height=84 align=LEFT bgcolor="#CCCCCC">Bitmap</td>
+ <td align=LEFT bgcolor="#CCCCCC">Desktop Color Separations (DCS), Encapsulated PostScript (EPS), Graphics Interchange Format (GIF), JPEG, Portable Networks Graphic (PNG), Photoshop Document (PSD), Tagged Image File Format (TIFF), Windows and OS/2 Bitmap (BMP), X PixMap (XPM)</td>
+ </tr>
+ <tr>
+ <td height=103 align=LEFT>Vector</td>
+ <td align=LEFT>Adobe Illustrator (AI), Calamus Vector Graphics (CVG), Dia Shapes (SHAPE), Encapsulated PostScript (EPS), Kivio Stencils (SML), OpenDocument Graphics (ODG), OpenOffice.org Draw (SXD), Macintosh PICT File (PICT), PostScript (PS), Scalable Vector Graphics (SVG, SVGZ), Scribus Objects (SCE), Windows Metafile (WMF), Xfig (FIG)</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT bgcolor="#CCCCCC">Color Palettes</td>
+ <td align=LEFT bgcolor="#CCCCCC">Adobe Illustrator (AI), Encapsulated PostScript (EPS), GIMP Palette (GPL), OpenDocument Swatch (SOC), PostScript (PS), Scribus Palette (XML)</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Other</td>
+ <td align=LEFT>PDF (direct opening and import into image frames), Scribus Unicode Glyph Palette (UCP)</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Export Filters:</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>PDF:</td>
+ <td align=LEFT>1.3, 1.4, 1.5, X-3</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">PostScript:</td>
+ <td align=LEFT bgcolor="#CCCCCC">Level 2, 3</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Vector:</td>
+ <td align=LEFT>Encapsulated PostScript (EPS), Scalable Vector Graphics (SVG, SVGZ)</td>
+ </tr>
+ <tr>
+ <td height=42 align=LEFT bgcolor="#CCCCCC">Bitmap:</td>
+ <td align=LEFT bgcolor="#CCCCCC">BMP, BW, EPS, ICO, JP2, JPEG, PCX, PIC, PNG, PPM, RGB, RGBA, SGI, TGA, TIFF, XBM, XPM, XV</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Text:</td>
+ <td align=LEFT>Plain Text</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Native File Formats</b></td>
+ <td align=LEFT bgcolor="#CCCCCC">SLA (XML-based Plain Text), SLA.GZ (Compressed SLA)</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Layout/Page Management</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Preset Margin Layouts</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Master Pages</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Grids/Guides</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Page Palette</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Layers</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Page Import</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Flexible Page Numbering</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Individual Page Layout/Dimensions</td>
+ <td align=LEFT>✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Table of Contents</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Bookmarks</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Text/Typography</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=19 align=LEFT>Paragraph/Character Styles</td>
+ <td align=LEFT>✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Style Manager</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Glyph Scaling</td>
+ <td align=LEFT>Manual/Automatic</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Character/Word Tracking</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Glyph Extension</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Optical Margins</td>
+ <td align=LEFT bgcolor="#CCCCCC">Left, Right</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Drop Caps</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">First Line Offset</td>
+ <td align=LEFT bgcolor="#CCCCCC">Maximum Ascent, Font Ascent, Line Spacing</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Baseline Grid</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Indent/Tabulators</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Columns/Text Distance from Frame</td>
+ <td align=LEFT>✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Text Flow around Objects</td>
+ <td align=LEFT bgcolor="#CCCCCC">Automatic/Flexible</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Hyphenation Control</td>
+ <td align=LEFT>Language-based, Consecutive Hyphenations, Smallest Word, Exception List, Ignore List</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Spellcheck</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓<sup>1</sup></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Linebreak Control for Abbreviations</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Inline Objects</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Supported Font Formats</td>
+ <td align=LEFT>Type 1 (Mac and PC), TrueType, OpenType</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Font Management</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Font Previewer</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Control Characters</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Integrated Text Editor (Story Editor)</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Glyph Collections</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Tables</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Text along Path</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Bitmap Images</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">RGB/CMYK/Spot Color</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Support for Embedded Clipping Paths</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Support for Layers/Blend Modes</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Non-destructive Image Effects</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Image Manager</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>EXIF Support</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Configurable Preview Resolution</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Assignment of Color Profiles to Individual Image Frames</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Launcher for External Image Editor</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Vector Graphics</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Import as Vector</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Import as Image</td>
+ <td align=LEFT>✓<sup>2</sup></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Color Import</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Drawing Tools</td>
+ <td align=LEFT>Straight Lines, Bézier Curves, Freehand Lines, Shape Library</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Line Styles/Line Style Editor</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Path Tools</td>
+ <td align=LEFT>Lens Effects, Mesh Distortion, Path Along Path, Connect Paths, Cut Polygon, Boolean Path Operations, Path from Stroke, Subdivide Path</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Text Import</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓<sup>3</sup></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Object Handling</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Duplicate/Multiple Duplicate/Transform</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Editable Frame Shapes</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Property-based Multiple Select</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Undo/Redo</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Action Manager</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Object Browser</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Align/Distribute/Mirror/Rotate</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Scratch Space around Pages</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Configurable Rulers</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Scrapbook for Reuseable Objects</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Measuring Tool</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Fill</td>
+ <td align=LEFT>Solid Colors, Gradients (Horizontal, Vertical, Diagonal, Cross, Radial), Patterns (Bitmap and Vector)</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Color Palette Management</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT>Solid/Spot Color Palettes</td>
+ <td align=LEFT>More than 150 color palettes, including Open Source Palettes, National/Government Standards, Resene® Colors, Crayola® Colors, GCMI Colors, dtp studio collection</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Frame Type Conversion</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Transparency/Blend Modes</td>
+ <td align=LEFT>✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Grouping/Locking/Combining of Objects</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Support for Traditional Measuring Units</td>
+ <td align=LEFT>Cicero, Pica</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Pre-Press/Printing</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>RGB/CMYK/Spot Colors</td>
+ <td align=LEFT>✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Color Management</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Printer Emulation on Screen</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Out-of-Gamut Warning</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Emulation of Color Blindness</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Knockout/Overprinting</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Color Separations</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Printing Marks</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Print/Separation Preview</td>
+ <td align=LEFT>✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Display of Ink Coverage</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Under Color Removal</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Document Bleed</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Font Embedding Control</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Preflight Verifier</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Collect for Output</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Scripting</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Supported Languages</td>
+ <td align=LEFT>Python</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Scripting Console</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Ready-to-Use Scripts via UI</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Sample Scripts</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Other Features</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=46 align=LEFT bgcolor="#CCCCCC">Render Frames to Render Markup Languages Inside Scribus</td>
+ <td align=LEFT bgcolor="#CCCCCC">Pre-configured for LaTeX, Lilypond, Gnuplot, GraphViz, POV-Ray</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>PDF-Forms</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">PDF JavaScript</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>PDF Presentations</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">PDF Encryption</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>PDF/EPS Embedding in PDF Files</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Color Wheel to Create Color Harmonies</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Barcode Generator</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Dublin Core Metadata Support</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT><b>Documentation/Support</b></td>
+ <td align=LEFT></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Tooltips</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Integrated Help/<br>Searchable/Bookmarks</td>
+ <td align=LEFT>✓/✓/✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Printed Manual</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓<sup>4</sup></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Templates</td>
+ <td align=LEFT>✓</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC"><b>Architecture</b></td>
+ <td align=LEFT bgcolor="#CCCCCC"></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Programming Language</td>
+ <td align=LEFT>C++ (some portions from third parties are written in C)</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Underlying UI Toolkit</td>
+ <td align=LEFT bgcolor="#CCCCCC">Qt 4.6 or later</td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT>Dependencies</td>
+ <td align=LEFT>See the list of <a href="install2.html">requirements</a></td>
+ </tr>
+ <tr>
+ <td height=24 align=LEFT bgcolor="#CCCCCC">Plug-in Interface</td>
+ <td align=LEFT bgcolor="#CCCCCC">✓</td>
+ </tr>
+</tbody>
+</table>
+<hr>
+<p><sup>1</sup> Not available on OS/2, eComStation and Windows.</p>
+<p><sup>2</sup> EPS and PostScript only.</p>
+<p><sup>3</sup> AI and EPS only.</p>
+<p><sup>4</sup> For the previous version. An update is being worked on.</p>
+<hr>
+<p><b>License</b>: <a href="scribuscopyright.html">GPL 2 with exceptions</a></p>
+</body>
+
+</html>
Index: Scribus/doc/it/install-dpkg.html
===================================================================
--- Scribus/doc/it/install-dpkg.html (nonexistent)
+++ Scribus/doc/it/install-dpkg.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/toolbox18.html
===================================================================
--- Scribus/doc/it/toolbox18.html (nonexistent)
+++ Scribus/doc/it/toolbox18.html (revision 17471)
@@ -0,0 +1,25 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>LibreOffice/OpenOffice.org</title>
+</head>
+<body>
+<h2>LibreOffice/OpenOffice.org</h2>
+
+<p><a href="http://www.libreoffice.org">LibreOffice</a> e <a href="http://www.openoffice.org">OpenOffice.org</a> sono due pacchetti open source di programmi da ufficio che hanno in comune il codice sorgente. Che preferiate l'uno o l'altro, dovreste considerarlo uno strumento di grande utilit&agrave; da usare con Scribus.</p>
+<p>In primo luogo, Scribus contiene alcuni <a href="importhints3.html">potenti filtri di importazione</a> per i vecchi formati nativi di OpenOffice.org, e per il pi&ugrave; recente standard internazionale ODF, che entrambi i pacchetti utilizzano molto bene.</p>
+
+<p>In secondo luogo, e altrettanto importante, entrambi i pacchetti sono in grado di utilizzare un grandissimo numero di formati di file diversi, il che significa che potete usarli come versatili convertitori di file, specialmente per documenti di testo e file grafici (vettoriali). Riportiamo di seguito un elenco dei formati di file che LibreOffice pu&ograve; aprire e convertire per l'uso in Scribus.</p>
+
+<p><b>Formati di documenti di testo:</b></p>
+<p>DocBook (*.xml), documento Hangui WP 97 (*.hwp), documento Lotus WordPro (*.lwp), documento MS Word 5, 6, 95, 97, 2000, XP (*.doc), modello MS Word 95, 97, 2000, XP (*.dot), documento MS Word 2003, 2007 (*.docx, *.docm, *.xml), modello MS Word 2003, 2007 (*.dotx, *.docm), documento MS Works (*.wps), documento Office Open XML (*.docx, *.docm, *.xml), modello Office Open XML (*.dotx, *.docm), Pocket Word (*.psw), Rich Text Format (*.rtf), documento StarOffice Writer 1, 2, 3, 4, 5 (*.sdw), modello StarOffice Writer 1, 2, 3, 4, 5 (*.vor), documento T602 (*.602, *.txt), documento Unified Office Format Text (*.uof, *.uot), documento WordPerfect (*.wpd)</p>
+
+<p><b>Formati grafici (solo formati vettoriali, poich&eacute; vi sono convertitori migliori per le immagini bitmap):</b></p>
+<p>AutoCAD Interchange Format (*.dxf), Computer Graphics Metafile (*.cgm), Enhanced Metafile (*.emf), OS/2 Metafile (*.met), StarOffice Writer Graphics File (*.sgf), StarOffice Drawing (*.sgv), StarView Metafile (*.svm)</p>
+
+<p>Inoltre, potete aprire diapositive create con programmi per presentazioni come PowerPoint o Impress e convertirle in un formato vettoriale o bitmap che Scribus &egrave; in grado di importare.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/tb-libreoffice.png" title="Modifica di un'immagine clipart con LibreOffice Draw" alt="Modifica di un'immagine clipart con LibreOffice Draw"/></td></tr><tr><td><div align="center"><i>Modifica di un'immagine clipart con LibreOffice Draw</i></div></td></tr></table>
+
+</body>
+</html>
Index: Scribus/doc/it/releases.html
===================================================================
--- Scribus/doc/it/releases.html (nonexistent)
+++ Scribus/doc/it/releases.html (revision 17471)
@@ -0,0 +1,51 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+<title>Release History</title>
+</head>
+<body>
+<h2>Release History</h2>
+<ul>
+<li><b>27/10/2010</b> - Scribus 1.3.9 (devel) </li>
+<li><b>23/07/2010</b> - Scribus 1.3.8 (devel) </li>
+<li><b>05/06/2010</b> - Scribus 1.3.7 (devel) </li>
+<li><b>22/03/2010</b> - Scribus 1.3.6 (devel) </li>
+<li><b>12/02/2010</b> - Scribus 1.3.3.14 </li>
+<li><b>28/05/2009</b> - Scribus 1.3.5 (devel) </li>
+<li><b>15/04/2008</b> - Scribus 1.3.3.13 </li>
+<li><b>12/06/2008</b> - Scribus 1.3.3.12 </li>
+<li><b>12/01/2008</b> - Scribus 1.3.3.11 </li>
+<li><b>08/01/2008</b> - Scribus 1.3.3.10 </li>
+<li><b>28/05/2007</b> - Scribus 1.3.4 (devel) </li>
+<li><b>05/05/2007</b> - Scribus 1.3.3.9 </li>
+<li><b>23/02/2007</b> - Scribus 1.3.3.8 </li>
+<li><b>09/01/2007</b> - Scribus 1.3.3.7 (added OS/2 Port)</li>
+<li><b>04/12/2006</b> - Scribus 1.3.3.6 </li>
+<li><b>09/11/2006</b> - Scribus 1.3.3.5 </li>
+<li><b>03/10/2006</b> - Scribus 1.3.3.4 </li>
+<li><b>07/08/2006</b> - Scribus 1.3.3.3 </li>
+<li><b>14/07/2006</b> - Scribus 1.2.5 </li>
+<li><b>29/05/2006</b> - Scribus 1.3.3.2 (devel) </li>
+<li><b>10/04/2006</b> - Scribus 1.3.3.1 (devel) </li>
+<li><b>27/01/2006</b> - Scribus 1.3.3 (devel) </li>
+<li><b>22/01/2006</b> - Scribus 1.3.2 (devel) (added Win32 port)</li>
+<li><b>05/01/2006</b> - Scribus 1.2.4.1 </li>
+<li><b>03/10/2005</b> - Scribus 1.3.1 (devel) </li>
+<li><b>12/09/2005</b> - Scribus 1.2.3 </li>
+<li><b>14/07/2005</b> - Scribus 1.3.0 (added Mac OSX port)</li>
+<li><b>05/07/2005</b> - Scribus 1.2.2.1 </li>
+<li><b>08/01/2005</b> - Scribus 1.2.1 </li>
+<li><b>28/08/2004</b> - Scribus 1.2 </li>
+<li><b>06/06/2004</b> - Scribus 1.1.7 </li>
+<li><b>28/03/2004</b> - Scribus 1.1.6 </li>
+<li><b>14/02/2004</b> - Scribus 1.1.5 </li>
+<li><b>18/12/2003</b> - Scribus 1.1.4 </li>
+<li><b>28/11/2003</b> - Scribus 1.1.3 </li>
+<li><b>28/10/2003</b> - Scribus 1.1.2 </li>
+<li><b>03/10/2003</b> - Scribus 1.1.1 </li>
+<li><b>06/09/2003</b> - Scribus 1.1.0 </li>
+<li><b>07/08/2003</b> - Scribus 1.0.1 </li>
+<li><b>21/06/2003</b> - Scribus 1.0 </li>
+
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/scripterapi-dialogs.html
===================================================================
--- Scribus/doc/it/scripterapi-dialogs.html (nonexistent)
+++ Scribus/doc/it/scripterapi-dialogs.html (revision 17471)
@@ -0,0 +1,85 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Using Dialogs from Scribus</title>
+</head>
+<body>
+<h2>Using Dialogs from Scribus</h2>
+
+<dl>
+
+<dt><a name="-fileDialog"><strong>fileDialog</strong></a>(...)</dt>
+<dd><code>fileDialog("caption", ["filter", "defaultname", haspreview, issave, isdir])<br> -&gt; string with filename</code>
+<p>Shows a File Open dialog box with the caption "caption". Files are filtered with the filter string "filter". A default filename or file path can also supplied, leave this string empty when you don't want to use it. A value of True for haspreview enables a small preview widget in the FileSelect box. When the issave parameter is set to True the dialog acts like a "Save As" dialog otherwise it acts like a "File Open Dialog". When the isdir parameter is True the dialog shows and returns only directories. The default for all of the opional parameters is False.<p>
+<p>The filter, if specified, takes the form 'comment (*.type *.type2 ...)'. For example 'Images (*.png *.xpm *.jpg)'.</p>
+<p>Refer to the Qt-Documentation for QFileDialog for details on filters.</p>
+<p>Example: <a href="#-fileDialog">fileDialog</a>('Open input', 'CSV files (*.csv)')<br>
+Example: <a href="#-fileDialog">fileDialog</a>('Save report', defaultname='report.txt', issave=True)</p></dd>
+
+<dt><a name="-fileQuit"><strong>fileQuit</strong></a>(...)</dt>
+<dd><code>fileQuit()</code>
+<p>Quit Scribus.</p></dd>
+
+<dt><a name="-getGuiLanguage"><strong>getGuiLanguage</strong></a>(...)</dt>
+<dd><code>getGuiLanguage() -&gt; string</code>
+<p>Returns a string with the -lang value.</p></dd>
+
+<dt><a name="-messagebarText"><strong>messagebarText</strong></a>(...)</dt>
+<dd><code>messagebarText("string")</code>
+<p>Writes the "string" into the Scribus message bar (status line). The text must be UTF8 encoded or 'unicode' string(recommended).</p></dd>
+
+<dt><a name="-messageBox"><strong>messageBox</strong></a>(...)</dt>
+<dd><code>messageBox("caption", "message",
+icon=ICON_NONE, button1=BUTTON_OK|BUTTONOPT_DEFAULT,
+button2=BUTTON_NONE, button3=BUTTON_NONE) -&gt; integer</code>
+<p>Displays a message box with the title "caption", the message "message", and an icon "icon" and up to 3 buttons. By default no icon is used and a single button, OK, is displayed. Only the caption and message arguments are required, though setting an icon and appropriate button(s) is strongly recommended. The message text may contain simple HTML-like markup.</p>
+<p>Returns the number of the button the user pressed. Button numbers start at 1.</p>
+<p>For the icon and the button parameters there are predefined constants available with the same names as in the Qt Documentation. These are the BUTTON_* and ICON_* constants defined in the module. There are also two extra constants that can be binary-ORed with button constants:</p>
+<ul>
+<li>BUTTONOPT_DEFAULT Pressing enter presses this button.</li>
+<li>BUTTONOPT_ESCAPE Pressing escape presses this button.</li>
+</ul>
+<p>Usage examples:</p>
+<pre>
+result = <a href="#-messageBox">messageBox</a>('Script failed',
+ 'This script only works when you have a text frame selected.',
+ ICON_ERROR)
+result = <a href="#-messageBox">messageBox</a>('Monkeys!', 'Something went ook! &lt;i&gt;Was it a monkey?&lt;/i&gt;',
+ ICON_WARNING, BUTTON_YES|BUTTONOPT_DEFAULT,
+ BUTTON_NO, BUTTON_IGNORE|BUTTONOPT_ESCAPE)
+</pre>
+<p>Defined button and icon constants: BUTTON_NONE, BUTTON_ABORT, BUTTON_CANCEL, BUTTON_IGNORE, BUTTON_NO, BUTTON_NOALL, BUTTON_OK, BUTTON_RETRY, BUTTON_YES, BUTTON_YESALL, ICON_NONE, ICON_INFORMATION, ICON_WARNING, ICON_CRITICAL.</p></dd>
+
+<dt><a name="-newDocDialog"><strong>newDocDialog</strong></a>(...)</dt>
+<dd><code>newDocDialog() -&gt; bool</code>
+<p>Displays the "New Document" dialog box. Creates a new document if the user accepts the settings. Does not create a document if the user presses cancel. Returns true if a new document was created.</p></dd>
+
+<dt><a name="-newStyleDialog"><strong>newStyleDialog</strong>(...)</a></dt>
+<dd><code>newStyleDialog() -&gt; string</code>
+<p>Shows 'Create new paragraph style' dialog. Function returns real style name or None when user cancels the dialog.</p></dd>
+
+<dt><a name="-statusMessage"><strong>statusMessage</strong></a>(...)</dt>
+<dd><code>messagebarText("string")</code>
+<p>Writes the "string" into the Scribus message bar (status line). The text must be UTF8 encoded or 'unicode' string(recommended).</p></dd>
+
+<dt><a name="-progressReset"><strong>progressReset</strong></a>(...)</dt>
+<dd><code>progressReset()</code>
+<p>Cleans up the Scribus progress bar previous settings. It is called before the new progress bar use. See progressSet.</p></dd>
+
+<dt><a name="-progressSet"><strong>progressSet</strong></a>(...)</dt>
+<dd><code>progressSet(nr)</code>
+<p>Set the progress bar position to "nr", a value relative to the previously set progressTotal. The progress bar uses the concept of steps; you give it the total number of steps and the number of steps completed so far and it will display the percentage of steps that have been completed. You can specify the total number of steps with <a href="#-progressTotal">progressTotal</a>(). The current number of steps is set with <a href="#-progressSet">progressSet</a>(). The progress bar can be rewound to the beginning with <a href="#-progressReset">progressReset</a>(). [based on info taken from Trolltech's Qt docs]</p></dd>
+
+<dt><a name="-progressTotal"><strong>progressTotal</strong></a>(...)</dt>
+<dd><code>progressTotal(max)</code>
+<p>Sets the progress bar's maximum steps value to the specified number. See progressSet.</p></dd>
+
+<dt><a name="-valueDialog"><strong>valueDialog</strong></a>(...)</dt>
+<dd><code>valueDialog(caption, message [,defaultvalue]) -&gt; string</code>
+<p>Shows the common 'Ask for string' dialog and returns its value as a string Parameters: window title, text in the window and optional 'default' value.</p>
+<p>Example: <a href="#-valueDialog">valueDialog</a>('title', 'text in the window', 'optional')</p></dd>
+
+</dl>
+
+</body>
+</html>
Index: Scribus/doc/it/gettexthowto.html
===================================================================
--- Scribus/doc/it/gettexthowto.html (nonexistent)
+++ Scribus/doc/it/gettexthowto.html (revision 17471)
@@ -0,0 +1,153 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>How To Write a Scribus Get Text Plugin</title>
+</head>
+<body>
+<h2>How To Write a Scribus Get Text Plugin</h2>
+<h4>Plugin interface and article written by Riku Leino</h4>
+<h3>Preface</h3>
+
+<p>This article shows you how to write Get Text plugins for Scribus. Plugins are dynamic loaded libraries in "so" format. Get Text Plugins are used to import formatted text from all kinds of file formats into a Scribus text frame.</p>
+
+<h4>Important</h4>
+
+<p>Wait here for a while! Maybe you are at the edge of reinventing the wheel - so join the mailing-list or visit #scribus channel at irc.freenode.net. Your topic will be discussed and you'll get support too. We cannot stop you to write anything you want - sure. :)))</p>
+
+<h3>An Example Plugin</h3>
+
+<h4>myimporter.h</h4>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+#ifndef MYIMPORTER_H
+#define MYIMPORTER_H
+
+#include &lt;scribus.h&gt;
+#include &lt;gtwriter.h&gt;
+
+extern "C" void GetText(QString filename, QString encoding, bool textOnly, gtWriter *writer);
+
+extern "C" QString FileFormatName();
+
+extern "C" QStringList FileExtensions();
+
+#endif // MYIMPORTER_H
+</pre>
+</td></tr></table></blockquote>
+<p>Now let's describe the source code. MYIMPORTER_H declaration is the standard way to ensure only one insertion of the header file. Scribus.h is required to access Scribus objects. The function GetText() is called when a user has selected to import a file that has a file extenison which matches one in the QStringList returned by FileExtensions(). FileFormatName() should return the name for the file format this importer works on f.e. "Text files" for plain text importer.</p>
+
+<h4>GetText parameters</h4>
+<ul>
+<li><strong>fileName</strong>: path to a file that a user wants to import</li>
+<li><strong>encoding</strong>: Character encoding a user has selected in a file dialog</li>
+<li><strong>textOnly</strong>: if true a user wants to import text from the file without any formatting</li>
+<li><strong>writer</strong>: gtWriter object that is used to import the text</li>
+</ul>
+
+<h4>File extensions</h4>
+<p>If your plugin is the only plugin for the file format return a QStringList with format's file extensions. If there already is an importer for the format you are also creating an importer for do not return file extensions but an empty QStringList. The most common and used plugin for a file format should return file extensions. Other more rarely used plugins should not return extensions. These plugins can be used by selecting them in the file dialog of Get Text.</p>
+
+<h4>myimporter.cpp</h4>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+#include "myimporter.h"
+#include &lt;qstring.h&gt;
+#include &lt;qstringlist.h&gt;
+
+QString FileFormatName()
+{
+ return QObject::tr("Nothing to import");
+}
+
+QStringList FileExtensions()
+{
+ // QStringList list("htm"); list << "html" << "php"; return list;
+ return QStringList();
+}
+
+void GetText(QString filename, QString encoding, bool textOnly, gtWriter *writer)
+{
+
+}
+</pre>
+</td></tr></table></blockquote>
+
+<p>The <code>importnothingplugin-1.0.tar.bz2</code> from http://docs.scribus.net can be used as a basis of your own get text plugin.</p>
+
+<h3>How does it work?</h3>
+
+<p>Text can be appended to a text frame with gtWriter::append() methods. append(QString text) appends text formatted with the style of the text frame. append(QString text, gtStyle *style) will use the style given as a parameter.</p>
+
+<p>gtStyle, gtParagraphStyle and gtFrameStyle can be used to set the style for imported text. The easiest way to get started is to use gtWriter's getDefaultStyle() method to get the text frame's current style and then use the gtFrameStyle returned to create new styles.</p>
+
+<p>gtStyle works on character styles and can be used inside a paragraph style. gtParagraphStyle creates a paragraph style in Scribus and can be used to apply a paragraph style to the text when importing. gtFrameStyle gives a possibility to change the default style of the text frame. Relation between these three classes is: gtStyle works as a base class. gtParagraphStyle extends gtStyle and gtFrameStyle extends gtParagraphStyle. They all have a gtFont object that can be obtained with getFont() method. gtFont object can be used to set some character based formatting. See the header files: gtfont.h, gtstyle.h, gtparagraphstyle.h and gtframestyle.h to get a better idea of the interfaces.</p>
+
+<p>There is also one helper class gtMeasure with static methods to convert length units to points which is the default unit scribus uses internally. For example converting 25 millimeters to points one can use gtMeasure's method i2d() (int to double): gtMeasure::i2d(25, MM). Second parameter tells the unit from where the conversion to points is done. All the possible units are defined as an enumeration Unit (see file gtmeasure.h).</p>
+
+<h3>Simple example</h3>
+
+<h4>Text to import</h4>
+
+Lorem ipsum dolor sit amet, consectetuer adipiscing elit. <strong>Ut a sapien.</strong> Aliquam aliquet purus molestie dolor. Integer quis eros ut erat posuere dictum. Curabitur dignissim. Integer orci. Fusce vulputate lacus at ipsum. Quisque in libero nec mi laoreet volutpat.<br>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Aliquam eros pede, scelerisque quis, tristique cursus, placerat convallis, velit. Nam condimentum. Nulla ut mauris. Curabitur adipiscing, mauris non dictum aliquam, arcu risus dapibus diam, nec sollicitudin quam erat quis ligula. Aenean massa nulla, volutpat eu, accumsan et, fringilla eget, odio. Nulla placerat porta justo. Nulla vitae turpis. Praesent lacus.
+
+<h4>Code for import</h4>
+
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+#include &lt;gtparagraphstyle.h&gt;
+#include &lt;gtframestyle.h&gt;
+#include &lt;gtmeasure.h&gt;
+
+...
+
+void GetText(QString filename, QString encoding, bool textOnly, gtWriter *writer)
+{
+
+/***** Create Paragraph Styles *************************************************/
+ gtFrameStyle* fstyle = writer->getDefaultStyle();
+
+ gtParagraphStyle* firstPara = new gtParagraphStyle(*fstyle);
+ firstPara->setName("First Paragraph");
+ firstPara->getFont()->setSize(12.0);
+ firstPara->setLineSpacing(14.4);
+
+ gtParagraphStyle* trailingPara = new gtParagraphStyle(*firstPara);
+ trailingPara->setName("Traling Paragraph");
+ trailingPara->setFirstLineIndent(gtMeasure::i2d(15, MM));
+
+/***** Import Text *************************************************************/
+ writer->append("Lorem ipsum dolor sit amet, consectetuer adipiscing elit. ", firstPara);
+
+ QString currentWeight = firstPara->getFont()->getWeight();
+ firstPara->getFont()->setWeight(BOLD); // from enum FontWeight (gtfont.h)
+ writer->append("Ut a sapien.", firstPara); // import with a bold font
+
+ firstPara->getFont()->setWeight(currentWeight);
+ writer->append(" Aliquam aliquet purus molestie dolor. Integer quis eros ut "
+ "erat posuere dictum. Curabitur dignissim. Integer orci. Fusce "
+ "vulputate lacus at ipsum. Quisque in libero nec mi laoreet "
+ "volutpat.\n", firstPara);
+
+ // 2nd Paragraph
+ writer->append("Aliquam eros pede, scelerisque quis, tristique cursus, placerat "
+ "convallis, velit. Nam condimentum. Nulla ut mauris. Curabitur "
+ "adipiscing, mauris non dictum aliquam, arcu risus dapibus diam, nec "
+ "sollicitudin quam erat quis ligula. Aenean massa nulla, "
+ "volutpat eu, accumsan et, fringilla eget, odio. Nulla placerat porta "
+ "justo. Nulla vitae turpis. Praesent lacus.", trailingPara);
+
+ delete firstPara;
+ delete trailingPara;
+}
+
+...
+</pre>
+</td></tr></table></blockquote>
+
+<p>Now after right clicking on a text frame, choosing "Get Text..." and selecting our just built importer and opening some file we get a text frame with the sample text formatted correctly.</p>
+<table width="100%"><tr><td align="center"><img src="images/result.png" alt="Sample frame"/></td></tr></table>
+
+<p>If you have any questions send mail to Riku Leino (IRC nick:Tsoots) tsoots at gmail.com, register for Scribus mailing list or join the irc channel #scribus at irc.freenode.net.</p>
+</body>
+</html>
Index: Scribus/doc/it/scripterapi-Printer.html
===================================================================
--- Scribus/doc/it/scripterapi-Printer.html (nonexistent)
+++ Scribus/doc/it/scripterapi-Printer.html (revision 17471)
@@ -0,0 +1,89 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Python: class Printer</title>
+</head>
+<body>
+<h2>Python: class Printer</h2>
+<p>
+<a name="Printer">class <strong>Printer</strong></a>(<a href="__builtin__.html#object">object</a>)
+</p>
+<hr />
+
+<p>Methods defined here:</p>
+<dd>
+ <dt><a name="Printer-Print"><strong>Print</strong></a>(...)</dt>
+ <dd><code>This method is deprecated - use <a href="#Printer-print">print</a>() instead.</code></dd>
+
+ <dt><a name="Printer-__init__"><strong>__init__</strong></a>(...)</dt>
+ <dd><code>x.<a href="#Printer-__init__">__init__</a>(...) initializes x; see x.__class__.__doc__ for signature</code></dd>
+
+ <dt><a name="Printer-print"><strong>print</strong></a>(...)</dt>
+ <dd><code>Prints selected pages.</code></dd>
+
+<hr>
+<p>Data and other attributes defined here:</p>
+<dd>
+ <dt><strong>__new__</strong> = &lt;built-in method __new__ of type object&gt;</dt>
+ <dd><code>T.<a href="#Printer-__new__">__new__</a>(S, ...) -&gt; a new object with type S, a subtype of T</code></dd>
+
+ <dt><strong>allPrinters</strong> = &lt;attribute 'allPrinters' of 'Printer' objects&gt;</dt>
+ <dd><code>List of installed printers -- read only</code></dd>
+
+ <dt><strong>cmd</strong> = &lt;attribute 'cmd' of 'Printer' objects&gt;</dt>
+ <dd><code>Alternative Printer Command</code></dd>
+
+ <dt><strong>color</strong> = &lt;member 'color' of 'Printer' objects&gt;</dt>
+ <dd><code>Print in color.<br>
+True - color -- Default<br>
+False - greyscale</code></dd>
+
+ <dt><strong>copies</strong> = &lt;member 'copies' of 'Printer' objects&gt;</dt>
+ <dd><code>Number of copies</code></dd>
+
+ <dt><strong>file</strong> = &lt;attribute 'file' of 'Printer' objects&gt;</dt>
+ <dd><code>Name of file to print into</code></dd>
+
+ <dt><strong>mph</strong> = &lt;member 'mph' of 'Printer' objects&gt;</dt>
+ <dd><code>Mirror Pages Horizontal<br>
+True<br>
+False -- Default</code></dd>
+
+ <dt><strong>mpv</strong> = &lt;member 'mpv' of 'Printer' objects&gt;</dt>
+ <dd><code>Mirror Pages Vertical<br>
+ True<br>
+False -- Default</code></dd>
+
+ <dt><strong>pages</strong> = &lt;attribute 'pages' of 'Printer' objects&gt;</dt>
+ <dd><code>List of pages to be printed</code></dd>
+
+ <dt><strong>printer</strong> = &lt;attribute 'printer' of 'Printer' objects&gt;</dt>
+ <dd><code>Name of printer to use.<br>
+Default is 'File' for printing into file</code></dd>
+
+ <dt><strong>pslevel</strong> = &lt;member 'pslevel' of 'Printer' objects&gt;</dt>
+ <dd><code>PostScript Level<br>
+Can be 1 or 2 or 3 -- Default is 3.</code></dd>
+
+ <dt><strong>separation</strong> = &lt;attribute 'separation' of 'Printer' objects&gt;</dt>
+ <dd><code>Print separationl<br>
+ 'No' -- Default<br>
+ 'All'<br>
+ 'Cyan'<br>
+ 'Magenta'<br>
+ 'Yellow'<br>
+ 'Black'<br>
+Beware of misspelling because a check is not performed</code></dd>
+
+ <dt><strong>ucr</strong> = &lt;member 'ucr' of 'Printer' objects&gt;</dt>
+ <dd><code>Apply Under Color Removal<br>
+True -- Default<br>
+False</code></dd>
+
+ <dt><strong>useICC</strong> = &lt;member 'useICC' of 'Printer' objects&gt;</dt>
+ <dd><code>Use ICC Profile<br>
+True<br>
+False -- Default</code></dd>
+
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/toolbox3.html
===================================================================
--- Scribus/doc/it/toolbox3.html (nonexistent)
+++ Scribus/doc/it/toolbox3.html (revision 17471)
@@ -0,0 +1,15 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Batik</title>
+</head>
+<body>
+<h2>Batik</h2>
+
+<p>Batik &egrave; una raccolta di moduli XML Apache per l'esportazione e la conversione istantanea di SVG. Tra essi, uno degli strumenti veramente utili &egrave; <strong>Squiggle</strong>, un'applicazione Java che visualizza file SVG. Potrebbe essere difficile compilare Batik su certe distribuzioni, ma fortunatamente esistono pacchetti pronti per tutte le principali distribuzioni e sistemi operativi. </p>
+
+<p>Perch&eacute; prendersi il disturbo di usarlo? Potete considerarlo un giudice lucido e integerrimo dell'SVG. Tra tutti i visualizzatori SVG, &egrave; probabilmente uno di quelli che pi&ugrave; rispettano le specifiche (e forse &egrave; quello che le rispetta di pi&ugrave;). Se ricevete o create un'immagine SVG che non viene importata correttamente, provate ad aprirla con Squiggle. Se non viene visualizzata correttamente, &egrave; pi&ugrave; che probabile che il problema dipenda dall'applicazione con cui &egrave; stata creata. L'eccezione sono i file SVG esportati da Adobe Illustrator, che spesso contengono estensioni specifiche della Adobe, e potrebbero essere apribili soltanto da applicazioni Adobe.</p>
+
+<table width="100%"><tr><td align="center"><img src="images/batik1.png" alt="Batik" /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/it/print2.html
===================================================================
--- Scribus/doc/it/print2.html (nonexistent)
+++ Scribus/doc/it/print2.html (revision 17471)
@@ -0,0 +1,56 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Strumenti per la stampa (1)</title>
+</head>
+<body>
+<h2>Strumenti per la stampa (1)</h2>
+<h3>La verifica preliminare</h3>
+<p>La verifica preliminare &egrave; uno strumento che permette di controllare la presenza in un documento di problemi potenziali o probabili che possono sorgere nella stampa commerciale. Fare errori nella preparazione di un documento pu&ograve; comportare costi finanziari notevoli, e pu&ograve; farvi sembrare e sentire incompetenti. La creazione di documenti che non causano problemi quando l'organizzazione del lavoro prevede la stampa commerciale non richiede anni di studio. Ci&ograve; che richiede &egrave; una certa preparazione, e questa guida in linea fornisce almeno una parte delle informazioni necessarie. Ancora meglio, Scribus contiene uno strumento, la &ldquo;verifica preliminare&rdquo;, che pu&ograve; aiutarvi a identificare pi&ugrave; facilmente i potenziali problemi; dovreste ignorare gli avvisi che fornisce solo se siete sicuri che questo non causer&agrave; errori.</p>
+<p>La verifica preliminare pu&ograve; essere eseguita dalla barra dei men&ugrave; da <i>Finestre &gt; Verifica preliminare</i>. Inoltre appare automaticamente se qualche errore viene rilevato quando si lancia la stampa, si apre l'anteprima di stampa, o si esporta in PDF, EPS o PostScript:</p><br>
+
+<table width="90%"><tr><td align="center"><img src="images/preflight-v.png"></td></tr></table>
+
+<p>In &ldquo;Profilo corrente&rdquo; potete selezionare il tipo di file a cui &egrave; destinata l'esportazione o la stampa: PostScript (che comprende l'EPS), PDF 1.3, 1.4, 1.5 o X-3. Il profilo predefinito &egrave; quello impostato in <i>Impostazioni Documento</i> o in <i>Preferenze</i> (vedi sotto). Al di sotto del men&ugrave; per la selezione del profilo &egrave; mostrato un elenco di tutti gli elementi del documento. Nella prima colonna, gli elementi per cui non &egrave; stato rilevato alcun errore sono marcati da un segno di spunta verde. Gli oggetti con potenziali errori sono indicati da un segnale di allarme. Nella seconda colonna &egrave; indicato l'errore potenziale, e la terza indica il <a href="layers.html">livello</a> su cui l'oggetto di trova, con il nome e il colore del livello stesso. Selezionando un oggetto in questa finestra, viene selezionato anche l'oggetto stesso, e Scribus si sposta alla rispettiva pagina. Dopo aver corretto un potenziale errore, potete ripetere la verifica. Potete anche decidere di ignorare gli avvisi ed esportare o stampare comunque.</p>
+
+<p>Spesso potreste considerare questi come semplici avvisi, piuttosto che come errori veri e propri. Ad esempio, nella finestra di dialogo qui sopra, potreste gi&agrave; sapere che l'immagine Image13 &egrave; una GIF e ha una bassa risoluzione, ma non avevate altra scelta che utilizzarla cos&igrave; com'&egrave;. Ma anche cos&igrave;, pu&ograve; servire a ricordarvi di controllare attentamente quell'immagine nel PDF per vedere se &egrave; adatta alle vostre necessit&agrave;. D'altra parte, &egrave; probabile che abbiate dimenticato di cancellare la Image12, che &egrave; vuota, o che abbiate dimenticato di caricarvi un'immagine; e probabilmente nella Text9 non volevate inserire un testo troppo lungo per la cornice. In un documento lungo, anche se eseguite pi&ugrave; volte dei controlli manuali, errori di questo genere possono capitare facilmente.</p>
+
+<p>Come quasi ogni altra funzione di Scribus, la verifica preliminare pu&ograve; essere <a href="settings1.html">configurata</a> nelle <i>Impostazioni documento</i> oppure nelle <i>Preferenze</i>:</p>
+<br>
+<table width="100%"><tr><td align="center"><img src="images/prefs_preflight.png"></td></tr></table>
+<p>Le opzioni in questo pannello sono le seguenti:</p>
+<ul>
+<li><b>Tipo di file (men&ugrave; a discesa):</b> qui potete selezionare, in base al tipo di file, quali potenziali problemi di stampa/esportazione Scribus verifica per impostazione predefinita.</li>
+<li><b>Ignora tutti gli errori:</b> in base a quanto avete letto prima, potete essere certi che attivare quest'opzione non &egrave; una buona idea: un errore scoperto <i>dopo</i> il completamento della stampa in tipografia pu&ograve; dimostrarsi costoso.</li>
+<li><b>Controllo automatico prima della stampa o dell'esportazione:</b> se questa opzione &egrave; attiva, la verifica preliminare, oltre che poter essere lanciata manualmente dall'utente, sar&agrave; eseguita automaticamente quando si stampa o si esporta un file PostScript o PDF e segnaler&agrave; eventuali errori rilevati.</li>
+<li><b>Controlla glifi mancanti:</b> questa opzione fa in modo che Scribus controlli la mancanza di glifi nei tipi di carattere utilizzati. <i>Non sottovalutate la sua importanza</i>, poiché il cambiamento del tipo di carattere, ad esempio in un foglio di stile o con la formattazione diretta, pu&ograve; far s&igrave; che il testo usi dei glifi non presenti nel nuovo carattere selezionato.</li>
+<li><b>Controlla oggetti che non sono sulla pagina:</b> potete facilmente spostare o persino creare oggetti al di fuori della pagina, cio&egrave; nello spazio di lavoro grigio (lo <a href="settings1.html#14">spazio appunti</a>) intorno alle pagine. Questa &egrave; una caratteristica utile, ma pu&ograve; rovinare un file PostScript o PDF destinato alla stampa commerciale, ed &egrave; piuttosto facile &ldquo;dimenticare&rdquo; un elemento che si trova nello spazio appunti (ad esempio, una cornice vuota). Quindi &egrave; fortemente consigliabile <i>non</i> disabilitare questa opzione.</li>
+<li><b>Controlla sovrapposizioni nelle cornici di testo:</b> come avidi lettori di questa guida in linea, sicuramente saprete che il lavoro con Scribus &egrave; per lo pi&ugrave; <a href="WwFrames.html">basato su cornici</a>, e sicuramente saprete della <a href="WwText.html">necessit&agrave;</a> di ridurre la dimensione del carattere, oppure di allargare la cornice o collegarla a una successiva, se il testo &egrave; troppo lungo per una particolare cornice. In modo simile a quanto accade per i &ldquo;glifi mancanti&rdquo;, uno dei possibili problemi che possono rovinare o degradare la vostra costosa stampa &egrave; il cambiamento del tipo di carattere, poiché l'ampiezza dei glifi &egrave; variabile a seconda del tipo di carattere stesso. In alcuni casi anche l'uso dello stesso carattere su piattaforme diverse, o persino sullo stesso computer, pu&ograve; far s&igrave; che il testo superi lo spazio disponibile, poiché un aggiornamento potrebbe aver installato una nuova versione di un file di caratteri in cui le misure dei glifi sono cambiate.</li>
+<li><b>Controlla le trasparenze usate:</b> il formato di file PostScript non accetta trasparenze, e nemmeno il PDF 1.3, che Scribus &egrave; tuttora in grado di utilizzare. Poiché anche il PDF/X-3 &egrave; basato sul PDF 1.3, &egrave; necessario che questa opzione sia attiva solo per queste tre destinazioni di esportazione/stampa.</li>
+<li><b>Controlla immagini mancanti:</b> Scribus non salva le immagini bitmap all'interno dei suoi file; invece, crea dei collegamenti alle immagini in uno dei formati bitmap che &egrave; in grado di <a href="importhints.html">utilizzare</a>. Pu&ograve; accadere facilmente che l'utente salvi un'immagine con un nome diverso, in un altro formato o in un'altra posizione: quindi il collegamento all'immagine potrebbe interrompersi, e la relativa <a href="WwImages.html">cornice immagine</a> sar&agrave; vuota. Un problema di questo genere pu&ograve; sfuggire facilmente: questa opzione fa in modo che Scribus lo segnali.</li>
+<li><b>Controlla risoluzione immagini:</b> poiché siete lettori illuminati, gi&agrave; <a href="importhints.html">sapete</a> che la risoluzione delle immagini bitmap pu&ograve; essere un elemento critico per la riuscita della stampa; se la risoluzione &egrave; troppo bassa, le immagini stampate avranno un aspetto orrendo, e se &egrave; troppo alta le dimensioni di un file PostScript o PDF esportato potrebbero essere troppo grandi perché un Raster Image Processor (RIP) commerciale possa elaborarlo. Questa opzione fa s&igrave; che Scribus controlli se la risoluzione di un'immagine &egrave; troppo alta o troppo bassa per una certa destinazione. Come potete vedere, potete modificare i limiti in entrambe le direzioni, ma tenete presente che i valori predefiniti sono sensati nella maggior parte dei casi.</li>
+<li><b>Controlla file PDF inseriti:</b> Scribus pu&ograve; importare file PDF nelle cornici immagine per mezzo di <a href="toolbox5.html">Ghostscript</a>. Scribus si serve di Ghostscript per &ldquo;rasterizzare&rdquo; (cio&egrave; per creare un'immagine bitmap di) un file PDF importato, e il risultato potrebbe non piacervi. Inoltre la qualit&agrave; dell'importazione del file dipende dalla versione di Ghostscript che avete installato. Da qui l'opzione che fa s&igrave; che Scribus controlli se sono presenti file PDF importati, che &egrave; utile soprattutto se scambiate file di Scribus tra computer con diverse versioni di Ghostscript installate.</li>
+<li><b>Controlla immagini GIF:</b> avete gi&agrave; <a href="importhints.html">imparato</a> che per i file GIF non c'&egrave; posto nella stampa professionale, ma anche se lo sapete potrebbe accadervi di ricevere da altri un archivio ZIP con un file di Scribus e le relative immagini, e alcune di esse potrebbero essere in formato GIF. Quindi, anche se la &ldquo;minaccia GIF&rdquo; potrebbe non essere imminente, non fa male lasciare attivata questa impostazione predefinita.</li>
+<li><b>Controlla campi e annotazioni PDF:</b> i file PDF contenenti annotazioni e campi vengono rifiutati da tutti i Raster Image Processor (RIP) commerciali, quindi se volete creare un file PDF pronto per la stampa dovreste lasciare questa opzione attiva.</li>
+<li><b>Ignora livelli non stampabili:</b> questa opzione serve per esportare soltanto i livelli contrassegnati come &ldquo;stampabili&rdquo;, il che &egrave; utile soprattutto se avete creato un file con un <a href="layers.html">livello</a> per ogni lingua.</li>
+<li><b>Controlla livelli con impostazioni visibile/stampabile non corrispondenti:</b> la possibilit&agrave; di rendere un livello invisibile quando lavorate sul documento &egrave; molto utile, ma se dimenticate di rendere i livelli di nuovo visibili, nel file PostScript o PDF finale potrebbero mancare certi elementi. Potrebbe accadere anche il contrario, ad esempio se create un documento con pi&ugrave; livelli per diverse lingue o diversi schemi di colore. Questa opzione fa s&igrave; che Scribus controlli se i livelli visibili sono anche &ldquo;stampabili&rdquo;, e in questo contesto &ldquo;stampabile&rdquo; significa anche che il livello o il suo contenuto saranno esportati.</li>
+</ul>
+<h3>L'anteprima di stampa</h3>
+<p>Come accennato nella pagina precedente, una delle sfide nell'uso di un'applicazione avanzata di DTP come Scribus consiste nel gestire l'output PostScript &ldquo;di alto livello&rdquo;. Se vi capita di poter usare una vera stampante PostScript (che non sar&agrave; una macchina piccola come quella con cui stampate le vostre foto), potreste cominciare ad apprezzare alcune delle capacit&agrave; di stampa PostScript di Scribus. Esaminiamo meglio l'anteprima di stampa, che si apre da <i>File &gt; Anteprima di stampa</i>.</p>
+<p>L'anteprima di stampa in Scribus &egrave; qualcosa di speciale, perché fa ben pi&ugrave; che semplicemente generare una visualizzazione del documento. Scribus crea l'anteprima di stampa creando e analizzando un file PostScript temporaneo. Dovreste avere un po' di pazienza quando generate l'anteprima di stampa, poiché dietro c'&egrave; un bel po' di lavoro! &Egrave; opportuno ricordare che questa &egrave; una delle funzioni di Scribus che hanno bisogno che Ghostscript sia installato sul computer.</p>
+<p>L'anteprima di stampa, utilizzata insieme alla verifica preliminare, pu&ograve; aiutarvi a identificare potenziali problemi quando l'organizzazione del lavoro prevede l'utilizzo di file e stampanti PostScript. L'affidabilit&agrave; e la precisione dell'anteprima di stampa dipendono principalmente dalle capacit&agrave; del vostro sistema di stampa, compresa la qualit&agrave; dei driver, e il tipo di caratteristiche avanzate comprese nei documenti che create. Le caratteristiche che possono creare problemi con la stampa comprendono ad esempio sfumature, trasparenze, maschere complesse.</p><br>
+
+<table width="100%"><tr><td align="center"><img src="images/printpreview.png" align="center" alt="Anteprima di stampa" title="Anteprima di stampa" /></td></tr></table>
+<p>La maggior parte delle opzioni nell'anteprima di stampa sono state create per la stampa avanzata PostScript o per la stampa commerciale. Quindi la maggior parte, se non tutte, le opzioni in questa finestra sono probabilmente superflue se vi servite di una semplice stampante da scrivania.</p>
+<p>Il primo gruppo di opzioni riguarda le &ldquo;Impostazioni di visualizzazione&rdquo; relative alla stampa:</p>
+<ul>
+<li><b>Abilita antialiasing:</b> attiva o disattiva l'anteprima del testo con caratteri dotati di anti-aliasing. Questo ha effetto soltanto sui <a href="fonts2.html">caratteri PostScript</a> e potrebbe rallentare lievemente la visualizzazione.</li>
+<li><b>Visualizza trasparenza:</b> mostra lo sfondo della pagina in modo trasparente.</li>
+<li><b>Visualizza CMYK:</b> questa opzione fornisce una simulazione a video di inchiostri CMYK generici e dei <a href="color1.html">colori spot</a>. Quando &egrave; attiva, &egrave; possibile abilitare o disabilitare la visualizzazione di ciascun colore CMYK o spot.</li>
+<li><b>Visualizza copertura inchiostro:</b> con questa opzione, Scribus calcola e mostra la copertura dell'inchiostro per ciascuna parte della pagina. Nella schermata qui sotto viene mostrata la copertura per l'inchiostro &ldquo;magenta&rdquo;.</li><br>
+<table width="100%"><tr><td align="center"><img src="images/ink-cov.png" alt="Anteprima della copertura di inchiostro" title="Anteprima della copertura di inchiostro" /></td></tr></table>
+</ul>
+<p>Il secondo gruppo di opzioni riguarda la visualizzazione del documento nell'anteprima di stampa. Sono spiegate nella <a href="print3.html">pagina sulla finestra di dialogo per la stampa</a>. Le opzioni nella parte inferiore dovrebbero essere di immediata comprensione.</p>
+
+</body>
+</html>
Index: Scribus/doc/it/toolbox.html
===================================================================
--- Scribus/doc/it/toolbox.html (nonexistent)
+++ Scribus/doc/it/toolbox.html (revision 17471)
@@ -0,0 +1,12 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <title>La cassetta degli attrezzi del DTP</title>
+
+</head><body>
+<h2>La cassetta degli attrezzi del DTP</h2>
+
+<p>Come avete gi&agrave; <a href="about2.html">imparato</a>, il desktop publishing consiste principalmente nell'assemblare contenuti creati in altri programmi. In questa parte della guida presentiamo una selezione di strumenti affidabili, consigliati dagli sviluppatori per l'uso con Scribus.</p>
+
+</body></html>
Index: Scribus/doc/it/tutorials.html
===================================================================
--- Scribus/doc/it/tutorials.html (nonexistent)
+++ Scribus/doc/it/tutorials.html (revision 17471)
@@ -0,0 +1,12 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Tutorials</title>
+</head>
+<body>
+<h2>Tutorials</h2>
+
+<p>Real world experience helps a lot when it comes to using any software. Please visit <a href="http://wiki.scribus.net/index.php">the Scribus Wiki</a> for more tutorials on how to perform specific tasks with Scribus. Among others, a great <a href="http://wiki.scribus.net/index.php/Get_Started_with_Scribus">"Getting Started with Scribus"</a> tutorial, orginally created by Niyam Bhushan and subsequently enhanced and translated into other languages by others, is available there. It covers basic layout theory, workflow and describes how to apply it to the creation of your next newsletter. It's not just about words and pictures on paper! Read this and find out why. You can directly access the tutorial from within Scribus via <i>Help > Tutorials</i>.
+
+</body>
+</html>
Index: Scribus/doc/it/install4.html
===================================================================
--- Scribus/doc/it/install4.html (nonexistent)
+++ Scribus/doc/it/install4.html (revision 17471)
@@ -0,0 +1,126 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
+ <title>Compilazione e installazione con l'uso di CMake e Scribus 1.4.x</title>
+</head>
+
+<body>
+ <h2>Compilazione e installazione con l'uso di CMake e Scribus 1.4.x</h2>
+
+ <p>Per molti anni gli sviluppatori di Scribus hanno generato il programma a partire dal codice sorgente utilizzando <em>autotools</em>, ma poi hanno deciso di sostituirlo con <em>CMake</em>. È uno strumento molto più flessibile, e allo stesso tempo molto meno complesso, e inoltre è compatibile con gli strumenti di compilazione presenti su Linux e varianti di UNIX, Windows e Mac&nbsp;OS&nbsp;X.</p>
+
+ <p>Per generare un programma con CMake, ovviamente avete bisogno di CMake stesso. CMake è compreso nella maggior parte delle distribuzioni Linux e in alcune di UNIX. Se nella vostra non è presente, potete <a href="http://www.cmake.org">scaricarlo qui</a>; dovreste accertarvi di prelevarne una versione recente, come la 2.8 o una superiore. Nel sito vi sono anche i pacchetti di installazione per Mac&nbsp;OS&nbsp;X, che possono anche essere ottenuti da <a href="http://macports.org">macports.org</a>. Scribus non usa ancora CMake per Windows, anche se questa capacità potrebbe essere aggiunta in futuro.</p>
+
+ <p>Uno dei vantaggi di CMake è la possibilità di generare il programma &ldquo;fuori sorgenti&rdquo;. Creando una cartella distinta in cui avviene la compilazione del programma, i file temporanei e i file dell'applicazione che vengono generati si trovano un una posizione diversa dai file del codice sorgente. Questo aiuta a mantenere pulite le strutture delle directory, e riduce un po' il tempo necessario per scaricare gli aggiornamenti del codice sorgente. Questo è il metodo migliore ed è fortemente consigliato dai nostri sviluppatori. Inoltre CMake è molto più semplice da mantenere in efficienza per gli sviluppatori, e gli errori sono comprensibili anche dai comuni mortali. <!--However, both methods are described below; the first is recommended.--></p>
+
+ <h3>Preparazione</h3>
+
+ <p>Supponiamo che vi troviate nella seguente situazione:</p>
+
+ <ul>
+ <li>il codice sorgente di Scribus si trova nella directory <code>/home/username/scribussource/</code> (dove <em>username</em> è il vostro nome utente)</li>
+
+ <li>CMake si trova in <code>/usr/bin/</code></li>
+
+ <li>volete installare Scribus in <code>/home/username/scribusinstall/</code></li>
+ </ul>
+
+ <h3>Iniziare la compilazione all'esterno del codice sorgente</h3>
+
+ <p>Spostatevi nella directory del codice sorgente:</p>
+ <pre>
+cd /home/username/scribussource/
+</pre>
+
+ <p>Create una directory in cui Scribus sarà compilato:</p>
+ <pre>
+mkdir builddir
+</pre>
+
+ <p>Spostatevi nella directory di compilazione:</p>
+ <pre>
+cd builddir
+</pre>
+
+ <p>Poi date il seguente comando:</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>Passare alla fase di compilazione</h3>
+
+ <p>Quando il comando CMake ha completato la sua esecuzione senza errori (ricordate che ha bisogno di trovare le dipendenze di Scribus e registrare la loro posizione), dovete dare il seguente comando:</p>
+ <pre>
+make &amp;&amp; make install
+</pre>
+
+ <h2>Opzioni avanzate</h2>
+
+ <h3>Opzioni di compilazione</h3>
+
+ <p>Ecco alcune opzioni presenti nei file Cmake di <b>Scribus 1.4.x</b> (altre ne seguiranno!):</p>
+
+ <ul>
+ <li><strong>WANT_VERSIONING=1</strong>: fa in modo che venga usato il valore di VERSION come suffisso per le directory di installazione e l'eseguibile (ad esempio l'eseguibile potrebbe essere scribus-1.4.0). Ciò significa che potete installare più versioni con lo stesso prefisso senza conflitti.</li>
+
+ <li><strong>WANT_DEBUG=1</strong>: genera una versione di debug e usa -O0 -g3, invece di -O2 (questa è attualmente l'impostazione predefinita, e può essere disattivata solo modificando il file CMakeFiles.txt).</li>
+
+ <li><strong>WANT_CAIRO=1</strong> (opzione predefinita): fa sì che CMake cerchi la libreria grafica Cairo e la utilizzi per la compilazione al posto di Arthur (che fa parte di Qt).</li>
+
+ <li><strong>WANT_QTARTHUR=1</strong>: fa sì che Cmake cerchi Qt Arthur e la utilizzi per la compilazione invece di Cairo.</li>
+
+ <li><strong>WANT_NOHEADERINSTALL=1</strong>: non installa i file header usati per gli sviluppatori. Le distribuzioni non dovrebbero usare questa opzione se suddividono Scribus in più pacchetti.
+
+ <li><strong>WANT_NORPATH</strong>: disabilita l'impostazione di uno specifico RPATH.</li>
+ <li><strong>WANT_DISTROBUILD</strong>: un'opzione per i distributori di sistemi operativi da usare per le loro opzioni di compilazione.</li>
+ <li><strong>WANT_LIB64</strong>: forza la compilazione a 64 bit.</li>
+ <li><strong>WANT_RELEASEWITHDEBUG</strong>: imposta le opzioni per la compilazione come release, ma aggiunge anche le informazioni di debug.</li>
+ <li><strong>WANT_UNIVERSAL_BUNDLE</strong>: solo per Mac&nbsp;OS&nbsp;X, abilita la compilazione di un pacchetto .app.</li>
+ <li><strong>WANT_QT4MAC_COCOA</strong>: solo per Mac&nbsp;OS&nbsp;X, abilita la compilazione della versione Cocoa con Qt 4.5+.</li>
+ <li><strong>WANT_QT3SUPPORT</strong>: abilita l'utilizzo di Qt 3 nel caso abbiate un plugin personalizzato non convertito a Qt4. Questa opzione non è necessaria per il codice ufficiale di Scribus.</li>
+ <li><strong>APPLICATION_DATA_DIR</strong>: imposta la posizione delle preferenze di Scribus (invece di quella predefinita, che è ~/.scribus su *nix e /Users/username/Library/Preferences/Scribus su Mac&nbsp;OS&nbsp;X.)</li>
+ </ul>
+ <p>Esempio: per generare una versione di debug con l'uso di Cairo, il comando da dare sarà simile al seguente (su una sola riga):</p>
+ <pre>
+/usr/bin/cmake . -DCMAKE_INSTALL_PREFIX:PATH=/home/username/scribusinstall -DWANT_CAIRO=1 -DWANT_DEBUG=1 -DWANT_VERSIONING=1
+</pre>
+
+ <h3>Specificare le posizioni delle librerie</h3>
+
+ <p>Quando la vostra distribuzione pubblica il proprio pacchetto per una libreria da cui Scribus dipende, esso potrebbe non essere la più recente versione stabile o instabile fornita dagli autori della libreria. A volte gli sviluppatori di Scribus hanno bisogno di usare il codice più recente per migliorare certe parti di Scribus. In questi casi è necessario che compiliate voi la versione adatta di tali librerie.</p>
+
+ <h3>Creare un archivio tar da distribuire</h3>
+
+ <p>Per creare un archivio tar da distribuire, il vecchio modo sarebbe: <code>make dist</code>.</p>
+
+ <p>Il nuovo modo consiste nel dare il seguente comando:</p>
+ <pre>
+make package_source
+</pre>
+
+ <p>oppure</p>
+ <pre>
+/usr/bin/cpack -G TBZ2 --config CPackSourceConfig.cmake
+</pre>
+
+ <p>per ottenere un pacchetto del codice sorgente.</p>
+
+ <p><strong>Importante:</strong> se dovete eseguire di nuovo cpack, eliminate <code>_CPack_Packages/</code> prima di lanciarlo una seconda volta.</p>
+
+ <p>Potete anche esportare da svn:</p>
+ <pre>
+/path/to/scribus/svn
+</pre>in una directory temporanea, e poi inserirla in un archivio tar o zip.
+
+ <h3>Problemi e successi</h3>
+
+ <p>Se avete letto bene queste istruzioni ma avete ancora problemi, contattateci su <a href="irc.html">IRC</a> o scrivete alla nostra <a href="resources.html">mailing list</a> spiegando il vostro problema. Siamo anche interessati ad avere notizie da utenti che sono riusciti a compilare Scribus su piattaforme diverse da Linux. Sappiamo già che la compilazione su Mac&nbsp;OS&nbsp;X è molto affidabile.</p>
+</body>
+</html>
Index: Scribus/doc/it/toolbox15.html
===================================================================
--- Scribus/doc/it/toolbox15.html (nonexistent)
+++ Scribus/doc/it/toolbox15.html (revision 17471)
@@ -0,0 +1,12 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Krita</title>
+</head>
+<body>
+<h2>Krita</h2>
+<p>Dopo essere risorto dalle ceneri, <a href="http://koffice.org/krita/">Krita</a>, che fa parte del pacchetto <a href="http://koffice.org/">KDE Office</a>, &egrave; divenuto una meravigliosa applicazione pensata principalmente per la pittura naturale, come CorelPainter. Usa una metafora a video del pennello, e ha alcune caratteristiche innovative e interessanti come la capacit&agrave; di emulare il modo in cui i colori si mescolano e asciugano su tela, una galleria di filtri con l'anteprima di ciascun filtro, livelli di aggiustamento, gruppi di livelli e strumenti per manipolare con precisione le pennellate. Solo per questo vale la pena di aggiungere Krita ai vostri strumenti per il DTP, ma il maggior vantaggio per gli utenti di Scribus &egrave; la sua versatilit&agrave; nella gestione di un gran numero di formati di file e spazi colore. Krita &egrave; compatibile non solo con RGB, CMYK, e scala di grigi (fino a 16 bit) con l'uso di littleCMS per la gestione del colore, come Scribus, ma anche con spazi colore piuttosto insoliti come XYZ e L*a*b. Krita &egrave; pienamente in grado di eseguire conversioni da RGB a CMYK in modo semplice e facile, e pu&ograve; anche convertire immagini da 16 bit a 8 bit per renderne possibile l'importazione in Scribus (che non &egrave; ancora in grado di utilizzare immagini a 16 bit.)</p>
+
+<table width="100%"><tr><td align="center"><img src="images/krita1.jpg" alt="Krita con un'immagine in modalit&agrave; CMYK e la gestione del colore attiva." /></td></tr></table>
+</body>
+</html>
Index: Scribus/doc/it/readme-win32.html
===================================================================
--- Scribus/doc/it/readme-win32.html (nonexistent)
+++ Scribus/doc/it/readme-win32.html (revision 17471)
@@ -0,0 +1,29 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus su Windows</title>
+</head>
+<body>
+<h3>Scribus su Windows</h3>
+
+<h3>Requisiti hardware/software minimi:</h3>
+<p>
+<ul>
+<li>Scribus pu&ograve; essere installato e utilizzato su Windows 2000 SP4, Windows XP, Vista o 7. <b>Non funziona</b> su Windows 98 e ME.</li>
+<li>&egrave; fortemente consigliato avere almeno 512 MB di RAM; maggiore &egrave; la quantit&agrave; di RAM, meglio &egrave;.</li>
+<li>processore Pentium III o superiore; 750 MHz o superiore.</li>
+<li>Scribus &egrave; disponibile soltanto in versioni a 32 bit per Windows. Su sistemi a 64 bit non risulta che vi siano problemi, e non richiede nessuna speciale preparazione n&eacute; configurazione post-installazione.</li>
+<li><i>&egrave; fortemente consigliato disabilitare eventuali temi personalizzati per il desktop. Se incontrate comportamenti strani (ad esempio, se nessun documento appare a video), usate il tema &ldquo;Windows Classico&ldquo;. Qt ha un problema noto con i temi personalizzati, che pu&ograve; ostacolare il caricamento dei documenti. Questo &egrave; accade specialmente con temi forniti da terzi.</i></li>
+</ul>
+</p>
+<h3>Prima di installare Scribus</h3>
+<p>&Egrave; consigliabile installare <a href="http://ghostscript.com/releases/">Ghostscript</a> 8.7 o successivo, che serve per l'importazione EPS. <br>Nota: dopo l'installazione troverete due file Ghostscript *.exe sul vostro sistema. Quello corretto da utilizzare nelle <a href="settings1.html#15">preferenze di Scribus</a> (in <i>Strumenti esterni</i>) per Ghostscript &egrave; <code>gswin32c.exe</code>, <b>non</b> <code>gswin32.exe</code>. Nella gran maggioranza dei casi, <b>se</b> Ghostscript viene installato correttamente prima di Scribus, Scribus individua automaticamente la sua posizione. Ci&ograve; detto, Ghostscript di solito non &egrave; essenziale per poter utilizzare Scribus. Se non avete installato Ghostscript, Scribus all'avvio vi avverte della mancanza di Ghostscript e vi d&agrave; un link per scaricarlo, ma potete anche decidere di non installare questo strumento esterno.</p>
+<h3>Durante l'installazione</h3>
+<p>Se selezionate l'opzione &ldquo;Extra Fonts&rdquo; nel programma di installazione, saranno installati due pacchetti di caratteri di alta qualit&agrave; liberamente distribuibili. Il primo comprende i caratteri URW da Ghostscript: si tratta di 45 tipi di carattere compatibili con quelli compresi nella maggior parte delle stampanti PostScript. Il secondo comprende la famiglia Bitstream Vera, ampiamente utilizzata in ambiente Linux e da alcuni dei modelli inclusi in Scribus.</p>
+<h3>Dopo l'installazione</h3>
+<p>Il primo avvio di Scribus, o quando un nuovo utente lancia Scribus, pu&ograve; richiedere molto pi&ugrave; tempo del normale. Questo accade perch&eacute; Scribus crea un file di cache dei caratteri presenti sul vostro sistema. I lanci successivi sono molto pi&ugrave; rapidi.</p>
+
+<h3>Modalit&agrave; console per la diagnostica</h3>
+<p>Nel men&ugrave; <i>Start &gt; Programmi</i> c'&egrave; un collegamento aggiuntivo: <strong>Scribus -console</strong>. Questa modalit&agrave; apre semplicemente un prompt dei comandi di Windows, in cui viene mostato riga per riga ciascun carattere e il suo percorso mentre Scribus lo carica. Vengono mostrati anche eventuali tipi di carattere non accettati da Scribus o duplicati, e in alcuni casi anche altre informazioni diagnostiche. I duplicati non vengono importati, anche se hanno nomi diversi.</p>
+</body>
+</html>
Index: Scribus/doc/it/scripterapi-getobjprop.html
===================================================================
--- Scribus/doc/it/scripterapi-getobjprop.html (nonexistent)
+++ Scribus/doc/it/scripterapi-getobjprop.html (revision 17471)
@@ -0,0 +1,89 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Getting Object Properties</title>
+</head>
+<body>
+<h2>Getting Object Properties</h2>
+
+<dl>
+
+<dt><a name="-getObjectType"><strong>getObjectType</strong></a>(...)</dt>
+<dd><code>getObjectType(["name"]) -&gt; string</code>
+<p>Get type of object "name" as a string. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getCornerRadius"><strong>getCornerRadius</strong></a>(...)</dt>
+<dd><code>getCornerRadius(["name"]) -&gt; integer</code>
+<p>Returns 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></dd>
+
+<dt><a name="-getFillColor"><strong>getFillColor</strong></a>(...)</dt>
+<dd><code>getFillColor(["name"]) -&gt; string</code>
+<p>Returns the name of the fill color of the object "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getFillBlendmode"><strong>getFillBlendmode</strong>(...)</a></dt>
+<dd><code>getFillBlendmode(["name"]) -&gt; integer</code>
+<p>Returns the fill blendmode of the object "name". If "name" is not given the currently selected Item is used.</p></dd>
+
+<dt><a name="-getFillShade"><strong>getFillShade</strong></a>(...)</dt>
+<dd><code>getFillShade(["name"]) -&gt; integer</code>
+<p>Returns the shading value of the fill color of the object "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getFillTransparency"><strong>getFillTransparency</strong>(...)</a></dt>
+<dd><code>getFillTransparency(["name"]) -&gt; float</code>
+<p>Returns the fill transparency of the object "name". If "name" is not given the currently selected Item is used.</p></dd>
+
+<dt><a name="-getImageFile"><strong>getImageFile</strong></a>(...)</dt>
+<dd><code>getImageName(["name"]) -&gt; string</code>
+<p>Returns the filename for the image in the image frame. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getImageScale"><strong>getImageScale</strong></a>(...)</dt>
+<dd><code>getImageScale(["name"]) -&gt; (x,y)</code>
+<p>Returns a (x, y) tuple containing the scaling values of the image frame "name". If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getLineBlendmode"><strong>getLineBlendmode</strong>(...)</a></dt>
+<dd><code>getLineBlendmode(["name"]) -&gt; integer</code>
+<p>Returns the line blendmode of the object "name". If "name" is not given the currently selected Item is used.</p></dd>
+
+<dt><a name="-getLineCap"><strong>getLineCap</strong></a>(...)</dt>
+<dd><code>getLineEnd(["name"]) -&gt; integer (see constants)</code>
+<p>Returns the line cap style of the object "name". If "name" is not given the currently selected item is used. The cap types are: CAP_FLAT, CAP_ROUND, CAP_SQUARE</p></dd>
+
+<dt><a name="-getLineColor"><strong>getLineColor</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="-getLineJoin"><strong>getLineJoin</strong></a>(...)</dt>
+<dd><code>getLineJoin(["name"]) -&gt; integer (see contants)</code>
+<p>Returns the line join style of the object "name". If "name" is not given the currently selected item is used. The join types are: JOIN_BEVEL, JOIN_MITTER, JOIN_ROUND</p></dd>
+
+<dt><a name="-getLineShade"><strong>getLineShade</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="-getLineStyle"><strong>getLineStyle</strong></a>(...)</dt>
+<dd><code>getLineStyle(["name"]) -&gt; integer (see constants)</code>
+<p>Returns the line style of the object "name". If "name" is not given the currently selected item is used. Line style constants are: LINE_DASH, LINE_DASHDOT, LINE_DASHDOTDOT, LINE_DOT, LINE_SOLID</p></dd>
+
+<dt><a name="-getLineTransparency"><strong>getLineTransparency</strong>(...)</a></dt>
+<dd><code>getLineTransparency(["name"]) -&gt; float</code>
+<p>Returns the line transparency of the object "name". If "name" is not given the currently selected Item is used.</p></dd>
+
+<dt><a name="-getLineWidth"><strong>getLineWidth</strong></a>(...)</dt>
+<dd><code>getLineWidth(["name"]) -&gt; integer</code>
+<p>Returns the line width of the object "name". If "name" is not given the currently selected Item is used.</p></dd>
+
+<dt><a name="-getPosition"><strong>getPosition</strong></a>(...)</dt>
+<dd><code>getPosition(["name"]) -&gt; (x,y)</code>
+<p>Returns a (x, y) tuple with the position of the object "name". If "name" is not given the currently selected item is used. The position is expressed in the actual measurement unit of the document - see UNIT_&lt;type&gt; for reference.</p></dd>
+
+<dt><a name="-getRotation"><strong>getRotation</strong></a>(...)</dt>
+<dd><code>getRotation(["name"]) -&gt; integer</code>
+<p>Returns the rotation of the object "name". The value is expressed in degrees, and clockwise is positive. If "name" is not given the currently selected item is used.</p></dd>
+
+<dt><a name="-getSize"><strong>getSize</strong></a>(...)</dt>
+<dd><code>getSize(["name"]) -&gt; (width,height)</code>
+<p>Returns a (width, height) tuple with the size of the object "name". If "name" is not given the currently selected item is used. The size is expressed in the current measurement unit of the document - see UNIT_&lt;type&gt; for reference.</p></dd>
+
+</dl>
+</body>
+</html>
Index: Scribus/doc/it/scripter-faq.html
===================================================================
--- Scribus/doc/it/scripter-faq.html (nonexistent)
+++ Scribus/doc/it/scripter-faq.html (revision 17471)
@@ -0,0 +1,133 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scripter FAQ</title>
+</head>
+<body>
+<h2>Scripter FAQ</h2>
+<p>Author: Craig Ringer</p>
+
+<dl>
+<h3>How do I use non-ASCII text in the scripter?</h3>
+<p>First, make sure to ensure that your script has a correct coding line. Your script should start with something like:
+<pre>
+ #!/usr/bin/env python
+ # -*- coding: latin-1 -*-
+</pre>
+or
+<pre>
+ #!/usr/bin/env python
+ # -*- coding: utf-8 -*-
+</pre>
+or
+<pre>
+ #!/usr/bin/env python
+ # -*- coding: ascii -*-
+</pre>
+</p>
+<p>Those lines <b>must</b> be the first two lines of your script. The coding <b>must</b> match the actual encoding of the file.</p>
+
+<p>To find out what the text encoding is in vim, type
+<code> :set fileencoding?<enter></code>
+How to find out the text encoding will vary for other editors, it may match your locale. The <code>file</code> command is <i>not</i> a reliable way to determine the text encoding of a file.</p>
+
+<p>You can convert files between encodings with the 'iconv' utility, but you will rarely need to given that Python can handle almost any text encoding if told what it is in the coding line.</p>
+
+<p>A few scripter functions require strict ASCII text, and cannot accept unicode or latin-1 text. If you call one of those with non-ASCII text, you'll get an error like:
+<code> UnicodeDecodeError: 'ASCII' codec can't decode byte 0xc3
+ in position 1: ordinal not in range(128)</code>
+which is admittedly less than helpful.</p>
+
+<p>There currently seems to be a bug with the u'' modifier for string literals in the script console. This problem has also been identified in the Python interactive interpreter on the command line. It does not affect script files. Until this is solved, use the unicode("mystring") constructor or just use plain strings (which can contain unicode text) from the script console.</p>
+
+
+<h3>What's a good structure to use for my scripts?</h3>
+<p>Start with 'boilerplate.py' in the samples directory. That script disables redraws (for speed) and has code to make sure they get turned back on, does some checking and reports a useful error if run outside of scribus, etc.</p>
+
+<h3>Why Python?</h3>
+<p>It's well suited to application embedding, but still full-featured and powerful. It's also accessible to new users and well documented. Additionally, it has solid unicode text support.</p>
+
+<p>Python makes a good glue language to connect different programs and components together. For example, you may wish you make it possible to use your in-house story database with Scribus - in which case the Python interface is probably the simplest and quickest way to get you there.</p>
+
+<p>It's also somewhat easier to write tidy Python code that other people can read and understand. If somebody else's script doesn't quite do what you need, with Python you have more of a chance of modifying it so it does.</p>
+
+<p>There are issues with embedding Python in applications, so from the perspective of pure automation scripting a language like Qt Script for Applications or lua might be better suited. If you want to get beyond simple automation, Python seems to be the way to go.</p>
+
+<h3>I want to provide a more complex GUI than is provided by the dialogs built into the scripting interface. How can I do that?</h3>
+
+<p>For most scripting tasks, building a simple GUI in Tkinter is your best choices at present. If you're looking to extend the user interface or provide palettes the user can work with while they continue to work in Scribus, you'll need to look into writing an 'extension script' with PyQt.
+
+<p>In most cases it's recommended to just choose Tkinter. It's the only GUI toolkit that works reliably in normal Scribus scripts due to the way they're executed in sub-interpreters. It's also almost universally packaged in Linux distributions, though not all install it by default. Tkinter is highly portable. Tkinter is also bundled with the Windows installer for Scribus, along with being included with the python on Mac OS X 10.4.x. Users may not particularly love the appearance of Tkinter, but it works well.</p>
+
+<p>If you're looking to write more advanced GUIs, the best choice is currently PyQt. You can write your own custom dialogs and palettes using PyQt, giving you the ability to extend the Scribus interface to a limited extent. PyQt will not work reliably from a normal script, but works fine from scripts that are run using the &quot;Load Extension Script...&quot; menu item. Please see the advanced section of the scripter manual for more details on this.</p>
+
+<p>Issues with event loop integration and initialization in sub-interpreters mean that PyGtk and wxPython are not currently recommended and probably won't work properly. Given that Tkinter works well for normal scripts, and PyQt for more advanced tasks, this isn't seen as a major problem.</p>
+
+<h3>Should I use 'from scribus import *' or 'import scribus'?</h3>
+<p>In general, 'import scribus' is preferred. 'from ... import' can get confusing in import loops, when reloading modules, when importing packages, and in some other circumstances. More info <a href="http://effbot.org/zone/import-confusion.htm" title="Extern link">http://effbot.org/zone/import-confusion.htm</a>.</p>
+
+<p>While 'import scribus' results in slightly more verbose code, it's generally worth it in improved code readability and explictness.</p>
+
+<h3>What about general programming style?</h3>
+<p>In general, we defer to the Python gurus. Have a look at <a href="http://www.python.org/peps/pep-0008.html" title="Extern link">http://www.python.org/peps/pep-0008.html</a> for a rather in-depth look at the subject.</p>
+
+<p>An exception is made for source code encodings, where either ASCII with escapes, latin-1, or utf-8 are recommended. Almost any encoding you choose should work fine, though.</p>
+
+<p>Please note that none of this is set in stone - you can code however you like. These recommendations are made for a reason though, and are a good idea to follow especially if you plan to share your code with others.</p>
+
+<h3>Are there any quirks specific to the Scribus python interface that I should know about?</h3>
+<p>Yes, there are a few differences you should be aware of:</p>
+
+<ul>
+ <li>Python scripts running in Scribus may not create threads. Qt, the toolkit Scribus is built with, provides its own threading framework that doesn't play well with the Python threading system. A interface to QThread may be provided if sufficient need for it can be shown, and if it can be made to work.</li>
+
+ <li>PyQt does not currently work correctly from Python scripts run from normal Scribus scripts, though it can now be used from the 'extension script' mode. Please enquire on the mailing list if you think you may be able to assist in solving this. Experience with the Python/C API, sub-interpreters, and PyQt would probably be required.</li>
+
+ <li>The Scribus python plug-in changes the Python default string encoding (sysdefaultencoding) to utf-8. Python defaults to ASCII. Because utf-8 is a (large) superset of ASCII, this should not affect scripts that only use ASCII-encoded strings. The Scribus functions have been tested to work correctly with this for unicode text, so there should not be any issues there either.<br>
+ Nonetheless, it is possible that third party C extension modules may have problems with this, if the author failed to consider the encoding of incoming text. Any such problems are almost always bugs that should be reported to the author of the module, and should be few and far between. If you encounter such an issue, please enquire on the mailing list or on IRC.</li>
+
+ <li>Python runs embedded inside Scribus. It is possible that loading certain C extension modules that perform complex initialization tricks may disrupt Scribus or the Python interpreter. If you encounter such a module, please report it on the mailing list or drop in on IRC. Anything that wants to run its own event loop is likely to be problematic, and interfaces to GUI toolkits also seem to be troublesome. Anything that spawns threads is also likely to cause issues.</li>
+</ul>
+
+<h3>Can I use the rest of the Python standard library or add-in modules?</h3>
+<p>Yes, and yes. Scribus imposes no restrictions on access to the rest of Python (except for the technical limitations explained above), and that's one of the things that makes the scripter so powerful. It is possible that some Python functions such as threading may be affected by the way the interpreter has been embedded, but most should be usable as normal.</p>
+
+<h3>I'd like to extend Scribus using Python, not just automate things with it...</h3>
+<p>Currently, that's not really possible. There is work on making it possible to extend Scribus with Python to some extent, especially the GUI. It's now possible to use PyQt to write your own palettes, but you won't be able to use custom Scribus widgets or get into the innards of the application. The Scribus core is unfortunately not well suited to extension from Python. More advanced or tightly integrated extensions are probably better written as C++ plug-ins.</p>
+
+<h3>What about security? Can I trust scripts not to destroy my data or compromise my computer?</h3>
+<p><b>No. Do not run a script if it is not from a trusted source, and preferably not unless you have read it.</b> The downside of the power of the Python scripting interface is that it imposes almost no security restrictions. Anything you can do from the shell without a password, a script can do too.</p>
+
+<p>If Python ever gets support for a restricted execution environment like versions &lt; 2.2 had, support for it may be added, but currently there are essentially no restrictions. It would be interesting to investigate a simple automation-only macro language for embedding in Scribus, but currently there aren't the resources to do this.</p>
+
+<h3>So ... can I embed scripts in documents or templates?</h3>
+<p>No, see above. We can't provide a restricted execution environment, so it's not safe to let scripts travel with documents. Otherwise a malicious script could use a document as a vector to infect other systems. Remember Word macro viruses? Yeah. We do too.</p>
+
+<h3>What about a startup script or event-triggered scripts?</h3>
+
+<p>Startup scripts are supported, and scripts that run when certain events happen may be supported in future. If a script is in a position to "infect" a startup script or your application, it's also able to modify your .bashrc or your X startup script. In other words, if you choose to run untrusted code on your machine, it's too late - having it insert its self into a Scribus startup script would be the least of your problems. This is not unique to Scribus, and is true of bash scripts, normal programs, and most plug-ins as well. <b>Remember, do not run scripts that are not from trusted sources, scripts are programs like any other you might run on your computer.</b>.
+
+<p>It's as safe for Scribus to load a script on startup as it is for the shell (e.g. <code>bash</code>), or your graphical login system. Scribus cannot protect you if you choose to run untrusted programs on your system. What it <i>can</i> prevent is providing any vector for untrusted code to spread. That is why Scribus supports startup scripts (though they are not run by default) and why scripts will not be permitted to be embedded in or run from documents.</p>
+
+<p><b>Do not run a program, script, or plug-in, of any sort, from any source, unless you have verified that the program is not malicious.</b> This is an important rule of basic computer security and applies to any program and operating system.</p>
+
+<h3>What about C++ plugins for Scribus? Are they secure?</h3>
+<p>Not at all. A Scribus C++ plug-in can do almost anything any other program on your computer can do, so do not download and run one you do not absolutely trust the author of. This is true of plug-ins for most programs, as it is very difficult to restrict what a plug-in written in C/C++ can do.</p>
+
+<h3>I can't find a way to do <i>something</i> from Python, but the main Scribus application supports it. What do I do?</h3>
+<p>The scripting interface currently requires each function to be written by hand - no automatic code generation / wrapping mechanism is used. This is partly because there isn't currently any tidy and stable underlying public API to wrap.</p>
+
+<p>In general, if a function is missing it is because nobody has found the time or need to write it yet. Sometimes the function is more complicated than it seems, and may be quite a lot of work to wrap. Sometimes it's five minutes work. Ask politely on IRC or the mailing list, and if someone has the time and inclination they may write one for you.</p>
+
+<h3>I asked on the mailing list or IRC but nobody offered to write this function I need for the scripter. What can I do?</h3>
+<p>You have a few options:</p>
+<ul>
+ <li>Waiting a while then politely trying again.</li>
+ <li>You may be able to add it yourself - the chances are that somebody who works on the scripter will be able to help give you an idea of how much work that would involve for what you want to do. In general, the scripter isn't very complicated, and many functions are fairly trivial to write, so even if you don't know much C++ you shouldn't assume you can't do it. When I started work on the scripter I knew absolutely no C or C++ at all ... I just _really_ wanted a few new capabilities.</li>
+
+ <li>If you do decide to add a function yourself, please remember to consider that not all text is ASCII. Use the 'es' format in PyArg_ParseTuple not the 's' format, and specify "utf-8" encoding. Use the QString::fromUtf8 and QString::utf8() methods when getting data into and out of, respectively, QString objects. Have a look at some of the other scripter code to see how this is done, or feel free to ask on IRC or the mailing list if you have trouble.</li>
+
+ <li>Offering to pay somebody to do it. This is probably only practical for larger amounts of work that would require quite a bit of time and effort (and money), but it's there as an option if you really need something.</li>
+</ul>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/scribuscopyright.html
===================================================================
--- Scribus/doc/it/scribuscopyright.html (nonexistent)
+++ Scribus/doc/it/scribuscopyright.html (revision 17471)
@@ -0,0 +1,33 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Scribus Copyright</title>
+</head>
+<body>
+<h2>Scribus Copyright</h2>
+<p><i>&copy;2001&ndash;2011 Franz Schmid and rest of the members of the Scribus Team.</i></p>
+<p>The &ldquo;Scribus Team&rdquo; is informally defined as the following people: Franz Schmid, Peter Linnell, Craig Bradney, Jean Ghali, Hermann Kraus, Riku Leino, Oleksandr Moskalenko, Christoph Sch&auml;fer, Petr Van&#283;k, Andreas Vox, and Jain Basil.</p>
+<p>Other contributors are listed in the &ldquo;Authors&rdquo; tab of the dialog <i>Help &gt; About Scribus</i>.</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 (GPL)</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>Parts of the code are distributed under one of the following licenses:
+<ul>
+<li>GNU Library/Lesser Public License (LGPL), version 2 or version 2.1</li>
+<li>3-clause BSD License</li>
+<li>MIT License</li>
+<li>Some parts of the code are distributed under a dual licensing scheme. See the respective source files for further information.</li>
+<li>Other parts of the code are in the Public Domain.</li>
+</ul></p>
+<table border="1" align="center"><tbody><tr><td><span style="color: red;"><i>Some third party files in the source code don&rsquo;t include proper copyright notices, but the Scribus developers have been told by their authors that the license is compatible to the GPL version (e.g. LGPL v. 2 or MIT license). This doesn&rsquo;t mean that you are allowed to copy or modify the code without obligations. It only means that the original authors forgot to add these notices. Without providing legal advice, we suggest that you contact the authors of the code who are mentioned in other files in the same directory and ask for permission or to update the files with appropriate licensing information.</i></tr></tbody>
+</table>
+
+<p><b>Antiword</b>, 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><b>Resources</b>, like the documentation, dictionary files, color profiles, color palettes, or templates, use their own licenses that need not be compatible with any of the licenses mentioned above, because resources are considered to be content, not functional code. <br><i>Note that some of these files, especially some color palettes, are subject to very strict licensing conditions.</i></p>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/lipsum.html
===================================================================
--- Scribus/doc/it/lipsum.html (nonexistent)
+++ Scribus/doc/it/lipsum.html (revision 17471)
@@ -0,0 +1,33 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Adding Sample Text in your Language</title>
+</head>
+<body>
+<h2>Adding Sample Text in your Language</h2>
+<h3>Why Sample Text?</h3>
+<p>When creating page layouts a sample text, also known as &ldquo;Lorem ipsum&rdquo; or &ldquo;lipsum&rdquo; to typesetting professionals, is often used as a placeholder for actual text before the real text is inserted. The original Lorem ipsum consists of nonsensical Latin, the reason being the desire of typesetters to not distract from the impression of the text layout (font choice, font size, linespacing etc.). This can most easily be achieved with a nonsensical text, as the viewer will not be tempted to read. However, since one of the purposes of a Lorem ipsum is to show all letters in an alphabet, the original may not be well-suited for languages other than English or Latin, as most languages use either an extended Latin alphabet or no Latin alphabet at all.</p>
+<p>Scribus makes it very convenient to insert a sample text by simply selecting, then right-clicking a text frame and selecting &ldquo;Sample Text&rdquo; from the Context Menu. This allows you to visualize the layout or experiment with different fonts and effects before finalizing your design.</p>
+<h3>Creating a Sample Text for your Language</h3>
+<P>This simple HOWTO shows you how easy it is to add your own language or alphabet if it&rsquo;s not yet included with Scribus. </P>
+<p>The structure of a lipsum file is very simple XML, which anyone can create in a text editor. Below is a shortened version of a Finnish sample text.</p>
+<pre>
+&#060;?xml version="1.0" encoding="utf8"?&#062;
+&#060;lorem>
+ &#060;name>Finnish&#060;/name&#062;
+ &#060;author>http://www.dlc.fi/~frank/ite.htm&#060;/author&#062;
+ &#060;url>http://www.dlc.fi/~frank/huumori/trans/&#060;/url&#062;
+
+&#060;p>Vaimo ja mies ajattelivat pitää illallisjuhlat kaikille Rooman silmäätekeville Italiassa.
+Vaimo jännitti kovasti ja halusi kaiken sujuvan täydellisesti. Viime minuuteilla hän tajusi, ettei
+hänellä ollut illallisille yhtään etanoita, jolloin hän käski miestään juoksemaan
+alas rannalle ja keräämään koriin joitain etanoita.&#060;/p&#062;
+&#060;/lorem&#062;
+</pre>
+
+<p>You can search on the internet for a lipsum in your language &ndash; there are many available &ndash; or simply create your own. Make sure that you can use and distribute an existing sample text without restrictions. If you create your own Lorem ipsum, you are advised to make sure that the sample text is as nonsensical as possible and that it contains all letters of your alphabet.</p>
+<p>Insert the text, replace the name, author and URL data with the correct ones. Then simply put HTML-like tags around each of the paragraphs.</p><p>Insert the text, then save is as <code>language.xml</code>, where &ldquo;language&rdquo; must be replaced with an <a href="http://en.wikipedia.org/wiki/ISO_639-1">ISO 639-1 language code</a>, a two letter abbreviation for the respective language, e.g. <code>ru.xml</code> for Russian. It&rsquo;s important to make sure that you save the text in <a href="http://en.wikipedia.org/wiki/UTF-8">UTF-8 encoding</a>. Otherwise, special characters won&rsquo;t be displayed correctly.</p>
+<p> To test your sample text, you can copy it to the subdirectory <code>~/share/scribus/loremipsum</code>, whose location will vary depending on your operating system and the way you installed Scribus (e.g. <code>/usr/share/scribus/loremipsum</code> on Linux).</p>
+<p>Once you made sure that your significant engineering effort works as expected, head over to the <a href="http://bugs.scribus.net">Scribus bugtracker</a>, file a bug report with the severity &ldquo;Feature&rdquo; and upload your XML file. One of the Scribus developers will add it to the next release of Scribus for all to enjoy.</p>
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/scripterapi-setobjprop.html
===================================================================
--- Scribus/doc/it/scripterapi-setobjprop.html (nonexistent)
+++ Scribus/doc/it/scripterapi-setobjprop.html (revision 17471)
@@ -0,0 +1,116 @@
+<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>setLineCap(captype, ["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="-setImageOffset"><strong>setImageOffset</strong></a>(...)</dt>
+<dd><code>setImageOffset(x, y [, "name"])</code>
+<p>Sets the position of the picture in the image frame "name". If "name" is not given the currently selected item is used. The specified offset values are equal to the values shown on properties palette when point unit 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><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>
Index: Scribus/doc/it/editorial.html
===================================================================
--- Scribus/doc/it/editorial.html (nonexistent)
+++ Scribus/doc/it/editorial.html (revision 17471)
@@ -0,0 +1,20 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Editorial Notes</title>
+</head>
+<body>
+<h2>Editorial Notes</h2>
+<h3>General</h3>
+<p>The Scribus Online Help is not a complete or detailed description of all the features provided by Scribus. Rather, its purpose is to provide enough information for you to use the program successfully. In addition, the authors intended to introduce those who are new to desktop publishing to concepts that are unique to this very special kind of software, as well as make users aware of traps and pitfalls lurking on the way from creating documents to professional printing.</p>
+<p>This documentation will grow with each Scribus release, so the available information will become more and more complete. In addition, the Scribus Team is working on a new edition of the printed Scribus manual, which will contain even more detailed information and examples.</p>
+<h3>Spelling</h3>
+<p>The English version of the Scribus Online Help uses (<i>cum grano salis</i>) US spelling. This was simply a pragmatic decision, since two out of three main authors are US citizens. Moreover, while most international standards bodies (most notably ISO) require the use of &ldquo;International&rdquo; (read: British) English, it&rsquo;s hard to imagine that anyone will have difficulties in understanding a text written in US spelling. An exception to the rule is screenshots, which may display the British or Australian version of the user interface.</p>
+<h3>Screenshots</h3>
+<p>Almost all screenshots in this Online Help have been created under the Fedora or OpenSUSE versions of KDE&nbsp;4. The dialogs may look slightly different on other operating systems or under other desktop environments, but thanks to the Qt toolkit, there shouldn&rsquo;t be any differences in actual usage.</p>
+<h3>Keyboard Shortcuts</h3>
+<p>Unless explicitly mentioned otherwise, all keyboard shortcuts in this Online Help refer to PC keyboards (Linux, UNIX, Windows, OS/2, eComStation).</p>
+<h3>Files and Directories</h3>
+<p>The authors of this documentation tried and continue to try to treat all supported operating systems equally. However, due to historical reasons, sometimes only file locations on Linux/UNIX may be mentioned. If you discover one of those instances, feel free to notify the development team, so this can be fixed.</p>
+</body>
+</html>
Index: Scribus/doc/it/toolbox8.html
===================================================================
--- Scribus/doc/it/toolbox8.html (nonexistent)
+++ Scribus/doc/it/toolbox8.html (revision 17471)
@@ -0,0 +1,16 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>ImageMagick</title>
+</head>
+<body>
+<h2>ImageMagick</h2>
+<p>ImageMagick &egrave; un convertitore di immagini da riga di comando. Esiste anche un'interfaccia grafica, chiamata &ldquo;Display&rdquo;. ImageMagick dimostra la sua utilit&agrave; specialmente sotto tre aspetti:</p>
+
+<ol><li> come applicazione per la conversione in modalit&agrave; &ldquo;batch&rdquo; (cio&egrave;, eseguita su un gruppo di immagini senza interazione con l'utente);</li>
+<li> pu&ograve; trattare un'ampia gamma di formati immagine;</li>
+<li> le versioni pi&ugrave; recenti sono compatibili con la gestione del colore e utilizzano littleCMS, proprio come Scribus.</li></ol>
+
+<p>ImageMagick elabora le immagini &ldquo;a scatola chiusa&rdquo;, ma &egrave; incredibilmente potente se usato correttamente. Ne esistono versioni per Linux, Windows e MacOSX.</p>
+</body>
+</html>
Index: Scribus/doc/it/install1.html
===================================================================
--- Scribus/doc/it/install1.html (nonexistent)
+++ Scribus/doc/it/install1.html (revision 17471)
@@ -0,0 +1,37 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Come procurarsi il codice sorgente di Scribus</title>
+</head>
+<body>
+<h2>Come procurarsi il codice sorgente di Scribus</h2>
+<p>Potete prelevare un archivio in formato tar della pi&ugrave; recente versione di Scribus da Sourceforge: <a href="http://sourceforge.net/projects/scribus/files/"> http://sourceforge.net/projects/scribus/files/</a>.</p>
+
+<p>Grazie ad <a href="http://Anduin.net">Anduin.net</a> c'&egrave; anche un repository SVN ad accesso anonimo, che &egrave; continuamente aggiornato. L'uso di questo codice &egrave; consigliato soltanto per coloro che desiderano tenersi aggiornati agli ultimi sviluppi. Ecco le istruzioni per procurarsi la pi&ugrave; recente versione del codice sorgente da SVN: </p>
+
+<p><strong>Ramo Scribus 1.4</strong>. Questo ramo contiene il codice per la versione stabile (1.4.x).</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+svn co svn://scribus.info/Scribus/branches/Version14x
+</pre>
+o, per chi ha le porte SVN chiuse sul proprio firewall,:
+<pre>
+svn co http://scribus.info/svn/Scribus/branches/Version14x
+</pre>
+</td></tr></table></blockquote>
+
+<p><strong>Scribus 1.5svn &ndash; versione di sviluppo</strong>. Questo ramo contiene il codice per la versione sperimentale (1.5svn). Questo codice pu&ograve; avere un grado elevato di instabilit&agrave;; potrebbe anche non funzionare o addirittura non essere compilabile!</p>
+<blockquote><table width="100%" border="1" bgcolor="#eeeeee"><tr><td border="0">
+<pre>
+svn co svn://scribus.info/Scribus/trunk
+</pre>
+o, per chi ha le porte SVN chiuse sul proprio firewall,:
+<pre>
+svn co http://scribus.info/svn/Scribus/trunk
+</pre>
+</td></tr></table></blockquote>
+
+<p>Dopo aver prelevato il codice, continuate con le istruzioni per <a href="install4.html">compilare e installare usando CMake</a>.</p>
+
+</body>
+</html>
\ No newline at end of file
Index: Scribus/doc/it/toolbox12.html
===================================================================
--- Scribus/doc/it/toolbox12.html (nonexistent)
+++ Scribus/doc/it/toolbox12.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/scripterapi-object.html
===================================================================
--- Scribus/doc/it/scripterapi-object.html (nonexistent)
+++ Scribus/doc/it/scripterapi-object.html (revision 17471)
@@ -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>
Index: Scribus/doc/it/scripterapi-PDFfile.html
===================================================================
--- Scribus/doc/it/scripterapi-PDFfile.html (nonexistent)
+++ Scribus/doc/it/scripterapi-PDFfile.html (revision 17471)
@@ -0,0 +1,206 @@
+<html>
+<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
+ <title>Python: class PDFfile</title>
+</head>
+<body>
+<h2>Python: class PDFfile</h2>
+<p><a name="PDFfile">class <strong>PDFfile</strong></a>(<a href="__builtin__.html#object">object</a>)
+</p>
+<hr />
+<p>Methods defined here:</p>
+<dl>
+ <dt><a name="PDFfile-Save"><strong>Save</strong></a>(...)</dt>
+ <dd><code>This method is deprecated - use <a href="#PDFfile-save">save</a>() instead.</code></dd>
+
+ <dt><a name="PDFfile-__init__"><strong>__init__</strong></a>(...)</dt><dd><code>x.<a href="#PDFfile-__init__">__init__</a>(...) initializes x; see x.__class__.__doc__ for signature</code></dd>
+
+ <dt><a name="PDFfile-save"><strong>save</strong></a>(...)</dt><dd><code>Save selected pages to pdf file</code></dd>
+</dl>
+
+<hr>
+<p>Data and other attributes defined here:</p>
+<dd>
+ <dt><strong>__new__</strong> = &lt;built-in method __new__ of type object&gt;</dt>
+ <dd><code>T.<a href="#PDFfile-__new__">__new__</a>(S, ...) -&gt; a new object with type S, a subtype of T</code></dd>
+
+ <dt><strong>aanot</strong> = &lt;member 'aanot' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Allow Adding Annotations and Fields. Bool value</code></dd>
+
+ <dt><strong>achange</strong> = &lt;member 'achange' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Allow Changing the Document. Bool value</code></dd>
+
+ <dt><strong>acopy</strong> = &lt;member 'acopy' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Allow Copying Text and Graphics. Bool value</code></dd>
+
+ <dt><strong>aprint</strong> = &lt;member 'aprint' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Allow Printing the Document. Bool value</code></dd>
+
+ <dt><strong>article</strong> = &lt;member 'article' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Save Linked Text Frames as PDF Articles<br> Bool value</code></dd>
+
+ <dt><strong>binding</strong> = &lt;member 'binding' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Choose binding.<br>
+ 0 - Left binding<br>
+ 1 - Right binding</code></dd>
+
+ <dt><strong>bleedb</strong> = &lt;member 'bleedb' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Bleed Bottom<br>Distance for bleed from the bottom of the physical page</code></dd>
+
+ <dt><strong>bleedl</strong> = &lt;member 'bleedl' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Bleed Left<br>Distance for bleed from the left of the physical page</code></dd>
+
+ <dt><strong>bleedr</strong> = &lt;member 'bleedr' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Bleed Right<br>Distance for bleed from the right of the physical page</code></dd>
+
+ <dt><strong>bleedt</strong> = &lt;member 'bleedt' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Bleed Top<br>Distance for bleed from the top of the physical page</code></dl>
+
+ <dt><strong>bookmarks</strong> = &lt;member 'bookmarks' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Embed the bookmarks you created in your document.<br>These are useful for navigating long PDF documents.<br>Bool value</code></dd>
+
+ <dt><strong>compress</strong> = &lt;member 'compress' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Compression switch. Bool value.</code></dd>
+
+ <dt><strong>compressmtd</strong> = &lt;member 'compressmtd' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Compression method.<br>
+ 0 - Automatic<br>
+ 1 - JPEG<br>
+ 2 - zip<br>
+ 3 - None.</code></dd>
+
+ <dt><strong>downsample</strong> = &lt;attribute 'downsample' of 'PDFfile' objects&gt;</dt>
+ <dd><code>Downsample image resolusion to this value. Values from 35 to 4000<br>Set 0 for not to downsample</code></dd>
+
+ <dt><strong>effval</strong> = &lt;attribute 'effval' of 'PDFfile' objects&gt;</dt>
+ <dd><code>List of effection values for each saved page.<br>
+ <pre>
+It is list of list of six integers. Those int have the following meaning:
+ - Length of time the page is shown before the presentation
+ starts on the selected page. (1-3600)
+ - Length of time the effect runs. (1 - 3600)
+ A shorter time will speed up the effect, a longer one will slow it down
+ - Type of the display effect
+ 0 - No Effect
+ 1 - Blinds
+ 2 - Box
+ 3 - Dissolve
+ 4 - Glitter
+ 5 - Split
+ 6 - Wipe
+ - Direction of the effect of moving lines for the split and blind effects.
+ 0 - Horizontal
+ 1 - Vertical
+ - Starting position for the box and split effects.
+ 0 - Inside
+ 1 - Outside
+ - Direction of the glitter or wipe effects.
+ 0 - Left to Right
+ 1 - Top to Bottom
+ 2 - Bottom to Top
+ 3 - Right to Left
+ 4 - Top-left to Bottom-Right
+</pre></code>
+</dt>
+
+<dt><strong>encrypt</strong> = &lt;member 'encrypt' of 'PDFfile' objects&gt;</dt>
+<dd><code>Use Encription. Bool value</code></dd>
+
+<dt><strong>file</strong> = &lt;attribute 'file' of 'PDFfile' objects&gt;</dt>
+<dd><code>Name of file to save into</code></dd>
+
+<dt><strong>fonts</strong> = &lt;attribute 'fonts' of 'PDFfile' objects&gt;</dt>
+<dd>