public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: alexe@rent-a-mind.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: preprocessor/3744: Wide string literals not interpreted according to locale Date: Thu, 19 Jul 2001 23:50:00 -0000 [thread overview] Message-ID: <20010720065018.26655.qmail@sourceware.cygnus.com> (raw) Synopsis: Wide string literals not interpreted according to locale State-Changed-From-To: open->suspended State-Changed-By: neil State-Changed-When: Thu Jul 19 23:50:17 2001 State-Changed-Why: We don't handle charsets with iconv yet. The preprocessor is not interpreting anything - the front ends are doing that. In the future, we will handle charsets better, but it will not be through the locale settings, since that is not appropriate. You may want to see what 3.0 and the development branch do; they are both different and may be closer to what you want. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3744&database=gcc
next reply other threads:[~2001-07-19 23:50 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-19 23:50 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-19 23:26 alexe
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=20010720065018.26655.qmail@sourceware.cygnus.com \ --to=neil@gcc.gnu.org \ --cc=alexe@rent-a-mind.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).