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: Jens Alfke <email@hidden>
- Date: Tue, 5 Jan 2010 11:12:02 -0800
On Jan 5, 2010, at 10:47 AM, Howard Moon wrote:
> 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.
Are you using any version control system? Most of them (I believe) will do the appropriate conversions when files are checked out. In Subversion you may have to make sure your file metadata specifies 'native' EOL mode.
> 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.
This only makes any difference if you use non-ASCII characters in source code.
If sharing code with Windows IDEs, the best setting is probably "Western (Windows Latin 1)" which is the default Windows encoding. Overall the best choice is UTF-8, but I have no idea whether Visual Studio supports that.
—Jens _______________________________________________
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