HylaFAX Difference between revisions of "Handbook:Advanced Server Configuration:Transcoding of Received Facsimile"
(remove useless advice since this doesn't seem to force receiving encoding... more searching required) |
|||
| Line 1: | Line 1: | ||
| − | ''Transcoding'' refers to the on-the-fly conversion of encoded data. HylaFAX supports transcoding of received facsimile so that received documents can be stored in files using an optimal compression algorithm. If the <tt>RecvDataFormat</tt> configuration parameter is set it defines the format for writing received facsimile data, one of: "1-D | + | ''Transcoding'' refers to the on-the-fly conversion of encoded data. HylaFAX supports transcoding of received facsimile so that received documents can be stored in files using an optimal compression algorithm. If the <tt>RecvDataFormat</tt> configuration parameter is set it defines the format for writing received facsimile data, one of: "1-D MR", "2-D MR", "2-D MMR", or "adaptive". An "adaptive" format is the default; it causes the received data to be written using the data format negotiated by the sender and receiver. Using |
RecvDataFormat: "2-D MMR" | RecvDataFormat: "2-D MMR" | ||
| − | gives the most space-efficient data format. | + | gives the most space-efficient data format. Note that <tt>RecvDataFormat</tt> defines the encoding of the page data, not the file format: this is always TIFF. |
| − | |||
| − | Note that <tt>RecvDataFormat</tt> defines the encoding of the page data, not the file format: this is always TIFF. | ||
Latest revision as of 19:41, 6 October 2009
Transcoding refers to the on-the-fly conversion of encoded data. HylaFAX supports transcoding of received facsimile so that received documents can be stored in files using an optimal compression algorithm. If the RecvDataFormat configuration parameter is set it defines the format for writing received facsimile data, one of: "1-D MR", "2-D MR", "2-D MMR", or "adaptive". An "adaptive" format is the default; it causes the received data to be written using the data format negotiated by the sender and receiver. Using
RecvDataFormat: "2-D MMR"
gives the most space-efficient data format. Note that RecvDataFormat defines the encoding of the page data, not the file format: this is always TIFF.
