• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: File encoding for files ported between Mac and Windows?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: File encoding for files ported between Mac and Windows?


  • Subject: Re: File encoding for files ported between Mac and Windows?
  • From: Jocelyn Houle <email@hidden>
  • Date: Tue, 5 Jan 2010 14:02:02 -0500

Not all revision control system convert source files to native formats.  But my personal experience is that you likely don't need it.

We've been using UTF-8 encoding with UNIX line endings everywhere except for Visual Studio *project* files, and everything is dandy so far.

Once in a while, some coder would bring non-conformant line endings, but a simple dos2unix call (or iconv if it's the encoding) and a slap on the wrist is the usual cure. ;-)


On 2010-01-05, at 13:54, Dix Lorenz 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.  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?
>
> How are you porting the files? You should be using some kind of Version Control System anyway and that way, when you check the sources out, they will be correctly formatted for the platform you are on.
>
> Cheers,
> Dix
>
>
> _______________________________________________
> 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

 _______________________________________________
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

References: 
 >File encoding for files ported between Mac and Windows? (From: Howard Moon <email@hidden>)
 >Re: File encoding for files ported between Mac and Windows? (From: Dix Lorenz <email@hidden>)

  • Prev by Date: Line Endings when Pasting from external apps into Xcode
  • Next by Date: Re: File encoding for files ported between Mac and Windows?
  • Previous by thread: Re: File encoding for files ported between Mac and Windows?
  • Next by thread: Re: File encoding for files ported between Mac and Windows?
  • Index(es):
    • Date
    • Thread