[Bug c/44310] New: utf8 quotes in warnings make them look like garbage in many contexts

[Bug c/44310] New: utf8 quotes in warnings make them look like garbage in many contexts

[jay dot krell at cornell dot edu]

gcc shouldn't use utf8 backticks for quotes.

Often I paste gcc output into email or cvs commit comments or bug reports, and
the backticks in like:

'foo' might used uninitialized

shows up with some garbage
!@#foo!@#$ might be used uninitialized

Imho this code should be removed:

gcc/intl.c

#if defined HAVE_LANGINFO_CODESET
      if (locale_utf8)
        {
          open_quote = "\xe2\x80\x98";
          close_quote = "\xe2\x80\x99";
        }
#endif
    }

Perhaps I need to:
.bashrc:
 export LOCALE=C

or somesuch..


Perhaps if gcc detects any characters over 127 in any of the source files or
perhaps headers, it could switch into this wierdo character set mode, but not
otherwise? (Given I don't control the headers, only my source, that may be
overly eager.)


-- 
           Summary: utf8 quotes in warnings make them look like garbage in
                    many contexts
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jay dot krell at cornell dot edu


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

[Bug c/44310] utf8 quotes in warnings make them look like garbage in many contexts

[jakub at gcc dot gnu dot org]

------- Comment #1 from jakub at gcc dot gnu dot org  2010-05-28 12:39 -------
Don't use UTF-8 locale if your terminal or applications aren't UTF-8 ready.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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

[Bug c/44310] utf8 quotes in warnings make them look like garbage in many contexts

[jay dot krell at cornell dot edu]

------- Comment #2 from jay dot krell at cornell dot edu  2010-05-28 12:42 -------
This is just whatever defaults I'm given. I haven't set anything.
I often get garbled output.


-- 


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

[Bug c/44310] utf8 quotes in warnings make them look like garbage in many contexts

[pinskia at gcc dot gnu dot org]

------- Comment #3 from pinskia at gcc dot gnu dot org  2010-05-28 18:30 -------
(In reply to comment #2)
> This is just whatever defaults I'm given. 

Then complain to your distro since they are the ones where the bug is.


-- 


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

[Bug c/44310] utf8 quotes in warnings make them look like garbage in many contexts

[jay dot krell at cornell dot edu]

------- Comment #4 from jay dot krell at cornell dot edu  2010-05-30 13:24 -------
It's MacOSX for local console, remote to Debian, Solaris, OpenBSD, etc., I
can't keep track of when it works and when it doesn't, but it often doesn't.


Local console works fine.
As the bug says "in many contexts", not "all contexts".


Things are garbled when pasted into web forms, cvs commits, going through ssh.
Is there really a way to communicate this stuff through the various usual
channels? I don't configure the heck out of everything and I expect defaults to
be reasonable. I don't expect compiler messages to be so quick to get garbled.


If input is only 7 bit ASCII, then output should only be 7 bit ASCII.
When I start presenting the compiler with characters beyond that, it can give
them back to me.


-- 


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