Reply to Re: question concering line returns [linux - win] and saveing .c files
If you don't have an account, just leave the password field blank.
Make sure you use UTF-8 for saving the files. Almost everything else is irrelevant.
Are you sure? I can see how freedink would support it, but I don't think unicode was invented when Dink was first released...
Anyway, just a warning: don't tell programs from Microsoft that you want to save as UTF-8. They will add an invisible code at the start (a "byte order mark", meant for UTF-16 and useless for UTF-8) which will probably break just about everything that tries to read it as a plain text file.
Although perhaps Windows will also strip this from the bytes that are read and thus it will not be seen by Dink and thus work even though it never expected it... Wasn't there a problem that Freedink on non-Windows would crash when it encountered a BOM? I don't remember the problem, it may have been fixed now in which case the BOM does no harm.
As you can tell, I haven't tried this.
Are you sure? I can see how freedink would support it, but I don't think unicode was invented when Dink was first released...
Anyway, just a warning: don't tell programs from Microsoft that you want to save as UTF-8. They will add an invisible code at the start (a "byte order mark", meant for UTF-16 and useless for UTF-8) which will probably break just about everything that tries to read it as a plain text file.
Although perhaps Windows will also strip this from the bytes that are read and thus it will not be seen by Dink and thus work even though it never expected it... Wasn't there a problem that Freedink on non-Windows would crash when it encountered a BOM? I don't remember the problem, it may have been fixed now in which case the BOM does no harm.
As you can tell, I haven't tried this.
