This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix incompatible quote handling
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Andi Kleen <ak at suse dot de>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 30 Oct 2004 12:09:28 -0400
- Subject: Re: [PATCH] Fix incompatible quote handling
- References: <20041030070951.GA18074@wotan.suse.de> <87sm7whdgc.fsf@codesourcery.com> <6FB95DBF-2A7A-11D9-9310-000A95D692F4@physics.uc.edu> <20041030140715.GA20611@wotan.suse.de> <50D46E03-2A7D-11D9-9310-000A95D692F4@physics.uc.edu> <20041030141138.GB20611@wotan.suse.de> <jept30l1vs.fsf@sykes.suse.de> <20041030144153.GC20611@wotan.suse.de> <20041030153128.GA25437@wotan.suse.de> <10C41D7B-2A8A-11D9-9310-000A95D692F4@physics.uc.edu> <20041030155912.GB11515@wotan.suse.de>
On Oct 30, 2004, at 11:59 AM, Andi Kleen wrote:
There is not any reasoning in that mail why the incompatible quotes
should
be better. I can see the point of translated quotes in other
languages,
but using UTF-8 quotes in English is unnecessary and causes problems in
common setups (old xterm sshing into modern linux)
It also violates the reasonable assumption that a console application
like
gcc should not make unnecessary requirements to the terminal.
How do you write quotes when you writing quotes by hand, I would assume
not " but “ and ” so should the computer be any different?
Again if your LC_* is set to *utf-8 then what do you expect but get
UTF-8 characters. This is not an additional requirement on the terminal
at all. If LC* is set to *utf-8 you are saying that your terminal
supports UTF-8 and you want UTF-8 characters.
(Yes I am repeating my self but this is because you don't get setting
LC_* says what your terminal supports).
-- Pinski