Typographical Guidelines/it: Difference between revisions

    From KDE UserBase Wiki
    (Updating to match new version of source page)
    (Updating to match new version of source page)
    Line 3: Line 3:
    ''Ci sono pagine a parte che spiegano la [[PageLayout|Struttura della pagina]] e la [[Toolbox|sintassi]] con codici di esempio.''
    ''Ci sono pagine a parte che spiegano la [[PageLayout|Struttura della pagina]] e la [[Toolbox|sintassi]] con codici di esempio.''


    <span class="mw-translate-fuzzy">
    Aderire a queste linee guida tipografiche ti garantisce che la tua documentazione potrà essere esportata in modo facile ed accurato per scopi di traduzione.
    Aderire a queste linee guida tipografiche ti garantisce che la tua documentazione potrà essere esportata in modo facile ed accurato per scopi di traduzione.
    </span>


    ==Testo grassetto==
    ==Testo grassetto==

    Revision as of 09:09, 7 July 2011

    Ci sono pagine a parte che spiegano la Struttura della pagina e la sintassi con codici di esempio.

    Aderire a queste linee guida tipografiche ti garantisce che la tua documentazione potrà essere esportata in modo facile ed accurato per scopi di traduzione.

    Testo grassetto

    Utilizza il testo grassetto per evidenziare

    • Titoli delle finestre
    • Etichette comuni non configurabili dall'utente
    • Didascalie delle icone
    • Nomi dei programmi

    Per esempio:

    • evidenziazione di una selezione di testo che sarà copiato in Klipper.

    Testo corsivo

    Utilizza testo corsivo per enfatizzare:

    • parole o frasi come nella normale scrittura;
    • titoli quando fanno riferimento ad altri lavori;
    • la prima occorrenza di una parola insolita.

    Alcuni esempi:

    • A questo punto salva il tuo lavoro.
    • I dettagli sono disponibili in Samba 3 tramite esempi...
    • I manuali KDE sono in formato Docbook.

    Suggerimento

    I programmi sono avviati dagli utenti, i componenti sono utilizzati dai programmi.


    Testo combinato grassetto e corsivo

    Utilizza questa combinazione per testo variabile o sostituibile.

    Alcuni esempi:

    • per connetterti al tuo server remoto digita ssh [email protected] in Konsole.
    • Nelle distribuzioni basate su rpm il comando rpm -q nomepacchetto darà come risultato pacchetto-versione-rilascio.

    Testo a larghezza fissa

    Code should be presented in mono-spaced text, usually boxed, as shown below. Input text will be on a pale yellow background. For output text, the background colour will be violet-grey.

    • Code, whether single lines or blocks, use templates to ensure consistency
    • Utilizza il modello Input così:
      {{Input|1=<nowiki>
      qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit
      rm -r ~/.kde/share/apps/nepomuk
      rm -r ~/.kde4/share/apps/nepomuk
      nepomukserver</nowiki>}}
      Verrà visualizzato in questo modo:
      qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit
      rm -r ~/.kde/share/apps/nepomuk
      rm -r ~/.kde4/share/apps/nepomuk
      nepomukserver


    • Output works the same way:
      {{Output|1=<nowiki>terminal output 
      is also shown as code, 
      but on a grey background</nowiki>}}
      which displays as
      terminal output 
      is also shown as code, 
      but on a grey background

    Note

    Note the use of 1=<nowiki> some text </nowiki> to avoid situations that break the display format


    • Starting an Input or Output template on a new line will break the display format if it is within lists. Simply continue on the same line if you need to correct this.
    • You can also combine input/output areas with GeSHi syntaxhiglighting. An input area like this
      {{Input|<syntaxhighlight lang="php" line>
      # Initialise common code
      $preIP = dirname( __FILE__ );
      require_once( "$preIP/includes/WebStart.php" );
      </syntaxhighlight>}}
      will result in
      # Initialise common code
      $preIP = dirname( __FILE__ );
      require_once( "$preIP/includes/WebStart.php" );
      
    • Single code words can be kept in-line by using
      <code></code>
      It will display like this.
    • <tt> </tt>
      is useful for displaying filenames and paths. This looks like this: a/path/to/here

    Block Quotes

    The tags <blockquote> and </blockquote> should be used when quoting other works or other pages. This produces a proportional italic font, with some padding.

    Here is an example of the display that you get by using the blockquote tags.

    Text in Section Headers

    Even though the criteria above may be met, do not use Bold text in section headers or in links.

    Text in Information, Note, Tip or Warning Templates

    Bold text should be avoided in the text within these templates. Italic text for emphasis may still be used - use sparingly for maximum effect.

    Elenchi

    You can have various kinds of lists in your pages — bulleted, numbered or itemized. Find details on the Toolbox page.

    Keeping things together

    After your text is written some markup is automatically added by the translation system. This means that whenever it sees a blank line, it starts a new unit. When your text is presented to translators, they typically see it one unit at a time, so it is important not to leave a blank lines in the middle of something that should be treated as a unit. Normally an entire paragraph should be kept in a single unit; and under no circumstance should a sentence be split between units!

    If you need a linebreak in the middle of a section, the preferred way to achieve this is without breaking units is to use <br /> at the end of the line where you want to break to occur (not on a new line). If you need space between the lines add <br /><br />.

    Unbalanced brackets

    The translation system marks any translated unit as incompletely translated if it contains any kind of unbalanced brackets. If you need to have unbalanced brackets in your text, please add a balancing bracket in a comment tag, like this:

    <!-- }} -->{{ A line 
    
    Another line}}<!-- {{ -->

    This goes for all kinds of brackets, even ordinary parentheses. (Of course it is normally better to avoid blank lines within a mark up unit - see Keeping things together.)

    Special Tags

    • <keycap> and </keycap> denote (keyboard) key names e.g. Enter
    • <keycap></keycap> can also be used around groups of keys to be used concurrently, e.g. Ctrl + Alt + F1 to launch a virtual terminal. (Note that "(space)+(space)" is used to link keys to be pressed concurrently).
    • Sequences of menu choices should use <menuchoice> and </menuchoice> for example View -> Message List -> Aggregation -> Standard Mailing List
    • In general, if the user needs to choose an element, even if it is not in a menu, the <menuchoice></menuchoiсe> markup should be used.

    The Problematic Pipe

    In some situations the pipe symbol can't be used - for instance when adding parameters into a template. In any such case, please use {{!}} which will display as a pipe symbol. For example, if you want to display a command line containing the pipe character using the {{Input|...}} template, the simplest way to do it is this: {{Input|1=cmd1 {{!}} cnd2}} which displays

    cmd1 | cnd2


    If you just write {{Input|cmd1 | cnd2}} you get instead

    cmd1 

    the problem being, that cmd2 is seen as a second parameter to the template, which in this case is not used.

    In many cases, you can also enclose the text containing the pipe character between <nowiki>... </nowiki> tags, like this {{Input|1=<nowiki>cmd1 | cmd2</nowiki>}}, which also displays

    cmd1 | cmd2

    Translatable Content

    Everything that is translatable is contained within <translate> and </translate> tags. In most cases any images should be contained within the translatable section, as it is sometimes necessary to use localised versions of the images to explain a point. The rule of thumb is "If in doubt, include it!".