On Sun, 1 Nov 2015, Vincent Lefevre wrote:
> The documentation should also say whether LC_CTYPE affects the
> command-line arguments (e.g. macro values via -D) and in what way
See bug 20183.
> it affects the output (e.g. messages and output of "gcc -E").
See bug 21521.
--
Joseph S. Myers
jos.
On 2015-10-22 20:11:15 +, Joseph Myers wrote:
> LC_CTYPE should affect the interpretation of multibyte character sequences
> as characters, including on output. That's the standard semantics.
That's only for the recommended default behavior. There are many
contexts where different charset in
On Thu, 22 Oct 2015, Martin Sebor wrote:
> > Again, LC_CTYPE does *not* affect source file interpretation.
>
> I understand what you're saying. What I am saying is that if this
> is how c99 behaves it's in conflict with POSIX because LC_CTYPE
> is exactly how source file interpretation is specifi
Again, LC_CTYPE does *not* affect source file interpretation.
I understand what you're saying. What I am saying is that if this
is how c99 behaves it's in conflict with POSIX because LC_CTYPE
is exactly how source file interpretation is specified to be
controlled:
LC_CTYPE
Determine the
On Thu, 22 Oct 2015, Joseph Myers wrote:
> multibyte characters in that output). (If an explicit character set is
> specified for LC_MESSAGES that's different from that in LC_CTYPE, you
> probably have a broken environment - multibyte characters need to have a
The specific wording in POSIX th
On Thu, 22 Oct 2015, Martin Sebor wrote:
> > LC_MESSAGES determines "the language and cultural conventions in which
> > messages should be written" (not necessarily the interpretation of
> > multibyte characters in that output).
>
> Yes, but setting LC_CTYPE shouldn't affect the format, language,
On 10/22/2015 10:53 AM, Joseph Myers wrote:
On Wed, 21 Oct 2015, Martin Sebor wrote:
That would go against the usual (i.e., POSIX) expected effect
of the environment variable. Specifically for GCC (or the c99
utility), POSIX requires LC_CTYPE to determine the locale used
to parse the input, an
On Wed, 21 Oct 2015, Martin Sebor wrote:
> That would go against the usual (i.e., POSIX) expected effect
> of the environment variable. Specifically for GCC (or the c99
> utility), POSIX requires LC_CTYPE to determine the locale used
> to parse the input, and LC_MESSAGE to determine the locale of
On 10/21/2015 03:23 PM, D. Hugh Redelmeier wrote:
Several of us don't want UTF-8 quotation marks in diagnostics in our
environment (Jove subshells). We'd like a way to turn them off. We don't
think that they are a bad idea but they are bad in our environment.
<https://g
On Wed, 21 Oct 2015, D. Hugh Redelmeier wrote:
> The LC_CTYPE environment variable specifies character
> classification. GCC uses it to determine the character
> boundaries in a string; this is needed for some multibyte
> encodings that contain quote and escape characters
Several of us don't want UTF-8 quotation marks in diagnostics in our
environment (Jove subshells). We'd like a way to turn them off. We don't
think that they are a bad idea but they are bad in our environment.
<https://gcc.gnu.org/gcc-4.0/changes.html>
Englis
11 matches
Mail list logo
