\textsc{tiff}
is not just one file format, it is a collection of different
compression and encoding mechanisms.

There are standards, i.e. ``\textsc{tiff} V6.0 baseline''
specifying collections of \textsc{tiff} tags.

Multiple extension tags were created by several software vendors.
It is not unusual for \textsc{tiff}-processing programs to complain
about unknown tags in input files.

Bmeps uses the \textit{TIFFReadRGBAImage()\/} from libtiff to read
\textsc{tiff} images,
so bmeps can only handle \textsc{tiff} images
fulfilling the following conditions:
\begin{itemize}
\item	The file must follow the ``\textsc{tiff} V6.0 baseline''
standard.
\item	The number of bits per component must be \(\leq 8\).
\item	The memory need for the image is \(4\cdot w\cdot h~\text{bytes}\).
The system must be able to allocate this memory in one piece.
\end{itemize}

\textsc{tiff} support was added to bmeps to convert files created
by a fax gateway to \textsc{pdf}. This was tested successfully.

For other \textsc{tiff} images bmeps will possibly fail. This is not a bug.

If your image editing or image creation software allows you to choose
a file type, choose \textsc{png} if available, not \textsc{tiff}.
Or choose any other file type which can be converted to 
\textsc{png} or NetPBM.