public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bensberg at justemail dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3465] New: mistaken messages [patch] Date: Mon, 06 Nov 2006 21:50:00 -0000 [thread overview] Message-ID: <20061106215028.3465.bensberg@justemail.net> (raw) During retranslation to Dutch I've found a few mistakes in libc's messages, ranging from simple typos to wrong words. The first patch repairs these. It also corrects two typos in comments that I noticed along the way, and gettextizes a forgotten little message. The second patch makes some of the messages equal to others, from which they unnecessarily and inconsistently differ, by a word, a letter, or a period. It also, for consistency, adds a period to some doc strings, and removes it from some other messages. -- Summary: mistaken messages [patch] Product: glibc Version: unspecified Status: NEW Severity: minor Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: bensberg at justemail dot net CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3465 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-11-06 21:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-06 21:50 bensberg at justemail dot net [this message] 2006-11-06 21:51 ` [Bug libc/3465] " bensberg at justemail dot net 2006-11-06 21:52 ` bensberg at justemail dot net 2006-11-06 22:10 ` jakub at redhat dot com 2006-11-06 23:01 ` bensberg at justemail dot net 2006-11-10 20:55 ` drepper at redhat dot com
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=20061106215028.3465.bensberg@justemail.net \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).