This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Windows Unicode and GCC
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Zack Weinberg <zackw at panix dot com>
- Cc: Nicolas De Rico <nicolas dot derico at sand dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 27 Apr 2006 17:16:10 -0700
- Subject: Re: Windows Unicode and GCC
- References: <444D268B.6030600@sand.com> <20060427235829.GB19786@panix.com>
[ Unicode, UTF-{8,16}, BOMs, etc ]
On Thu, Apr 27, 2006 at 07:58:29PM -0400, Zack Weinberg wrote:
> complicated) "Local Variables:" marker near the end of the file;
> other editors have similar, but of course incompatible, conventions
> (I know Vim has one but I don't know what it looks like). It would
> also be good to take advantage of the fact that 95+% of C source
> files start with "/*", "//", "#i", or "#d" to distinguish ASCII
> from EBCDIC. (This is in fact necessary in order to have any hope
> of detecting and processing an editor's code page marker in an EBCDIC
> source file.)
Is this really an important problem? EBCDIC is still around (barely), but
code page markers in EBCDIC source files? Perhaps I'm missing something.