TBH, the style of line-ending shouldn't really come into it. what's the problem with using UNIX style endings (\n only) on Mac OS, or DOS style (\r\n) on *nix? Sensible text editors support all three, and a myriad of others. Oh, and the encoding will be UTF-8, without question.
Personal I prefer ASCII encoding cos it's the most basic you can get, But i think UTF-8 is quite compiatble with ASCII isn't it. I have to read into that.
Fileformats internally should be \n is what I ment and should be the preferred format. We should try to keep 'our' archive clean this way and not mix and match. same goes for C files etc. (On a side note, does gcc even take UTF-8 chars as input?) that the engine works with both formats I guess shouldn't be a problem, eventually anyway, but we gotta keep things clean and concistent in our code stash.
As has been discussed before, we should ideally try and write as little code for these things as possible, making use of libraries instead. Somewhere in much earlier discussion, it was raised that with some libraries we can have an XML parser out-of-the-box, exactly as we can have the insides of a Vorbis player - the joys of well-defined standards
I agree that we should use as many _standard_ widley availble libraries as possible, but still keep the amount to a minium. Like not implementing 1000x features and use 10000x libs and go through library hell. Just because we write lesser code doesn't mean the game will then be less efficient. But I think I mentioned XML in my first post and I was reffering to using the XML(2) library for that yes.
I'd agree that support for free software should come first and foremost, so for screengrabs and static images we should definitely favour PNG over GIF or JPEG, and Vorbis for music over MP3 (of course, allowing the user to play their MP3s would be nice). The main problem with MP3 licensing is for apps that encode, not decode - the patent is over Fraunhofer's encoding algorithm, I believe. For video, given that, unless something changed recently, xvid is a free codec, I see no problem in being able to use it. Of course, we'd need some actual video first.
Atleast we totally agree on that one
What I was saying really was that (not with mp3's particulary but like 3ds files for example) if sometime ever the issue comes up 'how did you create these files, did you use an unlicensed, illegally licensed version of 3ds max, there might be some where some trouble. Let's just say now we use an open standard so we never have anything to worry about. (Same could go for mp3, did you legally encode that mp3 ...) avoid it and we're happy.
For video, IF we ever get that, I guess we could give Ogg Theora a try as it's supposed to be pretty good and everything and not known to be used for all the illegal stuff etc etc. I know you know what I mean : )
Any other thoughts from anyone? Other file formats to concider etc? Did we forget anything so far? Keep this thread alive for a while : )