Problems editing Hog 2 lib.lib files on a mac

[tharding]

I would avoid RTF as it allows for embedding graphics etc. Makes for larger files and invariably includes information not required.

Plain text is definitely the way to go.

[samsc]

I would avoid RTF as it allows for embedding graphics etc. Makes for larger files and invariably includes information not required.

Plain text is definitely the way to go.

you really dont want to do any rtf stuff.

when i started writing the software, i used to auto generate a library file, and the hog is very very sensitive to spurious information,
its very sensitive to line endings too.
they must be in the form <carriage return line feed> or "\n\r" to c programmers.
macs dont do this correctly.
and these characters are invisible. you cant see them in a text editor.
thats why danny uses the xcode editor, and i use code warrior - to edit library files