1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
# translation of Publican Users' Guide to Italiano
#
# Luigi Votta <lewis41@fedoraproject.org>, 2010.
# Mario Santagiuliana <fedora at marionline.it>, 2012.
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2014-10-03 13:17+1000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2012-01-16 02:59-0500\n"
"Last-Translator: Mario Santagiuliana <fedora at marionline.it>\n"
"Language-Team: Italian <fedora-trans-it at redhat.com>\n"
"Language: it\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Zanata 3.6.2\n"
msgid "Adding code samples"
msgstr "Aggiungere codice"
msgid "If your book contains code samples, place them in a directory named <filename>extras/</filename> in your source language directory and use an <tag><xi:include></tag> to pull the code file into the XML structure of your document. <application>Publican</application> does not parse any files that it finds in the <filename>extras/</filename> directory as XML."
msgstr "Se il libro contiene pezzi di codice, salvare il file in una sotto-cartella denominata <filename>extras/</filename> nella cartella della lingua originale, ed usare un <sgmltag><xi:include></sgmltag> per caricare il file del codice nella struttura XML del documento. Ogni file contenuto nella cartella <filename>extras/</filename> non viene analizzato sintatticamente (parsed) come XML da <application>Publican</application>."
msgid "Certain characters are reserved in XML, in particular, <literal>&</literal> and <literal><</literal>. If you insert code samples directly into the XML of your document, you must escape these characters, either by marking them as <literal>CDATA</literal> or by replacing them with entities (&amp; and &lt; respectively).<footnote> <para> Refer to section 2.4 \"Character Data and Markup\" in the XML 1.0 standard, available from <uri xlink:href=\"http://www.w3.org/TR/2008/REC-xml-20081126/\" xmlns:xlink=\"http://www.w3.org/1999/xlink\">http://www.w3.org/TR/2008/REC-xml-20081126/</uri>. </para> </footnote> If you place these files in the <filename>extras/</filename> directory, you do not need to escape these characters. This approach saves time, reduces the chances of introducing errors into either the document XML or the code itself, and makes future maintenance of the document and the code easier."
msgstr "Alcuni caratteri sono riservati in XML, in particolare, <literal>&</literal> e <literal><</literal>. Se si inserisce un pezzo di codice direttamente in un file XML di un documento, occorre fare l'<emphasis>escaping</emphasis> di questi caratteri, rendendoli <literal>CDATA</literal> o sostituendoli con entità (&amp; e &lt; rispettivamente).<footnote><para>Fare riferimento alla sezione 2.4 \"Character Data and Markup\" dello standard XML 1.0, disponibile su <ulink url=\"http://www.w3.org/TR/2008/REC-xml-20081126/\" />.</para></footnote> Posizionando questi file nella cartella <filename>extras/</filename>, non occorre alcun escaping di questi caratteri. Questo approccio risparmia tempo, riduce la possibilità di introdurre errori nell'XML e nel codice; oltre a semplificare il mantenimento del documento e del codice."
msgid "To include a code sample from the <filename>extras/</filename> directory in your document, follow this procedure:"
msgstr "Per includere nel documento, un pezzo di codice contenuto nella cartella <filename>extras/</filename>, seguire questa procedura: "
msgid "Create the extras directory"
msgstr "Creare la cartella extras"
msgid "<prompt>$</prompt> <command>mkdir <filename>en-US/extras</filename></command>"
msgstr "<command>mkdir <filename>en-US/extras</filename></command>\n"
msgid "Copy the code file to the extras directory"
msgstr "Copiare il file del codice nella cartella extras"
msgid "<prompt>$</prompt> <command>cp <filename>~/samples/foo.c en-US/extras/.</filename></command>"
msgstr "<command>cp <filename>~/samples/foo.c en-US/extras/.</filename></command>\n"
msgid "<tag>xi:include</tag> the sample file in your xml file"
msgstr "Nel file XML, includere il file di codice in un tag <sgmltag>xi:include</sgmltag>"
msgid ""
"<programlisting>\n"
"<xi:include parse=\"text\" href=\"extras/foo.c\" xmlns:xi=\"http://www.w3.org/2001/XInclude\" />\n"
"</programlisting>"
msgstr ""
"<programlisting>\n"
"<xi:include parse=\"text\" href=\"extras/foo.c\" xmlns:xi=\"http://www.w3.org/2001/XInclude\" />\n"
"</programlisting>"
msgid "You can now edit <filename>en-US/extras/foo.c</filename> in your favorite editor without having to be concerned about how it will affect the XML."
msgstr "Ora si può modificare il file <filename>en-US/extras/foo.c</filename> nel proprio editor preferito, senza doversi preoccupare di eventuali effetti nell'XML."
msgid "The same approach works when you want to annotate your code with callouts. For example:"
msgstr "Lo stesso approccio funziona annotando il codice con callout. Per esempio:"
#, fuzzy
msgid ""
"<programlistingco>\n"
" <areaspec>\n"
" <area id=\"orbit-for-parameter\" coords='4 75'/>\n"
" <area id=\"orbit-for-magnitude\" coords='12 75'/>\n"
" </areaspec>\n"
" <programlisting language=\"Fortran\"><xi:include parse=\"text\" href=\"extras/orbit.for\"\n"
" xmlns:xi=\"http://www.w3.org/2001/XInclude\" /></programlisting>\n"
" <calloutlist>\n"
" <callout id=\"callout-for-parameter\" arearefs=\"orbit-for-parameter\">\n"
" <para>\n"
" The <firstterm>standard gravitational parameter</firstterm>\n"
" (μ) is a derived value, the product of Newton's gravitational \n"
" constant (G) and the mass of the primary body.\n"
" </para>\n"
" </callout>\n"
" <callout id=\"callout-for-magnitude\" arearefs=\"orbit-for-magnitude\">\n"
" <para>\n"
" Since the mass of the orbiting body is many orders of magnitude \n"
" smaller than the mass of the primary body, the mass of the \n"
" orbiting body is ignored in this calculation.\n"
" </para>\n"
" </callout>\n"
" </calloutlist>\n"
"</programlistingco>"
msgstr ""
"<programlistingco>\n"
"\t<areaspec>\n"
"\t\t<area id=\"orbit-for-parameter\" coords='4 75'/>\n"
"\t\t<area id=\"orbit-for-magnitude\" coords='12 75'/>\n"
"\t</areaspec>\n"
"\t<programlisting language=\"Fortran\"><xi:include parse=\"text\" href=\"extras/orbit.for\"\n"
"\txmlns:xi=\"http://www.w3.org/2001/XInclude\" /></programlisting>\n"
"\t<calloutlist>\n"
"\t\t<callout id=\"callout-for-parameter\" arearefs=\"orbit-for-parameter\">\n"
"\t\t\t<para>\n"
"\t\t\t\tThe <firstterm>standard gravitational parameter</firstterm>\n"
"\t\t\t\t(μ) is a derived value, the product of Newton's gravitational \n"
"\t\t\t\tconstant (G) and the mass of the primary body.\n"
"\t\t\t</para>\n"
"\t\t</callout>\n"
"\t\t<callout id=\"callout-for-magnitude\" arearefs=\"orbit-for-magnitude\">\n"
"\t\t\t<para>\n"
"\t\t\t\tSince the mass of the orbiting body is many orders of magnitude \n"
"\t\t\t\tsmaller than the mass of the primary body, the mass of the \n"
"\t\t\t\torbiting body is ignored in this calculation.\n"
"\t\t\t</para>\n"
"\t\t</callout>\n"
"\t</calloutlist>\n"
"</programlistingco>"
msgid "Note the <tag><area></tag> elements that define the position of the callouts that will appear on the code sample. The <literal>coords</literal> attributes specify a line number and a column number separated by a space. In this example, callouts are applied to lines 4 and 12 of the code, lined up with each other in column 75. Although this approach means that you might have to adjust <literal>coords</literal> attributes if you ever modify the code to which they apply, it avoids mixing XML <tag><coords></tag> tags into the code itself."
msgstr "Notare gli elementi <sgmltag><area></sgmltag> che definiscono la posizione dei callout che compaiono nel codice. Gli attributi in <literal>coords</literal> specificano un numero di riga ed un numero di colonna, separati da uno spazio. In questo esempio, i callout sono applicati alle righe 4 e 12 del codice, entrambi allineati sulla colonna 75. Anche se questo approccio prevede di adattare gli attributi <literal>coords</literal> ad ogni modifica apportata al codice, ciò evita di combinare tag <sgmltag><coords></sgmltag> nel codice."
|
