Problems and Porting

Well, if the procedures described above don't work I have some hints. These hints may also be useful if you plan to port BibTool to other operating systems or C compilers.

Here is a small list of assumptions that I use.

• On ANSI systems there should be no problem at all. There is some support for non-ANSI systems. This support can be improved. (I don't know if it's worthwhile to do so).

• BibTool has been developed on UN*X (SunOS) and UN*X-like systems (Atari). Such file/directory naming conventions found their way into the code. Single character delimiters between directories and files can be modified in a resource file.

• ASCII encoding is assumed. I role my own type.h instead of using ctypes.h. This has mainly historical reasons. Maybe this code should be rewritten to be adapted at make time.

  If you port BibTool to a non-ASCII machine the table of characters (allowed[]) in type.h has to be adapted -- at least (please send me the diffs).

• Maybe some BSD-isms found their way into the code even if I am not aware of it.

Getting Started with BibTool Problems and Porting