Package: cron Version: 3.0pl1-186 Severity: minor Tags: patch X-Debbugs-CC: mario.blaetterm...@gmail.com
Dear Debian cron maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including cron) as
well for a large variety of target languages.
During their work translators notice different possible issues in the
original (english) man pages. Sometimes this is a straightforward
typo, sometimes a hard to read sentence, sometimes this is a
convention not held up and sometimes we simply do not understand the
original.
We use several distributions as sources and update regularly (at
least every 2 month). This means we are fairly recent (some
distributions like archlinux also update frequently) but might miss
the latest upstream version once in a while, so the error might be
already fixed. We apologize and ask you to close the issue immediately
if this should be the case, but given the huge volume of projects and
the very limited number of volunteers we are not able to double check
each and every issue.
Secondly we translators see the manpages in the neutral po format,
i.e. converted and harmonized, but not the original source (be it man,
groff, xml or other). So we cannot provide a true patch (where
possible), but only an approximation which you need to convert into
your source format.
Finally the issues I'm reporting have accumulated over time and are
not always discovered by me, so sometimes my description of the
problem my be a bit limited - do not hesitate to ask so we can clarify
them.
I'm now reporting the errors for your project. If future reports
should use another channel, please let me know.
(Btw., do you have a working e-mail address of upstream?)
Man page: cron.8
Issue: B<-L loglevel> → B<-L> I<loglevel>
"B<-L loglevel>"
--
Man page: crontab.1
Issue 1: I<-h> → B<-h>
Issue 2: I<crontab> → B<crontab>
"If the I<-h> option is given, I<crontab> shows a help message and quits "
"immediately."
--
Man page: crontab.1
Issue 1: I<-h> → B<-h>
Issue 2: I<crontab> → B<crontab>
"If the I<-n> option is given, it means \"dry run\": I<crontab> examines "
"\"your\" crontab for its syntax, and outputs a success message if this "
"syntax is correct, but nothing is written to any crontab."
--
Man page: crontab.1
Issue: if, they exist, → , if they exist,
"The files I</etc/cron.allow> and I</etc/cron.deny> if, they exist, must be "
"either world-readable, or readable by group ``crontab''. If they are not, "
"then cron will deny access to all users until the permissions are fixed."
--
Man page: crontab.1
Issue: crontab(5), cron(8), spc(1) → B<crontab>(5), B<cron>(8), B<spc>(1)
"crontab(5), cron(8), spc(1)"
--
Man page: crontab.5
Issue: I<su> → B<su>
"A I<crontab> file contains instructions to the I<cron>(8) daemon of the "
"general form: ``run this command at this time on this date''. Each user has "
"their own crontab, and commands in any given crontab will be executed as the "
"user who owns the crontab. Uucp and News will usually have their own "
"crontabs, eliminating the need for explicitly running I<su>(1) as part of a "
"cron command."
--
Man page: crontab.5
Issue: LOGNAME → I<LOGNAME>
"Several environment variables are set up automatically by the I<cron>(8) "
"daemon. SHELL is set to /usr/bin/sh, and LOGNAME and HOME are set from the /"
"etc/passwd line of the crontab's owner. HOME and SHELL may be overridden by "
"settings in the crontab; LOGNAME may not."
--
Man page: crontab.5
Issue: I<ncal> or I<calendar> For → B<ncal>(1) or B<calendar>(1). For
"If the program itself cannot do the checks then a wrapper script would be "
"required. Useful tools that could be used for date analysis are I<ncal> or "
"I<calendar> For example, to run a program the last Saturday of every month "
"you could use the following wrapper code:"
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
