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.
I suggested UTF-8 as opposed to say UTF-16 or UTF-32 as there is at least one mod by WC that for some reason uses UTF-16 for its c files and doesn't work at all in FreeDink but works fine in 1.08.
Scratcher tested a bunch of characters with diacritics and whatnot and he said they worked well but I don't know to which degree. Most text editors nowadays save as UTF-8 by default though so it's not really an issue. I think when Magicman went into it, he eventually ended up looking at which libraries were in use on Windows to read strings with, so it's probably some deep voodoo.
And to answer fooT's question, Shevek's a proper programmer whereas I am a computer janitor type person who tells people to turn things off and on again.
Scratcher tested a bunch of characters with diacritics and whatnot and he said they worked well but I don't know to which degree. Most text editors nowadays save as UTF-8 by default though so it's not really an issue. I think when Magicman went into it, he eventually ended up looking at which libraries were in use on Windows to read strings with, so it's probably some deep voodoo.
And to answer fooT's question, Shevek's a proper programmer whereas I am a computer janitor type person who tells people to turn things off and on again.