0 - en to it translation catalogue (41 entries)

en: Building a document
it: Creare un documento

en: Note — Customizing output
it: Nota — Personalizzare la presentazione

en: The parameters set in the document configuration file (by default, <filename>publican.cfg</filename>) allow you to control many aspects of the way in which a document is presented — refer to <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" />.
it: I parametri impostati nel file di configurazione del documento (per impostazione <filename>publican.cfg</filename>), permettono di controllare molti aspetti riguardanti la presentazione di un documento — fare riferimento a <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" />.

en: If you maintain multiple versions of a document, you can create a configuration file for each version. When building the document, you can use the <option>--config</option> to specify which configuration file (and therefore which set of parameters) to use in a particular build, for example:
it: Se si mantengono versioni multiple di un documento, si può creare un file di configurazione per ciascuna versione. Quando si crea un documento, si può usare l'opzione <option>--config</option> per specificare il file da usare per una particolare compilazione, per esempio:

en: <prompt>$</prompt> <command>publican build --formats html,pdf --langs en-US,de-DE,hu-HU --config community.cfg</command>
it: <command>publican build --formats html,pdf --langs en-US,de-DE,it-IT --config community.cfg</command>

en: To build a document:
it: Per creare un documento:

en: Confirm the <parameter>YEAR</parameter> and <parameter>HOLDER</parameter> entities have been configured in the <filename><replaceable>Doc_Name</replaceable>.ent</filename> file, as described in <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-Doc_Name.ent" />.
it: Verificare che nel file <filename><replaceable>Nome_Doc</replaceable>.ent</filename>, siano state configurate le entità <parameter>YEAR</parameter> e <parameter>HOLDER</parameter>, come descritto nella <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-Doc_Name.ent" />.

en: Change into the root directory of the document. For example, if the document is named <literal>Test_Book</literal> and is located in the <filename>~/books/</filename> directory, run the following command:
it: Spostarsi nella cartella radice del documento. Per esempio, se il documento ha il nome <literal>Libro_di_Prova</literal> e si trova in <filename>~/libri/</filename>, eseguire il seguente comando:

en: <prompt>$</prompt> <command>cd ~/books/Test_Book</command>
it: <command>cd ~/libri/Libro_di_Prova</command>

en: Run a test for any errors that would stop the book from building in your chosen language, for example:
it: Eseguire un test, per evitare che ci siano errori di compilazione nel linguaggio desiderato, per esempio:

en: <prompt>$</prompt> <command>publican build --formats=test --langs=en-US</command>
it: <command>publican build --formats=test --langs=it-IT</command>

en: Run the following command to build the book:
it: Eseguire il seguente comando per creare il libro:

en: <prompt>$</prompt> <command>publican build --formats=<replaceable>formats</replaceable> --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=<replaceable>formati</replaceable> --langs=<replaceable>lingue</replaceable></command>

en: Replace <replaceable>formats</replaceable> with a comma-separated list of the formats that you want to build; for example, <literal>html,html-single,pdf</literal>. Replace <replaceable>langs</replaceable> with a comma-separated list of the languages that you want to build; for example, <literal>en-US,sv-SE,uk-UA,ko-KR</literal>.
it: Sostituire <replaceable>formati</replaceable> con la lista dei formati d'uscita, separati da virgole, per esempio  <literal>html,html-single,pdf</literal>. Sostituire <replaceable>lingue</replaceable> con la lista dei codici linguistici, separati da virgole, per esempio <literal>en-US,sv-SE,it-IT,ko-KR</literal>.

en: Formats for the <command>build</command> action
it: Formati per l'azione <command>build</command>

en: <application>Publican</application> outputs the document as in multiple HTML pages, with each chapter and major section on a separate page. <application>Publican</application> places an index at the start of the document, and places navigational elements on each page.
it: <application>Publican</application> presenta il documento in multiple pagine HTML, con ciascun capitolo e le principali sezioni su pagine separate. <application>Publican</application> crea un indice all'inizio del documento e posiziona controlli di navigazione su ogni pagina.

