public inbox for gentoo-docs-it@lists.gentoo.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-docs-it@lists.gentoo.org
Subject: Re: [gentoo-docs-it] manuale completato e bugzilla
Date: Sun, 22 Jan 2012 23:52:30 +0100	[thread overview]
Message-ID: <2566652.Fca4JVXSNE@devil> (raw)
In-Reply-To: <CAP6dPAe2v0b26z221KhnAXOwTEd8Pra+zBw88XaQY6HAhfzq_w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]

On Sunday 22 January 2012 20:21:57 HUjuice wrote:
> Francamente, però, non ho capito bene in cosa consiste la revisione
> dell'XML di cui parli.
> Per quanto riguarda la validità, ci sono xmllint e mille altri strumenti
> ('find bump/ -type f -name \*.xml -exec xmllint --valid --noout {} +').
> 
> Quindi cosa bisogna controllare?
bisogna controllare che non ci siano state sviste come ad esempio qui:
https://gitorious.org/documentazione-italiana-gentoo-linux/documentazione-
italiana-gentoo-linux/commit/a2458ddffc9cf3ff7ccb30a3dbc4cfc1aa11e702

ho notato che c'era un pezzo che non doveva esserci.

Quindi io procedo a vedere le differenze tra il diff prodotto da cvs e il diff 
tra la nostra vecchia documentazione e quella aggiornata, per vedere se tutto 
è in ordine.
-- 
Agostino Sarubbo		ago -at- gentoo.org
Gentoo/AMD64 Arch Security Liaison
GPG: 0x7CD2DC5D

[-- Attachment #1.2: Type: text/html, Size: 3809 bytes --]

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-01-22 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 18:53 [gentoo-docs-it] manuale completato e bugzilla HUjuice
2012-01-22 19:05 ` Agostino Sarubbo
2012-01-22 19:21   ` HUjuice
2012-01-22 22:52     ` Agostino Sarubbo [this message]
2012-01-26 19:40 ` Agostino Sarubbo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2566652.Fca4JVXSNE@devil \
    --to=ago@gentoo.org \
    --cc=gentoo-docs-it@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox