public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug translation/42469] option help strings not properly using TAB
Date: Wed, 23 Dec 2009 12:08:00 -0000	[thread overview]
Message-ID: <20091223120818.21600.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42469-18195@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jsm28 at gcc dot gnu dot org  2009-12-23 12:08 -------
Part of this appears to be the same exgettext issue as bug 42467.

The rest appears to be option help strings using one or more spaces where
a single TAB should be used:

common.opt:-Wframe-larger-than=<number> Warn if a function's stack frame
requires more than <number> bytes
common.opt:-fcompare-debug[=<opts>] Compile with and without e.g. -gtoggle, and
compare the final-insns dump
common.opt:-fdbg-cnt=<counter>:<limit>[,<counter>:<limit>,...]    Set the debug
counter limit.   
common.opt:-fira-verbose=<number> Control IRA's level of diagnostic messages.
common.opt:-flto-compression-level=<number> Use zlib compression level <number>
for IL
common.opt:-fplugin-arg-<name>-<key>[=<value>] Specify argument <key>=<value>
for plugin <name>
c.opt:-imultilib <dir> Set <dir> to be the multilib include subdirectory
fortran/lang.opt:-fblas-matmul-limit=<n>        Size of the smallest matrix for
which matmul will use BLAS
fortran/lang.opt:-finit-character=<n> Initialize local character variables to
ASCII value n
fortran/lang.opt:-finit-integer=<n> Initialize local integer variables to n
fortran/lang.opt:-finit-logical=<true|false> Initialize local logical variables
fortran/lang.opt:-finit-real=<zero|nan|inf|-inf> Initialize local real
variables
fortran/lang.opt:-fmax-array-constructor=<n>        Maximum number of objects
in an array constructor


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |40883
              nThis|                            |
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-12-23 12:08:18
               date|                            |
            Summary|19 localization fails with  |option help strings not
                   |gcc ---help=fortran         |properly using TAB


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42469


  reply	other threads:[~2009-12-23 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 20:27 [Bug translation/42469] New: 19 localization fails with gcc ---help=fortran karvonen dot jorma at gmail dot com
2009-12-23 12:08 ` jsm28 at gcc dot gnu dot org [this message]
2010-01-07  8:39 ` [Bug translation/42469] option help strings not properly using TAB pzhao at gcc dot gnu dot org
2010-01-11  4:29 ` pzhao at gcc dot gnu dot org
2010-01-11  9:34 ` pzhao at gcc dot gnu dot 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=20091223120818.21600.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).