en: Use the <parameter>chunk_first</parameter> and <parameter>chunk_section depth</parameter> parameters in the <filename>publican.cfg</filename> file to control how <application>Publican</application> chunks sections in this format.
it: Usare i parametri <parameter>chunk_first</parameter> e <parameter>chunk_section depth</parameter> nel file <filename>publican.cfg</filename>, per controllare il tipo di suddivisione delle sezioni in questo formato d'uscita.

en: <application>Publican</application> outputs the document as a single HTML page with the table of contents near the top of the page.
it: <application>Publican</application> presenta il documento in una singola pagina HTML con la tabella dei contenuti posta in cima alla pagina.

en: <application>Publican</application> outputs the document as a single HTML page with the table of contents located in a separate pane on the left side of the document.
it: <application>Publican</application> presenta il documento in una singola pagina HTML con la la tabella dei contenuti posta in un pannello separato a sinistra del documento.

en: <application>Publican</application> outputs the document as a manual page ("man page") for use with Linux, UNIX, and similar operating systems.
it: <application>Publican</application> presenta il documento in pagine di manuale (o "man page"), in uso nei Sistemi Operativi Linux, Unix e simili.

en: <application>Publican</application> outputs the document as a PDF file.
it: <application>Publican</application> presenta il documento in un file PDF.

en: <application>Publican</application> validates the XML structure of the book, but does not transform the XML into another format.
it: <application>Publican</application> controlla la validità della struttura XML del libro, senza effettuare nessuna trasformazione.

en: <application>Publican</application> outputs the document as a single text file.
it: <application>Publican</application> presenta il documento in un singolo file di testo.

en: <application>Publican</application> outputs the document as an e-book in EPUB format.
it: <application>Publican</application> presenta il documento in un e-book in formato EPUB.

en: <application>Publican</application> outputs the document as an <application>Eclipse</application> help plugin. Refer to <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" /> for details of specifying <application>Eclipse</application>'s <parameter>id</parameter>, <parameter>name</parameter>, and <parameter>provider-name</parameter> parameters with <application>Publican</application>'s <parameter>ec_id</parameter>, <parameter>ec_name</parameter>, and <parameter>ec_provider</parameter> parameters.
it: <application>Publican</application> presenta il documento come un plugin d'aiuto di <application>Eclipse</application>. Vedere la <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" /> per i dettagli sui parametri d'impostazione <parameter>ec_id</parameter>, <parameter>ec_name</parameter> ed <parameter>ec_provider</parameter>.

en: The following examples demonstrate commonly used <prompt>$</prompt> <command>publican build</command> commands:
it: I seguenti esempi mostrano alcuni comandi comunemente usati con <command>publican build</command>:

en: <prompt>$</prompt> <command>publican build --help</command>
it: <command>publican build --help</command>

en: List available <prompt>$</prompt> <command>publican build</command> options for building a book.
it: Elenca le opzioni disponibili in <command>publican build</command> per creare un libro.

en: <prompt>$</prompt> <command>publican build --formats=test --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=test --langs=<replaceable>lingue</replaceable></command>

en: Check that the book can be built correctly. Build <command>--formats=test</command> before running any other <prompt>$</prompt> <command>publican build</command> command, and before checking a book back into a version-controlled repository from which other contributors might download it.
it: Controlla che il libro compili correttamente. Compilare con <command>--formats=test</command> prima di eseguire ogni altro comando <command>publican build</command>, e prima di riportarlo su un repository di controllo versione, da cui altri contributori possano scaricarlo.

en: <prompt>$</prompt> <command>publican build --formats=html --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=html --langs=<replaceable>lingue</replaceable></command>

en: Build the book in multi-page HTML format. The HTML output will be located in the <filename><replaceable>Doc_Name</replaceable>/tmp/<replaceable>language</replaceable>/html/</filename> directory. Each chapter and major section is placed in a separate HTML file. You can control the depth at which <application>Publican</application> places subsections into separate HTML files with the <literal>chunk-section-depth</literal> parameter in the <filename>publican.cfg</filename> — refer to <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" />.
it: Compila il libro in formato HTML su pagine multiple. Il documento in HTML viene salvato nella directory <filename><replaceable>Nome_Doc</replaceable>/tmp/<replaceable>lingua</replaceable>/html/</filename>. Ogni capitolo e ogni sezione principale viene disposto in un file HTML separato. E' possibile controllare il livello di suddivisione delle sotto-sezioni da presentare su pagine HTML separate, con il parametro <literal>chunk-section-depth</literal> in <filename>publican.cfg</filename> — fare riferimento alla <xref linkend="sect-Publican-Users_Guide-Files_in_the_book_directory-The_publican.cfg_file" />.

