Code in ASCII UTF8??

[chunhui_true]

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.
But some say ASCII characters in UTF8 is unchanged.
Now I want to know in UTF8 '\r' and '\n' are already 0x0d and 0x0a??
Could anybody can tell me? Very Thanks!!!!

[Serge Paccalin]

Le jeudi 17 février 2005 à 09:38, chunhui_true a écrit dans
comp.lang.c*:

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.
But some say ASCII characters in UTF8 is unchanged.
Now I want to know in UTF8 '\r' and '\n' are already 0x0d and 0x0a??
Could anybody can tell me? Very Thanks!!!!

That's correct. All ASCII characters (0x00 to 0x7f) are unchanged in
UTF-8. All Unicode values from 0x80 up are encoded into 2, 3, or 4 bytes
that never reuse 0x00 to 0x7f.

--
___________ 17/02/2005 11:21:46
_/ _ \_`_`_`_) Serge PACCALIN -- sp ad mailclub.net
\ \_L_) Il faut donc que les hommes commencent
-'(__) par n'être pas fanatiques pour mériter
_/___(_) la tolérance. -- Voltaire, 1763

[Lawrence Kirby]

On Thu, 17 Feb 2005 00:38:52 -0800, chunhui_true wrote:

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.

Wasn't that the other way around on Macs?

Lawrence

[infobahn]

Lawrence Kirby wrote:

On Thu, 17 Feb 2005 00:38:52 -0800, chunhui_true wrote:

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.

Wasn't that the other way around on Macs?

<shrug> depends what you mean by '\r' and '\n'. :-)

On a Mac, a text file's end-of-line indicator (C89 draft 2.1.1.2)
is 0x0D. When this is read into a C program, it is translated into
a '\n' character.

If anyone's got a Mac with a C compiler, could they please tell us
what this program prints on that system?

#include <stdio.h>

int main(void)
{
printf("\\\r = %d\n", '\r');
printf("\\\n = %d\n", '\n');
return 0;
}

[Jirka Klaue]

infobahn wrote:
....

If anyone's got a Mac with a C compiler, could they please tell us
what this program prints on that system?

#include <stdio.h>

int main(void)
{
printf("\\\r = %d\n", '\r');
printf("\\\n = %d\n", '\n');
return 0;
}

Probably not what you think. ;-)

Jirka

[Clark S. Cox III]

On 2005-02-17 11:52:54 -0500, infobahn <in******@btint ernet.com> said:

include <stdio.h>

int main(void)
{
printf("\\\r = %d\n", '\r');
printf("\\\n = %d\n", '\n');
return 0;
}

ITYM:
#include <stdio.h>

int main(void)
{
printf("\\r = %d\n", '\r');
printf("\\n = %d\n", '\n');
return 0;
}
Which outputs:
\r = 13
\n = 10

--
Clark S. Cox, III
cl*******@gmail .com

[Clark S. Cox III]

On 2005-02-17 11:57:51 -0500, Lawrence Kirby <lk****@netacti ve.co.uk> said:

On Thu, 17 Feb 2005 00:38:52 -0800, chunhui_true wrote:

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.

Wasn't that the other way around on Macs?

No, the actual values of '\r' and '\n' are unchanged on the Mac. The
difference was when reading/writing a file in text mode on a MacOS
before 10. (As of 10, the UNIX convention has been adopted; i.e. text
mode and binary mode are identical).
--
Clark S. Cox, III
cl*******@gmail .com

[infobahn]

"Clark S. Cox III" wrote:

On 2005-02-17 11:52:54 -0500, infobahn <in******@btint ernet.com> said:

include <stdio.h>

int main(void)
{
printf("\\\r = %d\n", '\r');
printf("\\\n = %d\n", '\n');
return 0;
}
ITYM:
#include <stdio.h>

int main(void)
{
printf("\\r = %d\n", '\r');
printf("\\n = %d\n", '\n');

\E\r\,\ \y\e\s\,\ \I\ \d\i\d\ \m\e\a\n\ \t\h\a\t\.

Which outputs:
\r = 13
\n = 10

I expected as much, but since I haven't used a Mac since 1989, I
didn't want to risk making an idiot of myself. (Seems I did that
anyway, in a rather unexpected direction.)

[Peter Nilsson]

infobahn wrote:

Lawrence Kirby wrote:

On Thu, 17 Feb 2005 00:38:52 -0800, chunhui_true wrote:

I know in ASCII '\r' is 0x0d,'\n' is 0x0a.
Wasn't that the other way around on Macs?

<shrug> depends what you mean by '\r' and '\n'. :-)

True, <cr> is 0x0D and <lf> is 0x0A would be better description.
On a Mac, a text file's end-of-line indicator (C89 draft 2.1.1.2)
is 0x0D. When this is read into a C program, it is translated into
a '\n' character.

If anyone's got a Mac with a C compiler, could they please tell us
what this program prints on that system?

#include <stdio.h>

int main(void)
{
printf("\\r = %d\n", '\r'); [corrected]
printf("\\n = %d\n", '\n'); [corrected]
return 0;
}

Metrowerks 3.0, Mac IIvx, swap \n and \r enabled...

\r = 10
\n = 13

The compiler option allows mac implementations to avoid having
to perform runtime translations of text file end-of-lines.

--
Peter

[chunhui_true]

Does ASCII characters remain unchanged under UTF8????Since it
unchanged,Why I can't printf thme in screen?
I use libcap get the FTP commands from Ethernet.I have one class to

get all packages and flowed,buffered them,Then aonther class can
readline (ended with \r\n)from buffer.Every time I readline from buffer

to get a command.
When I use CuteFTP I can get all commands an printf them in
screen.But when I use IE to FTP I can see one command "set utf8 on" and

then next commands I can't printf them in screen.Should I conver utf8
to ASCII?:(