On 7/6/20 12:12 PM, Helge Kreutzmann wrote: > Dear linux man page maintainer, > the manpage-l10n project maintains a large number of translations of > man pages both from a large variety of sources (including linux man > pages) 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. > > ** > > Man page: fork.2 > Issue: any fork handlers → any B<fork>() handlers > > "Since version 2.3.3, rather than invoking the kernel's B<fork>() system " > "call, the glibc B<fork>() wrapper that is provided as part of the NPTL " > "threading implementation invokes B<clone>(2) with flags that provide the " > "same effect as the traditional system call. (A call to B<fork>() is " > "equivalent to a call to B<clone>(2) specifying I<flags> as just " > "B<SIGCHLD>.) The glibc wrapper invokes any fork handlers that have been " > "established using B<pthread_atfork>(3)." No. "fork handler" is a term. Just like exit handler. Or clean-up handler. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