en: <prompt>$</prompt> <command>publican build --formats=html-single --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=html-single --langs=<replaceable>lingue</replaceable></command>

en: Build the book in single-page HTML format. The output will be a single HTML file located in the <filename><replaceable>Doc_Name</replaceable>/tmp/<replaceable>language</replaceable>/html-single/</filename> directory.
it: Crea il libro in formato HTML su una pagina singola. Il documento è un unico file HTML salvato nella directory <filename><replaceable>Nome_Doc</replaceable>/tmp/<replaceable>lingua</replaceable>/html-single/</filename>.

en: <prompt>$</prompt> <command>publican build --formats=pdf --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=pdf --langs=<replaceable>lingue</replaceable></command>

en: Build the book as a PDF file. <application>Publican</application> relies on an external application, <application>FOP</application> to render PDF. Therefore, building PDF might not be available on all systems, depending on the availability of <application>FOP</application>. The output will be a single PDF file located in the <filename><replaceable>Doc_Name</replaceable>/tmp/<replaceable>language</replaceable>/pdf/</filename> directory.
it: Crea il libro in formato PDF. <application>Publican</application> si appoggia ad una applicazione esterna, <application>FOP</application> per rendere il PDF. Quindi, la compilazione per PDF potrebbe non essere disponibile su tutti i sistemi, dipendendo dalla disponibilità di <application>FOP</application>. Il documento è un unico file PDF salvato nella directory <filename><replaceable>Nome_Doc</replaceable>/tmp/<replaceable>lingua</replaceable>/pdf/</filename>.

en: <prompt>$</prompt> <command>publican build --formats=html,html-single,pdf --langs=<replaceable>languages</replaceable></command>
it: <command>publican build --formats=html,html-single,pdf --langs=<replaceable>lingue</replaceable></command>

en: Build the book in multi-page HTML, single-page HTML, and PDF formats.
it: Crea il libro nei formati HTML su pagine multiple e su pagina singola, e PDF.

en: Building a document without validation
it: Compilare un documento senza controllo di validità

en: <application>Publican</application> validates your XML against the DocBook <firstterm>document type definition</firstterm> (DTD) before it builds the content. However, while a document is under development, you might sometimes want to skip validation while building, especially if the document contains cross-references (<tag>&lt;xref&gt;</tag>s) to sections of the document that do not yet exist. To skip validation, run <prompt>$</prompt> <command>publican build</command> with the <option>--novalid</option> option. Cross-references to non-existent content appear in the built document as three question marks: <literal>???</literal>.
it: <application>Publican</application> controlla la validità della struttura XML con il <firstterm>DTD</firstterm> (Document Type Definition) prima di compilare il contenuto. Tuttavia in certe situazioni, come quando un documento è in fase di sviluppo, si potrebbe voler saltare la validazione durante la compilazione, soprattutto se il documento contiene riferimenti incrociati (<sgmltag>&lt;xref&gt;</sgmltag>) a sezioni del documento che ancora non esistono. Per saltare la validazione, eseguire <command>publican build</command> con l'opzione <option>--novalid</option>. I riferimenti a contenuto non esistente, nel documento creato, appaiono con tre punti interrogativi, <literal>???</literal>.

en: Because the document has not been validated against the DTD, the quality of the output produced when you build with the <option>--novalid</option> option is highly suspect. Do not publish documentation that you have built with the <option>--novalid</option> option.
it: Poiché il documento non risulta validato con il DTD, la qualità della presentazione prodotta usando l'opzione <option>--novalid</option> è quantomeno sospetta. Non pubblicare i documenti compilati con l'opzione <option>--novalid</option>.
