public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nilgun@fide.org, nobody@gcc.gnu.org Subject: Re: other/5927: the PO files may contain full sentences rather than phrases Date: Sat, 20 Apr 2002 08:43:00 -0000 [thread overview] Message-ID: <20020420154331.6416.qmail@sources.redhat.com> (raw) Synopsis: the PO files may contain full sentences rather than phrases State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Sat Apr 20 08:43:30 2002 State-Changed-Why: Although the sentences may exist as fragments in the code, they more or less make sense when the end-user sees the messages on the screen. Can you supply patches which fix the relevant error messages in English and makes them complete sentences? See: http://gcc.gnu.org/contribute.html for instructions as to how to prepare patches for submission. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5927
next reply other threads:[~2002-04-20 15:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-20 8:43 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-14 23:08 bangerth 2002-03-12 13:26 Nilgün Belma Bugüner
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=20020420154331.6416.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nilgun@fide.org \ --cc=nobody@gcc.gnu.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).