Re: Encoding issues with literal strings (C++)
- From: jasen <jasen@xxxxxxxxxxx>
- Date: 22 Dec 2006 07:20:01 GMT
On 2006-12-20, Carlos Moreno <moreno_at_mochima_dot_com@xxxxxxxxxxxxxx> wrote:
The literal string is: " ..... espec\xEDficos ..... "
The hexdump output (the relevant line) is:
65 73 20 65 73 70 65 63 df 69 63 6f 73 2e 20 20 |es espec.icos. |
Why did that happen? How do I avoid it? --- without having to
manually edit the executable, that is). I have the feeling that
it has to do with UTF-8 encoding, perhaps invalid UTF-8 sequences
that the compiler is "fixing" --- but, if that is the case, why?
The compiler definately should not miss with string literals
like that.
2) The other thing is that I'm getting a compiler warning of hex
escape sequence out of range for the \xF3 --- yet that character
shows up ok (the o with acute accent).
odd...
Post something we can compile, and the full text of the warning,
and the full version number of the compiler you are using.
Bye.
Jasen
.
- Follow-Ups:
- Re: Encoding issues with literal strings (C++)
- From: Carlos Moreno
- Re: Encoding issues with literal strings (C++)
- References:
- Encoding issues with literal strings (C++)
- From: Carlos Moreno
- Encoding issues with literal strings (C++)
- Prev by Date: Re: crontab
- Next by Date: Re: about control the cdrom drive
- Previous by thread: Re: Encoding issues with literal strings (C++)
- Next by thread: Re: Encoding issues with literal strings (C++)
- Index(es):
Relevant Pages
|
