I am co-writing a book and I've been sent the publishers LaTeX template which contains their style files. At first I was getting the error ietbook.cls file not found - the following seemed to be the error:


The file name was:


After I have changed this to:


I am now getting the following warnings (The compiled file is clearly wrong in format):

./IETBook.cls: LaTeX Warning: You have requested document class `IETBook', but the document class provides `book'.
./fleqn.sty: LaTeX Warning: inputting `fleqn.clo' instead of obsolete `fleqn.sty'.
./IETBook.cls:765: Package crop Warning: Requested option `' not provided on input line 765.

What could be causing this issue?

EDIT: Line referred to in third warning:

\if@cropmarkson \crop[cam,info] \fi

  • 1
    They all seem to be errors in the class file provided by the publisher. Complain to them.... – David Carlisle Apr 15 '15 at 8:24
  • Before I complain is the error regarding fleqn.sty ignorable or does it also look like a serious issue? – Colin747 Apr 15 '15 at 9:11
  • It's ignorable as in latex does fix it but fleqn.sty has been obsolete and replaced by fleqn.clo since 1994. They have had time to make the one line change required by now.... – David Carlisle Apr 15 '15 at 9:17
  • Thanks for your input, hopefully I was just sent an archived template by mistake. – Colin747 Apr 15 '15 at 9:18

This means that the class file is IETBook.cls but has the line


presumably just copied without thought from the standard book class.

Or possibly it uses


instead of


which would make a similar warning.

As it's a publisher supplied class there is not much you can do other than complain to them and ask that they fix it.

You could of course fix it locally just putting the correct name into the \ProvidesClass line, but generally it's best not to edit publisher supplied classes. It should be fixed at source.

  • Thanks, I'll try that tomorrow and accept if it fixes the problem. At least it will give the publisher something to go on if it fixes the problem. – Colin747 Apr 15 '15 at 15:03
  • 1
    @Colin747 only addresses the first warning, with the other ones it's a bit harder to guess exactly what is wrong without seeing the code – David Carlisle Apr 15 '15 at 15:11
  • I'll add the line the warning is referring too in my original post. – Colin747 Apr 15 '15 at 19:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.