[Bug other/38363] Use of Unicode quotes depends on LC_CTYPE rather than LC_MESSAGES

2010-05-22 Thread jsm28 at gcc dot gnu dot org


--- Comment #2 from jsm28 at gcc dot gnu dot org  2010-05-22 17:42 ---
As discussed, not a bug.


-- 

jsm28 at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID


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



[Bug other/38363] Use of Unicode quotes depends on LC_CTYPE rather than LC_MESSAGES

2008-12-01 Thread joseph at codesourcery dot com


--- Comment #1 from joseph at codesourcery dot com  2008-12-02 01:36 ---
Subject: Re:   New: Use of Unicode quotes depends on LC_CTYPE
 rather than LC_MESSAGES

On Tue, 2 Dec 2008, debian-gcc at lists dot debian dot org wrote:

 gcc uses Unicode quote marks with LC_CTYPE=en_US.UTF-8, but not with
 LC_CTYPE=C.  Shouldn't that depend on LC_MESSAGES instead, not LC_CTYPE?
 LC_CTYPE should only affect character classification, such as this
 character counts as uppercase.

LC_CTYPE should determine the character set for messages and LC_MESSAGES 
their language.  For translated messages, gettext should automatically 
convert the messages in the .mo file to the user's terminal's character 
set as specified by LC_CTYPE (or overridden by OUTPUT_CHARSET).  For 
English messages, this is handled directly in the compiler.


-- 


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