Reply to Re: Improvements
If you don't have an account, just leave the password field blank.
@MsDinkalot:
It is specific for WinDinkEdit, though you can also use it for WinDinkEdit plus. The scripting part is more general, it doesn't really matter what editor you're using.
And the PDF has the 'correct' symbols, but when copying directly to a .c script the symbols are changed. (Or perhaps they were like that all the time, but didn't look like that? I'm not sure really)
If you copy to a .txt file the symbols look exactly as they have to, but if you copy to a .c file the format changes for some mysterious reason.
EDIT: Using word gives exactly the same problems, guess a version made in word is out of the question as well then...
EDIT2: Yay me! I solved the problem, I managed to replace the glyphed quotation marks in OpenOffice with typewriter quotes (from “this†to "this"), and now you can copy safely once more!
EDIT3: Well, if there aren't anymore of these nasty copy-paste bugs around. And after I submit the updated version... Obviously...
It is specific for WinDinkEdit, though you can also use it for WinDinkEdit plus. The scripting part is more general, it doesn't really matter what editor you're using.
And the PDF has the 'correct' symbols, but when copying directly to a .c script the symbols are changed. (Or perhaps they were like that all the time, but didn't look like that? I'm not sure really)
If you copy to a .txt file the symbols look exactly as they have to, but if you copy to a .c file the format changes for some mysterious reason.
EDIT: Using word gives exactly the same problems, guess a version made in word is out of the question as well then...
EDIT2: Yay me! I solved the problem, I managed to replace the glyphed quotation marks in OpenOffice with typewriter quotes (from “this†to "this"), and now you can copy safely once more!
EDIT3: Well, if there aren't anymore of these nasty copy-paste bugs around. And after I submit the updated version... Obviously...
