*** Version History for the Bitmap Converter Module ***

The first eight versions are undocumented since a number of test compilations has been done without creating a working application. These first eight versions has only been used for internal verfication of the application.

Also note that versions 1.0 and 1.1 only are internal releases.

1.0.9
This is the first version of the module as a working GFM module. This is still an internal version. When the first external version is compiled will this be stated in that version. Also will the version number be changed to the external version syntax when this happens.

1.0.10
When converting from TIFF to EPS is the /jobname variable in StatusDict set to the PageName Tag of the TIFF file. If the tag isn't present will the /jobname variable be set to the actual filename of the TIFF file. This is only when converting TIFF to EPS. The %%Title comment will be created in the same manner.

1.0.11
The CCITT Group 4 compression handling has been improved.

1.0.12
The %%PlateColor DSC comment has been inserted when creating EPS files.

1.0.13
A bug when decompressing large CCITT Group files in Harlequin RIPs has been corrected. The problem was that some 'extra' and garbish bytes where inserted in the image data.

1.0.14
In previous versions the module read the complete source file into memory and then did the conversion. This could cause long conversion times due to swap disk usage. From this version is the source file read into memory in portions and then converted. The buffer size has been set to 64 KByte.

1.0.15
A bug when converting files smaller than 64 KByte has been corrected.

1.0.16
The buffer size has been increased to 128 KByte to have better performance.

1.0.17
The PackBits compression algorithm handling has been added, tested and verified. In this version has only test on Harlequin version 4.14 RIP been done.

The Compression Tag when reading and parsing TIFF files has been set to the default value 1 (no compression) as defined in the TIFF 6.0 Specification. Default value was earlier set to 0 which was incorrect.

1.0.18
The option to use files converted for the HyWay RIP has been added. This options can only handle CCITT Group 4 images in this version. There has been created a new Postscript dictionary for this purpose, called HWayDict.

1.0.19
A new configuration check box has been added. Pad to Byte. By enabling this option will the module expect extra 0 bits inserted before each scanline so that the line begins on a byte boundary. By disabling the option will the module not expect extra bits. See the documentation for more information about this. Note! that still can only files not padded to nearest byte be handled.

The CCITT Group 3 compression algorithm handling has been added. The compression can only be used with the Pad to Byte option disabled.

1.0.20
The HWayDict has been modified and renamed to BCMFaxDict.
NOTE! The option for using HyWay RIPs shall from now on only be checked if the source TIFF file is compressed with PackBits. This will although be changed in a later version, i.e. this option shall be removed and the application shall insert the correct dictionary automatically depending on the compression used in the source file.

The CCITT Group 3 compression algorithm handling has been improved. Now can the module also handle and convert TIFF files padded to nearest byte boundary.

1.0.21
A bug sometimes causing Postscript error
Error: limitcheck; OffendingCommand: string
in the RIP when decompressing has been corrected. The problem was a fault in the BCMFaxDict.

1.1.0
Since there are a number of changes and enhancements in this new version is this regarded as a minor version change from 1.0.21 to 1.1.0.

--- Changes from version 1.0.21 ---
* The BCMFaxDict has been changed so that all CCITT compressed files will use this dictionary. Each compression method will do minor changes in the dictionary.

* The BCMDict will be used if the image data is uncompressed or compressed used PackBits compression. Also here will the EPS 'wrapper' be changed depending on if the image is compressed or not.

* The use HyWay RIP option has been removed. All RIPs will use the same dictionaries as described above.

* All compression methods has been tested on Harlequin RIPs Version 3.3 rev 6 and 4.14. This has also been tested on Taipan RIP version 2.01 and HyWay RIPs. All compression works on all RIPs but on the HyWay RIP is the decompression time to long for practical use. This will be investigated and hopefully corrected in a later version. On all other RIPs is the decompression time not a problem.

* The options to convert from EPS and Postscript files has been removed. These functions will be present in separate modules later. That is, the module can only convert TIFF images to EPS Binary and Postscript Binary. Note! The PostScript Binary option doesn't work properly in this version.

* An option called Negative has been added. This option will only work for CCITT compressed images in this version. The option will set the BlackIs1 key in the CCITT dictionary to different values (true or false).

