Hello Georges, Am Sun, Mar 03, 2024 at 06:37:25PM +0100 schrieb Georges Khaznadar: > thank you for your detailed bug report.
You are welcome. > Helge Kreutzmann a écrit : > > We use several distributions as sources and update regularly (at > > least every 2 month). > > Most changes here are probably specific to Debian; however they will > also apply to Debian derivatives. Yes, given that I could not reach upstream, I only reported those issues which were actually present in the Debian version. I don't know when and how I can report the rest. > > 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. > > The original format for Debian's manpages regarding cron is groff. That's usual, but po4a transforms this in a more friendly format for us translators. > Unfortunately, it is not the easiest format for human translators, as it > is probably split in small chunks written to PO files, with little > meaning in each of them. That's fine, don't worry. If in doubt we can always build the full translated page and read it for consisteny. And small paragraphs are usually better to handle and, potentially, reuse. > > (Btw., do you have a working e-mail address of upstream?) > > The upstream developer, Paul Vixie, had an e-mail address: p...@vix.com Ok, so nothing new. > However, he does no longer maintain cron, and Debian's cron package > comes from a fork, dated "Sun, 1 Dec 1996 16:21:52 -0600". So, for > twenty eight years now, all of the development was made by various > debian developers, and is structured as a heap of 84 patches > (see the file > https://salsa.debian.org/debian/cron/-/blob/master/debian/patches/series?ref_type=heads) > > Regarding the issues listed below, I do not fully understand the syntax. > > If I consider the very first issue: > > > > Man page: cron.8 > > Issue: B<-L loglevel> → B<-L> I<loglevel> > > > > "B<-L loglevel>" > > -- > > and take a look at the manpage, which is in groff format, I can find some > matching line: > > ------------------------8<------------------------------- > $ zgrep loglevel /usr/share/man/man8/cron.8.gz > .IR loglevel ] > .B \-L loglevel > ------------------------8<------------------------------- > > The last line (in groff) means: write "-L loglevel" with a bold font. > This probably has the same meaning as the line "B<-L loglevel>" in the > snipped above. Yes, and this is what should be corrected. > So how can I help? can I answer that the line "B<-L loglevel>" is the > current valid source for localizations? I'm not very good (if at all) at groff, by I think the following might work: .B \-L .I loglevel or even .BI \-L loglevel > Now let us consider the next issues: > > > 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." > > -- > > > How can I help? Here is the match which I can find: > > ------------------------8<------------------------------- > zgrep -- -h /usr/share/man/man1/crontab.1.gz > crontab [ \-h] > .I \-h > ------------------------8<------------------------------- > > The last line (in groff format) would probably match Issue 1 above, > however once again I do not guess how I can help. You put it in Italics, but the convention (see man-pages(7) and man(7)) is to use bold, so this one is simply: .B \-h > It would probably be a waste of energy to discuss now all and every > issue you sent me. Maybe we can first agree about a method to make the > task easier for both of us, and for the many contributors to translation > teams. I hope this explains it. > Please can you suggest me one or more techniques which might improve the > feedback, regarding the simple examples cited above? The main question > is "how can I help?", which can be rephrased as "what kind of answer > would you expect?". First thanks for your ultra fast response - this is extraordinary help already. And for your verbose questions, which make it easier for me to respond. I think most of the report boils down that you update the patches by using .B instead of .I or sometimes .BI I hope this explains it better. Greetings Helge P.S. And since there is probably little changes in cron nowadays, most likely few if none further reports from my side… -- 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
