| Re: [translations] updating an up-to-date file?!? |
[ Thread Index |
Date Index
| More lilynet.net/translations Archives
]
- To: Francisco Vila <paconet.org@xxxxxxxxx>
- Subject: Re: [translations] updating an up-to-date file?!?
- From: Federico Bruni <fedelogy@xxxxxxxxx>
- Date: Sun, 28 Nov 2010 01:08:36 +0100
- Cc: Jean-Charles Malahieude <lilyfan@xxxxxxxxx>, Translations list at lilynet <translations@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=3vubSJ4FzzcECTqAe10UsfR2pSMl/1bTpOXO6ltguO4=; b=Uh58KIzmIrFhBbVtgh9+c/hkgJ3h7OSwIB2oQi1/hiMGZBWJkT1W6FL27dSPSdzoXk 2IH9KcQMt1ziWBKLBBANPoAGw+vydayk76A82bNBYGPmZUH/H38lCtVO+5075lTZ0YjW R5YJYze3RjL6dOoBM7wKpiQjcX/w1XkiABUu0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=mjteGDDFcA/xZTReUhm71uBYZn2l674G7FH7zCcBfrHi8PiAaPuRVU/t+pE585VTky GYsOKy5/WueDGPK3H/+SYFeQUF1AMMF+Jr7ueYsrK+Lu7/oyuXPPwVWER00PRxuNBdOe zZ0wh/L00XofAtk9yK3kc58abIXKRSD2D6KlM=
Il giorno sab, 27/11/2010 alle 23.41 +0100, Francisco Vila ha scritto:
> > Francisco, would you mind having a look at it?
>
> Documentation is [maybe too] abbreviated in this case. The example
> just shows what has to be added to the command line for checking some
> given files. But the part 'make [whatever] check-translation' must be
> understood as 'make ISOLANG=[your language id] check-translation'.
> Different options to achieve a given result have to be taken as added
> to the command line as options. It is easier and more readable not to
> put always every possible option in examples.
This is not straightforward for those (like me) who know nothing about
make files.
Also, in that page (CG 4.8.3) ISOLANG=MY_LANGUAGE is always specified
except for commands using CHECKED_FILES=
I could think that there's no need to add ISOLANG= because the script
can set automatically the language by looking at the path of the file
I'm checking (CHECKED_FILES=MY_LANGUAGE/manual/foo.itely).
(Yes, I could also think about adding ISOLANG= if it's not working...
but I trust doc editors so much! :-))
IMO we need consistency, so I suggest two possible ways:
- add ISOLANG=MY_LANGUAGE in all commands wich require it
- don't add ISOLANG=MY_LANGUAGE in any command, just put a warning at
the beginnning of the page, saying something like "you need to specify
your language in all the following commands by adding the
ISOLANG=MY_LANGUAGE option"