* An option called Mirror has been added. This option is not working properly in this version, therefore has it been disabled (grayed out).

* The configuration file has been changed. Options not used has been removed and new options has been added to the file. This means that old configuration files has to be opened and saved again to have the correct syntax.

--- End of changes from version 1.0.21 ---

To summarize:
* The module can only convert TIFF bi-level files.
* The module can handle and convert uncompressed images, CCITT Group 31D (Huffman), CCITT Group 32D, CCITT Group 4 and PackBits compressed images.
* The file format to create can only be EPS Binary in this version.
* The negative option will only work on CCITT compressed images.

This is also the first 'candidate' for an external release of the module. NOTE! By this doesn't this mean that this is an external release. The module needs more testing before it can be considered to be an external release.

1.1.1
The Mirror option has been enabled. It works on uncompressed images and on all supported compressions.

1.1.2
The layout of the configuration menu has been changed. A tab named Advanced has been added allowing to set different keys in the CCITTFaxDecode filter. These options shall only be used by persons that have deep knowledge about the Postscript language and the CCITT filter.
This version will only display the different options as the user has selected, the module will not take any notice of the options. That is, the code to actually do the changes has not been implemented but the configuration file will change as the user makes different selections. The code that will do the changes is planned to be implemented in version 1.1.3.

1.13
This is the first beta version of the module that should be seen as the actual candidate for an external release of the module. The version number has been changed to reflect that this is an external release. The first actual external version will be 1.2. The document that belongs to this module is Doc No #200022-01.

The PhotometricInterpretation Tag can now be set to 1, BlackIsZero. The module will not change to negative imaging but this has to be done with the Negative check button.

The verbosity reporting has been improved. Each tag will be written to BCM.TXT with its name and value.

1.14
The Postscript generation has been enabled. The layout of the configuration menu has been changed because of this. A tab named Page Layout has been added allowing to set different margins when generating Postscript files. These settings will have no meaining when creating EPS files. The Postscript file works on uncompressed files and on all compression methods supported by the module.

There is also a combo box named Units under the Page Layout tab. In this version will only the mm unit work. Changing the unit to any other measurement will have no meaning to the module. This will be corrected in a later version.

The EPS generation has not been affected because of this change.

1.15
The layout of the configuration menu has been changed. Most of the changes are that items has been moved between different tabs in order to give the menu a more logical appearance. One item has been added as described below.

The function when reading and parsing the TIFF file has been improved. In the configuration menu there has been a check box added saying: Abort And Stop Parsing. If this check box is enabled will the module stop parsing the TIFF file if the tag is not supported or unknown. If the check box is unchecked will the module try to parse the file anyway. The configuration file has been changed to have this option. The option is called AbortOnUnknownTag and can have two values 0 or 1.

The EPS and Postscript headers has also been cleaned up.

1.16 (1998-06-17)
This version has no changes in the source code compared with version 1.15. The reason that there is a new version is because there has been a number of changes of system files used by the module. These changes comes from Microsoft. To make it clear that there was a change has this version been compiled. Note that when upgrading to this version, all system files must be updated simultainously, otherwise will the module not work.

1.17 (1998-06-18)
If the BitsPerSample tag in the TIFF file is set to anything but 1 will the TIFF file be rejected and an error will occur: TIFF: Unsupported Color Space <Tag: BitsPerSample> or error number 12. This has been a bug that has been corrected now.

Also has the thread handling been changed. There will now be a thread created for each object created. That is, for each instance of the module will there be a new and distinct thread created and this thread will not interfere with any other thread.

1.18 (1998-06-22)
A bug when parsing the TIFF source file been corrected. The bug caused the module not to report unknown files correctly. It used to report that the version of the TIFF file was not correct even if this wasn't a TIFF file. Now will the module report any file that isn't a TIFF file as an unknown file type.

1.19 (1998-07-09)
The support to create PDF-1.2 files has been implemented. There are a few restrictions in this version as descibed below:

* PackBits compression does not work since the PackBits compression is not a part of the PDF specification.

1.20 (1998-07-26)
This is the first external release of the BCM Module. See the release notes that was installed with the module as 'Release Notes For BCM 1.2.txt' or the document 'Release Notes for the BCM.WRI' that is a WordPad file. Especially you should read the part about the Postscript file generation. There has been some changes compared to 1.19 in this generation.

