Initial commit - Typo3 11.5.41

This commit is contained in:
Matteo Gallo
2026-07-03 17:53:31 +02:00
commit 5ca4743197
6811 changed files with 568848 additions and 0 deletions

View File

@@ -0,0 +1,427 @@
<?xml version='1.0' encoding='utf-8'?>
<xliff xmlns:t3="http://typo3.org/schemas/xliff" version="1.0">
<file t3:id="1415814793" source-language="en" datatype="plaintext" original="messages" date="2011-10-17T20:22:32Z" product-name="context_help" target-language="it">
<header/>
<body>
<trans-unit id="layout.description" xml:space="preserve" approved="yes">
<source>The Frontend Layout can change the way a page design appears.</source>
<target state="translated">Il Layout di Frontend può cambiare l'aspetto di una pagina.</target></trans-unit>
<trans-unit id="layout.details" xml:space="preserve" approved="yes">
<source>This option may not have any impact on the Frontend page design since it depends on whether the Frontend template uses it. Most templates do not use it.</source>
<target state="translated">Questa opzione potrebbe non avere alcun impatto sul design della pagina di Frontend dato che dipende dal fatto che il template di Frontend la usi o meno. La maggior parte dei template non la usano.</target></trans-unit>
<trans-unit id="doktype.description" xml:space="preserve" approved="yes">
<source>Page Type determines whether the page is normal webpage, a shortcut to another webpage, or used in other internal ways.</source>
<target state="translated">Il Page Type determina se la pagina è una normale pagina web, un collegamento ad una pagina web esterna o un collegamento ad una pagina interna.</target></trans-unit>
<trans-unit id="doktype.details" xml:space="preserve" approved="yes">
<source>'Standard' is the most common Page Type and is used for normal webpages.
'Backend User Section' is an option which creates pages that are only visible in the Frontend for Backend users who are logged in.
&lt;b&gt;Link&lt;/b&gt;
'Shortcut' pages jump to another page in the Pagetree.
'Mount Point' pages bring content from another branch of the Pagetree into the current branch.
'Link to External URL' is similar to 'Shortcut' but points to external URLs instead of TYPO3 pages.
&lt;b&gt;Special&lt;/b&gt;
'Folder' is a page type which is not shown as a webpage but is instead stores records of your choice.
'Recycler' is a garbage can. Pages and records in the Recycler are not visible in the Frontend.
'Menu Separator' is only useful if your Frontend memus are programmed to use it. It does not represent a page with content but is intended to be an unclickable placeholder in the menu.
&lt;b&gt;Notice&lt;/b&gt; Each Page Type is represented by a unique icon. The available page types can be restricted for users so all of the options described above may not be visible. Finally, particuilar record typoes may only be allowed on certain page types, but any record can be placed in a 'Folder.'</source>
<target state="translated">'Standard' indica un tipo comune di pagina ed è usato per le pagine web normali.
'Backend User Section' (Sezione Utente di Backend) è una opzine che crea pagine che saranno visibili nel Frontend destinate agli utenti di Backand che hanno fatto login.
&lt;b&gt;Link&lt;/b&gt;
Pagine di tipo 'Shortcut' sevono come scorciatoia o segnaposto per saltare a un'altra pagina dell'albero dellle pagine.
'Mount Point' prendono il contenuto da un'altro ramo dell'albero delle pagine e lo rendono disponibile nell'attuale ramo.
'Link a URL esterno' è simile a 'Shortcut' ma punta a un URL esterno invece che ad una pagina dell'albero.
&lt;b&gt;Special&lt;/b&gt;
'Folder' è una pagina che non viene vista come una pagina web ma in luogo serve per memorizzare records.
'Recycler' è un cestino. Le pagine inserire nel cestino non saranno visibli nel Frontend.
'Separatore di menu' è utile solo se i menu di Frontend sono programmati per utilizzarlo. Non raoppresenta una pagina che ha dei contenuti; bensì è un segnaposto non cliccabile che si trova tra i menu.
&lt;b&gt;Nota&lt;/b&gt; Ogni tipo di pagina è rappresentato da una specifica icona. Le pagine disponibili possono esserre ristrette agli utenti cosicchè molte opzioni descritte sopra possono non essere disponibili. Infine particolari tipi di record possono non essere permessi in certi tipi di pagina, ma qualunque tipo di record può venir memorizzato in un 'Folder'.</target></trans-unit>
<trans-unit id="_doktype.seeAlso" xml:space="preserve" approved="yes">
<source>pages:shortcut,
pages:url</source>
<target state="translated">pages:shortcut,
pages:url</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="hidden.description" xml:space="preserve" approved="yes">
<source>If this is checked, the page will be disabled on the website.</source>
<target state="translated">Se selezionato, la pagina sarà disabilitata nel sito web</target></trans-unit>
<trans-unit id="hidden.details" xml:space="preserve" approved="yes">
<source>The 'Disable,' 'Start,' 'Stop,' and 'Access' options are all about limiting access to pages and are thus related in functionality. When a page is not visible due to one of these options, the page will not show up in the site navigation.
Notice, these options are related &lt;em&gt;only&lt;/em&gt; to the page for which they are set. If you want their effect to cover the subpages as well, you must enable the 'Extend to Subpages' option.
When you're logged in as a Backend user you can preview disabled pages if you have read access to them.</source>
<target state="translated">Le opzioni "Disabilitare", "Avviare", "Stop", "Accesso" sono tutte relative a limitare l'accesso alle pagine e sono quindi legate a questa funzionalità. Quando una pagina non è visibile a causa di una di queste opzioni, la pagina non verrà visualizzata nella navigazione del sito.
Avviso, queste opzioni sono correlate &lt;em&gt;solo&lt;/em&gt; alla pagina per quale sono impostate. Se si desidera estendere queste opzioni alle sottopagine, è necessario abilitare l'opzione "Estendi alle sottopagine".
Quando si è registrati come utente backend è possibile visualizzare le pagine disabilitate se si ha l'accesso in lettura delle pagine.</target></trans-unit>
<trans-unit id="_hidden.seeAlso" xml:space="preserve" approved="yes">
<source>pages:starttime,pages:endtime,pages:fe_group,pages:extendToSubpages</source>
<target state="translated">pages:starttime,pages:endtime,pages:fe_group,pages:extendToSubpages</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_hidden.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/hidden_page.gif,
EXT:context_help/cshimages/pages_1.png</source>
<target state="translated">EXT:context_help/cshimages/hidden_page.gif,
EXT:context_help/cshimages/pages_1.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="hidden.image_descr" xml:space="preserve" approved="yes">
<source>The page icon of a disabled page is dimmed and a red X is added.
If you view a page that is hidden and you are logged in into the Backend you will still be able to see the page. The red "Preview" box will tell you that this page is visible to you because of this special circumstance.</source>
<target state="translated">L'icona di una pagina disabilitata sarà grigia ed è sovrapposta una X rossa.
Se è presente una pagina nascosta e sei loggato nel Backend, puoi comunque vedere la pagina. L'avviso rosso di antemprima (Preview) ti avvisa che la pagina è visibile solo a te, in quanto amministratore del sito.</target></trans-unit>
<trans-unit id="starttime.description" xml:space="preserve" approved="yes">
<source>The Publish Date determines when the page will be visible online. If the Publish Date is not set, the page will be available immediately.</source>
<target state="translated">La Data di Pubblicazione determina quando la pagina sarà visibile online. se la Data di Pubblicazione non viene indicata, la pagina sarà disponibile immediatamente.</target></trans-unit>
<trans-unit id="starttime.syntax" xml:space="preserve" approved="yes">
<source>The Publish Date Format is either DD-MM-YYYY or MM-DD-YYYY depending on how TYPO3 is configured. There are also several shortcuts you can use when entering the date.
If you insert a 'd' the current date will be inserted. You can also append any value in the field with a number such as '+10' which will add 10 days to the current value. For example, entering 'd+10' would result in a date 10 days from now.</source>
<target state="translated">Il Formato della Data di Pubblicazione può essere GG-MM-AAAA oppure MM-GG-AAAA dipende da come è configurato TYPO3. Ci sono inoltre diverse scorciatoie per inserire la data.
Se inserisci un 'd' la data odierna verrà inserita. Puoi anche inserire un qualsiasi valore nel campo con un numero, come '+10' aggiungerà 10 giorni alla data odierna. Esempio, se inserisci 'd+10' il risultato sarà 10 giorni dalla data odierna.</target></trans-unit>
<trans-unit id="_starttime.seeAlso" xml:space="preserve" approved="yes">
<source>pages:endtime,pages:hidden</source>
<target state="translated">pages:endtime,pages:hidden</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content</source>
<target state="translated">tt_content</target></trans-unit>
<trans-unit id="endtime.description" xml:space="preserve" approved="yes">
<source>The Expiration Date specifies when the page will no longer be visible online.</source>
<target state="translated">La Data di Scadenza specifica quando la pagina non sarà più visibile online.</target></trans-unit>
<trans-unit id="endtime.syntax" xml:space="preserve" approved="yes">
<source>See Page / Publication Date (click below)</source>
<target state="translated">Visualizza la Pagina / Data di Pubblicazione (clicca qui sotto)</target></trans-unit>
<trans-unit id="_endtime.seeAlso" xml:space="preserve" approved="yes">
<source>pages:starttime</source>
<target state="translated">pages:starttime</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="fe_group.description" xml:space="preserve" approved="yes">
<source>If Usergroup Access Rights is set to a usergroup name, only website users who are members of the selected usergroup will be able to view the page. The special option 'Hide at Login' means the page will &lt;em&gt;not&lt;/em&gt; be visible for any website users that are logged in. Likewise "Show at Any Login" will make the page visible for any logged in Frontend user.</source>
<target state="translated">Se il Permesso di Accesso del gruppo utenti è settato ad uno specifico gruppo, solo gli utenti di frontend che sono membri del gruppo saranno abilitati a vedere la pagina. L'opzione speciale 'Nascondi al login' indica che la pagina &lt;em&gt;non&lt;/em&gt; sarà visibile ad alcun utente di frontend che non è loggato. Allo stesso modo 'Mostra ad ogni login' renderà la pagina visibile a chiunque sia loggato da frontend.</target></trans-unit>
<trans-unit id="_fe_group.seeAlso" xml:space="preserve" approved="yes">
<source>fe_groups</source>
<target state="translated">fe_groups</target></trans-unit>
<trans-unit id="_fe_group.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/fegroups_4.png</source>
<target state="translated">EXT:context_help/cshimages/fegroups_4.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="extendToSubpages.description" xml:space="preserve" approved="yes">
<source>By default the Publication Date, Expiration Date, Usergroup Access Rights, and Page Visibility options &lt;em&gt;only&lt;/em&gt; affect the page where they are set. If the option 'Extend to Subpages' is checked for the page, then all subpages are affected as well.</source>
<target state="translated">Di base le opzioni della Data di Pubblicazione, la Data di Scadenza, gli Accessi degli Usergroup, e la Visibilità della Pagina hanno effetto &lt;em&gt;solo&lt;/em&gt; se vengono impostate nella pagina. Se l'opzione "Estendi alle Sottopagine" è spuntata per la pagina, tutte le sottopagine subiranno le impostazioni della pagina madre.</target></trans-unit>
<trans-unit id="extendToSubpages.details" xml:space="preserve" approved="yes">
<source>Consider a scenario where you want to create a section of subpages that are only visible for logged in users. Setting the Usergroup Access Rights for the top page in the section would remove the page from menus if no user was logged in.
However, the subpage could still be accessed by guessing the ID number of the page and entering it manually in the URL. Setting the 'Extend to Subpages' option would extend the Usergroup Access Rights from the top page through all subpages as well.</source>
<target state="translated">Considera lo scenario dove vuoi crare una sezione di sottopagine che siano visibili solo ad utenti loggati. Settando i Permessi di Accesso del gruppo utente per la pagina principale della sezione, rimuoverà la pagina dai menu se nessun utente è loggato.
Comunque la sottopagina sarà ancora accessibile indicando l'ID di pagina ed inserendolo manualmente nell'URL. Spuntando l'opzione 'Estendi alle sottopagine' si estenderanno i diritti di accesso del gruppo utenti dalla pagina principale a tutte le sottopagine.</target></trans-unit>
<trans-unit id="_extendToSubpages.seeAlso" xml:space="preserve" approved="yes">
<source>pages:hidden,
pages:starttime,
pages:endtime,
pages:fe_group</source>
<target state="translated">pages:hidden,
pages:starttime,
pages:endtime,
pages:fe_group</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_extendToSubpages.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/pages_2.png</source>
<target state="translated">EXT:context_help/cshimages/pages_2.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="extendToSubpages.image_descr" xml:space="preserve" approved="yes">
<source>This page has access restricted to a certain group and has "Extend to Subpages" set as well. This is reflected in the way the page icon has changed.</source>
<target state="translated">L'accesso alla pagina non è consentito a determinati gruppi e è impostato anche 'Estendi alle sottopagine'. Questo risulta anche dall'icona di pagina che è cambiata.</target></trans-unit>
<trans-unit id="alias.description" xml:space="preserve" approved="yes">
<source>A URL Alias is a unique identification string for a page. You can use this string instead of the ID number to refer to the page.</source>
<target state="translated">Un URL Alias è un identificatore univoco per la pagina. Puoi usare questa stringa invece dell'ID per far riferimento alla pagina.</target></trans-unit>
<trans-unit id="alias.details" xml:space="preserve" approved="yes">
<source>Ultimately a page is identified by its ID number. For example, you may access a page in TYPO3 at '.../?id=123'. If the page with ID '123' has the URL Alias 'one_two_three', then the URL '.../?id=one_two_three' would display exactly the same page, because 'one_two_three' is a URL Alias for the ID '123'.
URL Aliases are normally assigned to only the most frequently used pages rather than all pages. In most TYPO3 configurations you would be able to use the syntax '.. &amp;lt;link one_two_three&amp;gt;go to the page&amp;lt;/link&amp;gt; ..' to create a link to the page. This is easier to remember.
Another use is if you need to change which page a commonly used link points to. In this case you can delete the URL Alias for the original page and re-add it on the new page. All links using the URL Alias would now refer to the new page and its ID number.</source>
<target state="translated">Una pagina è identificata dal suo ID. Per esempio puoi accedere ad una pagina in TYPO3 con '../?id=123'. Se la pagina con ID '123' ha come URL Alias 'uno_due_tre' allora l'URL '.../?id=uno_due_tre' visualizzerà esattamente la stessa pagina, perchè 'uno_due_tre' è un URL Alias per l'ID '123'.
Gli URL Alias sono normalmente assegnati alle pagine più frequentate piuttosto che a tutte le pagine. Nella maggior parte delle configurazioni TYPO3 potrete usare la sintassi '.. &amp;lt;link uno_due_tre&amp;gt;vai alla pagina&amp;lt;/link&amp;gt; ..' per creare un link alla pagina. Questo è più facile da ricordare.
Un altro uso è se devi cambiare il link della pagina a cui solitamente punta. In questo caso puoi cancellare l'URL Alias della pagina originale e riaggiungerlo alla nuova pagina. Tutti i link che stanno usando l'URL Alias da adesso faranno riferimento alla nuova pagina e al suo ID.</target></trans-unit>
<trans-unit id="alias.syntax" xml:space="preserve" approved="yes">
<source>A URL Alias can contain only lowercase alphanumeric characters and must be unique.
Please note: If the URL Alias already exists in the site, it will have a number added to the end of it.</source>
<target state="translated">Un URL Alias può contenere caratteri minuscoli alfanumerici e deve essere unico.
Notare: Se l'URL Alias esiste già nel sito, avrà un numero aggiunto alla fine di esso.</target></trans-unit>
<trans-unit id="target.description" xml:space="preserve" approved="yes">
<source>This sets the default Link Target for menu items linking to this page. Can also used to open the page as a popup window.</source>
<target state="translated">Questo imposta il Link Target di default per le voci di menu che hanno un link a questa pagina. Può anche essere usato per aprire la pagina come una finestra popup.</target></trans-unit>
<trans-unit id="target.details" xml:space="preserve">
<source>The Link Target overrides the default Link Target behavior, which should already be configured correctly for most pages in the website TypoScript template.
There are additional options available by using the Link Target field
Setting an integer value at the beginning of the field sets it as the default type for the page.
For example, if an RSS feed is configured in TypoScript as typeNum=100, setting the Link Target to 100 could be used to add an RSS link in the menu.
The following syntax is used to open the page in a popup window:
400x200 - Opens the page in a 400x200 popup window.
230x450:resizable=0,location=1 - Opens the page in a 230x450 popup window that is not resizable and has an address bar.
Combined:
100 600x350 - Opens the page in a 600x350 popup with type=100
2 _blank - Opens the page with target "_blank" and type=2</source>
<target></target></trans-unit>
<trans-unit id="no_cache.description" xml:space="preserve" approved="yes">
<source>This option disables server caching of the page.</source>
<target state="translated">Questa opzione disabilita il caching lato server della pagina.</target></trans-unit>
<trans-unit id="no_cache.details" xml:space="preserve" approved="yes">
<source>Normally pages in TYPO3 are cached on the server after being constructed for the first time. This means a page is displayed much faster the second time it's requested.
For most pages this presents no problems; indeed, it boosts the performance of the website.
However you may need to disable caching for a page if it contains dynamic content which must not be cached under any circumstances. Normally the PHP-code rendering such content is programmed to disable the caching automatically. But with this option you can force the page not to be cached.</source>
<target state="translated">Di norma le pagine in TYPO3 vengono scritte nella memoria del server (Cache) dopo essere state composte per la prima volta. Questo significa che una pagina quando viene pubblicata per la seconda volta e successive, sarà molto più veloce da scaricare da parte del visitatore.
Per la maggior parte delle pagine non ci sono problemi con la memoria Cache; le prestazioni migliorano sensibilmente.
Comunque in alcuni casi puoi disabilitare la memorizzazione nella Cache, ad esempio quando deve essere visualizzato del contenuto dinamico. Normalmente il codice PHP per ll rendering è programmato per disabilitare il caching automaticamente. Ma con questa opzione puoi forzare la pagina a non essere conservata in cache.</target></trans-unit>
<trans-unit id="_no_cache.seeAlso" xml:space="preserve" approved="yes">
<source>pages:cache_timeout</source>
<target state="translated">pages:cache_timeout</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="cache_timeout.description" xml:space="preserve" approved="yes">
<source>Sets the Cache Lifetime for the page.</source>
<target state="translated">Definisce la durata della pagina da conservare in Cache.</target></trans-unit>
<trans-unit id="cache_timeout.details" xml:space="preserve" approved="yes">
<source>By default, pages are cached for 24 hours. After 24 hours, the page is constructed again and rewritten to the cache. Depending on your configuration, the cache may be cleared at midnight.
When specific pages need a longer or shorter cache lifetime than the default, this option can be used.</source>
<target state="translated">Per default le pagine durano in cache per 24 ore. Dopo 24 ore la pagina viene rigenerata e scritta nuovamente in cache. Dipende dalla configurazione del tuo sito; la cache può essere cancellata a mezzanotte.
Puoi usare questa opzione per pagine specifiche che necessitano di una permanenza in cache superiore al tempo di &lt;i&gt;default&lt;/i&gt;.</target></trans-unit>
<trans-unit id="_cache_timeout.seeAlso" xml:space="preserve" approved="yes">
<source>pages:no_cache</source>
<target state="translated">pages:no_cache</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="no_search.description" xml:space="preserve" approved="yes">
<source>If enabled, this option excludes the page from searching operations on the website.</source>
<target state="translated">Se abilitata, questa opzione esclude la pagina dalle operazioni di indicizzazione per la ricerca nel sito web.</target></trans-unit>
<trans-unit id="author.description" xml:space="preserve" approved="yes">
<source>Enter the page author's name.</source>
<target state="translated">Inserisci il nome dell'autore della pagina</target></trans-unit>
<trans-unit id="author.details" xml:space="preserve" approved="yes">
<source>Whether the author name is used or not depends on the setup of your TypoScript template.
- You may use it in a meta-tag.
- If you're using TYPO3 pages as 'articles' then you could use this field to display the name of the page (article) author.</source>
<target state="translated">Se viene usato il nome dell'autore o non dipende da opzioni di configurazione passate dal template di Typoscript.
- puoi usarlo nei meta-tage.
- se stai utilizzando pagine di TYPO3 come 'articoli' allora puoi usare questo campo per visualizzare il nome dell'autore della pagina-articolo.</target></trans-unit>
<trans-unit id="_author.seeAlso" xml:space="preserve" approved="yes">
<source>pages:author_email</source>
<target state="translated">pages:author_email</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="author_email.description" xml:space="preserve" approved="yes">
<source>Enter the page author's email address.</source>
<target state="translated">Inserisci l'indirizzo e-mail dell'autore della pagina.</target></trans-unit>
<trans-unit id="_author_email.seeAlso" xml:space="preserve" approved="yes">
<source>pages:author</source>
<target state="translated">pages:author</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="module.description" xml:space="preserve" approved="yes">
<source>Define the page as containing a Frontend plugin.</source>
<target state="translated">Definisce la pagina come contenitore per un plugin di Frontend.</target></trans-unit>
<trans-unit id="module.details" xml:space="preserve">
<source>Setting this option lets the Backend knows this page contains specific content or has a specific purpose, such as containing a forum or acting as the root page of a shop section on the website. Based on this setting the Backend is able to display a shortcut list as well as relevant functionality in the 'Web&gt;Modules' module. The Frontend display is largely not affected.
Marking a page as containing a 'Shop' plugin simply means it'll show up in the shortcut list of modules in the backend.
For additional details on this option, refer to the administration documentation.
It's recommended that only admin-users have access to this field!</source>
<target></target></trans-unit>
<trans-unit id="media.description" xml:space="preserve" approved="yes">
<source>Attach media files related to the page.</source>
<target state="translated">File media in allegato relazionali alla pagina.</target></trans-unit>
<trans-unit id="media.details" xml:space="preserve" approved="yes">
<source>This field allows you to attach various files to the page, but how these files are used depends on your template.
As an example the template could be use this field to allow a logo to be attached to the page or it might expect the first file to be an image used as a link in the navigation menu. Remember, this totally depends on how the template is programmed.</source>
<target state="translated">Questo campo permette di allegare diversi file alla pagina; tuttavia il loro utilizzo dipende dal template Typoscript
Per esempio il template potrebbe utilizzare questo campo come logo per la pagina oppure utilizzare il primo file di tipo immagine come link nel menu di navigazione. In ogni caso, l'utilizzo di queste informazioni dipende esclusivamente dal template.</target></trans-unit>
<trans-unit id="subtitle.description" xml:space="preserve" approved="yes">
<source>Enter a subtitle if needed.</source>
<target state="translated">Inserisci un sottotitolo, se necessario.</target></trans-unit>
<trans-unit id="subtitle.details" xml:space="preserve" approved="yes">
<source>Whether this field is used or not depends on the template. In most cases it's not used.</source>
<target state="translated">L'utilizzo di questo campo dipende o meno dal template in uso. In molti casi non viene usato.</target></trans-unit>
<trans-unit id="url.description" xml:space="preserve" approved="yes">
<source>Enter the URL this page redirects to.</source>
<target state="translated">Inserisci l'URL della pagina alla quale effettuare la redirezione.</target></trans-unit>
<trans-unit id="url.details" xml:space="preserve" approved="no">
<source>For example, 'http://www.typo3.org' or just 'www.typo3.org' if the 'Protocol' selector is set to 'http://'.
Use the 'Protocol' selector to select a prefix for the URL.
This option is used only if the page 'Type' is set to 'Link to External URL.'</source>
<target state="needs-translation">Per esempio 'http://www.typo3.org' o il solo 'www.typo3.org' se il selettore 'Protocollo' e' configurato come 'http://'.
Utilizzare il selettore 'Protocollo' per indicare il prefisso dell'URL.
Questa opzione viene usata solo se il tipo di pagina scelto è 'Collegamento a Url esterno'.</target></trans-unit>
<trans-unit id="_url.seeAlso" xml:space="preserve" approved="yes">
<source>pages:urltype</source>
<target state="translated">pages:urltype</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="shortcut.description" xml:space="preserve" approved="yes">
<source>Select a page to act as the Shortcut Target. When the current page is requested in the Frontend, it will be redirected to the Shortcut Target.</source>
<target state="translated">Selezionare una pagina che agirà come destinazione per la scorciatoia (Shortcut). Quando la pagina corrente sarà richiesta nel frontent, typo3 effettuerà una redirezione alla pagina di destinazione (shortcut target).</target></trans-unit>
<trans-unit id="shortcut.details" xml:space="preserve" approved="no">
<source>Click the 'Browse for Records' icon and a new window will appear in which you can easily select a page to act as the Shortcut Target.
This option is used only if the page 'Type' is set to 'Shortcut.'</source>
<target state="needs-translation">Clicca l'icona 'Naviga nei records' e una nuova finestra sarà visualizzata, con la quale potrai scegliere in modo semplice la pagina di destinazione della scorciatoia (Shortcut Target).
Questa opzione è disponibile solo se il tipo di pagina è 'scorciatoia' (Shortcut).</target></trans-unit>
<trans-unit id="_shortcut.seeAlso" xml:space="preserve" approved="yes">
<source>pages:doktype,
pages:shortcut_mode</source>
<target state="translated">pages:doktype,
pages:shortcut_mode</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_shortcut.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/page_shortcut.gif</source>
<target state="translated">EXT:context_help/cshimages/page_shortcut.gif</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="shortcut.image_descr" xml:space="preserve" approved="yes">
<source>Select a Shortcut Target page with the Element Browser.</source>
<target state="translated">Selezionare la pagina di destinazione (Shortcut Target) attravero il navigatore (element browser).</target></trans-unit>
<trans-unit id="keywords.description" xml:space="preserve" approved="yes">
<source>Enter keywords for the page separated by commas. You may also use short phrases.</source>
<target state="translated">Inserisci le parole-chiave (keywords) per la pagina separate da virgole. E' possibile utilizzare anche frasi brevi.</target></trans-unit>
<trans-unit id="keywords.details" xml:space="preserve" approved="yes">
<source>Most TYPO3 websites use these keywords in a meta-tag on the page, but you may have to setup the appropriate TypoScript template yourself.
To optimize your page for search engines like Google you should not use more than 3 to 6 keywords. You should also make sure that the keywords are found in the content of the page.
Note that search engine extensions for TYPO3 such as Indexed Search can also be configured to make use of the keywords.
The keywords can also be used to create a menu of related pages. Create a Content Element of type 'Sitemap' and then choose the menu type &lt;i&gt;Related pages (based on keywords)&lt;/i&gt;.</source>
<target state="translated">Diversi siti con TYPO3 usano queste parole chiave nei meta-tag di pagina, ma tu puoi disporre anche di una diversa configurazione nel template di Typoscript.
Per ottimizzare la pagina ai fini dei motori di ricerca come Google non dovresti usare più di 3-6 parolel chiave. Dovresti anche accertarti che le parole chiave siano pubblicate nella pagina corrente.
Nota che alcune estensioni per implementare un motore di ricerca interno al sito, come ad esempio l'estensione 'Indexed Search' possono essere configurate per l'uso di queste parole chiave.
Le parole chiave possono anche essere usate per creare un meno di pagine relazionate. Per farlo basta creare un tipo di contenuto come 'mappa del sito' (Sitemap) e scegliere dal menu a tendina il tipo &lt;i&gt;Pagine relazionate (basate sulle parole chiave)&lt;/i&gt;.</target></trans-unit>
<trans-unit id="_keywords.seeAlso" xml:space="preserve" approved="yes">
<source>pages:description</source>
<target state="translated">pages:description</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="description.description" xml:space="preserve" approved="yes">
<source>Enter a short description of the page. It will be displayed in the result lists of most search engines.</source>
<target state="translated">Inserire una breve descrizione della pagina. Sarò visualizzata tra i risultati della ricerca elencate in vari motori.</target></trans-unit>
<trans-unit id="description.details" xml:space="preserve">
<source>Most websites insert this description in a meta-tag on the page, but you may have to configure this yourself in your TypoScript template.
Most search engines will display the description in their result list. Thus, the text should be short (about 160 characters maximum), and its wording should make sense when it shows up in the result list.
In addition, the description will be displayed if you create a Content Element of type 'Sitemap' and then choose the menu type &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt;. If an abstract exists for the page, it will be used instead of the description.
&lt;b&gt;Note:&lt;/b&gt; Some search engines only use the description if the text is not found elsewhere in the content. So do not just repeat yourself.</source>
<target></target></trans-unit>
<trans-unit id="_description.seeAlso" xml:space="preserve" approved="yes">
<source>pages:keywords
pages:abstract</source>
<target state="translated">pages:keywords
pages:abstract</target></trans-unit>
<trans-unit id="abstract.description" xml:space="preserve" approved="yes">
<source>Enter an abstract of the contents. It may be displayed in an overview of articles.</source>
<target state="translated">Inserire un abstract dei contenuti. Potrà essere visualizzato in una anteprima degli articoli.</target></trans-unit>
<trans-unit id="abstract.details" xml:space="preserve">
<source>An abstract is a short description of the page content that might be a little longer than the one in the &lt;i&gt;Description&lt;/i&gt; field.
Unlike the description, the abstract is not meant for display in search engine result lists, but is instead intended for you own use.
If you create a Content Element of type &lt;i&gt;Sitemap&lt;/i&gt; and then choose &lt;i&gt;Menu of subpages to these pages (with abstract)&lt;/i&gt; an overview of pages will be created. If an abstract is available for a page it will be used instead of the description.
&lt;b&gt;Note:&lt;/b&gt; You do not have to enter the text of the description into the &lt;i&gt;Abstract field&lt;/i&gt; again.
Admins can also make custom use of this field via their TypoScript templates.</source>
<target></target></trans-unit>
<trans-unit id="_abstract.seeAlso" xml:space="preserve" approved="yes">
<source>pages:description</source>
<target state="translated">pages:description</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="newUntil.description" xml:space="preserve" approved="yes">
<source>Enter the date at which this page is no longer considered new.</source>
<target state="translated">Inserisci la data a partire dalla quale la pagina non sarà più considerata come 'nuova'.</target></trans-unit>
<trans-unit id="newUntil.details" xml:space="preserve">
<source>The 'New Until' date of the page has no effect on the display of the webpage. This value is instead for internal use as a reminder of the date when the content of this page should be revised. If the content of the page will become outdated on a certain day, you could set this value to that approximate date.
To get an overview of when pages will be outdated, use the 'Pagetree overview' in the 'Web&gt;Info' Module.</source>
<target></target></trans-unit>
<trans-unit id="newUntil.syntax" xml:space="preserve" approved="yes">
<source>See Page / Publication Date (click below)</source>
<target state="translated">Vedi la Pagina / Data di Pubblicazione (clicca sotto)</target></trans-unit>
<trans-unit id="_newUntil.seeAlso" xml:space="preserve" approved="yes">
<source>pages:starttime</source>
<target state="translated">pages:starttime</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="lastUpdated.description" xml:space="preserve">
<source>Enter the date and time of the most recent update to this page.</source>
<target></target></trans-unit>
<trans-unit id="lastUpdated.details" xml:space="preserve">
<source>How the value of this field is used is determined by the TypoScript template of the website. 'Last Update' content needs to be inserted on the pages and the TypoScript template must be configured to use this value.
The most common use is to display the date from the automatically updated 'tstamp' field &lt;em&gt;unless&lt;/em&gt; the 'Last Update' field is set. In this case, the date in 'Last Update' is used.</source>
<target></target></trans-unit>
<trans-unit id="lastUpdated.syntax" xml:space="preserve">
<source>The format is HH:MM DD-MM-YYYY or HH:MM MM-DD-YYYY depending on your TYPO3 configuration.
If you insert a 'd' the current time and date is inserted. You can also append any value in the field with a number lie '+10' which will add 10 days to the current value.</source>
<target></target></trans-unit>
<trans-unit id="nav_hide.description" xml:space="preserve">
<source>With this option the page will be not appear in menus in the Frontend. The page can still be viewed if linked by going directly to its URL.</source>
<target></target></trans-unit>
<trans-unit id="_nav_hide.seeAlso" xml:space="preserve" approved="yes">
<source>pages:nav_title</source>
<target state="translated">pages:nav_title</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="nav_title.description" xml:space="preserve">
<source>Alternative Navigation Title for menu items in the Frontend. When set, this value is used instead of the Page Title.</source>
<target></target></trans-unit>
<trans-unit id="content_from_pid.description" xml:space="preserve">
<source>If set, this is an alternative page to select Content Elements from.
Whether this field is used depends on the website's TypoScript template.</source>
<target></target></trans-unit>
<trans-unit id="urltype.description" xml:space="preserve" approved="yes">
<source>Set the Protocol for the URL.</source>
<target state="translated">Configura il protocollo per l'URL</target></trans-unit>
<trans-unit id="shortcut_mode.description" xml:space="preserve">
<source>Select a Shortcut Mode. By default the shortcut page must have a Shortcut Target to jump to. Other options are to go to the first subpage, to a random subpage, or back up to the parent page.</source>
<target></target></trans-unit>
<trans-unit id="mount_pid.description" xml:space="preserve">
<source>Mount this page. If set, subpages of this page come from the Mounted Page instead.</source>
<target></target></trans-unit>
<trans-unit id="mount_pid.details" xml:space="preserve" approved="yes">
<source>In the Frontend this is done by adding a new variable, &amp;MP, to the URL. This links the mounted branch to the main branch by pairing page ids.</source>
<target state="translated">Nel frontend questo viene fatto aggiungendo una nuova variabile, &amp;MP, all'URL. Questo stabilisce un collegamento tra il ramo montato (mounted branch) e quello principale tramite due id di pagina.</target></trans-unit>
<trans-unit id="_mount_pid.seeAlso" xml:space="preserve" approved="yes">
<source>pages:mount_pid_ol</source>
<target state="translated">pages:mount_pid_ol</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="mount_pid_ol.description" xml:space="preserve" approved="yes">
<source>Show content for the current page or replace it completely with the Mounted Page.</source>
<target state="translated">Mostra il contenuto della pagina corrente o lo sostituiscilo completamente con quello della pagina montata (Mounted Page).</target></trans-unit>
<trans-unit id="_mount_pid_ol.seeAlso" xml:space="preserve" approved="yes">
<source>pages:mount_pid</source>
<target state="translated">pages:mount_pid</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="title.description.+" xml:space="preserve" approved="yes">
<source>This is normally shown in the website navigation.</source>
<target state="translated">Questo è normalmente visualizzato nella navigazione del sito web.</target></trans-unit>
<trans-unit id="TSconfig.details.+" xml:space="preserve">
<source>&lt;strong&gt;Example:&lt;/strong&gt;
The 'Web&gt;Page' module lets you create content in four columns, Left, Normal, Right, Border if the template has been configured to use this option. (However, most websites use only one or two columns so some of these content columns are just taking up space and confusing users.)
If you enter this string in the 'TSConfig' field, the 'Web&gt;Page' Module will only show the 'Normal' and 'Border' column!
&lt;em&gt;mod.web_layout.tt_content.colPos_list = 0,3&lt;/em&gt;
(Must be entered in a single line!)</source>
<target></target></trans-unit>
<trans-unit id="l18n_cfg.description" xml:space="preserve" approved="yes">
<source>Affect availability of pages in the various languages.</source>
<target state="translated">Influenza la disponibilità delle pagine nelle varie lingue</target></trans-unit>
<trans-unit id="l18n_cfg.details" xml:space="preserve">
<source>&lt;b&gt;Hide default translation of page&lt;/b&gt;
If set, the page is only available in translated versions and not in the default language. Any attempt to access the page in the default language will result in an error message.
&lt;b&gt;Hide page if no translation for current language exists&lt;/b&gt;
If set, any attempt to access the page in a translation that does not exist will result in an error message. By default, accessing an untranslated page will just show the default language instead.</source>
<target></target></trans-unit>
</body>
</file>
</xliff>

