EPOC   SDK Home Glossary Indexes Previous Next Up

Fax store API


Contents


Overview

The EPOC faxstore component implements the ITU-T T.4 standard, which deals with the encoding, decoding and formatting of faxes. Developers wishing to simply send and receive fax store files do not need to use this API, as its functionality is abstracted by the ETel fax client.

This documentation might be used by developers who, for example, want to produce fax converters, e.g. to use OCR to convert a fax to text.


Storage of fax data

Section Contents

The files created by faxstore are used by the fax engine for sending and receiving all fax data. The format is proprietary, but only in the sense that it uses EPOC’s stream store technology to implement a storage method that is optimised for the quick and efficient display and preview of faxes. Each T.4 scan line in a fax is stored as a descriptor, with the scan lines being grouped together in bands, and the bands into pages. Each page, together with the distinct T.4 resolution and compression options it uses, is stored separately.


Storing a fax file

The key classes used for storing a fax are CWriteFaxFile and CWriteFaxPages. The first class provides the functionality to create and open a named fax file, commit pages to the file, and close the file. CWriteFaxFile contains a pointer to a CWriteFaxPages object, which provides the functionality to add the individual fax pages before they are committed.

For code fragments showing how to store faxes, see Using CWriteFaxFile.


Reading a fax file

Reading a fax file is similar to writing one, except that the key classes used are CReadFaxFile and CReadFaxPages. The first class provides the functionality to open and close a fax file. CReadFaxFile contains a pointer to a CReadFaxPages object, which provides the functionality to actually read individual pages from the file.

For code fragments showing how to read fax files, see Using CReadFaxFile.

EPOC       SDK Home Glossary Indexes Previous Next Up