1.20.1 (1998-09-07)
The rotate option has been enhanced. The earlier rotate option could sometime cause pages to disappear. The new code has corrected this so that the page will be visible in all rotate options (0, 90, 180 and 270 degrees).

Also has the control box in the Information menu been removed.

1.20.2 (1998-11-02)
The option to create EPS files used for DCS generation has been implemented. This functionallity can be enabled with a new check box in the configuration menu. If this option is enabled will the %%PlateColor comment not be inserted in the EPS header.

1.21 (1998-11-10)
The BCMFaxDict has been cleaned up. The earlier dictionary could cause DCS files generated by the Page Combiner Module to be corrupt and not outputed correctly.

Also has the check box as described in version 1.20.2 been removed and replaced with a new format in File Format combo box called: EPS Binary (For DCS). The functionallity is although the same: the %%PlateColor will not be inserted in the EPS header.

1.3.0 (1998-12-10)
This version has no changes in the source code compared with the previous version. The reason that there is a new version is because there has been a number of changes of system files used by the module. These changes comes from Microsoft. To make it clear that there has been a change has this version been compiled. Note that when upgrading to this version, all system files must be updated simultainously, otherwise will the module not work.

Note that you must upgrade to GFM Engine version 1.3.0 or higher to be able to use this version.

1.31.0 (1999-02-18)
The way how the %%BoundingBox values are calculated has been improved to be more accurate.

1.32 (1999-02-23)
The option to create accurate %%BoundingBox has been changed to be a configuration item. Under the Advanced Tab is there now an option saying Accurate BoundingBox. When enabled will the BCM generate %%BoundingBox values with decimals, when disabled will the values always be integers. Default value is disabled.

1.33 (1999-04-07)
The color name generation has been changed as the following: You can now select if the module should use the ImageDescription Tag or use the actual source file name when generating the color name. By manually editing the configuration file you can set each color by the following syntax:

/BlackPlate (B) def
/CyanPlate (C) def
/YellowPlate (Y) def
/MagentaPlate (M) def

In german for example yellow is gelb. In that case you should change the /YellowPlate (Y) def to /YellowPlate (G) def. See the release notes for more information.

Also has the following corrections been done:
The Orientation tag been set to its default value 1 as defined in the TIFF 6.0 specification. The earlier value was 0 and that was not correct.
If a configuration file doesn't exist will an error be generated and the loading of the configuration file will be aborted.
When generating a new configuration file the default value for the rotation is set to 0 degrees.
When generating a new configuration file the default value for Verbosity level is set to level 0 - No Messages.
The EPS Binary (For DCS) file format has been renamed to EPS Binary (No %%PlateColor).
When generating EPS No PlateColor the GFM Engine would crash because the module didn't create the destination file (EPS) correctly. This has been corrected.

1.34 (1999-04-13)
A new format has been added. The format is named EPS Binary (Color Plane) and should only be used when sending files to the GFM Page Combiner and the GFM Page Combiner should create recombine separations into a composite Postscript file. No other formats has been changed in this version.

1.35 (1999-08-09)
The EPS Binary (Color Plane) format has been removed as this functionallity now has a different approach. See the Page Combiner release notes for more information about this.

A new tab in the configuration menu has been added. This new tab is named Page Size and is only effectiv when creating Postscript files. Under the tab you now have the possibility to position the job within the page if you have created a larger page size than job size. None of these settings will work if the Page Size has been set to zero or no value at all.

The color name generation has been changed. Now will the color mapping only be available if the Use File Name has been selected. If the Use File Name isn't enabled will the ImageDescription tag in the source TIFF file be used. This is the old way of extracting the color for the current page.

1.35.1 (1999-08-13)
The %%Title and /jobname previously depended on the PageName tag or the source file name. From this version will always the %%Title and /jobname hold the destination file name.

1.35.2 (2000-01-04)
The name of the module has been changed from BiLevel Converter Module to Bitmap Converter Module.

1.35.3 (2000-01-11)
The statusdict call when generating EPS files has been removed. The old behaivor did not actually cause any problems but according to the EPS specification shall there never be any calls done to statusdict in an EPS file.


*** End Of Version History for the Bitmap Converter Module ***