View File

@@ -0,0 +1,140 @@
<?xml version="1.0" encoding="UTF-8"?>
<T3locallangExt>
<data type="array">
<languageKey index="it" type="array">
<label index="layout.description">Il Layout di Frontend può cambiare l'aspetto di una pagina.</label>
<label index="layout.details">Questa opzione potrebbe non avere alcun impatto sul design della pagina di Frontend dato che dipende dal fatto che il template di Frontend la usi o meno. La maggior parte dei template non la usano.</label>
<label index="doktype.description">Il Page Type determina se la pagina è una normale pagina web, un collegamento ad una pagina web esterna o un collegamento ad una pagina interna.</label>
<label index="doktype.details">'Standard' indica un tipo comune di pagina ed è usato per le pagine web normali.
'Backend User Section' (Sezione Utente di Backend) è una opzine che crea pagine che saranno visibili nel Frontend destinate agli utenti di Backand che hanno fatto login.
&lt;b&gt;Link&lt;/b&gt;
Pagine di tipo 'Shortcut' sevono come scorciatoia o segnaposto per saltare a un'altra pagina dell'albero dellle pagine.
'Mount Point' prendono il contenuto da un'altro ramo dell'albero delle pagine e lo rendono disponibile nell'attuale ramo.
'Link a URL esterno' è simile a 'Shortcut' ma punta a un URL esterno invece che ad una pagina dell'albero.
&lt;b&gt;Special&lt;/b&gt;
'Folder' è una pagina che non viene vista come una pagina web ma in luogo serve per memorizzare records.
'Recycler' è un cestino. Le pagine inserire nel cestino non saranno visibli nel Frontend.
'Separatore di menu' è utile solo se i menu di Frontend sono programmati per utilizzarlo. Non raoppresenta una pagina che ha dei contenuti; bensì è un segnaposto non cliccabile che si trova tra i menu.
&lt;b&gt;Nota&lt;/b&gt; Ogni tipo di pagina è rappresentato da una specifica icona. Le pagine disponibili possono esserre ristrette agli utenti cosicchè molte opzioni descritte sopra possono non essere disponibili. Infine particolari tipi di record possono non essere permessi in certi tipi di pagina, ma qualunque tipo di record può venir memorizzato in un 'Folder'.</label>
<label index="_doktype.seeAlso">pages:shortcut,
pages:url</label>
<label index="hidden.description">Se selezionato, la pagina sarà disabilitata nel sito web</label>
<label index="hidden.details">Le opzioni "Disabilitare", "Avviare", "Stop", "Accesso" sono tutte relative a limitare l'accesso alle pagine e sono quindi legate a questa funzionalità. Quando una pagina non è visibile a causa di una di queste opzioni, la pagina non verrà visualizzata nella navigazione del sito.
Avviso, queste opzioni sono correlate &lt;em&gt;solo&lt;/em&gt; alla pagina per quale sono impostate. Se si desidera estendere queste opzioni alle sottopagine, è necessario abilitare l'opzione "Estendi alle sottopagine".
Quando si è registrati come utente backend è possibile visualizzare le pagine disabilitate se si ha l'accesso in lettura delle pagine.</label>
<label index="_hidden.seeAlso">pages:starttime,pages:endtime,pages:fe_group,pages:extendToSubpages</label>
<label index="_hidden.image">EXT:context_help/cshimages/hidden_page.gif,
EXT:context_help/cshimages/pages_1.png</label>
<label index="hidden.image_descr">L'icona di una pagina disabilitata sarà grigia ed è sovrapposta una X rossa.
Se è presente una pagina nascosta e sei loggato nel Backend, puoi comunque vedere la pagina. L'avviso rosso di antemprima (Preview) ti avvisa che la pagina è visibile solo a te, in quanto amministratore del sito.</label>
<label index="starttime.description">La Data di Pubblicazione determina quando la pagina sarà visibile online. se la Data di Pubblicazione non viene indicata, la pagina sarà disponibile immediatamente.</label>
<label index="starttime.syntax">Il Formato della Data di Pubblicazione può essere GG-MM-AAAA oppure MM-GG-AAAA dipende da come è configurato TYPO3. Ci sono inoltre diverse scorciatoie per inserire la data.
Se inserisci un 'd' la data odierna verrà inserita. Puoi anche inserire un qualsiasi valore nel campo con un numero, come '+10' aggiungerà 10 giorni alla data odierna. Esempio, se inserisci 'd+10' il risultato sarà 10 giorni dalla data odierna.</label>
<label index="_starttime.seeAlso">pages:endtime,pages:hidden</label>
<label index="_.seeAlso">tt_content</label>
<label index="endtime.description">La Data di Scadenza specifica quando la pagina non sarà più visibile online.</label>
<label index="endtime.syntax">Visualizza la Pagina / Data di Pubblicazione (clicca qui sotto)</label>
<label index="_endtime.seeAlso">pages:starttime</label>
<label index="fe_group.description">Se il Permesso di Accesso del gruppo utenti è settato ad uno specifico gruppo, solo gli utenti di frontend che sono membri del gruppo saranno abilitati a vedere la pagina. L'opzione speciale 'Nascondi al login' indica che la pagina &lt;em&gt;non&lt;/em&gt; sarà visibile ad alcun utente di frontend che non è loggato. Allo stesso modo 'Mostra ad ogni login' renderà la pagina visibile a chiunque sia loggato da frontend.</label>
<label index="_fe_group.seeAlso">fe_groups</label>
<label index="_fe_group.image">EXT:context_help/cshimages/fegroups_4.png</label>
<label index="extendToSubpages.description">Di base le opzioni della Data di Pubblicazione, la Data di Scadenza, gli Accessi degli Usergroup, e la Visibilità della Pagina hanno effetto &lt;em&gt;solo&lt;/em&gt; se vengono impostate nella pagina. Se l'opzione "Estendi alle Sottopagine" è spuntata per la pagina, tutte le sottopagine subiranno le impostazioni della pagina madre.</label>
<label index="extendToSubpages.details">Considera lo scenario dove vuoi crare una sezione di sottopagine che siano visibili solo ad utenti loggati. Settando i Permessi di Accesso del gruppo utente per la pagina principale della sezione, rimuoverà la pagina dai menu se nessun utente è loggato.
Comunque la sottopagina sarà ancora accessibile indicando l'ID di pagina ed inserendolo manualmente nell'URL. Spuntando l'opzione 'Estendi alle sottopagine' si estenderanno i diritti di accesso del gruppo utenti dalla pagina principale a tutte le sottopagine.</label>
<label index="_extendToSubpages.seeAlso">pages:hidden,
pages:starttime,
pages:endtime,
pages:fe_group</label>
<label index="_extendToSubpages.image">EXT:context_help/cshimages/pages_2.png</label>
<label index="extendToSubpages.image_descr">L'accesso alla pagina non è consentito a determinati gruppi e è impostato anche 'Estendi alle sottopagine'. Questo risulta anche dall'icona di pagina che è cambiata.</label>
<label index="alias.description">Un URL Alias è un identificatore univoco per la pagina. Puoi usare questa stringa invece dell'ID per far riferimento alla pagina.</label>
<label index="alias.details">Una pagina è identificata dal suo ID. Per esempio puoi accedere ad una pagina in TYPO3 con '../?id=123'. Se la pagina con ID '123' ha come URL Alias 'uno_due_tre' allora l'URL '.../?id=uno_due_tre' visualizzerà esattamente la stessa pagina, perchè 'uno_due_tre' è un URL Alias per l'ID '123'.
Gli URL Alias sono normalmente assegnati alle pagine più frequentate piuttosto che a tutte le pagine. Nella maggior parte delle configurazioni TYPO3 potrete usare la sintassi '.. &amp;lt;link uno_due_tre&amp;gt;vai alla pagina&amp;lt;/link&amp;gt; ..' per creare un link alla pagina. Questo è più facile da ricordare.
Un altro uso è se devi cambiare il link della pagina a cui solitamente punta. In questo caso puoi cancellare l'URL Alias della pagina originale e riaggiungerlo alla nuova pagina. Tutti i link che stanno usando l'URL Alias da adesso faranno riferimento alla nuova pagina e al suo ID.</label>
<label index="alias.syntax">Un URL Alias può contenere caratteri minuscoli alfanumerici e deve essere unico.
Notare: Se l'URL Alias esiste già nel sito, avrà un numero aggiunto alla fine di esso.</label>
<label index="target.description">Questo imposta il Link Target di default per le voci di menu che hanno un link a questa pagina. Può anche essere usato per aprire la pagina come una finestra popup.</label>
<label index="target.details"/>
<label index="no_cache.description">Questa opzione disabilita il caching lato server della pagina.</label>
<label index="no_cache.details">Di norma le pagine in TYPO3 vengono scritte nella memoria del server (Cache) dopo essere state composte per la prima volta. Questo significa che una pagina quando viene pubblicata per la seconda volta e successive, sarà molto più veloce da scaricare da parte del visitatore.
Per la maggior parte delle pagine non ci sono problemi con la memoria Cache; le prestazioni migliorano sensibilmente.
Comunque in alcuni casi puoi disabilitare la memorizzazione nella Cache, ad esempio quando deve essere visualizzato del contenuto dinamico. Normalmente il codice PHP per ll rendering è programmato per disabilitare il caching automaticamente. Ma con questa opzione puoi forzare la pagina a non essere conservata in cache.</label>
<label index="_no_cache.seeAlso">pages:cache_timeout</label>
<label index="cache_timeout.description">Definisce la durata della pagina da conservare in Cache.</label>
<label index="cache_timeout.details">Per default le pagine durano in cache per 24 ore. Dopo 24 ore la pagina viene rigenerata e scritta nuovamente in cache. Dipende dalla configurazione del tuo sito; la cache può essere cancellata a mezzanotte.
Puoi usare questa opzione per pagine specifiche che necessitano di una permanenza in cache superiore al tempo di &lt;i&gt;default&lt;/i&gt;.</label>
<label index="_cache_timeout.seeAlso">pages:no_cache</label>
<label index="no_search.description">Se abilitata, questa opzione esclude la pagina dalle operazioni di indicizzazione per la ricerca nel sito web.</label>
<label index="author.description">Inserisci il nome dell'autore della pagina</label>
<label index="author.details">Se viene usato il nome dell'autore o non dipende da opzioni di configurazione passate dal template di Typoscript.
- puoi usarlo nei meta-tage.
- se stai utilizzando pagine di TYPO3 come 'articoli' allora puoi usare questo campo per visualizzare il nome dell'autore della pagina-articolo.</label>
<label index="_author.seeAlso">pages:author_email</label>
<label index="author_email.description">Inserisci l'indirizzo e-mail dell'autore della pagina.</label>
<label index="_author_email.seeAlso">pages:author</label>
<label index="module.description">Definisce la pagina come contenitore per un plugin di Frontend.</label>
<label index="module.details"/>
<label index="media.description">File media in allegato relazionali alla pagina.</label>
<label index="media.details">Questo campo permette di allegare diversi file alla pagina; tuttavia il loro utilizzo dipende dal template Typoscript
Per esempio il template potrebbe utilizzare questo campo come logo per la pagina oppure utilizzare il primo file di tipo immagine come link nel menu di navigazione. In ogni caso, l'utilizzo di queste informazioni dipende esclusivamente dal template.</label>
<label index="subtitle.description">Inserisci un sottotitolo, se necessario.</label>
<label index="subtitle.details">L'utilizzo di questo campo dipende o meno dal template in uso. In molti casi non viene usato.</label>
<label index="url.description">Inserisci l'URL della pagina alla quale effettuare la redirezione.</label>
<label index="url.details">Per esempio 'http://www.typo3.org' o il solo 'www.typo3.org' se il selettore 'Protocollo' e' configurato come 'http://'.
Utilizzare il selettore 'Protocollo' per indicare il prefisso dell'URL.
Questa opzione viene usata solo se il tipo di pagina scelto è 'Collegamento a Url esterno'.</label>
<label index="_url.seeAlso">pages:urltype</label>
<label index="shortcut.description">Selezionare una pagina che agirà come destinazione per la scorciatoia (Shortcut). Quando la pagina corrente sarà richiesta nel frontent, typo3 effettuerà una redirezione alla pagina di destinazione (shortcut target).</label>
<label index="shortcut.details">Clicca l'icona 'Naviga nei records' e una nuova finestra sarà visualizzata, con la quale potrai scegliere in modo semplice la pagina di destinazione della scorciatoia (Shortcut Target).
Questa opzione è disponibile solo se il tipo di pagina è 'scorciatoia' (Shortcut).</label>
<label index="_shortcut.seeAlso">pages:doktype,
pages:shortcut_mode</label>
<label index="_shortcut.image">EXT:context_help/cshimages/page_shortcut.gif</label>
<label index="shortcut.image_descr">Selezionare la pagina di destinazione (Shortcut Target) attravero il navigatore (element browser).</label>
<label index="keywords.description">Inserisci le parole-chiave (keywords) per la pagina separate da virgole. E' possibile utilizzare anche frasi brevi.</label>
<label index="keywords.details">Diversi siti con TYPO3 usano queste parole chiave nei meta-tag di pagina, ma tu puoi disporre anche di una diversa configurazione nel template di Typoscript.
Per ottimizzare la pagina ai fini dei motori di ricerca come Google non dovresti usare più di 3-6 parolel chiave. Dovresti anche accertarti che le parole chiave siano pubblicate nella pagina corrente.
Nota che alcune estensioni per implementare un motore di ricerca interno al sito, come ad esempio l'estensione 'Indexed Search' possono essere configurate per l'uso di queste parole chiave.
Le parole chiave possono anche essere usate per creare un meno di pagine relazionate. Per farlo basta creare un tipo di contenuto come 'mappa del sito' (Sitemap) e scegliere dal menu a tendina il tipo &lt;i&gt;Pagine relazionate (basate sulle parole chiave)&lt;/i&gt;.</label>
<label index="_keywords.seeAlso">pages:description</label>
<label index="description.description">Inserire una breve descrizione della pagina. Sarò visualizzata tra i risultati della ricerca elencate in vari motori.</label>
<label index="description.details"/>
<label index="_description.seeAlso">pages:keywords
pages:abstract</label>
<label index="abstract.description">Inserire un abstract dei contenuti. Potrà essere visualizzato in una anteprima degli articoli.</label>
<label index="abstract.details"/>
<label index="_abstract.seeAlso">pages:description</label>
<label index="newUntil.description">Inserisci la data a partire dalla quale la pagina non sarà più considerata come 'nuova'.</label>
<label index="newUntil.details"/>
<label index="newUntil.syntax">Vedi la Pagina / Data di Pubblicazione (clicca sotto)</label>
<label index="_newUntil.seeAlso">pages:starttime</label>
<label index="lastUpdated.description"/>
<label index="lastUpdated.details"/>
<label index="lastUpdated.syntax"/>
<label index="nav_hide.description"/>
<label index="_nav_hide.seeAlso">pages:nav_title</label>
<label index="nav_title.description"/>
<label index="content_from_pid.description"/>
<label index="urltype.description">Configura il protocollo per l'URL</label>
<label index="shortcut_mode.description"/>
<label index="mount_pid.description"/>
<label index="mount_pid.details">Nel frontend questo viene fatto aggiungendo una nuova variabile, &amp;MP, all'URL. Questo stabilisce un collegamento tra il ramo montato (mounted branch) e quello principale tramite due id di pagina.</label>
<label index="_mount_pid.seeAlso">pages:mount_pid_ol</label>
<label index="mount_pid_ol.description">Mostra il contenuto della pagina corrente o lo sostituiscilo completamente con quello della pagina montata (Mounted Page).</label>
<label index="_mount_pid_ol.seeAlso">pages:mount_pid</label>
<label index="title.description.+">Questo è normalmente visualizzato nella navigazione del sito web.</label>
<label index="TSconfig.details.+"/>
<label index="l18n_cfg.description">Influenza la disponibilità delle pagine nelle varie lingue</label>
<label index="l18n_cfg.details"/>
</languageKey>
</data>
</T3locallangExt>

