* Errors in man pages, here: utmp(5): Missing closing bracket
@ 2020-04-19 6:48 Helge Kreutzmann
2020-04-19 20:36 ` Michael Kerrisk (man-pages)
0 siblings, 1 reply; 2+ messages in thread
From: Helge Kreutzmann @ 2020-04-19 6:48 UTC (permalink / raw)
To: mtk.manpages; +Cc: linux-man
Dear manpages maintainers.
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including manpages) as
well for a large variety of target languages.
During their work translators notice different possible issues in the
original (english) man pages. Sometiems 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 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 translate 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. As requested, each
issue is sent in an unique mail for easier tracking on your side. If
future reports should use another channel, please let me know.
**
Mining closing bracket at init(1), i.e. init (1 → init(1)
"struct utmp {\n"
" short ut_type; /* Type of record */\n"
" pid_t ut_pid; /* PID of login process */\n"
" char ut_line[UT_LINESIZE]; /* Device name of tty - \"/dev/\" */\n"
" char ut_id[4]; /* Terminal name suffix,\n"
" or inittab(5) ID */\n"
" char ut_user[UT_NAMESIZE]; /* Username */\n"
" char ut_host[UT_HOSTSIZE]; /* Hostname for remote login, or\n"
" kernel version for run-level\n"
" messages */\n"
" struct exit_status ut_exit; /* Exit status of a process\n"
" marked as DEAD_PROCESS; not\n"
" used by Linux init (1 */\n"
" /* The ut_session and ut_tv fields must be the same size when\n"
" compiled 32- and 64-bit. This allows data files and shared\n"
" memory to be shared between 32- and 64-bit applications. */\n"
"#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32\n"
" int32_t ut_session; /* Session ID (B<getsid>(2)),\n"
" used for windowing */\n"
" struct {\n"
" int32_t tv_sec; /* Seconds */\n"
" int32_t tv_usec; /* Microseconds */\n"
" } ut_tv; /* Time entry was made */\n"
"#else\n"
" long ut_session; /* Session ID */\n"
" struct timeval ut_tv; /* Time entry was made */\n"
"#endif\n"
--
Dr. Helge Kreutzmann debian@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/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Errors in man pages, here: utmp(5): Missing closing bracket
2020-04-19 6:48 Errors in man pages, here: utmp(5): Missing closing bracket Helge Kreutzmann
@ 2020-04-19 20:36 ` Michael Kerrisk (man-pages)
0 siblings, 0 replies; 2+ messages in thread
From: Michael Kerrisk (man-pages) @ 2020-04-19 20:36 UTC (permalink / raw)
To: Helge Kreutzmann; +Cc: mtk.manpages, linux-man
On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> Dear manpages maintainers.
> the manpage-l10n project maintains a large number of translations of
> man pages both from a large variety of sources (including manpages) as
> well for a large variety of target languages.
>
> During their work translators notice different possible issues in the
> original (english) man pages. Sometiems 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 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 translate 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. As requested, each
> issue is sent in an unique mail for easier tracking on your side. If
> future reports should use another channel, please let me know.
>
> **
>
> Mining closing bracket at init(1), i.e. init (1 → init(1)
Fixed.
Thanks,
Michael
> "struct utmp {\n"
> " short ut_type; /* Type of record */\n"
> " pid_t ut_pid; /* PID of login process */\n"
> " char ut_line[UT_LINESIZE]; /* Device name of tty - \"/dev/\" */\n"
> " char ut_id[4]; /* Terminal name suffix,\n"
> " or inittab(5) ID */\n"
> " char ut_user[UT_NAMESIZE]; /* Username */\n"
> " char ut_host[UT_HOSTSIZE]; /* Hostname for remote login, or\n"
> " kernel version for run-level\n"
> " messages */\n"
> " struct exit_status ut_exit; /* Exit status of a process\n"
> " marked as DEAD_PROCESS; not\n"
> " used by Linux init (1 */\n"
> " /* The ut_session and ut_tv fields must be the same size when\n"
> " compiled 32- and 64-bit. This allows data files and shared\n"
> " memory to be shared between 32- and 64-bit applications. */\n"
> "#if __WORDSIZE == 64 && defined __WORDSIZE_COMPAT32\n"
> " int32_t ut_session; /* Session ID (B<getsid>(2)),\n"
> " used for windowing */\n"
> " struct {\n"
> " int32_t tv_sec; /* Seconds */\n"
> " int32_t tv_usec; /* Microseconds */\n"
> " } ut_tv; /* Time entry was made */\n"
> "#else\n"
> " long ut_session; /* Session ID */\n"
> " struct timeval ut_tv; /* Time entry was made */\n"
> "#endif\n"
>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-04-19 20:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-04-19 6:48 Errors in man pages, here: utmp(5): Missing closing bracket Helge Kreutzmann
2020-04-19 20:36 ` Michael Kerrisk (man-pages)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).