Release notes for MECCA 2000 version 5.03. Nov/11/2009 Fixed: 1. Grid lines were displayed as black (m2kbin). 2. Nested "%%BoundingBox:" statements occurring in an EPS sometimes caused the correct bounding box values being ignored (typdrv, isepsfile, m2kbin, galeyc). 3. When attempting to re-install a barcode/border/panto font, the font installation procedure errors out (t1font.tcl). 4. Corrected the "ppmtoix" converter for cases where input RGB data was optimized to grayscale but inverted (ppmtoix). 5. The "bcompose" batch compose command now sets working directory for each input file on the command line (bcompose). New/Changed: 1. Barcode Code128 handling has been changed (m2kbin, code128.tcl, barcodes.tcl, tclIndex): a. Under Query, the "minimize" state of an existing Code128 is now reflected (before, it was always cleared when queried). b. The HR (human readable) of a Code128 no longer includes any control codes. Please view "v5.03code128" text file in this directory for more detailed description on what changed. Also, the one-page "code128chart.pdf" in this directory is an updated Appendix G Code128 table in the User's Guide. Please see that PDF file for character codes usable with Code128. Code128 barcodes created before this release would still display and print with the old style HR, and still query with "minimize" cleared. However, selecting Okay (perhaps with "minimize" set) under query will update the code. 2. Added "tiff2ix" to convert TIFF image to MECCA internal format (tiff2x, preview, typdrv, m2kbin, combinefile.tcl). Please note: a. 1-bit BW, 8-bit or 16-bit Gray/RGB/CMYK uncompressed TIFF's are directly converted; TIFF's using indexed-color or other color spaces, as well as other bit-depths, are converted to RGB only. b. Conversion to RGB is also applied when the source TIFF employs compression methods such as LZW, regardless color type or bit depth. If you have color images that need be output in CMYK seps, consider using some other utility to turn them into uncompressed CMYK TIFF, then combine the CMYK TIFF or use them in batch commands (see below). c. Finally, conversion to RGB requires sufficient amount of system memory to hold the (uncompressed) entire image. Also added "tiff_info" and "tiff_dims" command-line scripts to ease getting image size, resolution info from TIFF files. Note that these scripts make use of "tiffinfo" utility in "tiff-3.x" FreeGBSD package. tiff_info reports image width (pixels), height (pixels), samples/pixel and resolution for each TIFF file given on the command line. tiff_dims reports image width and height in units of inches or cm, per resolution unit indicated in the TIFF file. Please note that some TIFF's may not contain Resolution setting, in which case default 72 dpi will be used. 3. For batch compose commands FIGURE and MFORM, "TYPE=TIFF" is now added (galeyc, preview, typdrv, m2kbin). Please note: a. When using a TIFF image in these commands, "WIDTH=" and "DEPTH=" must be specified. b. If batch compose to graphic (.g) file, TIFF images will be converted when MECCA loads the file, thereafter the saved drawing file can be much larger in size. 4. Also for batch compose commands FIGURE and MFORM, the referenced external file name will now be resolved (galeyc). It is best to use some examples to explain what "resolved" means (assuming a FIGURE command in the text file residing in "/usr/home/me/reports", and the login HOME is "/usr/home/me"): NAME= resolved to -------------------------------------------------------------------------- ~/figs/f001.g /usr/home/me/figs/f001.g ~/f001.g /usr/home/me/f001.g chart3.g /usr/home/me/reports/chart3.g ../rpt1.g /usr/home/me/rpt1.g ../../chapter3/003.g /usr/home/chapter3/003.g /tmp/myreport.g /tmp/myreport.g -------------------------------------------------------------------------- Please note: a. The resolution occurs in galey composer. b. Resolution is based on "current directory", not the input command file path name. Both "bcompose" and MECCA interactive "Batch Compose" under "Batch and More", set "current directory" to where the command file resides before invoking galey composer. Customers using custom scripts that invoke the galey composer directly, need to be cautious in using relative path names, because the script may set "current directory" to somewhere else. c. The "tilde as HOME" short-cut can only appear as the first character in the file name, and it must be followed by a / (slash). d. The internal limit for the resolved, absolute path name is 511 single- byte characters. ::Addendum:: http://www.amgraf.com/updates/m2k/v503A.txt http://www.amgraf.com/updates/m2k/v503B.pdf