View File

@@ -0,0 +1,807 @@
<?xml version='1.0' encoding='utf-8'?>
<xliff xmlns:t3="http://typo3.org/schemas/xliff" version="1.0">
<file t3:id="1415814794" source-language="en" datatype="plaintext" original="messages" date="2011-10-17T20:22:32Z" product-name="context_help" target-language="it">
<header/>
<body>
<trans-unit id=".description" xml:space="preserve" approved="yes">
<source>All visible content on webpages is typically made by "Page Content" records, often referred to as "Content Elements". Content Elements are managed by the "Page" Module which organizes Content Elements in multiple columns and languages.</source>
<target state="translated">Tutti i contenuti visibili nelle pagine web sono solitamente creati tramite i record "Page Content", che spesso viene definiti come "Elemento di Contenuto". Gli elementi di contenuto sono gestiti tramite il modulo "Page" che li organizza in colonne multiple e lingua.</target></trans-unit>
<trans-unit id=".details" xml:space="preserve">
<source>"Page Content" records are sortable and can be rearranged. The "Language" and "Column" selectors of the "Page Content" records determines when and where they appear. If you do not change the value of the "Language" and "Column" selectors the Content Element will appear in the default configuration.</source>
<target></target></trans-unit>
<trans-unit id="_.seeAlso" xml:space="preserve" approved="yes">
<source>Page Content Principles | http://typo3.org/documentation/document-library/doc_tut_quickstart/Page_content/,
_MOD_web_layout</source>
<target state="translated">Principi di Page Content | http://typo3.org/documentation/document-library/doc_tut_quickstart/Page_content/,
_MOD_web_layout</target></trans-unit>
<trans-unit id="_.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/ttcontent_1.png,
EXT:context_help/cshimages/ttcontent_2.png,
EXT:context_help/cshimages/ttcontent_3.png</source>
<target state="translated">EXT:context_help/cshimages/ttcontent_1.png,
EXT:context_help/cshimages/ttcontent_2.png,
EXT:context_help/cshimages/ttcontent_3.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id=".image_descr" xml:space="preserve" approved="yes">
<source>The Page Module is used to manage Content Elements arranged in columns and languages.
A Content Element has an editing form with many options. The "Type" determines which options are visible.
In the Frontend, a Content Element like the above could look like this.</source>
<target state="translated">Il modulo Pagina è usato per gestire gli elementi di contenuto disposti in colonne e lingue.
Un elemento di contenuto ha un modulo per la modifica con varie opzioni. Il "Tipo" definisce quali opzioni saranno visibili.
Nel fronted un elemento di contenuto puo' apparire simile a quello sopra.</target></trans-unit>
<trans-unit id="CType.description" xml:space="preserve" approved="yes">
<source>Select the kind of Page Content this element represents. New options will appear when you save the record.</source>
<target state="translated">Selezionare il tipo di Page Content che l'elemento rappresenta. Nuove opzioni appariranno qando il record viene salvato.</target></trans-unit>
<trans-unit id="CType.details" xml:space="preserve">
<source>The 'Type' of content you select determines which options are available in the editing form so be sure to save the record before making other changes.
This is a description of the various types:
&lt;strong&gt;Header&lt;/strong&gt;
This type allows you to insert a standard Content Element header and nothing more.
Almost all the other types described below also include the Header and its options. The Header type provides a way to insert a header without any other content.
&lt;strong&gt;Text&lt;/strong&gt;
The Text type allows you to insert regular page content. It is generally used for text only content.
&lt;strong&gt;Text &amp; Images&lt;/strong&gt;
This is the same as the Text type (regular page content) but with the option of attaching images.
&lt;strong&gt;Image&lt;/strong&gt;
The Image type allows you to insert image only page content.
&lt;strong&gt;Bullet List&lt;/strong&gt;
Lets you create a bullet list. Each line in the text field will appear as a single bullet.
&lt;strong&gt;Table&lt;/strong&gt;
Lets you create &lt;em&gt;simple&lt;/em&gt; tables. Each line represents a row in the table and vertical bars ('|') separate each column. A popup wizard is also available.
&lt;strong&gt;File Links&lt;/strong&gt;
Allows you to present a list of files for download. Thumbnails can be attached to the list and you can also display the file size.
&lt;strong&gt;Form&lt;/strong&gt;
Lets you create mail forms using a special syntax or a popup wizard.
&lt;strong&gt;Search&lt;/strong&gt;
This inserts a search box and also shows the search results when a search is performed on the page.
&lt;strong&gt;Login&lt;/strong&gt;
Displays a login box for website users. This is only useful if you have already created website users and usergroups.
&lt;strong&gt;Menu/Sitemap&lt;/strong&gt;
Offers a selection of menus and a sitemap you can insert on a page.
&lt;strong&gt;Insert records&lt;/strong&gt;
This acts as placeholder for other records. With this Content Element, you can resuse multiple content elements from other pages.
&lt;strong&gt;Insert plugin&lt;/strong&gt;
This will allows you to insert news, forums, guestbooks, lists of addresses, and other functionality. Plugins are typically provided by TYPO3 extensions. The available fields and required configuration depend on the extension.
&lt;strong&gt;Divider&lt;/strong&gt;
This inserts a simple horizontal rule on a page.
&lt;strong&gt;HTML&lt;/strong&gt;
This is plain HTML content. Anything added in the HTML Code of this Content Element will be displayed directly on the page without any preprocessing.</source>
<target></target></trans-unit>
<trans-unit id="_CType.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:colPos,
tt_content:sys_language_uid,
About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</source>
<target state="translated">tt_content:colPos,
tt_content:sys_language_uid,
About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</target><note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
<note>A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_CType.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/ttcontent_4.png</source>
<target state="translated">EXT:context_help/cshimages/ttcontent_4.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
come immagine potrebbe essere mantenuta</note></trans-unit>
<trans-unit id="hidden.description" xml:space="preserve" approved="yes">
<source>Check this box if you wish to disable the Content Element and keep it from being displayed on the website.</source>
<target state="translated">Seleziona questa casella se desideri disabilitate l'elemento di contenuto ed escluderlo dalla visualizzazione nel sito web.</target></trans-unit>
<trans-unit id="_hidden.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:starttime,
tt_content:endtime,
tt_content:fe_group,
tt_content:colPos,
tt_content:sys_language_uid</source>
<target state="translated">tt_content:starttime,
tt_content:endtime,
tt_content:fe_group,
tt_content:colPos,
tt_content:sys_language_uid</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="starttime.description" xml:space="preserve" approved="yes">
<source>Enter the date when the Content Element should be published and displayed on the website.</source>
<target state="translated">Inserire la data a partire dalla quale il contenuto sarà pubblicato e quindi visibile nel sito web.</target></trans-unit>
<trans-unit id="_starttime.seeAlso" xml:space="preserve" approved="yes">
<source>pages:starttime,
tt_content:endtime,
tt_content:hidden,
tt_content:fe_group</source>
<target state="translated">pages:starttime,
tt_content:endtime,
tt_content:hidden,
tt_content:fe_group</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="endtime.description" xml:space="preserve" approved="yes">
<source>Enter the date when the Content Element should expire and disappear from the website.</source>
<target state="translated">Inserire la data a partire dalla quale il contenuto scadrà e quindi sparirà dal sito web, non essendo più visibile.</target></trans-unit>
<trans-unit id="_endtime.seeAlso" xml:space="preserve" approved="yes">
<source>pages:endtime,
tt_content:starttime,
tt_content:hidden,
tt_content:fe_group</source>
<target state="translated">pages:endtime,
tt_content:starttime,
tt_content:hidden,
tt_content:fe_group</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="fe_group.description" xml:space="preserve">
<source>If Usergroup Access Rights are set to a usergroup name, only website users who are logged in and members of the selected usergroup will be able to view the Content Element. The special option 'Hide at Login' means the Content Element will &lt;em&gt;not&lt;/em&gt; be visible for any website users that are logged in. Likewise "Show at Any Login" will make the Content Element visible for any logged in website user.</source>
<target></target></trans-unit>
<trans-unit id="fe_group.details" xml:space="preserve">
<source>The 'Hide at Login' option is is useful if you want to present information like "How to Login" that becomes irrelevant when a website user is actually logged in.</source>
<target></target></trans-unit>
<trans-unit id="_fe_group.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:hidden,
tt_content:starttime,
tt_content:endtime,
pages:fe_group,
fe_users,
fe_groups</source>
<target state="translated">tt_content:hidden,
tt_content:starttime,
tt_content:endtime,
pages:fe_group,
fe_users,
fe_groups</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="sys_language_uid.description" xml:space="preserve">
<source>Select the system language of this Content Element. &lt;strong&gt;Notice:&lt;/strong&gt; This will affect the Content Element visibility by limiting it to a certain language.</source>
<target></target></trans-unit>
<trans-unit id="sys_language_uid.details" xml:space="preserve">
<source>This allows you to assign a specific language to the Content Element. If you select anything but the default value, the element will &lt;em&gt;not&lt;/em&gt; be visible unless the language assigned is also configured by the TypoScript template.
The available system languages are created by the administrator.</source>
<target></target></trans-unit>
<trans-unit id="_sys_language_uid.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:colPos,
sys_language,
Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
_MOD_web_layout:language_list</source>
<target state="translated">tt_content:colPos,
sys_language,
Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
_MOD_web_layout:language_list</target><note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
<note>A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="layout.description" xml:space="preserve" approved="yes">
<source>Select a Layout.</source>
<target state="translated">Seleziona un Layout.</target></trans-unit>
<trans-unit id="layout.details" xml:space="preserve" approved="yes">
<source>This option does not work by default for all Content Elements but your website may display Content Elements differently depending on the layout.
The File Links Content Element does make use of the Layout field by default:
"Normal" will provide a list of file links with no thumbnail.
"Layout 1" adds a file icon to the left of the link
"Layout 2" adds a thumbnail for image files and an icon for other files. A black border is wrapped around the icon.
"Layout 3" is similar to Layout 2, but without the black border.</source>
<target state="translated">Questa opzione non viene supportata come impostazione predefinita per tutti i Content Elements, in questo caso i Content Elements saranno visualizzati utilizzando il layout base del tuo sito web.
I File Links ai Content Elements non utilizzeranno il campo Layout di defautl:
"Normal" la lista dei file sarà mostrata come collegamenti senza anteprime o icone.
"Layout 1" un'icona sarà aggiunta alla sinistra del collegamento
"Layout 2" un'anteprima sarà mostrata per i file di tipo immagine e un'icona per i file di altro tipo. Le icone e le anteprime saranno circondate da un bordo nero.
"Layout 3" come il Layout 2, ma senza bordo nero.</target></trans-unit>
<trans-unit id="colPos.description" xml:space="preserve">
<source>Select the column position of this element. &lt;strong&gt;Notice:&lt;/strong&gt; This may affect whether the Content Element is visible depending on your website template.</source>
<target></target></trans-unit>
<trans-unit id="colPos.details" xml:space="preserve">
<source>Many websites only use one column of content. Some templates, however, let you put content in multiple columns using the Column option.
&lt;strong&gt;Notice:&lt;/strong&gt; Selecting a column other than "Normal" may cause the Content Element to disappear if the website template does not use that column. If your Content Element mysteriously disappears make sure the Column and Language selectors are set correctly.</source>
<target></target></trans-unit>
<trans-unit id="_colPos.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:sys_language_uid,
_MOD_web_layout:columns_multi,
_MOD_web_layout:columns_single</source>
<target state="translated">tt_content:sys_language_uid,
_MOD_web_layout:columns_multi,
_MOD_web_layout:columns_single</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="date.description" xml:space="preserve">
<source>Enter a date to be displayed above the header.</source>
<target></target></trans-unit>
<trans-unit id="header.description" xml:space="preserve" approved="yes">
<source>Enter header text for the Content Element.</source>
<target state="translated">Inserisci il testo per l'intestazione dell'elemento di contenuto.</target></trans-unit>
<trans-unit id="header.details" xml:space="preserve">
<source>Almost all Content Elements will display this header above the content. If you don't want the header displayed, set the header Layout to "Hidden". You can also choose not to enter any content in this field.
Some content element types do not display the header by default. In those cases the Header field is typically labeled "Name" instead. One example is the HTML Content Element.</source>
<target></target></trans-unit>
<trans-unit id="_header.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header_position,
tt_content:header_link,
tt_content:header_layout,
tt_content:date,</source>
<target state="translated">tt_content:header_position,
tt_content:header_link,
tt_content:header_layout,
tt_content:date,</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_header.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/ttcontent_6.png</source>
<target state="translated">EXT:context_help/cshimages/ttcontent_6.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="header_position.description" xml:space="preserve" approved="yes">
<source>Aligns the header to the left, center, or right.</source>
<target state="translated">Allineamento dell'intestazione (sinistra, centrata, destra)</target></trans-unit>
<trans-unit id="_header_position.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header</source>
<target state="translated">tt_content:header</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="header_link.description" xml:space="preserve">
<source>Creates a link from the header to a Page ID, email address, or URL.</source>
<target></target></trans-unit>
<trans-unit id="header_link.syntax" xml:space="preserve">
<source>If you insert a Page ID (ex. 51), the link will point to the page with id=51 &lt;em&gt;inside&lt;/em&gt; TYPO3.
If you insert an email address (ex. name@my-domain.test), the link will point to that email address.
If you insert an URL or domain, (ex. www.typo3.org or http://www.my-domain.org), the link will point to that website.</source>
<target></target></trans-unit>
<trans-unit id="_header_link.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header</source>
<target state="translated">tt_content:header</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="header_layout.description" xml:space="preserve" approved="yes">
<source>Select a visual design for the header.</source>
<target state="translated">Seleziona il design visuale per l'intestazione (header).</target></trans-unit>
<trans-unit id="header_layout.details" xml:space="preserve" approved="yes">
<source>If you select "Default" the standard design (which is one of the layouts 1-5) will be used.
Alternatively you can select from Layout 1 through 5 which are configured in the website template with individual visual designs.
If you select "Hidden" the header will simply not appear. This is useful when you don't need a header to display on the website but still want to identify the Content Element in the Backend.</source>
<target state="translated">Se selezioni "Predefinito" (Default) sarà usato il design standard (che è uno dei layout da 1 a 5).
In alternativa puoi fare una scelta da Layout1 a Layout5; questi elementi sono configurati nel template per il sito web come design visuali individuali.
Se selezioni "Nascondi" (Hidden) l'intestazione (header) non sarà visualizzata. Questo è utile quando non hai bisogno di visualizzare una intestazione nel sito ma vuoi identificare il contenuto nel Backend.</target></trans-unit>
<trans-unit id="_header_layout.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header</source>
<target state="translated">tt_content:header</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="subheader.description" xml:space="preserve" approved="yes">
<source>Enter a subheader to be displayed below the main header. If the Content Element is a "Form" this field is instead used as the Recipient Email.</source>
<target state="translated">Inserire una sottotitolo che sarà visualizzato sotto l'intestazione principale. Se il contenuto è di tipo "Form" questo campo sarà utilizzato come Email per l'indirizzo di destinazione.</target></trans-unit>
<trans-unit id="subheader.details" xml:space="preserve">
<source>A subheader is displayed only with "Header" Content Elements and with "Form" Content Elements (as the Recipient Email).</source>
<target></target></trans-unit>
<trans-unit id="_subheader.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header
tt_content:bodytext</source>
<target state="translated">tt_content:header
tt_content:bodytext</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="bodytext.description" xml:space="preserve" approved="yes">
<source>Enter the main text.</source>
<target state="translated">Inserisci il testo principale.</target></trans-unit>
<trans-unit id="bodytext.details" xml:space="preserve">
<source>The main text of the Content Element is entered here and can be formatted with HTML or a Rich Text Editor.
The field is reused in other Content Element types so changing the type will cause any text to be reused in that new Content Element type.
When you're using this field with the "Text" and "Text &amp; Images" types, the content is normal body text. Each linebreak signifies a new paragraph, you can use the special TYPO3 tag, &amp;lt;LINK&amp;gt;, for making links. You can use many HTML tags but there are limitations depending on your website configuration.
A Rich Text Editor is commonly used to add a visual editing interface for 'Text' and 'Text &amp; Images' Content Elements.
&lt;b&gt;Bullet Lists:&lt;/b&gt;
If the type is "Bullet List" each line in this field is a bullet item.
&lt;b&gt;Tables:&lt;/b&gt;
If the type is "Table" each line represents a table row. Within each line, columns are divided by a vertical bar ('|'). A table row with 3 columns could look like "This is column 1 | Column 2 here | Third column!". The table wizard can also be used for creating tables and is much easier than hand coding them.
&lt;b&gt;Parameters:&lt;/b&gt;
Types like "Form" and "Multimedia" use this field for parameters than can be passed to the Content Element. The "HTML" type expects raw HTML which is simply displayed on the website without any processing.
&lt;b&gt;Making a mail form:&lt;/b&gt;
When you have selected the "Form" Content Element you can enter form field and other options. This is a brief example:
Your name: | *name=input,40 | [Enter name!]
Your email: | *email=input,40
Your address: | address=textarea,40,10
Your haircolor: |hair=radio|Blue=blue, Red=red
|formtype_mail = submit | Send Form
|subject=hidden| Enter a subject here!
|html_enabled=hidden | 1
The first two lines makes input fields for name and email. Both are marked as "required" and are designated by the *, and the name field has a default value of "[Enter name!]".
The third line is a text box and the fourth makes radio buttons to select a hair color.
After the input fields, there are three important lines in the end. The first makes a submit button with the label "Send Form", the second line is the subject of the email the receiver gets, and the third line formats the email using HTML.
Like the table wizard, it is easier to use the form wizard rather than hand coding the forms.
&lt;b&gt;Note:&lt;/b&gt; For a form to work you must add an email address for the Recipient Email in its field.</source>
<target></target></trans-unit>
<trans-unit id="_bodytext.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:CType,
tt_content:subheader,
xMOD_csh_corebe:wizard_forms_wiz,
xMOD_csh_corebe:wizard_table_wiz</source>
<target state="translated">tt_content:CType,
tt_content:subheader,
xMOD_csh_corebe:wizard_forms_wiz,
xMOD_csh_corebe:wizard_table_wiz</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="image.description" xml:space="preserve" approved="yes">
<source>Insert one or more images.</source>
<target state="translated">Inserire una o più immagini.</target></trans-unit>
<trans-unit id="image.details" xml:space="preserve">
<source>You can attach multiple images to the Content Element.
Depending on the configuration of TYPO3, you can attach images in many formats without worrying about size and compression. TYPO3's graphics processing handles these details for you.
When you use the "Text &amp; Images" type, it's important to select a proper position for images. For this purpose, use the Position and Aligment selector. See link to "Page Content / Position" below.
You can also display images in multiple columns and even enable an option that opens full size images when thumbnails are clicked.</source>
<target></target></trans-unit>
<trans-unit id="_image.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:imagewidth,
tt_content:imageheight,
tt_content:imageorient,
tt_content:imageborder,
tt_content:image_noRows,
tt_content:image_link,
tt_content:image_zoom,
tt_content:imagecols,
tt_content:imagecaption,
tt_content:image_effects,
tt_content:image_frames,
tt_content:image_compression,
Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</source>
<target state="translated">tt_content:imagewidth,
tt_content:imageheight,
tt_content:imageorient,
tt_content:imageborder,
tt_content:image_noRows,
tt_content:image_link,
tt_content:image_zoom,
tt_content:imagecols,
tt_content:imagecaption,
tt_content:image_effects,
tt_content:image_frames,
tt_content:image_compression,
Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</target><note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
<note>A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_image.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/ttcontent_5.png</source>
<target state="translated">EXT:context_help/cshimages/ttcontent_5.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="image.image_descr" xml:space="preserve">
<source>This shows all the options related to inserting images in Content Elements. Depending on user permissions, you may not be able to use all of them.</source>
<target></target></trans-unit>
<trans-unit id="imagewidth.description" xml:space="preserve" approved="yes">
<source>Enter the width (in pixels) for displaying the image in the Frontend of your website.</source>
<target state="translated">Inserire la larghezza (in pixel) per visualizzare l'immagine nel Frontend del sito web.</target></trans-unit>
<trans-unit id="imagewidth.details" xml:space="preserve">
<source>The TypoScript template is normally configured with maximum image width so you shouldn't need to specify a width. In unique cases, this provides additional flexibility though.</source>
<target></target></trans-unit>
<trans-unit id="_imagewidth.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:imageheight,
tt_content:image</source>
<target state="translated">tt_content:imageheight,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="imageheight.description" xml:space="preserve" approved="yes">
<source>Enter the height (in pixels) for displaying the images in the Frontend of your website.</source>
<target state="translated">Inserire l'altezza (in pixel) per visualizzare le immagini in Frontend del sito web.</target></trans-unit>
<trans-unit id="_imageheight.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:imagewidth,
tt_content:image</source>
<target state="translated">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="imageorient.description" xml:space="preserve">
<source>Select the position and alignment of the images relative to the body text.</source>
<target></target></trans-unit>
<trans-unit id="imageorient.details" xml:space="preserve">
<source>The positions above and below the body text are pretty straight forward.
The options for "In text" mean that images are displayed with text wrapped around them. When you select this option the template will probably force the images into smaller dimensions to accomodate the width of the template and the width of the text. The bodytext will float &lt;em&gt;under&lt;/em&gt; the image block when it reaches the end of the image block. In other words, the body text &lt;em&gt;wraps around&lt;/em&gt; the image block. If you select "In text" below the "No wrap" divider, the body text will not float under the image block, but simply continue in its column.
Apart from the visual difference there is a technical aspect as well. If you choose to allow the content to wrap the image block you will experience a strange phenomenon when you do not have enough bodytext to make it float around the image: subsequent content elements on the page will appear to be layered on top of the image block. However it's easily solved by changing the "In text" position to the equal value but below the "No wrap" divider.</source>
<target></target></trans-unit>
<trans-unit id="imageborder.description" xml:space="preserve" approved="yes">
<source>Displays a colored border around the images.</source>
<target state="translated">Visualizza un bordo colorato intorno all'immagine.</target></trans-unit>
<trans-unit id="_imageborder.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:imagecols,
tt_content:image</source>
<target state="needs-translation">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
87%</note></trans-unit>
<trans-unit id="image_noRows.description" xml:space="preserve">
<source>Disables tablerows in the image block.</source>
<target></target></trans-unit>
<trans-unit id="image_noRows.details" xml:space="preserve">
<source>To illustrate, imagine you have 2 or more columns &lt;em&gt;and&lt;/em&gt; rows of images. If one image in the upper row is taller than the second this will generate empty space beneath the second image. This is due to the normal flow in which the images are placed in table cells.
If you enable the No Rows option, the table will place the images in a column into a single table cell which make the distance between them vertically identical throughout. This may provide a better look if the alternative is unacceptable.</source>
<target></target></trans-unit>
<trans-unit id="_image_noRows.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:imagecols,
tt_content:image</source>
<target state="needs-translation">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
87%</note></trans-unit>
<trans-unit id="image_link.description" xml:space="preserve" approved="yes">
<source>Enter a link for the image. For multiple images, separate the links with commas.</source>
<target state="translated">Inserire un link per l'immagine. Per immagini multiple, bisogna separare i link con le virgole.</target></trans-unit>
<trans-unit id="image_link.details" xml:space="preserve" approved="yes">
<source>By default all images share the same link. Your TypoScript template may be configured to allow a separate link for each image. If this is the case, you simply separate the links with a comma.
See Page Content&gt;Link below for details on syntax.</source>
<target state="translated">Di base tutte le immagini condividono lo stesso link. Il TypoScript template dovrebbe essere configurato per consentire un link separato per ogni immagine. Se questo è il caso, si devono semplicemente separare i link con una virgola.
Per avere dettagli sulla sintassi guardare in basso Contenuto di Pagina &gt; Link.</target></trans-unit>
<trans-unit id="_image_link.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:header_link,
tt_content:image_zoom,
tt_content:image</source>
<target state="translated">tt_content:header_link,
tt_content:image_zoom,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="image_zoom.description" xml:space="preserve" approved="yes">
<source>When enabled, clicking an image will open a larger version in a popup window.</source>
<target state="translated">Quando è abilitato, cliccando su una immagine si aprirà una finestra di popup con l'immagine in formato grande.</target></trans-unit>
<trans-unit id="image_zoom.details" xml:space="preserve" approved="yes">
<source>This option overrides the value in the Links field.</source>
<target state="translated">Questa opzione sovrascrive il valore del campo Link.</target></trans-unit>
<trans-unit id="_image_zoom.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:image_link,
tt_content:image</source>
<target state="needs-translation">tt_content:imageheight,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
87%</note></trans-unit>
<trans-unit id="image_effects.description" xml:space="preserve">
<source>Select special image processing effects, such as rotation and color adjustments.</source>
<target></target></trans-unit>
<trans-unit id="_image_effects.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:image_compression,
tt_content:image_frames,
tt_content:image</source>
<target state="translated">tt_content:image_compression,
tt_content:image_frames,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="image_frames.description" xml:space="preserve">
<source>Select special image framing options.</source>
<target></target></trans-unit>
<trans-unit id="_image_frames.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:image_compression,
tt_content:image_effects,
tt_content:image</source>
<target state="translated">tt_content:image_compression,
tt_content:image_effects,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="image_compression.description" xml:space="preserve" approved="yes">
<source>Select image quality and image type options.</source>
<target state="translated">Seleziona la qualità e il tipo di immagine.</target></trans-unit>
<trans-unit id="_image_compression.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:image_frames,
tt_content:image_effects,
tt_content:image</source>
<target state="translated">tt_content:image_frames,
tt_content:image_effects,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="imagecols.description" xml:space="preserve" approved="yes">
<source>Set the number of columns when the images are displayed in the Frontend of the website.</source>
<target state="translated">Impostare il numero di colonne quando le immagini vengono visualizzate nel Frontend del sito web.</target></trans-unit>
<trans-unit id="_imagecols.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:image_noRows,
tt_content:image</source>
<target state="needs-translation">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
82%</note></trans-unit>
<trans-unit id="imagecaption.description" xml:space="preserve" approved="yes">
<source>Enter captions for the images. For multiple images, enter one caption per line.</source>
<target state="translated">inserire la didascalia per le immagini. Per immagini multiple, inserire una didascialia per linea</target></trans-unit>
<trans-unit id="imagecaption.details" xml:space="preserve">
<source>By default, the caption is positioned below the images. However, your TypoScript template may be configured to allow individual image captions by setting "styles.content.imgtext.captionSplit=1" in your template constants.
In this case, each line in this field will be the image caption of the corresponding image in the list.
The caption text field is also used by the Content Element type "File Links" where each line represents a description of a file in the list.</source>
<target></target></trans-unit>
<trans-unit id="_imagecaption.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:imagecaption_position,
tt_content:image</source>
<target state="needs-translation">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
85%
82%
100%
100%</note></trans-unit>
<trans-unit id="imagecaption_position.description" xml:space="preserve" approved="no">
<source>Aligns the image captions to the left, center, or right.</source>
<target state="needs-translation">Allineamento dell'intestazione (sinistra, centrata, destra)</target><note>78%</note></trans-unit>
<trans-unit id="_imagecaption_position.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:imagecaption,
tt_content:image</source>
<target state="needs-translation">tt_content:imagewidth,
tt_content:image</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
85%</note></trans-unit>
<trans-unit id="cols.description" xml:space="preserve">
<source>Select a fixed number of table columns</source>
<target></target></trans-unit>
<trans-unit id="pages.description" xml:space="preserve">
<source>Select a target page or multiple target pages.</source>
<target></target></trans-unit>
<trans-unit id="pages.details" xml:space="preserve">
<source>This field is used by many of the Content Element types to create a relation to either a single target page or multiple target pages. If no target page is specified, the current page will generally be used.
Using the "Search" Content Element, the target page is where search results will appear. You must make sure that this page has a similar "Search" Content Element to display the results.
The "Login" Content Element (not to be confused with the Login plugin available when the felogin extension is installed) also uses this field to redirect the login to a certain page. That page does not need to contain a "Login" Content Element in order to perform the authentication since any TYPO3 page can handle a login request.
If you specify a second page in this list, the ID will be passed to the login system as the page inside TYPO3 where website users are found. You should use this only if your template is not already configured to pass this value on.
In order for the login procedure to work you must make sure that you have created website users and website usergroups, have specified where these website users can be found (typically a SysFolder), a page ID in the page list, and ensured that cookies are enabled for the site.
The "Menu/Sitemap" Content Elements also use this field. In this case the page will determine the starting point for the menu or the actual pages shown in the menu. This behavior depends on the menu type you have selected.
Finally the "Form" element uses this field as the target page to which the form is submitted. A common use is the "Thank you" page after the form is completed.</source>
<target></target></trans-unit>
<trans-unit id="_pages.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:CType,
tt_content:recursive</source>
<target state="translated">tt_content:CType,
tt_content:recursive</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="recursive.description" xml:space="preserve">
<source>The number of subpage levels that should also be included for each page in the list.</source>
<target></target></trans-unit>
<trans-unit id="recursive.details" xml:space="preserve">
<source>This feature depends on the TypoScript template configuration and Content Element type. If enabled, each page listed in the "Pages" field will also have its subpages included to the specified depth.
&lt;strong&gt;Warning:&lt;/strong&gt; If there are many subpages, be aware that this option may return a large number of results</source>
<target></target></trans-unit>
<trans-unit id="_recursive.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:pages</source>
<target state="needs-translation">tt_content:header</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
76%</note></trans-unit>
<trans-unit id="menu_type.description" xml:space="preserve">
<source>Select the type of menu you wish to create.</source>
<target></target></trans-unit>
<trans-unit id="menu_type.details" xml:space="preserve">
<source>This is a short description of each type:
&lt;strong&gt;Menu of selected pages&lt;/strong&gt;
This will create a menu with links to the pages in the Selected Pages list.
&lt;strong&gt;Menu of subpages of selected pages&lt;/strong&gt;
This will create in a menu with links to the subpages of the pages in the Selected Pages list. If you do not specify any pages, the subpages to the current page will be used.
&lt;strong&gt;Menu of subpages of selected pages (with abstract)&lt;/strong&gt;
Like the previous option, but also displays the content of the Abstract field (or the Description field) for each page in the menu. The Abstract field is given priority over the Description field if both are complete.
&lt;strong&gt;Menu of subpages of selected pages + sections&lt;/strong&gt;
Like the previous option, but includes links to all Content Elements on the page that are marked to Show In Section Menus.
&lt;strong&gt;Sitemap&lt;/strong&gt;
Generates a classic tree sitemap. Notice that the sitemap will begin from the current page unless you select another page instead.
&lt;strong&gt;Section index (page content marked for section menus)&lt;/strong&gt;
This makes a menu of Content Elements on the selected pages for all Content Elements marked to Show In Section Menu. This is a great way to make an index at the top of the page.
If you don't want certain Content Elements to appear in the list, just uncheck the Show in Section Menus checkbox for those elements.
&lt;strong&gt;Recently updated pages&lt;/strong&gt;
This displays the 10 most recently updated pages.
&lt;strong&gt;Notice:&lt;/strong&gt; If you update a page and the updated page is not included in this list, clearing the Page Cache will resolve the issue.
&lt;strong&gt;Related pages (based on keywords)&lt;/strong&gt;
Displays other related pages based on the keywords of the selected pages matched against the keywords of other pages.</source>
<target></target></trans-unit>
<trans-unit id="_menu_type.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:pages,
tt_content:sectionIndex</source>
<target state="translated">tt_content:pages,
tt_content:sectionIndex</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="list_type.description" xml:space="preserve" approved="yes">
<source>Select a plugin to insert.</source>
<target state="translated">Seleziona un plugin da inserire.</target></trans-unit>
<trans-unit id="list_type.details" xml:space="preserve" approved="yes">
<source>The list of plugins you can insert on a page. The available plugins depend on which extensions are installed.</source>
<target state="translated">La lista dei plugins che puoi inserire in una pagina. I plugin disponibili dipendono dalle estensioni installate.</target></trans-unit>
<trans-unit id="_list_type.seeAlso" xml:space="preserve" approved="yes">
<source>_MOD_tools_em</source>
<target state="translated">_MOD_tools_em</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="_list_type.image" xml:space="preserve" approved="yes">
<source>EXT:context_help/cshimages/ttcontent_7.png</source>
<target state="translated">EXT:context_help/cshimages/ttcontent_7.png</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
come immagine potrebbe essere mantenuta
97%</note></trans-unit>
<trans-unit id="select_key.description" xml:space="preserve">
<source>Enter a special string to define the Content Element's operation or leave it blank for the default mode. Possible values depend on the Content Element being used.</source>
<target></target></trans-unit>
<trans-unit id="select_key.details" xml:space="preserve">
<source>Whether or not the content of this field is used and how it's intepreted depends on the Content Element and/or plugin being used. It is considered obsolete for plugins today, but is used in some Content Elements such as File Links.</source>
<target></target></trans-unit>
<trans-unit id="_select_key.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:list_type</source>
<target state="translated">tt_content:list_type</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note></trans-unit>
<trans-unit id="table_bgColor.description" xml:space="preserve" approved="yes">
<source>Select the table background color.</source>
<target state="translated">Seleziona il colore di sfondo della tabella.</target></trans-unit>
<trans-unit id="table_border.description" xml:space="preserve" approved="yes">
<source>Select the table border thickness.</source>
<target state="translated">Seleziona lo spessore del bordo della tabella.</target></trans-unit>
<trans-unit id="table_cellspacing.description" xml:space="preserve" approved="yes">
<source>Select the table cell spacing.</source>
<target state="translated">Selezionare la spaziatura delle celle della tabella. </target></trans-unit>
<trans-unit id="table_cellspacing.details" xml:space="preserve">
<source>Cell spacing is the distance between table cells in rows and columns. The distance is equally applied in all directions, top, bottom, left, and right.</source>
<target></target></trans-unit>
<trans-unit id="table_cellpadding.description" xml:space="preserve" approved="no">
<source>Select the table cellpadding.</source>
<target state="needs-translation">Selezionare la spaziatura delle celle della tabella. </target><note>86%
100%
100%</note></trans-unit>
<trans-unit id="table_cellpadding.details" xml:space="preserve">
<source>Cell padding is the 'internal' margin of a table cell. The distance is equally applied in all directions, top, bottom, left, and right.</source>
<target></target></trans-unit>
<trans-unit id="media.description" xml:space="preserve">
<source>Files can be added to the list here.</source>
<target></target></trans-unit>
<trans-unit id="multimedia.description" xml:space="preserve">
<source>Insert a multimedia element here (ex. Flash movie)</source>
<target></target></trans-unit>
<trans-unit id="filelink_size.description" xml:space="preserve">
<source>Enable the display of file sizes.</source>
<target></target></trans-unit>
<trans-unit id="records.description" xml:space="preserve">
<source>Insert records to be displayed on this page.</source>
<target></target></trans-unit>
<trans-unit id="spaceBefore.description" xml:space="preserve">
<source>Top Margin (in pixels) inserts whitespace &lt;em&gt;before&lt;/em&gt; this Content Element.</source>
<target></target></trans-unit>
<trans-unit id="_spaceBefore.seeAlso" xml:space="preserve">
<source>tt_content:spaceAfter,
tt_content:section_frame</source>
<target></target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="spaceAfter.description" xml:space="preserve">
<source>Bottom Margin (in pixels) inserts whitespace &lt;em&gt;after&lt;/em&gt; this Content Element.</source>
<target></target></trans-unit>
<trans-unit id="_spaceAfter.seeAlso" xml:space="preserve">
<source>tt_content:spaceBefore,
tt_content:section_frame</source>
<target></target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="section_frame.description" xml:space="preserve">
<source>Select indention or framing options for the Content Element.</source>
<target></target></trans-unit>
<trans-unit id="_section_frame.seeAlso" xml:space="preserve">
<source>tt_content:spaceAfter,
tt_content:spaceBefore</source>
<target></target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="sectionIndex.description" xml:space="preserve">
<source>If set, the Content Element will appear in Section Menus.</source>
<target></target></trans-unit>
<trans-unit id="sectionIndex.details" xml:space="preserve">
<source>See more details about Section Menus by clicking below.</source>
<target></target></trans-unit>
<trans-unit id="_sectionIndex.seeAlso" xml:space="preserve" approved="no">
<source>tt_content:menu_type</source>
<target state="needs-translation">tt_content:list_type</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
80%
100%
100%</note></trans-unit>
<trans-unit id="linkToTop.description" xml:space="preserve">
<source>If checked, a small "To Top" link will be added after the Content Element, linking back to the top of the page.</source>
<target></target></trans-unit>
<trans-unit id="rte_enabled.description" xml:space="preserve">
<source>If checked, the Rich Text Editor will be disabled for the "Text" and "Text &amp; Image" types (&lt;em&gt;in this Content Element only&lt;/em&gt;).</source>
<target></target></trans-unit>
<trans-unit id="_rte_enabled.seeAlso" xml:space="preserve">
<source>tt_content:bodytext</source>
<target></target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="pi_flexform.description" xml:space="preserve">
<source>Plugin Configuration</source>
<target></target></trans-unit>
<trans-unit id="pi_flexform.details" xml:space="preserve">
<source>Some plugins may provide configuration options, but the actual options vary based on the plugin. Behind the scenes, these are based on FlexForms and stored as XML.</source>
<target></target></trans-unit>
<trans-unit id="_pi_flexform.seeAlso" xml:space="preserve" approved="yes">
<source>tt_content:list_type</source>
<target state="translated">tt_content:list_type</target><note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
<note>This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.
100%</note></trans-unit>
</body>
</file>
</xliff>

View File

@@ -0,0 +1,205 @@
<?xml version="1.0" encoding="UTF-8"?>
<T3locallangExt>
<data type="array">
<languageKey index="it" type="array">
<label index=".description">Tutti i contenuti visibili nelle pagine web sono solitamente creati tramite i record "Page Content", che spesso viene definiti come "Elemento di Contenuto". Gli elementi di contenuto sono gestiti tramite il modulo "Page" che li organizza in colonne multiple e lingua.</label>
<label index=".details"/>
<label index="_.seeAlso">Principi di Page Content | http://typo3.org/documentation/document-library/doc_tut_quickstart/Page_content/,
_MOD_web_layout</label>
<label index="_.image">EXT:context_help/cshimages/ttcontent_1.png,
EXT:context_help/cshimages/ttcontent_2.png,
EXT:context_help/cshimages/ttcontent_3.png</label>
<label index=".image_descr">Il modulo Pagina è usato per gestire gli elementi di contenuto disposti in colonne e lingue.
Un elemento di contenuto ha un modulo per la modifica con varie opzioni. Il "Tipo" definisce quali opzioni saranno visibili.
Nel fronted un elemento di contenuto puo' apparire simile a quello sopra.</label>
<label index="CType.description">Selezionare il tipo di Page Content che l'elemento rappresenta. Nuove opzioni appariranno qando il record viene salvato.</label>
<label index="CType.details"/>
<label index="_CType.seeAlso">tt_content:colPos,
tt_content:sys_language_uid,
About Content Elements | http://typo3.org/documentation/document-library/doc_tut_quickstart/Content_element_type/</label>
<label index="_CType.image">EXT:context_help/cshimages/ttcontent_4.png</label>
<label index="hidden.description">Seleziona questa casella se desideri disabilitate l'elemento di contenuto ed escluderlo dalla visualizzazione nel sito web.</label>
<label index="_hidden.seeAlso">tt_content:starttime,
tt_content:endtime,
tt_content:fe_group,
tt_content:colPos,
tt_content:sys_language_uid</label>
<label index="starttime.description">Inserire la data a partire dalla quale il contenuto sarà pubblicato e quindi visibile nel sito web.</label>
<label index="_starttime.seeAlso">pages:starttime,
tt_content:endtime,
tt_content:hidden,
tt_content:fe_group</label>
<label index="endtime.description">Inserire la data a partire dalla quale il contenuto scadrà e quindi sparirà dal sito web, non essendo più visibile.</label>
<label index="_endtime.seeAlso">pages:endtime,
tt_content:starttime,
tt_content:hidden,
tt_content:fe_group</label>
<label index="fe_group.description"/>
<label index="fe_group.details"/>
<label index="_fe_group.seeAlso">tt_content:hidden,
tt_content:starttime,
tt_content:endtime,
pages:fe_group,
fe_users,
fe_groups</label>
<label index="sys_language_uid.description"/>
<label index="sys_language_uid.details"/>
<label index="_sys_language_uid.seeAlso">tt_content:colPos,
sys_language,
Localization concepts [Technical] | http://typo3.org/documentation/tips-tricks/multi-language-sites-in-typo3/,
_MOD_web_layout:language_list</label>
<label index="layout.description">Seleziona un Layout.</label>
<label index="layout.details">Questa opzione non viene supportata come impostazione predefinita per tutti i Content Elements, in questo caso i Content Elements saranno visualizzati utilizzando il layout base del tuo sito web.
I File Links ai Content Elements non utilizzeranno il campo Layout di defautl:
"Normal" la lista dei file sarà mostrata come collegamenti senza anteprime o icone.
"Layout 1" un'icona sarà aggiunta alla sinistra del collegamento
"Layout 2" un'anteprima sarà mostrata per i file di tipo immagine e un'icona per i file di altro tipo. Le icone e le anteprime saranno circondate da un bordo nero.
"Layout 3" come il Layout 2, ma senza bordo nero.</label>
<label index="colPos.description"/>
<label index="colPos.details"/>
<label index="_colPos.seeAlso">tt_content:sys_language_uid,
_MOD_web_layout:columns_multi,
_MOD_web_layout:columns_single</label>
<label index="date.description"/>
<label index="header.description">Inserisci il testo per l'intestazione dell'elemento di contenuto.</label>
<label index="header.details"/>
<label index="_header.seeAlso">tt_content:header_position,
tt_content:header_link,
tt_content:header_layout,
tt_content:date,</label>
<label index="_header.image">EXT:context_help/cshimages/ttcontent_6.png</label>
<label index="header_position.description">Allineamento dell'intestazione (sinistra, centrata, destra)</label>
<label index="_header_position.seeAlso">tt_content:header</label>
<label index="header_link.description"/>
<label index="header_link.syntax"/>
<label index="_header_link.seeAlso">tt_content:header</label>
<label index="header_layout.description">Seleziona il design visuale per l'intestazione (header).</label>
<label index="header_layout.details">Se selezioni "Predefinito" (Default) sarà usato il design standard (che è uno dei layout da 1 a 5).
In alternativa puoi fare una scelta da Layout1 a Layout5; questi elementi sono configurati nel template per il sito web come design visuali individuali.
Se selezioni "Nascondi" (Hidden) l'intestazione (header) non sarà visualizzata. Questo è utile quando non hai bisogno di visualizzare una intestazione nel sito ma vuoi identificare il contenuto nel Backend.</label>
<label index="_header_layout.seeAlso">tt_content:header</label>
<label index="subheader.description">Inserire una sottotitolo che sarà visualizzato sotto l'intestazione principale. Se il contenuto è di tipo "Form" questo campo sarà utilizzato come Email per l'indirizzo di destinazione.</label>
<label index="subheader.details"/>
<label index="_subheader.seeAlso">tt_content:header
tt_content:bodytext</label>
<label index="bodytext.description">Inserisci il testo principale.</label>
<label index="bodytext.details"/>
<label index="_bodytext.seeAlso">tt_content:CType,
tt_content:subheader,
xMOD_csh_corebe:wizard_forms_wiz,
xMOD_csh_corebe:wizard_table_wiz</label>
<label index="image.description">Inserire una o più immagini.</label>
<label index="image.details"/>
<label index="_image.seeAlso">tt_content:imagewidth,
tt_content:imageheight,
tt_content:imageorient,
tt_content:imageborder,
tt_content:image_noRows,
tt_content:image_link,
tt_content:image_zoom,
tt_content:imagecols,
tt_content:imagecaption,
tt_content:image_effects,
tt_content:image_frames,
tt_content:image_compression,
Using images ("Getting Started") | http://typo3.org/documentation/document-library/doc_tut_quickstart/Managing_files_in_TY/
Using images (Animation) | FILE:EXT:welcome/modsub/ani_10.gif</label>
<label index="_image.image">EXT:context_help/cshimages/ttcontent_5.png</label>
<label index="image.image_descr"/>
<label index="imagewidth.description">Inserire la larghezza (in pixel) per visualizzare l'immagine nel Frontend del sito web.</label>
<label index="imagewidth.details"/>
<label index="_imagewidth.seeAlso">tt_content:imageheight,
tt_content:image</label>
<label index="imageheight.description">Inserire l'altezza (in pixel) per visualizzare le immagini in Frontend del sito web.</label>
<label index="_imageheight.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="imageorient.description"/>
<label index="imageorient.details"/>
<label index="imageborder.description">Visualizza un bordo colorato intorno all'immagine.</label>
<label index="_imageborder.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="image_noRows.description"/>
<label index="image_noRows.details"/>
<label index="_image_noRows.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="image_link.description">Inserire un link per l'immagine. Per immagini multiple, bisogna separare i link con le virgole.</label>
<label index="image_link.details">Di base tutte le immagini condividono lo stesso link. Il TypoScript template dovrebbe essere configurato per consentire un link separato per ogni immagine. Se questo è il caso, si devono semplicemente separare i link con una virgola.
Per avere dettagli sulla sintassi guardare in basso Contenuto di Pagina &gt; Link.</label>
<label index="_image_link.seeAlso">tt_content:header_link,
tt_content:image_zoom,
tt_content:image</label>
<label index="image_zoom.description">Quando è abilitato, cliccando su una immagine si aprirà una finestra di popup con l'immagine in formato grande.</label>
<label index="image_zoom.details">Questa opzione sovrascrive il valore del campo Link.</label>
<label index="_image_zoom.seeAlso">tt_content:imageheight,
tt_content:image</label>
<label index="image_effects.description"/>
<label index="_image_effects.seeAlso">tt_content:image_compression,
tt_content:image_frames,
tt_content:image</label>
<label index="image_frames.description"/>
<label index="_image_frames.seeAlso">tt_content:image_compression,
tt_content:image_effects,
tt_content:image</label>
<label index="image_compression.description">Seleziona la qualità e il tipo di immagine.</label>
<label index="_image_compression.seeAlso">tt_content:image_frames,
tt_content:image_effects,
tt_content:image</label>
<label index="imagecols.description">Impostare il numero di colonne quando le immagini vengono visualizzate nel Frontend del sito web.</label>
<label index="_imagecols.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="imagecaption.description">inserire la didascalia per le immagini. Per immagini multiple, inserire una didascialia per linea</label>
<label index="imagecaption.details"/>
<label index="_imagecaption.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="imagecaption_position.description">Allineamento dell'intestazione (sinistra, centrata, destra)</label>
<label index="_imagecaption_position.seeAlso">tt_content:imagewidth,
tt_content:image</label>
<label index="cols.description"/>
<label index="pages.description"/>
<label index="pages.details"/>
<label index="_pages.seeAlso">tt_content:CType,
tt_content:recursive</label>
<label index="recursive.description"/>
<label index="recursive.details"/>
<label index="_recursive.seeAlso">tt_content:header</label>
<label index="menu_type.description"/>
<label index="menu_type.details"/>
<label index="_menu_type.seeAlso">tt_content:pages,
tt_content:sectionIndex</label>
<label index="list_type.description">Seleziona un plugin da inserire.</label>
<label index="list_type.details">La lista dei plugins che puoi inserire in una pagina. I plugin disponibili dipendono dalle estensioni installate.</label>
<label index="_list_type.seeAlso">_MOD_tools_em</label>
<label index="_list_type.image">EXT:context_help/cshimages/ttcontent_7.png</label>
<label index="select_key.description"/>
<label index="select_key.details"/>
<label index="_select_key.seeAlso">tt_content:list_type</label>
<label index="table_bgColor.description">Seleziona il colore di sfondo della tabella.</label>
<label index="table_border.description">Seleziona lo spessore del bordo della tabella.</label>
<label index="table_cellspacing.description">Selezionare la spaziatura delle celle della tabella. </label>
<label index="table_cellspacing.details"/>
<label index="table_cellpadding.description">Selezionare la spaziatura delle celle della tabella. </label>
<label index="table_cellpadding.details"/>
<label index="media.description"/>
<label index="multimedia.description"/>
<label index="filelink_size.description"/>
<label index="records.description"/>
<label index="spaceBefore.description"/>
<label index="_spaceBefore.seeAlso"/>
<label index="spaceAfter.description"/>
<label index="_spaceAfter.seeAlso"/>
<label index="section_frame.description"/>
<label index="_section_frame.seeAlso"/>
<label index="sectionIndex.description"/>
<label index="sectionIndex.details"/>
<label index="_sectionIndex.seeAlso">tt_content:list_type</label>
<label index="linkToTop.description"/>
<label index="rte_enabled.description"/>
<label index="_rte_enabled.seeAlso"/>
<label index="pi_flexform.description"/>
<label index="pi_flexform.details"/>
<label index="_pi_flexform.seeAlso">tt_content:list_type</label>
</languageKey>
</data>
</T3locallangExt>