public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "debian at helgefjell dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/29916] New: Issues with glibc man pages Date: Sun, 18 Dec 2022 16:06:04 +0000 [thread overview] Message-ID: <bug-29916-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29916 Bug ID: 29916 Summary: Issues with glibc man pages Product: glibc Version: unspecified Status: UNCONFIRMED Severity: minor Priority: P2 Component: manual Assignee: unassigned at sourceware dot org Reporter: debian at helgefjell dot de CC: mtk.manpages at gmail dot com Target Milestone: --- Dear Glibc maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including Glibc) 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: locale.gen.5 Issue: B</etc/locale.gen> → file I</etc/locale.gen> "The file B</etc/locale.gen> lists the locales that are to be generated by " "the B<locale-gen> command." -- Man page: locale.gen.5 Issue: Missing Markup B<> "locale-gen(8), localedef(1), locale(1)" -- Man page: update-locale.8 Issue: B</etc/default/locale> → I</etc/default/locale> "This program can be called by maintainer scripts when Debian packages are " "installed or removed, it updates the B</etc/default/locale> file to reflect " "changes in system configuration related to global locale settings. When " "variables have no value assigned, they are removed from the locale file. " "Some basic checks are performed to ensure that requested settings are valid." "Define file containing locale variables. (Default: B</etc/default/locale>)" "B</etc/default/locale>" -- Man page: update-locale.8 Issue: locale-gen(8), locale(1) → B<locale-gen>(8), B<locale>(1) "locale-gen(8), locale(1)" -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-12-18 16:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-18 16:06 debian at helgefjell dot de [this message] 2022-12-18 16:33 ` [Bug manual/29916] " schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29916-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).