Re: File encoding for files ported between Mac and Windows?
Re: File encoding for files ported between Mac and Windows?
- Subject: Re: File encoding for files ported between Mac and Windows?
- From: "Paul Sanders" <email@hidden>
- Date: Tue, 5 Jan 2010 19:10:54 -0000
What version of Visual Studio are you using? I also share
source code between the Mac and Windows and I don't actually
have a problem with line-endings. Sure, Xcode seems to mess
around with them when it has promised not to, but Visual Studio
(2005, in my case) doesn't care. You just get the odd
'inconsistent line endings' message, which is harmless. And I
happen to be using a revision control system (CVS) which
normalises all line endings to CRLF on checkin, which is lucky
for me, otherwise it would cause me some grief.
As for file encodings, the best bet is to stick to stricly ASCII
characters (32 .. 126) in your source files. Then it doesn't
matter what encoding you choose.
Paul Sanders.
----- Original Message -----
From: "Howard Moon" <email@hidden>
To: "Xcode Users" <email@hidden>
Sent: Tuesday, January 05, 2010 6:47 PM
Subject: File encoding for files ported between Mac and Windows?
Hi all,
I write a lot of C++ code that is shared between Mac and
Windows. I
just went through all my files (using CodeWarrior) to make sure
that
they're all set to use Windows line endings (CR/LF), so that
they will
load properly in Visual Studio on the PC. However, I'm
wondering if I
need to do anything about the "file encoding" setting I see on
the Mac
when I do a Get Info on a file. The files I have mostly say
"Western
(Mac OS Roman)", but the Preferences setting is "Unicode
(UTF-8)".
I'm wondering if this makes any difference at all, and if I need
to go
through and change each file individually to one or the other
encoding.
I've had a LOT of troubles with the line endings not being
consistent
(and I'm still not entirely convinced that sometimes Xcode isn't
giving me incorrect line endings when doing a lot of copy/paste
operations, since files I work on sometimes revert to
"unspecified" or
give errors when loading in Visual Studio). So I want to be
sure that
the "file encoding" setting might not also be causing me
problems.
Anyone know if this something I need to address, or is it ok to
just
leave it alone?
Thanks,
Howard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden